otbrown / qoqd-workstation Goto Github PK

User should be able to specify just qpeek jobID and receive some meaningful output. This requires the first argument to be optional. Argument handling will have be made more sophisticated to allow this.

This is an obviously Good Idea. Compile the information I generally just email ad-hoc into a README document which will be displayed on the front page of the repo, aiding consistency and discoverability. Suggested by @EdmundOwen

Follow on from issue #4
The repo WIki should be used to explain in more detail the contents of the repo as well as provide help for new users.

TASKLIST:
[ ] Explain TORQUE commands, and link to TORQUE documentation
[ ] Explain job submission scripts
[ ] Explain qpeek
[ ] Explain queue settings files
[ ] Explain how to connect to workstation

The tools head and tail allow the user to specify the number of lines to be returned, but qpeek does not allow this information to be passed in. It should allow it for example in the format

qpeek -t20 jobID

The second of two jobs requesting equal resources to be submitted by the same user began running first, but the queue was presumed to be FIFO. Investigate, is the queue something else or was this a boundary case? Some information can be found in the files qstata.out and qstatf.out.