The OPAL Discussion Forum

["Thomas, Sebastian" <sthomas AT uni-mainz.de>]

Dear Jochen,

Dear Bettina,

Thank you so much for your detailed answers! They really helped and gave me some fuel to go over the holidays.

Attached to the mail you can find a minimal example of my input. If you change the particle number in the track command, after running it, from 1000 to 4000, OPAL will not only append 3000 new particles to the monitor{}.loss files but also introduce a new header in line 1002. If you change the particle amount back to 1000, the file will remain 4002 lines long. Maybe this is a problem of the ACSII output alone?

Cheers

Sebastian

---

From: opal-request AT lists.psi.ch <opal-request AT lists.psi.ch> on behalf of Thomas, Sebastian <sthomas AT uni-mainz.de>
Sent: 18 December 2019 13:46:08
To: Snuverink Jochem (PSI); opal AT lists.psi.ch
Subject: Re: [Opal] Automated Override of Monitoroutput, Visualize Elements & Elegant Lattice

 

Dear Jochen,

That is actually the workaround that I am using right now: I just put some system commands in the input file. I will try to recreate the original problem and send you the input file.

Thank you for providing that link regarding the evaluation tool. I couldn't find it in the wiki on the gitlab page. Was I just blind?

Thanks for the quick help!

Cheers

Sebastian

---

From: Snuverink Jochem (PSI) <jochem.snuverink AT psi.ch>
Sent: 18 December 2019 12:23:45
To: Thomas, Sebastian; opal AT lists.psi.ch
Subject: RE: Automated Override of Monitoroutput, Visualize Elements & Elegant Lattice

 

Dear Thomas,

 

Ø  I have some problems with the output of OPAL, specifically the monitors. I have three monitors in my beam line and try to evaluate their ASCII Output with a Python Script of my own. The thing is, I realised that OPAL sometime just "appends" the output file instead of completely overriding it. Of course, that leads to corrupted data. It happened after I changed the amount of macroparticles. Is there a way to make sure that OPAL deletes or overrides all old data in its folders?

 

That should not happen and sounds like a bug. What version are you using? Can you send a minimal example input file? There is no option in OPAL that deletes all old output. To circumvent the behaviour you see, I would recommend writing a small script that deletes the output files and then executes opal.

 

Ø  I did not found a documentation regarding how to handle the "Visualize Elements"  part in the data output after a successful run in OPAL. Did I overlook it or is there none?

 

Do you mean the monitor output file? In general https://gitlab.psi.ch/OPAL/pyOPALTools  is the recommended way to analyse the different output files.

 

Ø  I will have to implement an Elegant Lattice in OPAL. Since I want to be smart in what I do, I thought I ask you, whether someone already has done a conversion like that and could provide me with some documentation, insights and/or tools. I will gladly do the same once I finished the conversion and the lattice proofed to be stable.

 

I don’t know of a conversion script, but perhaps someone has done this before.

 

Cheers, Jochem

Attachment: test_append.in
Description: test_append.in