In the mad6t.sh from sixjobs/sixtrack_input (which is used as the mask for running the madx jobs to generate sixtrack input), it checks after run grep -i "TWISS fail" on the madx output-log, and if present flags the job as failed.
In my case I am calling the file /afs/cern.ch/eng/lhc/optics/runII/2016/toolkit/Orbit_Routines.madx which unfortunately contains the line
! preliminary correction with recovery from Twiss failure (unstable machine)
which triggers the grep and causes SixDesk to assume the job has failed.
In the
mad6t.shfromsixjobs/sixtrack_input(which is used as the mask for running the madx jobs to generate sixtrack input), it checks after rungrep -i "TWISS fail"on the madx output-log, and if present flags the job as failed.In my case I am calling the file
/afs/cern.ch/eng/lhc/optics/runII/2016/toolkit/Orbit_Routines.madxwhich unfortunately contains the line! preliminary correction with recovery from Twiss failure (unstable machine)which triggers the
grepand causes SixDesk to assume the job has failed.