Aron,
there is no right or wrong. As said
utils/lrn.C is a script.
~v3/lrn is a compiled code (lrn.cc)
both are right but only lrn is "supported" or upgraded. As said
you should analyze in v3. I'll move lrn.C out of path.
-- ________________________________________________________________________________ Tancredi Botto, phone: +1-617-253-9204 mobile: +1-978-490-4124 research scientist MIT/Bates, 21 Manning Av Middleton MA, 01949 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^On Fri, 18 Jul 2003, Aaron Joseph Maschinot wrote:
> > because it would be too simple to only have one, the blast directory > currently has two 'lrn' files. one is the 'good' one, and one is the > 'bad' one. > > the good one is located in /home/blast/blast/pro2003/analysis/CRUNCH/v3 > and is actually a symbolic link to the following file: > > /home/blast/blast/cvs_v3/BlastLib2/lrn* > > when you crunch data files, you want to use this one. to use it, go to > the /home/blast/blast/pro2003/analysis/CRUNCH/v3 and type: > > lrn xxxx > > where xxxx is the run number to be crunched. > > the bad 'lrn' file WHICH YOU SHOULD NOT USE is in the > /home/blast/blast/pro2003/analysis/utils directory and is called lrn.C. > DO NOT USE THIS FILE!!!!!!! i'm not quite sure why it even exists except > to cause crunching confusion. > > as recently as yesterday, the wrong 'lrn' file was used to crunch data. > data crunched using the wrong 'lrn' file is wrong (duh). > > aaron >
This archive was generated by hypermail 2.1.2 : Mon Feb 24 2014 - 14:07:29 EST