Difference between revisions of "Mott Analysis"
| Line 29: | Line 29: | ||
The data are deleted from local disks if they have been written in duplicate with correct byte count to the MSS tape silo. The data stay on disk for an amount of time that is related to the amount of disk space is available. | The data are deleted from local disks if they have been written in duplicate with correct byte count to the MSS tape silo. The data stay on disk for an amount of time that is related to the amount of disk space is available. | ||
If lots of disk available, the data stay forever. If not much disk, the data are deleted aggressively. | If lots of disk available, the data stay forever. If not much disk, the data are deleted aggressively. | ||
| + | |||
| + | The data is copied to: /mss/accel/peppo/raw | ||
Revision as of 11:51, 29 October 2013
Data Files
CODA writes the data to this disk: /data/mott
Analyze a run
In the directory: /work/idaq/Mott/Analysis/decoder/ Type: decode.pl RunNumber
Analysis Macros
There are several macros to be used for the analysis. All are in opsmdaq0 in the directory:
/work/idaq/Mott/Analysis/macro/
Backup CODA Data Files to SILO
Cron scripts are installed on the idaq account on opsmdaq0 to back up data and delete it from /data and /data1.
Do not attempted to copy, delete, move, or rename files. Never !
The scripts assume that data appears in /data*/DIR where DIR = "annihilation" or "compton" or "mott" Files must have the keywords "PEPPo" or "Scalers" or at least "dat". This avoids writing scratch files like root output. Do not start putting data in some new place or with new names. It won't be backed up to MSS if you do that.
The data are deleted from local disks if they have been written in duplicate with correct byte count to the MSS tape silo. The data stay on disk for an amount of time that is related to the amount of disk space is available. If lots of disk available, the data stay forever. If not much disk, the data are deleted aggressively.
The data is copied to: /mss/accel/peppo/raw
Issues and FAQ
- RunNumber: if the in the msql is different from the one in cool database, coda doesn't work. To solve it open dbedit => localhost => sessions and change the RunNumber