 |
 |
This is something that we should be able to add to the database fairly quickly (couple days including testing). I agree that we should just do it ASAP.
Jeremy, can you just create a new branch and add these things to the conditions system? I know you have a branch in which you have made several back end changes to the conditions system but I think it's a bad idea to make the changes there. When do you think you can get this done by?
Yes. Seriously. We at JLab will hack stuff together, because we need it now - we absolutely need a working recon pipeline before the end of the run (and I would like to have had it last weekend, really), that's the whole point of DQM.
But the hacks and scripts we use for this will never reach the point of being a reproducible recon "pass" unless we can get the DB stuff and other infrastructure we need. And I don't see why that work can't start now. Just keep it out of the trunk.
On Wed, 29 Apr 2015, Nathan Baltzell wrote:
It seems SVT position is a pretty fundamental thing to have in the db,
and well before the end of this May run.
On Apr 29, 2015, at 8:34 PM, "Graham, Mathew Thomas" <[log in to unmask]> wrote:
That would be awesome if you have time?
On Apr 29, 2015, at 5:28 PM, Sho Uemura <[log in to unmask]> wrote:
For now I would be happy to have a script that I can run by hand to fire off an Auger job.
e.g. "runCurrentRecon XXXX Y 2mm" to do the recon on file hps_00XXXX.evio.Y and put the output in volatile.
I might do it tonight if I have time.
On Wed, 29 Apr 2015, Nathan Baltzell wrote:
If we want to process data with all 1-6 layers tracking, we will need it in the db
such that hps-java knows which detector to use based on the run number.
Else someone has to tune the batch farm scripts by run number according to
SVT position. Another option is to do only 4-6 recon.
Let me know what you think.
-Nathan
On Apr 28, 2015, at 5:34 PM, Nathan Baltzell <[log in to unmask]> wrote:
If "detector" name needs to change by run, we need it in database.
On Apr 28, 2015, at 4:29 PM, "Graham, Mathew Thomas" <[log in to unmask]> wrote:
I?m going go ahead and say it?s good to go:
org.hps.steering.recon.EngineeringRun2015FullRecon.lcsim
HPS-EngRun2015-XXX-v1 detectors
On Apr 28, 2015, at 11:46 AM, Graham, Mathew Thomas <[log in to unmask]> wrote:
Sho has been putting one together?Sho, do you think it?s ready for prime-time?
On Apr 28, 2015, at 11:44 AM, Nathan Baltzell <[log in to unmask]> wrote:
Hi Matt,
It is probably time to process a bunch of new data.
Do we have a steering and jar file with SVT ready to go
that I should use?
-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