Mathieu Germain
Mathieu Germain
As suggested in #112 we should write some documentation. - [ ] Set up a [ReadTheDoc](https://readthedocs.org/), learn the good practices and how to sync it with the README.md - [...
When a job is terminated and needs to be relaunched, aka autoresumed, we should add a dependency on the new job to the current one to prevent some unforeseeable crashes....
- [x] Also make sure that the jobs are appended properly to jobs_id.txt when we resume. - [x] Allow using both path and Batch UID to resume jobs. - [x]...
If you ask for more resources than what is available on the requires queue we just crash. We should handle that gracefully and throw a proper error message. See #124...
- [ ] Add queues - [ ] Make sure it uses msub - [ ] Make sure it returns the right ID. See #137
Upon execution, smartdispatch should create that folder if it does not exist and then copy the queue file of the appropriate cluster so the user can modify it at will....
Add support for -M {gigPerNode}, -m {gigPerCommand} and make sure that this is properly handled in the PBS file.
For example, let say we launch a job on colosse and smartdispatch does not add the #PBS -A ycy-xxx-xx then msub will warn that the config is not proper but...
Add the `-d`, `--duplicate` command line argument that will add a #PBS -t 0-4 to give the option to launch duplicate of the same command. See: http://docs.adaptivecomputing.com/torque/3-0-5/2.1jobsubmission.php#jobarrays It is also...
Add a command line option to specify with which RAPID a job should be run. Double check on the compute canada website that this is the proper way to name...