<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi everyone,<br class=""><br class="">I am glad to say that the roll-out of the new random triggers for <span style="font-style: normal;" class=""><u class="">Spring 2017 is finally complete and ready to be used by all</u></span>.<br class=""><br class="">The new version of random trigger files is <b class="">recon-2017_01-ver03.2</b><br class="">The most recent software version that should be used to produce realistic MC for Spring 2017 is <b class="">recon-2017_01-ver03.5 </b>which uses<b class=""> recon-2017_01-ver03_27.xml</b><div class=""><br class=""></div><div class="">Please make sure to take care when setting up the version sets. I also want to remind you that you get an email in case your project fails the initial test. This email contains an error log which can be used to debug the issue. It also contains a link which you can use to update your submission in order to solve the problem. >90% of all issues can be resolved this way. If you are stuck please email me and I can help.</div><div class=""><br class=""></div><div class="">Please use the new version set and random triggers to redo your MC and report any discrepancies you see.</div><div class=""><br class=""></div><div class="">It was also decided to remove 9 runs from the list of “good” runs due to some lingering issues with the FCAL gain calibration. Therefore, you should expect <b class="">338 runs with "@is_production and @status_approved”</b> in the RCDB. As far as I understand these runs might be salvaged at some point but for now it is safer to omit them from analyses.</div><div class=""><br class=""></div><div class="">Cheers,</div><div class="">Peter</div></body></html>