<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><span class="">Hi everybody,</span><blockquote class="" style="margin: 0px 0px 0px 40px; border: none; padding: 0px;"></blockquote><br class=""><blockquote class="" style="margin: 0px 0px 0px 40px; border: none; padding: 0px;"></blockquote><span class="">as Thomas already mentioned in the Analysis and Production meeting yesterday there is a problem the way most people probably use MCwrapper to produce their MC. The version.xml that can be specified</span><span class=""> </span><span class="">contains a halld_recon version that should be chosen to match the halld_recon at the time of data production (for the latest reconstruction of spring17 that would be </span><span class="">recon-2017_01-ver03_hdr as e.g. in </span><span class="">version_recon-2017_01-ver03_8.xml). So the problem is that the analysis launches that produced the trees afterwards used more recent halld_recon builds with sometimes substantial changes to the analysis libraries. That means that if one produces MC with </span>version_recon-2017_01-ver03_8.xml the reconstruction matches what was used for real data but the trees produced by ReactionFilter will not match what was produced in a subsequent analysis launch.<br class="">If this is a big or a small problem is very much channel dependent but surely we all agree that we want to be able to produce our MC such that it matches the trees that we analyse and not just the REST files. A quick fix to this problem is that each individual user needs to check the version.xml used for the analysis launch in question and rerun over the REST files produced by MCwrapper. This should yield the correct trees. Although this will work I don’t think it is a good solution in the long run and we should come up with something better in this working group.<br class=""><br class="">Cheers,<br class=""><div class=""><span class="">Peter</span></div></body></html>