[BLAST_ANAWARE] problem with autocruncher

From: Chris Crawford (chris2@lns.mit.edu)
Date: Mon Dec 13 2004 - 18:53:20 EST


  i discovered the cause of missed runs and double-crunched runs from
the autocruncher. the end-of-run tcl script gets the run-number for the
run that just ended from the coda msql database 'current-run-number'
entry. so if you start a new run before the end-of-run elog window pops
up, it will start crunching the new run instead of the one that just
finished. it also messes up the end-of-run elog entry. cf. runs 13207-8
  there is no easy fix for this, so this is one of the cases where it
pays to be inefficient and wait for the elog script to pop up before
starting a new run.
--chris



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