Dear Nate and Curtis,
I read a bit in the documentation of the python and underlying C
library.. and played a bit around.
I can't speak for GridEngine's specific behavior because I haven't used
it in a long time, but it's not surprising that jobs "disappear" as soon
as they've exited. Unfort
Matthias,
We have had this problem on our SGE based installation for years. We referred
to it as the "green screen of death" - as it would allow a biologist to
continue analysis using output that was partial, at best, often resulting in
seemingly successful completion of the entire analysis, b
Hi Matthias,
I can't speak for GridEngine's specific behavior because I haven't used it
in a long time, but it's not surprising that jobs "disappear" as soon as
they've exited. Unfortunately, Galaxy uses periodic polling rather than
waiting on completion. We'd need to create a thread-per-submitted
