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  April 2014

HPS-SOFTWARE April 2014

Subject:

ECAL conditions

From:

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

Reply-To:

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

Date:

Thu, 24 Apr 2014 11:06:36 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (44 lines)

Hi,

We went over some ECAL conditions topics in the software meeting, today.  

Here is a collection of information for you about current development on this task, some of which is answering your previous emails.

1) I removed the ability to set a 'default' run number in the ConditionsDriver, because this does not really make any sense in terms of the architecture.  The processing of each event header would cause this to be reset, anyways.  I think it makes more sense to have the run numbers in your data that match the conditions system, at least for now.

2) The best way right now to test the readout code is going to be setting run numbers in your SLIC test data to match ones from the test run.  You can do this using the '-r' option to slic for your batch job.  I would use '1351' for this and the detector 'HPS-TestRun-v5'.  

It would look something like...

slic -g HPS-TestRun-v5.lcdd -r 1351 [rest of options]

Can you try this and let me know if it works?  

3) I did merge in some changes from trunk to the branches that Sho had made, as I am trying to keep the branches in sync so that the merge back to trunk doesn't have major conflicts.  I apologize if this caused conflicts in the branch, and from now on I'll ask before doing this.  You will need to hand merge these now on the branch by editing the files that do not compile anymore to put in the changes from trunk.  The best way to make sure everything always works for merges FROM trunk to the branches would be making sure to checkin in all of your code at the end of each work day.  This way when merging to the branches, it will be likely the merge can just happen automatically.  When you have modified code that isn't in SVN, and then I merge from trunk, when you 'svn up' you'll get conflicts because the SVN doesn't know about your current version.  This is a reason to make sure the branch code is up to date with your working copy on a daily basis.

4) We should establish a development conditions database that can be used once the software is ported to use the new conditions system.  Right now there are text files in HPS Java that have all the gains set to '1.0' and the pedestals at a fixed value, as well as time shifts at zero, for '2014' conditions.  These more-or-less dummy values can be imported  to the development database for you, but I don't believe it is very useful in the task of porting from the old conditions system, as there is nothing to test it against.  I think usage of the development database should happen once the move has been made from the old system, but if this is urgent please let me know and I'll work on it now.  In the development database, we'll establish a run '0' set of conditions that will by default used with 2014 detector MC data.

5) It may be useful to communicate via chat rather than a lot of emails.  I am 'jeremyslac' on AIM and [log in to unmask] so if you have any immediate issues or questions that need answers please feel free to contact me there.  Probably your evenings after 6 pm or so would be the best time.  The AIM app is always active on my phone, too, so I usually answer that right away.

6) There is a useful way to find class references in Eclipse by highlighting a class name, right clicking on it, and selecting 'References > Workspace'.  This will then show all the references to this class in your workspace.  You can do this on the class 'trunk/conditions/src/main/java/org/hps/conditions/deprecated/EcalConditions.java' to find usages of the old conditions system that need to be replaced.

7) I forgot that there is a significant amount of code in the 'evio' module that is calling the old conditions system.  I can branch this for you, too.  In fact, we probably should do this.  But we may want to complete work on the ecal-recon and ecal-readout-sim branches, first, and verify that it is working before doing this.

8) I looked at the changes you have made on this task that were put into SVN, and they look good actually.  I think you are going in the right direction.

9) Testing this code is absolutely crucial, and we need to convince ourselves that the conditions are working correctly in the ecal-recon and ecal-readout-sim before doing the merge back to the trunk.  See #2 about the best way to test the readout simulation with MC data.  In fact, before you make any more alterations to the code, you will want to setup a proper system for testing the changes.  Trying to fix up everything after making many un-tested changes can be a mini-disaster, so I recommend you don't do this and instead test every change as you go along.

10) The conditions module itself should not be considered unalterable, so if there are methods or functionality missing, especially from the ecal package, please let me know.  We can add directly to any of the classes in the conditions module, and some code may make more sense there, especially if you find yourself repeating code snippets in many places.  Those should more properly be methods in the conditions system itself.  Once you get a feel for it, also please feel free to add methods or classes to the conditions system that you think make more sense there.  That should be done on the trunk copy of the conditions module.  (It isn't branched.)

There was probably some other stuff too from the meeting, but my note from Evernote didn't update properly to my work machine!

As always, if you have any questions, let me know.

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

June 2024
May 2024
April 2024
March 2024
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