 |
 |
Yes, setting a run number other than zero will by default cause the database constants to be applied to the detector model. You will want to run with the flag set to disable this. In general the flag should be enabled for all compact.xml files with a hard-coded opening angle where per-run alignment should be ignored. -----Original Message----- From: [log in to unmask] [mailto:[log in to unmask]] On Behalf Of Bradley T Yale Sent: Tuesday, July 12, 2016 3:03 PM To: hps-software Subject: 1.5mm detector geometry If running readout/recon MC using a 1.5mm detector geometry, does the run number cause the database to overwrite the SVT positions, or are the positions from the lcdd/compact always used? Does "-DdisableAlignmentConstants" or some other flag prevent this? Also, there is currently only a 1_5mm-v3-4-fieldmap detector available for 2015 (not v4-4-fieldmap). Would it be difficult to update the 1.5 and 2mm geometries to otherwise match the current Nominal ones (v4-4-fieldmap) with the ECal shift? Does it only involve switching the B-field in "HPS-PhysicsRun2016-1_5mm-v4-4" to the fieldmap used for 1.056 GeV, or are there other differences? Bradley ________________________________ 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