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 2014

HPS-SOFTWARE November 2014

Subject:

Re: aida.IPlotter

From:

Nathan Baltzell <[log in to unmask]>

Reply-To:

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

Date:

Mon, 17 Nov 2014 23:43:19 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (180 lines)

I believe your 5 should be 6; there are 3 FADC channels per crate that are real 
but are not ecal channels.  The last three channels (13,14,15) on slot 20 are not
ecal channels.  While Sho already wrote some code to deal with them, how they're
being interpreted in the relevant code I don't know.
-Nathan




On Nov 17, 2014, at 11:31 PM, "McCormick, Jeremy I." <[log in to unmask]> wrote:

> There will be 5 unrecognized channels every event for the data that is not assigned to crystals but is in the same bank.  If there are more than this, you should check the log to make sure the run number is being used correctly.  Monte Carlo data all has run number zero so it is not good for testing this.  I'm pretty sure the cosmic runs should work fine here, or at least last I checked it this was working fine.
> 
>> On Nov 17, 2014, at 7:33 PM, Nathan Baltzell <[log in to unmask]> wrote:
>> 
>> To be sure, I did a rigorous test of all 442 channels from the conditions DB at jlab for table "ecal_channels".
>> And the match is perfect regarding (x,y) <-> (crate,slot,channel) with respect to the working table I have that
>> we believe to be physically correct.  This was done on collection_id=2, which is currently the active set for
>> 2000<=run<=10000.
>> 
>> -Nathan
>> 
>> 
>>> On Nov 17, 2014, at 9:23 PM, Nathan Baltzell <[log in to unmask]> wrote:
>>> 
>>> Hi All,
>>> 
>>>> Was there more that was needed for the mapping of channels between the detector geometry and the DAQ?
>>> No, (crate,slot,channel) uniquely determines the calorimeter channel (x,y).
>>> 
>>> I just now checked by eye a dozen random channels in the ecal_channels tables in jlab's conditions database,
>>> and they are as I expect regarding (crate,slot/channel)<->(x,y).  I did not do a full 442 test, but could.
>>> How many channels are not recognized?
>>> 
>>> -Nathan
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>>> On Nov 17, 2014, at 5:21 PM, "McCormick, Jeremy I." <[log in to unmask]> wrote:
>>>> 
>>>> Hi,
>>>> 
>>>> I'm not sure about this, but doesn't the set of EcalChannel conditions replace what we used to use for the DAQ map?
>>>> 
>>>> It has a mapping of geometric IDs (ix and iy) to the crate, slot and channel.  
>>>> 
>>>> Was there more that was needed for the mapping of channels between the detector geometry and the DAQ?
>>>> 
>>>> If there is something we left out then let me know and we can add any additional classes needed by the ECAL Drivers, 
>>>> but it seems to me that EcalChannel has all the information you should need.
>>>> 
>>>> --Jeremy
>>>> 
>>>> -----Original Message-----
>>>> From: Andrea Celentano [mailto:[log in to unmask]] 
>>>> Sent: Monday, November 17, 2014 2:14 PM
>>>> To: McCormick, Jeremy I.
>>>> Cc: Nathan Baltzell
>>>> Subject: Re: aida.IPlotter
>>>> 
>>>> This can explain the errors I got with the ECAL DAQ monitor driver (some channels not recognized) However, the ECAL reconstruction seems to work properly, so it is loading the ecal DAQ map from "somewhere"..
>>>> Wasn't the file I sent around with conditions loaded on the database?
>>>>> On 11/17/2014 11:10 PM, McCormick, Jeremy I. wrote:
>>>>> Hi,
>>>>> 
>>>>> It looks to me like we never ported the ECAL DAQ map to the new conditions system...
>>>>> 
>>>>> --Jeremy
>>>>> 
>>>>> -----Original Message-----
>>>>> From: Andrea Celentano [mailto:[log in to unmask]]
>>>>> Sent: Sunday, November 16, 2014 3:02 PM
>>>>> To: McCormick, Jeremy I.; Nathan Baltzell
>>>>> Subject: Re: aida.IPlotter
>>>>> 
>>>>> Hi,
>>>>> currently on the trunk:
>>>>> 
>>>>> - All the drivers that are involved in EcalLedCommissioning.lcsim steering file use the new condition system. This steering file works with the monitoring app
>>>>> 
>>>>> - I am working on the drivers involved in the EcalMonitoringFinal.lcsim steering file, but I have problems.
>>>>> In particular, I am not sure that EcalDaqPlots is using the new condition system, since the DAQ map that I get seems to me the old one.
>>>>> Jeremy, can you please have a look at it? In particular, can you check the "detectorChanged" method?
>>>>> 
>>>>> In this method, I want to determine which DAQ slots are used for ECAL top and ECAL bottom. I do this by performing a loop on all crystals, and using the conditions system to determine the corresponding crate/slot/channel. Then, I determine the slots that are used for the two halves.
>>>>> 
>>>>> Andrea
>>>>> 
>>>>>> On 11/16/2014 09:49 PM, McCormick, Jeremy I. wrote:
>>>>>> Hi,
>>>>>> 
>>>>>> It may be that the threads aren't killed properly for other plots too, but it is just noticeable here because you click the event display hundreds of times.
>>>>>> I don't think this should be too terribly hard to fix.  The previous
>>>>>> plot state just needs to be cleared up or the histograms should be
>>>>>> cleared and reused rather than recreated.  I'll can look at it Monday
>>>>>> but...
>>>>>> 
>>>>>> We need to update the LED Driver to use the database conditions, and
>>>>>> we need to get current, valid ecal_led conditions into the database.  I don't think we should work on the ecal-commissioning branch any longer.  When will this get done?  It shouldn't be a lot of work, but someone just needs to do it.
>>>>>> 
>>>>>> -Jeremy
>>>>>> 
>>>>>>> On Nov 16, 2014, at 4:57 AM, Nathan Baltzell <[log in to unmask]> wrote:
>>>>>>> 
>>>>>>> It only happens in the drivers from Andrea that working interactively
>>>>>>> by clicking on a crystal in Kyle's gui and then updating the histos.
>>>>>>> The neverending thread(s) is spawned in the crystalClicked method by
>>>>>>> the call to  hep.aida.IPlotterRegion.plot (exactly one thread per
>>>>>>> plot call) at line 377 of
>>>>>>> org.hps.monitoring.ecal.plots.EcalEventDisplay
>>>>>>> and
>>>>>>> line 325 of org.hps.monitoring.ecal.EcalLedCommissioning
>>>>>>> and the lockup is definitely caused by too many threads.  Steering
>>>>>>> file ECalLedCommissioning.  Maybe Andrea's code is misusing the plot command.
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>>> On Nov 16, 2014, at 7:06 AM, "McCormick, Jeremy I." <[log in to unmask]> wrote:
>>>>>>>> 
>>>>>>>> Can you tell me exactly how I can reproduce this issue?  I have not seen this while testing.  I would need to know the steering file you are running and what you are doing during the session to cause the machine to lock up.  Is this something that happens only with the interaction of the event display and the plotting?  Or does it happen with simpler noninteractive usage?
>>>>>>>> 
>>>>>>>>> On Nov 16, 2014, at 3:11 AM, Nathan Baltzell <[log in to unmask]> wrote:
>>>>>>>>> 
>>>>>>>>> It doesn't technically crash, just eventually bricks the system by
>>>>>>>>> having spawned so many neverending threads that the system cannot
>>>>>>>>> do anything.  Every time plot is called, we get another thread.
>>>>>>>>> -nathan
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>>> On Nov 16, 2014, at 5:56 AM, "McCormick, Jeremy I." <[log in to unmask]> wrote:
>>>>>>>>>> 
>>>>>>>>>> Hi,
>>>>>>>>>> It could be a bug.  Can you give me more info?  What is the error traceback?
>>>>>>>>>> --Jeremy
>>>>>>>>>> ________________________________________
>>>>>>>>>> From: Nathan Baltzell <[log in to unmask]>
>>>>>>>>>> Sent: Sunday, November 16, 2014 1:33 AM
>>>>>>>>>> To: McCormick, Jeremy I.
>>>>>>>>>> Cc: Kyle McCarty
>>>>>>>>>> Subject: aida.IPlotter
>>>>>>>>>> 
>>>>>>>>>> Hi Jeremy,
>>>>>>>>>> 
>>>>>>>>>> While on a beamless shift, Kyle and I were investigating why the
>>>>>>>>>> montioring app sometimes crashes.  It seems to be because
>>>>>>>>>> hep.aida.IPlotterRegion.plot forks a new thread that never dies everytime it's called.  In hps-java, this is called from org.hps.monitoring.ecal.plots.
>>>>>>>>>> Any ideas?
>>>>>>>>>> 
>>>>>>>>>> -Nathan
>>>> 
>>>> ########################################################################
>>>> 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

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

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