 |
 |
> > As far as background simulations are concerned, probably it could be an issue, but how many bunches before and after the event bunch can overlap within the readout? Do we really need to simulate entire detector run time or one-two bunches around the trigger only? To give a scale, the SVT readout window is 6*25ns = 150ns, with a shaping time of ~50ns (for the test run…we’ll probably crank it down to ~35ns for the full run). So, yes you need a lot of bunches around the main event if you want to realistically simulate things. As mentioned, if you don’t care about the beam background effects there is a different way to run readout/recon. > > Best Regards, > Mikhail. > > > > > On 10/03/2014 04:47 PM, Sho Uemura wrote: >> way to run FilterMCBunches as part of the readout simulation. We could (I think) rewrite FilterMCBunches so that it can run the readout simulation, and it can insert the > > > ######################################################################## > 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 > <osipenko.vcf> ######################################################################## 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