I have fixed the database for runs 16095, 16141, 16286 and
16287. All these runs were missing the StopTime, and ValidConf, ValidData
were both set to UNCONFIRMED. I suspect the next run was started before
the big red Done button was pushed for all these runs. BE PATIENT -- the
end-of-run screen talks to the database and that can take a minute!!!
I submitted 16095, 16141 and 16286 to the autocruncher. 16287 had
been partially repaired by someone and resubmitted already.
Run 16281 has no entry in the database at all. I'll have to look
back through elog/BLAST_TALK to see how to create an entry.
While fixing the entry for run 16286, I realized that when we
resumed with unpol running yesterday, people didn't change the entries for
the beginning-of-run screen, so runs 16282-16288 were all marked as
BlastCurrent=0, BlastPolarity OFF, Target COSMICS. I corrected the entries
to 6730, e- INBENDING, UNPOL. The autocruncher may not use those entries,
but as Michael pointed out last week, searching the database is a LOT more
useful if the information in it is correct!!! There are not a lot of
things to do on shift any more -- make life easier for everyone doing
analysis, carefully record the running conditions!!!
Karen
At 11:46 AM 5/26/2005 -0400, Chi Zhang wrote:
>same applies to runs 16281 16286.
>
>On Thu, 26 May 2005, Chi Zhang wrote:
>
> >
> > Hi, 16141 and 16095 did not have elog entries but are listed as good ABS
> > D2 in RUNLIST. 16095 was the run just before Michael's message about elog
> > fixed. because the missing elog, these two runs are not crunched.
> >
> > Chi
> >
> >
This archive was generated by hypermail 2.1.2 : Mon Feb 24 2014 - 14:07:32 EST