Hi,
the *raw* data disks (NOTE: spud5 and spud6) were getting full so I had
to move around data to spud1 and 7.
After the data is transferred it is easy to ~daqstore/makelinks (just be
daqstore). But since moving 700 Gb of data takes several hours, be advised
that some runs may seem as "missing" in the transition. After transfer I
will take care of the tape backup.
Regarding *crunched* data. Some older data (before Thanksgiving last year)
was moved to net/data/8. However, we still have only 100 Gb left on spud4.
Part of this is because copies from two large re-crunches have been left
on disk (i.e. $ANALDIR/v3_1, $ANALDIR/v3_2).
I understand the mechanics of why ntuple data is duplicated. However we
should avoid this, since we should be able to reproduce ntuple data
quickly from dst so having only one ntuple copy (the "last") should be
enough.
In addition, I propose to just leave "flr" data and just scrap the "lr"
data. The only application I can see for "lr" data is the wch efficiency
which anyways requires more sofisticated tof-filtering which can be done
straight from dst. Any problems ?
Note that "flr" only takes 50 % disk space of "lr". We do not have room
for another recrunch.
regards,
tancredi
P.S.
For this we need to update DST to contain at least "trigger type" (so that
lr can be disposed) and the db "recrunch flag"+comment, so that the
history is documented.
________________________________________________________________________________
Tancredi Botto, phone: +1-617-253-9204 mobile: +1-978-490-4124
research scientist MIT/Bates, 21 Manning Av Middleton MA, 01949
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This archive was generated by hypermail 2.1.2 : Mon Feb 24 2014 - 14:07:31 EST