Peter Willendrup
Peter Willendrup
When using a user-defined field-function in McStas 2.x (feature not available in 3.x) e.g. like in ```Test_Magnetic_Userdefined.instr```, it seems that the field-function is not evaluated correctly. (In the listede instrument...
Currently, the combination of propagation including both a precession-field and gravitation is not supported. (This means that e.g. Guide_gravity can not be placed in a field-region.) In 2.7.1 the user...
McStas-3.x limitation wrt. polarisation: Currently, the Pol_Bfield component in McStas-3.x only supports "analytically defined" fields. The component may be "open-ended" by setting concentric=1, leaving field-exit to Pol_Bfield_stop - thus allowing...
Ideas: a) ```ASSERT ( isnotnan(par), par1>par2, par2>0)``` Uses code-generator to evaluate post-```INITIALIZE``` conditions on comp/instr input parameters. McDoc could then list these requirements in a in the comp / instr...
Observations from @antoinepado and @mads-bertelsen indicate that both the McStas and McXtrace Single_crystal have an issue with correctly defining (e.g.) lattice-orientation via the input-parameters. In other words, it seems as...
(From debugging-session with Steffen Sloth) Compilation with MPI fails on Windows since linking with non-existent -lmpi fails. Lib is -lmsmpi (as e.g. defined in mpicc.bat)
It seems that a user-provided conda environment on macOS often conflicts with an internally defined miniconda from within the McStas/McXtrace install / app. We should likely find a way to...
There is often very little physical meaning in plots of "event data" from Monitor_nD, it also happens very often that the data become very big and hence take long time...
Transfer comps, lib code and test instruments to the McCode repo before next release(s).
Debugging with @antoinepado I found that ``` COMPONENT Source = Bending_magnet( E0=22, B=1.72, dE = 18, Ee=2.75, focus_xw=0.5, focus_yh=0.5, dist=0.5) AT (0, 0, 0) RELATIVE origin ``` produces 99% zero-weighted...