[VoxBo] Many vbbatch sequences in the queue

[Daniel Kimberg]

"Eduardo Europa" <europaed at einstein.edu> wrote:
> I recently tried to simultaneously run multiple jobs where each
> yielded multiple vbbatch sequences in the Voxbo queue. Some jobs would
> run all the vbbatch sequences and complete without error. Other jobs
> would only run some vbbatch sequences and the remaining files for the
> job would be considered "bad" (e.g. the other vbbatch sequences were
> not "dispatched" to the queue). The error message was something to the
> effect of "vbbatch was unable to schedule sequence".

I'm trying to decode this, and I think I need a bit more information about what you did and what happened.

I'll make up some numbers to make it more concrete.  So first you submitted, say, 10 jobs to the queue (either all in the same sequence or each in its own).  Each of those 10 jobs was supposed to create 7 vbbatch sequences, for a total of 70 sequences.  For some of those 10 jobs, all 7 sequences ran.  But for others, only some ran.  And somewhere along the line, you got an error message.

It would be a great help if you could forward the exact error message, and tell me whether you got it by email, by looking at a log file, or at the command line.

My best guess is that if the invocations of vbbatch were using the -a and -s flags, the separate jobs inadvertently used the same private sequence name, and were overwriting each other's files.  This would certainly lead to some jobs running and not others, and often an error submitting the sequence if two vbbatch -s commands are run without any jobs added to the private sequence in between.  There's no reason why the magical number would be 8, though.  Are you sure it always runs perfectly with 7 and never with 8?

dan