Elegant users forum

A work-around I found is that I can put the offending commands in a different script and call that script from trackErrors, and it works without any other changes. I'm not sure if that is of general interest, but maybe that fact will help a future reader.

This is a bit of a long shot, but I don't have any better ideas on where to ask for help on this problem. I'm trying to get the length of the beamline into the track.lost file from track.twi. To do this, I use two commands: sddsprocess track.twi -noWarnings -process=s,last,length sddsxref track.lost...

Ohh wow, thank you for the example and the explanation! In the hopes a saving future readers some time, here is the relevant script. Very helpful for the -print command, too! #!/bin/bash # sddsprocess: select rows for sextupole's K2 values # print a new string column containing a "tag" identifying t...

I suppose I should add what I tried to get what I want. The following appears to be one step away from ParameterName = ParameterValue: sddsexpand hebt_run.par -pipe=out | sddsprocess -pipe -filter=par,ElementOccurence,1,1 -match=par,ElementType=KQUAD -match=par,ElementParameter=K1 -print=par,Paramet...

I'm trying to take values from the parameter file defined in elegant's &run_setup and create data parameters for insertion into the .twi file also created by elegant. (As a note, the word parameter is used with 3 different meanings in this question. I'm trying to be really careful with how I use it,...

I've discovered what looks like an off-by-one error in output of the parallel optimizer into the pop file. When I optimize a lattice, the stout printout gives me the following values for the optimized parameters: Q13H.K1: -5.183953524225921e+00 1.604647577407903e-02 (was -5.200000000000000e+00) Q23H...

I am trying to &correct the beam trajectory of a beam that I import from an earlier simulation. The manual seems to say that I can simply load the particles using &sdds_beam and set use_actual_beam = 1 inside &correct. However, when I do this the &correct command is considerably less verbose and the...

Thanks for the help moving on to the parallel optimizer. I've noticed something I did not expect about the solution. The optimized beam line has two instances of the MARKER MARK-MDLS.01, one comes just before TM1 (a TWISS object) and the other just after. To reset the twiss parameters at TM1 I use t...

I am trying to optimize a beam line that is split by a dipole that can be either on or off. I'm working with the Twiss parameters, so I pull the Twiss parameters from just before the dipole and paste the straight beam line on to the end of the bent beam line. I have attached all the files necessary ...

Ohh wow, thanks!

This option appears to be undocumented in the sdds toolkit manual, though the newest version I can find through google is from 2017:
https://ops.aps.anl.gov/manuals/SDDStoo ... olkit.html

Thanks again!