Sorry to disturb again, how did you get the LED data in the CSV file? I have not checked it, but I know that what is in the slac database it is not correct. I sent Jeremy a file with the proper LED conditions last week. Jeremy, have you uploaded them to the database? If so, which database? If not, as we said, it is better to clear all the LED conditions in both databases and re-load them (after tomorrow I'll know how to!)
Ok good to know. These are the conditions for run number 2000?
Hi, thanks!
Sorry to disturb again, how did you get the LED data in the CSV file? I have not checked it, but I know that what is in the slac database it is not correct. I sent Jeremy a file with the proper LED conditions last week. Jeremy, have you uploaded them to the database? If so, which database? If not, as we said, it is better to clear all the LED conditions in both databases and re-load them (after tomorrow I'll know how to!)
Thanks
Andrea
On 12/10/2014 10:22 PM, Kyle McCarty wrote:
Hello Jeremy,
The LED channels currently stored in the database all match those in the CSV file, so they should be good.
Thanks,
Kyle
On Wed, Dec 10, 2014 at 4:05 PM, McCormick, Jeremy I. <[log in to unmask]> wrote:
This is just an oversite on my part. Please just go ahead and add the "public" modifier to these methods and checkin your changes to SVN.
Thanks.
-----Original Message-----
From: Kyle McCarty [mailto:[log in to unmask]]
Sent: Wednesday, December 10, 2014 1:03 PM
To: McCormick, Jeremy I.
Cc: hps-software
Subject: Re: ECAL LED conditions
Hello Jeremy,
I can access the conditions module fine, but the methods like "getEcalChannelId()" are not visible for EcalLed objects within the event display package. This is what would need to be changed.
Thanks,
Kyle
On Wed, Dec 10, 2014 at 3:50 PM, McCormick, Jeremy I. <[log in to unmask]> wrote:
Checked the pom file....I don't think this is the case. The ecal-event-display module depends on ecal-recon which pulls in conditions. You should be able to import any class from the conditions module from within ecal-event-display.
-----Original Message-----
From: [log in to unmask] [mailto:[log in to unmask]] On Behalf Of McCormick, Jeremy I.
Sent: Wednesday, December 10, 2014 12:40 PM
To: Kyle McCarty
Cc: hps-software
Subject: RE: ECAL LED conditions
Yes, I can fix this...
-----Original Message-----
From: Kyle McCarty [mailto:[log in to unmask]]
Sent: Wednesday, December 10, 2014 12:34 PM
To: McCormick, Jeremy I.
Cc: hps-software
Subject: Re: ECAL LED conditions
Hello Jeremy,
The calorimeter LED information does not appear to visible to the event display package. Can you correct this? I will need it to be able to load the LED information from the database and also to perform the check to see if it matches what we currently have.
Thanks,
Kyle
On Wed, Dec 10, 2014 at 12:24 AM, McCormick, Jeremy I. <[log in to unmask]> wrote:
Hi, Kyle.
There’s a test to dump the ECAL LED mapping in the conditions module.
cd trunk/conditions
mvn test -Dtest=EcalLedTest
The test code is in src/test/java/org/hps/conditions/ecal
Though it uses run 0. The conditions at JLab for this are tagged with run_start of 2000.
So you should setDetector(“someDetectorName”, 2000) to set this up correctly if you want to access the currently loaded LED info.
—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
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
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