Yeah, we need to work out a more sane system for this…and other stuff. On Apr 23, 2015, at 2:03 PM, Omar Moreno <[log in to unmask]<mailto:[log in to unmask]>> wrote: You are right. I just realized that the detector HPS-ECalCommissioning-v3 is hard coded into the steering file under the conditions driver. If I don't specify the detector, it works. Of course, if you don't specify the detector, you can no longer freeze the conditions for a given run number .... We should probably update all of the steering files to use the engineering run nominal detector. On Thu, Apr 23, 2015 at 1:38 PM, Graham, Mathew Thomas <[log in to unmask]<mailto:[log in to unmask]>> wrote: Actually, I take it back…all of the files in: /mss/hallb/hps/production/slic/beam-tri/1pt1/ should be using HPS-EngRun2015-Nominal-v0 On Apr 23, 2015, at 1:06 PM, Graham, Mathew Thomas <[log in to unmask]<mailto:[log in to unmask]>> wrote: Dammit…I'll run slic with one of the v0 geometries….I’ll make one with the settings from last night (3.1 (bottom) & 3.0 mm (top)). On Apr 23, 2015, at 12:49 PM, Omar Moreno <[log in to unmask]<mailto:[log in to unmask]>> wrote: Hi Matt, It looks like the 1.1 GeV slic output files that you pointed us to were generated using a geometry that doesn't contain the SVT. Specifically, they were generated using the HPS-ECalCommissioning-v3 geometry. Are there slic output files anywhere which use the correct geometry? --Omar Moreno ________________________________ 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