Hi,
I've requested a parameters output file using run_setup's "parameters=\"%s.parms\" thinking that I would get an easily parseable file containing the element parameters and values in the lattice (I know of the disclaimer in the documentation)
I thought I could just add the line to run_setup, but elegant did not create the expected file. If found that I have to add the bunched_beam and track commands in order to get the output file.
Why is that? It doesn't look like anything in the output file should be dependent on the beam
parameters output file
Moderators: cyao, michael_borland
-
- Posts: 1933
- Joined: 19 May 2008, 09:33
- Location: Argonne National Laboratory
- Contact:
Re: parameters output file
Michelle,
There's not a really good reason for this. It is mostly because the original idea of the parameters file was that it was created after optimization, for example.
I'll put this on my list of things to improve.
--Michael
There's not a really good reason for this. It is mostly because the original idea of the parameters file was that it was created after optimization, for example.
I'll put this on my list of things to improve.
--Michael