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:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

HPS-SOFTWARE Home

HPS-SOFTWARE Home

HPS-SOFTWARE  December 2014

HPS-SOFTWARE December 2014

Subject:

Re: extra ECAL conditions information

From:

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

Reply-To:

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

Date:

Wed, 10 Dec 2014 20:24:31 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (1 lines)

Thanks, this is helpful.

I put the items that are currently not represented in the conditions system into a comment here on the relevant JIRA item I created yesterday.

https://jira.slac.stanford.edu/browse/HPSJAVA-355

Basically, it seems like there are 6 new fields (APD, PreAmp, Splitter, HVGroup, Jout, MB) which show up in the event display under crystal info which are not currently in the conditions framework.

We can add these as an EcalWiring conditions class which would be associated to a channel by the ecal_channel_id. Likely we only need to do this once for the Engineering Run.

In order to support these new fields, I would just need a text file to import in the correct format, basically first column with the ecal_channel_id and other columns with the assigned wiring information.

Can you come up with this for me?

Obviously, the ecal_channel_id must correspond to what is used now for the Eng Run (tagged as collection_id 2 in ecal_channels table I believe).

-----Original Message-----
From: Kyle McCarty [mailto:[log in to unmask]]
Sent: Wednesday, December 10, 2014 12:19 PM
To: McCormick, Jeremy I.
Cc: hps-software
Subject: Re: extra ECAL conditions information

Hello Jeremy,

Here is the information on each of the entries in the CSV file and what the data type is. Some of them already exist in the database and don't need to be added, but the others do. Note that these are all hardware mappings and are important so that if something goes wrong, we know what to fix and what is connected to what. Having it in the event display provides an easy look-up and an easy way to check if there are patterns if we start getting odd results in the data output.


* X/Y

* These are the x- and y- indices for the crystals.
* These correspond to your database's ix and iy values.

* APD

* This is the manufacturer number of the APD attached to a crystal. It can be used if we need to know what the specifications are for the APD at a later date.
* These are integers from 1 to 516.

* PreAmp

* This is the number of the preamplifier attached to the crystal. Note that there are a few that have the same number, but use a different colored wire to differentiate them. These are the ones with the [NUM]red and [NUM]blue entries.
* These are integers that range from 1 to 509. Some also have a color associated with them.

* LEDchan

* This is the channel for the LED associated with this crystal, which is used for LED commissioning and testing. This is useful because the LED GUI requires you to enter the LED channel to activate an LED and does not allow you to input an X/Y index, so having this makes it easy to look up the mapping between a certain crystal and the LED channel for that crystal.
* This is an integer between 2 and 223.

* FADCchan

* This is the crystal's channel on the FADC.
* This corresponds the condition database's "Channel" field.

* FADCslot

* This is the crystal's FADC slot.
* This corresponds to the condition database's "Slot" field.

* Splitter

* This is the identifier for the splitter associated with the crystal.
* This is an integer ranging from 1 to 16.

* HVGroup

* This is the high voltage group for the crystal.
* This is an integer from 1 to 28.

* JOUT

* This is a channel grouping.

* It is an integer from 1 to 16.

* MB

* This is the motherboard to which the crystal is attached.
* This has four values: RT, RB, LT, and LB. These represent:

* R = Right
* L = Left
* T = Top
* B = Bottom

* The top two motherboards are wired to crate 1 and the bottom to crate 2condition database's "Crate" value of 1 and bottom to a value of 2.

* Channel

* This is the signal channel.

* This is an integer that ranges from 1 to 230.

* Gain

* Ignore this; the value is not really sensible and the gain you already have is the one we should use.

Is JIRA the correct place to document this? Maybe a confluence page would be better if it needs a permanent reference page?

Thanks,

Kyle


On Wed, Dec 10, 2014 at 12:31 AM, McCormick, Jeremy I. <[log in to unmask]> wrote:


Hi, Kyle.

Can you give me a simple list of these extra channel information fields that should be added which aren’t already present in the conditions database in the EcalChannel or EcaLed classes? (see org.hps.conditions.ecal in conditions module)

(It is hard for me to interpret exactly which fields need to be picked out of the CSV file.)

It would be good to have a brief explanation of the field as well as a note about what the valid data values should like (e.g. a valid number range).

Please add this information as a comment here.

https://jira.slac.stanford.edu/browse/HPSJAVA-355

Once I have this information, then I can add a ecal_wiring table that will be able to contain this extra information keyed on channel_id.

After this, I’ll need a text file mapping ecal_channel_id to the supplementary ECAL wiring information which can then be loaded into the database.

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

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