[Sqs-general] SQS report

[Brian Salter-D. <b_...@bi...>]

I have no idea how many people are subscribed to this list or use SQS. I
may be talking to myself, but there have been 17 downloads of SQS this
year already.  So first, I would be delighted to hear from you about
your problems and requests for changes to SQS.

As you know, I finally uploaded version 3.1 to sourceforge last October.
I am now thinking about version 3.2.

I wrote SQS because I need it. I submit quantum chemistry program runs
to the queue because they use a lot of resources and need to run one at
a time, and some runs need information from the previous run. A queue is
ideal for that. Almost always I submit a job via a script that calls
qsub after creating a jobfile. However, more recently I have started
using a program where it is normal for the input file to be a script.
This means that qsub is called directly. I found that this had a few
annoying points that I have fixed. 

First, it was too easy to delete the input script if the job was removed
by qdel. The default for qdel was delete unless '-nd' was used. I have
changed that so the job file is only deleted if '-d' is specifically
called on qdel, as it is with qsub.

Second, qsub expects a full path to the job file. This is easy in a
script, but not ideal for direct submission. qsub now submits anything
starting with '/' directly, replaces './' at the start of the name with
the value of the global variable $PWD, and adds $PWD to any other name.
Does anyone use SQS where $PWD is not defined?

So, is anyone submitting jobs directly with qsub and not via a script?
Do you have any other suggestions for making this easier and work
better?

Finally is there anything else you would like to see in version 3.2? 

Best wishes to all SQS users for 2012.

Brian.

-- 
  Brian Salter-Duke (Brian Duke)      b_...@bi... 
  Adjunct Associate Professor, Dept. of Medicinal Chemistry
  Monash University (Parkville Campus), VIC 3052, Australia
              SQS - the Simple Queueing System.