If I add up Single0+Singe1+Pair0+Pair1+Pulser, I would expect to recover the number of events in the file. There are 261442 events in the file, but the output shows only 5893 Single0 triggers. I think there is something wrong here.
It would be nice to re-order the output. The Trigger info should be listed in order, right below each other: Single0,Single1,Pair0,Pair1, the first and last physics events should follow each other, scaler banks and epics events should follow each other.
The only time you now show is when the data was crawled. It is much more relevant when the data was taken, i.e. timestamp of the first event and timestamp of the last event. Perhaps also the timestamps of the prestart and go events if they are present, but less important.
As this is a data catalog, it would be great if there were links to the processed datafiles and the DQM info, if available, and some status indicator if these are not available. I hope that such info would then allow us to query which files have or have not been processed already.
Also, will there be a way to incorporate the MC output into this data catalog? There, some query features would be very useful. MC data would need to include what the type of MC it was (tri-trig-beam, A’, pure-moller, etc etc)

This is a nice start, but I don’t think we are close to a re-crawl. Would it be more efficient to combine crawling with the next pass of cooking?

On Nov 7, 2015, at 10:26 AM, Graf, Norman A. <[log in to unmask]> wrote:

Jeremy,
I'd like to see formal sign-off from the principals before proceeding to crawl through all the data again. Nathan, Matt, can you arrange this?
Thanks,
Norman
________________________________________
From: [log in to unmask] <[log in to unmask]> on behalf of McCormick, Jeremy I. <[log in to unmask]>
Sent: Friday, November 6, 2015 3:35 PM
To: hps-software
Cc: [log in to unmask]
Subject: datacat example

Hi,

I'm close to starting the Auger jobs that will populate the JLAB datacat with the EVIO files from the Engineering Run.

Here is an example...

http://hpsweb.jlab.org/datacat/display/datasets/HPS/data/raw/hps_005688.evio.0

The built-in metadata fields are:

file format - always set to 'EVIO'

data type - always set to 'RAW'

size - file size on disk

master site - always set to 'JLAB'

master resource - path of EVIO file on MSS

run min/max - set to the file's run number

events - count of physics events (does not include control or EPICS events)

The per file custom metadata fields I have added thusfar are the following:

BAD_EVENTS - number of bad (unparseable) events

BLINDED - flag if file is blinded

END - flag if END event exists

EPICS_EVENTS - number of EPICS events

FILE - file sequence number

FIRST_PHYSICS_EVENT - first physics event ID

FIRST_TIMESTAMP - first timestamp

GO - flag if GO event is present

LAST_PHYSICS_EVENT - last physics event number

LAST_TIMESTAMP - last event timestamp

LED_COSMIC - number of cosmic triggers

PAIRS0 - number of PAIRS0 triggers

PAIRS1 - number of PAIRS1 triggers

PRESTART - flag if PRESTART event exists

PULSER 0 - number of pulser triggers

SCALER_BANKS - number of scaler banks found

SINGLE0 - number of SINGLE0 triggers

SINGLE1 - number of SINGLE1 triggers

Please tell me if there is any other metadata that should be included here. I would prefer not to go back and assign additional metadata later unless it becomes absolutely necessary. (It would have to be done in a separate step or the files would need to be deleted/re-added.)

Also, if you want any of these metadata field names modified for clarity of meaning, let me know.

Thanks.

--Jeremy

########################################################################
Use REPLY-ALL to reply to list

To unsubscribe from the HPS-SOFTWARE list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1

_______________________________________________
Hps-analysis mailing list
[log in to unmask]
https://mailman.jlab.org/mailman/listinfo/hps-analysis