Test cases #5
Description
Add test cases for DYNK - check that attributes are correctly set for all supported elements, and that functions are correctly generated.
The general idea is to:
- Check that the kicks are correctly applied, by running one simulation with no DYNK and setting the element properties in fort.2, comparing that to another simulation (with same initial conditions etc.) where the settings in fort.2 is something stupid, immediately reset in by DYNK from turn 1.
- Check that we actually generate the correct functions and store them to the DYNK output file.
If there is a "standard" lattice used for testing SixTrack, we should use this. There may also be some kind of standard "test harness", i.e. a pile of scripts for automatically running the code with different input, checking the results, and producing some kind of GO/NO-GO output.