Project

General

Profile

Support #22598

Update mindata crontab entries for post data taking

Added by Arthur Kreymer 2 months ago. Updated 10 days ago.

Status:
Work in progress
Priority:
Normal
Start date:
05/16/2019
Due date:
08/13/2019
% Done:

40%

Estimated time:
10.00 h
Spent time:
Duration: 90

Description

Minos data taking stopped on May 3, 2019.

Update the mindata account crontab entries as appropriate.


Related issues

Copied from BATCH - Support #22582: remove minospro crontab entriesResolved2019-05-112019-05-17

History

#1 Updated by Arthur Kreymer 2 months ago

#2 Updated by Arthur Kreymer 2 months ago

  • Estimated time changed from 5.00 h to 10.00 h
  • % Done changed from 100 to 20

On 05/15 minos-data, I removed obsolete entries running or starting

bluegrid - summarized grid access to /minos/data, no longer in use
lockclean - cleaned up stale cpn locks, no longer in use
acc_log - recorded beam intensities and temperatures each supercycle. Moot now.
beamdbu - beam files are no longer being produced
predator - declared new raw data files to SAM.

Updated and committed admin/crontab/minos-data.mindata in CVS.

We need to review mindata crontabs on other Minos hosts.

#3 Updated by Arthur Kreymer about 2 months ago

  • % Done changed from 20 to 30
 crontab -l | grep -v ^#

minos60 
    BEAMDATA

minos61
    all comments

minos62 - NA

minos63 - 
    make_monthly_cf_tarfile.sh

minos-nearline
    DataValidation
    Dqm
    om
    bfield plots
    beammonspill plots
    archiver

minos-data
    many things

#4 Updated by Arthur Kreymer 10 days ago

  • % Done changed from 30 to 40
  • Due date changed from 05/24/2019 to 08/13/2019

I have disabled the mindata@minos_nearline crontab entry.

It had entries related to data taking,
which ended months ago for Minerva and years ago for Minos

Entries were related to
    Data Validation
    DQM
    OM
    Beam archives
    Beam plots
    Bfield plots



Also available in: Atom PDF