modified from PAR/frequencyMap example

adding a CHARGE element causes a segmentation fault, but only if
the recirc element is removed.

parTrack.lte is modified just to add 4 extra lattices in addition to par:
parnoR, parQ, parQnoR, parQmove corresponding to the following 5 runs:

elegant parTrack.ele, uses par, original example

elegant parTracknoR.ele, uses parnoR, removing recirc element

elegant parTrackQ.ele, uses parQ, adding charge element at the beginning

elegant parTrackQnoR.ele, uses parQnoR, adding charge element and removing recirc element

elegant parTrackQmove.ele, uses parQmove, adding charge element but placing it AFTER the recirc element

Only the last two examples cause the segmentation fault
