USER CHANGES

the user can provide the sixtrack jobs with additional files, either created by MADX or provided by the user. These files are also used in one-turn jobs - if not necessary, this step can be used also as a final check of consistency of the input files. The manual has been updated accordingly;
BOINC has been given version pinning capability. Hence, the user can ask a specific sixtrack version via an appropriate variable in sysenv. The manual has been updated accordingly;
the fort.3.local is also used in one-turn jobs;
the template sixdeskenv has been updated in bunch charge and emittance to comply with HL-LHC parameters (template .mask file is an HL-LHC one);

ADMIN CHANGES

crontab jobs on BOINC server have been harmonised, such that they differ only by appname and related variables; in addition, calls to crontab jobs creating work on BOINC have an upper limit of 3k WUs (previously: 1k) per study per call. A script for commuting changes between sixtrack and sixtracktest apps has been added;
scripts monitoring the activity on BOINC have been made compliant with their deployment by the sixtadm account and no longer by amereghe;
a script for commuting sixtrack and sixtracktest app names in relevant scripts has been added;