LISTSERV mailing list manager LISTSERV 16.5

Help for HPS-SOFTWARE Archives


HPS-SOFTWARE Archives

HPS-SOFTWARE Archives


HPS-SOFTWARE@LISTSERV.SLAC.STANFORD.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

HPS-SOFTWARE Home

HPS-SOFTWARE Home

HPS-SOFTWARE  November 2015

HPS-SOFTWARE November 2015

Subject:

Re: [Hps-analysis] datacat example

From:

"McCormick, Jeremy I." <[log in to unmask]>

Reply-To:

Software for the Heavy Photon Search Experiment <[log in to unmask]>

Date:

Tue, 10 Nov 2015 21:28:36 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (1 lines)

Hi,

The example datacat page is updated now.

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

It has the following improvements from last iteration.

1) Trigger types (SINGLES0, PAIRS0, etc.) should now be assigned accurately from the TI bank int data.

2) Added LAST_PHYSICS_TIMESTAMP and FIRST_PHYSICS_TIMESTAMP fields with timestamps from the first and last physics event headers.

3) Added a few more fields for counting event types such as SYNC events.

4) Added trigger rate calculation as TRIGGER_RATE_KHZ which is number of events that occurred between the first and last physics timestamps in the file divided by that time interval in seconds.

5) Changed event count to include all event types in the file; the PHYSICS_EVENTS field can be used to get the number of physics events.

As before, the existing FIRST_TIMESTAMP and LAST_TIMESTAMP fields may include dates from control events such as GO, PRESTART and END (or will use physics event timestamps for the intermediate files).

I wrote some scratch code to calculate charge in the file, but since it is only using one file at a time, it is not very accurate.  I think if we want to assign Q to the EVIO files, it should be done by assigning a few new metadata fields in a separate step from the initial data crawling (which is straighforward with either the Python or Java datacat APIs that are available).

I asked the datacat author about ordering the fields in the webpage, and he said that alphabetical ordering on the keys will be added soon in an updated version of the web interface.  I suggested also being able to provide a custom ordering for the keys using parameters in the URL but I'm not sure that this is something which would be added soon as it is more difficult to implement.  The ordering of the fields themselves is not preserved from when they are added so they are essentially displayed in a random order.  There is also the possibility that we can write our own webpages based on the datacat backend if we are not happy with the provided web pages.

--Jeremy

-----Original Message-----
From: Maurik Holtrop [mailto:[log in to unmask]] 
Sent: Sunday, November 08, 2015 9:03 AM
To: Graf, Norman A.
Cc: McCormick, Jeremy I.; hps-software; [log in to unmask]
Subject: Re: [Hps-analysis] datacat example

Hi Jeremy,

I am looking at the output from the Web. 

Perhaps I am getting confused between the “DataCat” and the “RunDatabase”, but I thought that one of the important things to have in here were some computed values: FCup and FCup-Gated, probably being the most important.  

Some comments:


1.	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.
2.	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.
3.	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.
4.	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. 
5.	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?

Best,
Maurik


	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
	



########################################################################
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

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
June 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011

ATOM RSS1 RSS2



LISTSERV.SLAC.STANFORD.EDU

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager

Privacy Notice, Security Notice and Terms of Use