[mcstas-users] MCSTAS_FORMAT=gnuplot leads to wrong 1D detector output

[Peter Kjær Willendrup]

Dear Andre,


With which version of McStas did you experience this? - Under some very special circumstances McStas 2.0 can exhibit this type of issue.

It would also help to try reproducing the problem to know the exact system you are running on, i.e. what OS and which version.

I firmly believe the setting of MCSTAS_FORMAT to gnuplot will not affect anything: In the internal c-code of McStas the “gnuplot” format is actually unhandled and we revert to the traditional McStas or PGPLOT format. The setting of gnuplot only affects the tool-layer, i.e. mcplot etc.


Best,

Peter

> On 11 Feb 2015, at 15:41 , André Kusmin <a.kusmin at tudelft.nl> wrote:
> 
> Hi everyone,
> I had a problem of an incorrect output for a 1D detector in case when environmental variable
> MCSTAS_FORMAT was set to  gnuplot. (only one column was written in the output file instead of four)
> 2D output (such as e.g. PSDMonitor.dat) was correct.
> 
> Short summary to test reproducibility
> export  variable MCSTAS_FORMAT = gnuplot
> Load TestSANS.instr (from "examples"), compile it, and run with default parameters.
> When running via mcgui, you can set output PGPLOT or gnuplot, it doesn not matter  - your output
> files QDetector.dat  and RDetector.dat will have only 100 values instead of 400.
> 
> If you set MCSTAS_FORMAT="" then (after restarting mcgui)
> you will get correct output.
> 
> I tried other components  such as L_monitor, the same behaviour.
> 
> I hope this will help someone and the bug can be fixed,
> 
> best regards
> 
> Andre
> _______________________________________________
> mcstas-users mailing list
> mcstas-users at mcstas.org
> http://mailman.mcstas.org/cgi-bin/mailman/listinfo/mcstas-users