Just in preparation , I added BLASTRUN/Batchname to the blast
login file and to a ~/.BLASTRUN file. All definitions then follow
setenv DATADIR /net/data/4/Daq/$BLASTRUN/
setenv ANALDIR /net/data/4/Analysis/$BLASTRUN/
setenv ONLINEDIR /scratch/dblast07/blast/data/$BLASTRUN/
setenv BLAST_PARAM /home/blast/blast/$BLASTRUN/Blast_Params
....
right now BLASTRUN is still set to pro2003. Users are encouraged to update
their login file. Data transfer will automatically switch over once we
change value to BatchName/BLASTRUN.
By the looks of it there are not too many macros that need to be changed
and they will all go to CVS. It is hoped that that passage can now be done
a lot more conveniently since the whole ~proXXXX is now finally a CVS
module (thanks to chris)
-- ________________________________________________________________________________ Tancredi Botto, phone: +1-617-253-9204 mobile: +1-978-490-4124 research scientist MIT/Bates, 21 Manning Av Middleton MA, 01949 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^On Fri, 16 Jan 2004, Adrian T Sindile wrote:
> Hi, Taylan, Tancredi! > > > The voting polls are open... Then how about BLAST_RUN ? > > If we care to be consistent with the RUN table in the MySQL database, I > would suggest BatchName (this name was suggested some time ago at an > analysis meeting - see MySQL, RUN table). > A run is fully described by BatchName (commis, pro*, etc.) and RunNumber... > > Adrian > > > > > The name "pro" is transparent (at least to me) as usually systems > > had two copies of cernlibs in /cern/pro and /cern/new, where pro (which > > stands for "production") was the absolutely safe fall back. > > > > -tancredi > > > > > > P.S. > > I realize I have managed to live long enough not to remember of any > > cerlib update for a quite a stretch now... > > > > > > > > > Taylan > > > > > > On Fri, 16 Jan 2004, Tancredi Botto wrote: > > > > > > > > > > > Hi, > > > > coda session name and file name will change. Everything will be pro2004 > > > > > > > > One comment: actually we should take this chance to stop hardcoding > > > > pro2003 anymore. The et_transfer, the root search path, init getters (and > > > > maybe a few other things) should set via the environment variable $PRO > > > > > > > > In this way (depending on your shell) we need only toggle one of these > > > > possible choices > > > > > > > > setenv PRO pro2003 > > > > setenv PRO pro2004 > > > > setenv PRO commis > > > > > > > > in the login file. For the blast account I plan to make $DATADIR/$ANALDIR > > > > dependent on the PRO variable. > > > > > > > > Users should make these changes in their environment as well (minimally, > > > > you should only have to set "PRO" in you login, and do that after CVS is > > > > updated and redownloaded in your account) > > > > > > > > > > > > > > > > > > > > >
This archive was generated by hypermail 2.1.2 : Mon Feb 24 2014 - 14:07:30 EST