Page 1 of 1

input distributions plt-file different for TraceWin and TraceWin_noX11

Posted: Thu 7 Nov 2024 11:07
by Lennert.dk
Hi Didier,

when running TraceWin through the GUI and with TraceWin_noX11, I noticed subtle differences in the input distributions saved to the plt-file.
Between the two, it looks like there is a linear scaling applied (see picture in the attachment showing the delta as a function of the parameter values).
Is this a bug or is there a simple explanation?

Kind regards,

Lennert

Re: input distributions plt-file different for TraceWin and TraceWin_noX11

Posted: Thu 7 Nov 2024 11:25
by Didier
Dear Lennert,

I tried it with one of my projects and didn't see any difference, so I'd really need your specific case (your project files) to understand the problem you're having.

Regards,

Didier

Re: input distributions plt-file different for TraceWin and TraceWin_noX11

Posted: Thu 7 Nov 2024 12:02
by Lennert.dk
Hi Didier,

you can find .zip file in the attachment.
For the noX11 run I used the following commandline prompt:
'TraceWin_noX11 i1lb.ini path_cal=output_cmd partran=1 nbr_part1=535332 use_dst_file dst_file1=RFQ_exit_acc_centered.dst energy1=1.494 cancel_matchingp'

Be aware that in this particular case, the input reference energy of the beam was purposely lowered from 1.52 MeV (taken from the distribution file) to 1.494 MeV. Could it be related to this?

Kr,

Lennert

Re: input distributions plt-file different for TraceWin and TraceWin_noX11

Posted: Thu 7 Nov 2024 12:17
by Lennert.dk
P.s.: I just did the check myself and indeed it's related to the energy shift. without the shift and leaving the energy as is (1.52 MeV) the results are identical.

Re: input distributions plt-file different for TraceWin and TraceWin_noX11  [SOLVED]

Posted: Fri 8 Nov 2024 13:53
by Didier
Dear Lennert,

It's fixed, please upgrade your code.

Regards,

Didier

Re: input distributions plt-file different for TraceWin and TraceWin_noX11

Posted: Fri 8 Nov 2024 15:46
by Lennert.dk
Dear Didier,

I can confirm that the issue is resolved with the latest upgrade. Thanks a lot!

Kind regards,

Lennert