dmwm / t0wmadatasvc Goto Github PK

Hi-
I notice that one can not determine a few things in the TIer0 config from the reco API Eg

• what data tiers are produced
• how many threads

are these derivable somewhere else?

New call to replace the use of runs. Should return
the reco release status, the reco release time
and the start and end time. Still under discussion.

"we might end up replacing it with a call that just returns the GT" @hufnagel , any more details to add?

PCL people asked to get only a number not a [{run_id : number}]

The express config call expects a run parameter in it's input, not run_id. Also, both run and stream parameters should be passable independently. At the moment one can pass run and run/stream, but not stream alone (it's ignored).

The reco_config call expects a run parameter in it's input, not run_id. Also, both run and primary_dataset parameters should be passable independently. At the moment one can pass run and run/primary_dataset, but not primary_dataset alone (it's ignored).

Query needs to be changed. Logic stays the same (at
least for as long as all datasets have the same
PromptReco delay).

Can be used more or less as-is with slight query
changes. Used by both Dropbox and PCL monitoring, but
only to retrieve GT, might eventually be able to simplify.
The visualization uses the express_config call to get
the complete express config though. Easiest to port
as-is for now (also to reduce needed client changes)
and look at simplifying later.

Old Code :

http://cmssw.cvs.cern.ch/cgi-bin/cmssw.cgi/COMP/T0/src/python/T0/DAS/Database/Oracle/Configs/ExpressStreamConfig.py?revision=1.10&view=markup