 |
 |
Be careful though, because you will need to update a lot of steering files if you change this... On Apr 15, 2014, at 6:27 PM, Graf, Norman A. <[log in to unmask]> wrote: > Yes. We should try to not have any hidden dependencies. > > ________________________________________ > From: [log in to unmask] [[log in to unmask]] On Behalf Of Sho Uemura [[log in to unmask]] > Sent: Tuesday, April 15, 2014 6:25 PM > To: Graham, Mathew Thomas > Cc: hps-software > Subject: Re: duplicate svt channels > > Yeah. > > TrackerReconDriver is just a wrapper for SeedTracker, and I don't think > the cleanup driver really belongs in there. If we take it out, the cleanup > driver will always be visible in the steering file. Agree? > > On Tue, 15 Apr 2014, Matt Graham wrote: > >> Lame. >> >> On 4/15/2014 5:39 PM, Sho Uemura wrote: >>> The cleanup driver isn't in the standard steering files because it's a >>> subdriver of TrackerReconDriver. If you're not running TrackerReconDriver, >>> you need to add the cleanup driver on its own. >>> >>> On Tue, 15 Apr 2014, Mathew Graham wrote: >>> >>>> Hi All, >>>> >>>> For some reason I seeing duplicate channel errors from the SVT clusterer >>>> again?I know we?ve seen this before due to collections not getting cleaned >>>> out event-by-event, but I thought that was fixed a long time ago. Below >>>> is some output of what I?m seeing in my log file. >>>> >>>> ?. >>>>>> Event 4 >>>>>> Event 5 >>>>>> Event 6 >>>>>> Event 7 >>>> Duplicate channel number: 27 >>>>>> Event 8 >>>> Duplicate channel number: 27 >>>>>> Event 9 >>>> Duplicate channel number: 27 >>>>>> Event 10 >>>> Duplicate channel number: 27 >>>> Duplicate channel number: 110 >>>> Duplicate channel number: 242 >>>>>> Event 11 >>>> ?..and it grows from there until it crashed due to memory overload. >>>> >>>> Here are the drivers I?m using (well the names, but they are pretty >>>> descriptive). The only custom one is DQMDatabaseDriver, which shouldn?t >>>> matter. >>>> >>>> <execute> >>>> <driver name="EventMarkerDriver"/> >>>> <driver name="DQMDatabaseDriver"/> >>>> <driver name="CalibrationDriver"/> >>>> <driver name="RawTrackerHitSensorSetup"/> >>>> <driver name="BadChannelFilter" /> >>>> <driver name="RawTrackerHitFitterDriver" /> >>>> <driver name="TrackerHitDriver"/> >>>> <driver name="HelicalTrackHitDriver"/> >>>> <driver name="AidaSaveDriver"/> >>>> </execute> >>>> >>>> >>>> ?I know we used to have a cleanup driver in this list, but I don?t see it >>>> in the official ones and I thought we had fixed this bug anyway. Anyone >>>> have any ideas? >>>> >>>> Thanks, Matt >>>> ######################################################################## >>>> 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 ######################################################################## 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