TMAP requires a controlled clean up from time to time.
The general job structure of TMAP is
#!/bin/sh
set +x;. ${HOME}/.jobstart
# do not edit the beginning of this file
########################
## own job following ##
########################
# do not edit the rest of this file
#####################
set +x; ${HOME}/.jobend ${TMPDIR}
${HOME}/.jobstart creates a working directory of the form
/scratch/weekly/<username>/YYYY-MM-DD_hh:mm:ss
that is deleted at the end of a job by ${HOME}/.jobend. In case of a user break (<CTRL C>), the
working directory and all data therein remain on the scratch disk. These have to be deleted regularly by
~rauch/tools/clearTMAPscratch@all_linux_no_ask .
Be aware, that this command deletes all TMAP working directories. In case that TMAP jobs are still running, they will fail!
In case that TMAP jobs were started using the nohup command, they will continue even if the user logged out or if the console was rebooted. Then, these jobs can be killed individually on the respective machines (cf. user of the STOP file, Sect.. 5), or with the procedure
~rauch/tools/kill@all_linux_no_ask .
Be aware, that this command kills all your jobs (not only TMAP jobs) on all linux machines but at your local machine!