bryngemark
bryngemark
that's great news, @tomeichlersmith ! i strongly prefer a solution where we fix what was broken, in this case, over enforcing migration to a new version across the board. some...
When we tuned the PN biasing factor to 450 and 550 respectively, the advice from Natalia was to pick the highest biasing factor (to reasonable level of precision) where these...
Sorry to be late here but then I think we should retweak the biasing factor. 20 warnings per event is way too high in my opinion, if I were to...
Huh. Then it might be a beam energy thing? Hopefully it goes away with the right biasing _and_ filter threshold (550, 5000).
@tvami i agree this is bizarre. does going to something very low (100? 10? 2? 1?) make the warning go away?
hm. i thought that as the xsec for PN events **decreases** with higher beam energy, it made sense that we could increase the biasing. but i admit i haven't thought...
so i will give you some context for the number chosen here. the main use for large numbers of pileup events is in central production. the number of events in...
i guess you could set it larger (1e5?) if you want to make really sure you don't always miss the last events in a large pileup file, `EventFile::skipToEvent()` still takes...
i guess i just fail to see the point/need to tailor this to every individual use case. if you feel strongly about it, go ahead.
this was pretty random, i think i started in the end of not knowing whether the first event was 0 or 1 and then just decided to overshoot it a...