@@ -100,7 +100,7 @@ This 1st job will be very quick, as it just computes psd (should be done in less
...
@@ -100,7 +100,7 @@ This 1st job will be very quick, as it just computes psd (should be done in less
You can check the status of the job with `condor_q`:
You can check the status of the job with `condor_q`:
1. If you see that the status of this job is idle or running, you have to wait some more.
1. If you see that the status of this job is idle or running, you have to wait some more.
2. If the status of the job is `held`, it probably needs more resources. Run `condor_q -hold` to see the reason behind the problem. The probable cause is not enough disc or memory. For individual job run `condor_qedit jobID RequestMemory 8000` or some other number bigger than the one that caused the problem (`RequestDisk1 if the disk is the problem). If you have multiple problematic jobs, I suggest `condor_qedit -constraint 'JobStatus == 5' RequestMemory 8000` to modify all held jobs at once. You then have to release the jobs for them to start again with `condor_release -all`.
2. If the status of the job is `held`, it probably needs more resources. Run `condor_q -hold` to see the reason behind the problem. The probable cause is not enough disc or memory. For individual job run `condor_qedit jobID RequestMemory 8000` or some other number bigger than the one that caused the problem (`RequestDisk` if the disk is the problem). If you have multiple problematic jobs, I suggest `condor_qedit -constraint 'JobStatus == 5' RequestMemory 8000` to modify all held jobs at once. You then have to release the jobs for them to start again with `condor_release -all`.
3. If the job is not appearing in the que, then either it finished successfully or an error occured. Run `asimov monitor` and the asimov will check job completion status and tell you of any errors. It updates information at most every 15 min. If you want to force the update earlier, you have to delete cashe file: `.asimov/_cache_jobs.yaml`. If there is an error, you can find error logs in `working/<event name>/Prod0/logs/` with `.err` suffix. Let me know if it happens, as it shouldn't have.
3. If the job is not appearing in the que, then either it finished successfully or an error occured. Run `asimov monitor` and the asimov will check job completion status and tell you of any errors. It updates information at most every 15 min. If you want to force the update earlier, you have to delete cashe file: `.asimov/_cache_jobs.yaml`. If there is an error, you can find error logs in `working/<event name>/Prod0/logs/` with `.err` suffix. Let me know if it happens, as it shouldn't have.
If the `asimov monitor` told you that the jobs finished ok, you can now submit analysis proper. Run (remember to have your credentials generated if you haven't done so this session):
If the `asimov monitor` told you that the jobs finished ok, you can now submit analysis proper. Run (remember to have your credentials generated if you haven't done so this session):
