Submitting jobs to IonMan1. Map a drive to \\ionman.chem.indiana.edu\jobs 2. Gather your data, either locally or in the staging area folder on ionman. Create a folder named after your sample, for instance, 0823H. You will need the following files in this folder to submit a job:
| SAMPLE.trc | Raw data | | SAMPLE.tym | Time of flight file? | | SAMPLE.inf | Pedestal information | | bin100.txt | bin100? configuration | | go3d.inp | go3d? (parent) | | pp3d.inp | pp3d? input file (CID) | | drftcal.inp | drift_calib? input | | mak2.inp | make_dta? for charge state 2 | | mak3.inp | make_dta? for charge state 3 | | ms-mak2.inp | MascotSearch? for charge state 2 (OPTIONAL) | | ms-mak3.inp | MascotSearch? for charge state 3 (OPTIONAL) |
NOTE: UNIX is case sensitive, so you will need to make sure your input files match the same case as above. Input files named after the sample should have the same case as the sample folder, with a lowercase file extension. All other files submitted should be lowercase for the time being. 3. When you are ready, move this folder into the input folder on jobs. Within 60 seconds, the folder should disappear. If it does not, see if a file named jobhunter.txt exists in the folder. If so, open it up and see why your job is not being submitted. 4. Your job should now be relocated to the queue directory, and running along. You can monitor the status of your job by looking at condor/output.txt and condor/error.txt. You can see what processes it has already completed by looking at perf.txt. You may also see the status of your job at http://ionman.chem.indiana.edu/status/ or by running jobstatus. 5. When your job has completed, it will send you an e-mail with the exit status. If the exit status is 0, your job has successfully been processed and relocated to the output folder. If it is higher than 0, something is wrong and it has been moved to the rejects folder.
|