Re: [BLAST_SHIFTS] Shift summary 07/18/2004 A (1-9)

From: Tancredi Botto (tancredi@lns.mit.edu)
Date: Sun Jul 18 2004 - 10:37:55 EDT


> Good runs: 9046-9048, 9050-9053, 9055-9061; crunching was caught up. One
> problem is that during crunching too many runs met the "segmentation
> violation" problem. Don't know why. Can some expert give an answer?

well the code sometimes seg faults. This runs are not lost but may not
be immediately used. It would be nice if they show up clearly in the
runlist/logbook as "run #### crashed after event 81,500..."

Another problem is that sometimes lrn does not start on a given spud
("file not found"). I suspect this is some sort of NFS time out, however
I've also noticed that in these cases it is enough to do

cd
lrn ####

and all is well.



This archive was generated by hypermail 2.1.2 : Mon Feb 24 2014 - 14:07:31 EST