|
[Rivet] compatibility issues between 2.2.0 and 2.X.XFrank Siegert frank.siegert at cern.chThu Oct 29 14:30:14 GMT 2015
Hi Andy, >> The first 2 things that come into my mind are the deprecation of >> >> jetproj.jetsByPt(pt,MAXDOUBLE,etmin,etmax,PSEUDORAPIDITY); > > > I'm not quite sure when we removed that -- apologies if it wasn't clearly > deprecated before. We brought the Cuts system in in 2.2.0 and it was > intended to be a complete replacement for all these confusing numeric > signatures. > > I'm pretty sure that none of the hundreds of standard analyses were using > this full 5-double signature, hence we didn't maintain the temporary > backward compatibility for as long as we have done with some other e.g. > projection constructor signatures. But if I understand correctly, there must have been an explicit action to remove this particular function, right? So Niccolo is probably asking why it was not just left in for a bit longer. >> and the removal of the '#' from yodas (ie, from '# BEGIN HISTO' to >> 'BEGIN HISTO'). > > This was not intended to be a "visible" change -- the last several versions > of YODA are able to read the format with or without leading # signs. So an > upgrade to the latest YODA should fix that issue for you, and for further > iterations of the YODA format we now have a way to maintain backward > compatibility with old files. I guess that Niccolo and others operated directly on the YODA files, instead of using the YODA reader functions (which would have coped with these changes)? Or did you have older YODA versions still in operation, which didn't cope with the missing #? Cheers, Frank
More information about the Rivet mailing list |