Overview
Ideally, job management would be a system that lived in ASE that "abstracted out" the concepts of determining if a job was:
*running
*completed
*exited with error
It would ideally also abstract out the directory structure that a user wanted for his/her jobs. This would probably be a significant amount of work, so here we just summarize what has been done, in the hope that other people can re-use and perhaps improve, over time.
Scripts described below for job management can be found in /afs/slac/g/suncat/share/scripts. Less user-friendly scripts can be found in the "devel" subdirectory. Anyone in the g-suncat afs group can put scripts in these directories (type "pts mem g-suncat" to see if you're in the list ... if not, email cpo). If you don't want someone to modify scripts that you have put there, remember to "chmod -w" the file.
Andy Peterson Job Management
Andy has two reusable scripts that are in the above directory: "running" and "rundirs". Change the username to yours within the python script. He has some help enabled (e.g., "running -h"). Those are for dealing with jobs in the queue.
He also has scripts for dealing with jobs and determining if they are done. These are not as "clean" – that is, they won't just work for you like the two scripts above should, so they are in the "devel" subdirectory. The one he uses for dealing with the hundreds of alloys he screens is called "checkdone.py". He organizes the output with "analyze". Both have the "-h" option enabled, so you might get an idea of how he approached the problem but they probably won't work directly for you.