ROOT Review planning
Present: ROOT team, Marcin, John A., David L., Andrea, Liz (R), Markus (R)
Release Schedules:
LHCb: the final decision for ROOT6 will be taken at the beginning of November during the LHCb computing workshop. LHCb is historically very proactive in picking up latest releases, the amount of changes foreseen for 6.04 is a bit scary though for data taking: the amount of changes is big (pcm+mcjit). The release adopted for data taking will be the same until LS2.
Atlas: Atlas needs a fully working release plus externals for the beginning of December. For 6.04 will not be picked up before reprocessing of data in late 2015. For analysis: the decision for picking up ROOT6 is up to the analysis groups.
CMS: 6.02 work by the end of the month. The release will be used until the end of 2015. Intermediate releases will be integrated in development CMSSW releases during 2015 if available in order to prepare, if needed, a switch in 2016.
Axel:
o v6-02-00-patches is a special "patch release branch". Not only bug fixes, but also resources optimisations: for example memory.
o Plan to get a production release out in May 2014
Marcin:
o Issue: complex template which is either compiling on clang or gcc. Not a problem of ROOT.
o Duplication of dummy istantiations: 15 packages to be fixed.
o It seems that a huge quantity of dictionaries is created: this is an overhead and is being investigated
Marco:
o Two issues still blockers, for 6.02:
1) Negociation between ccache and xrootd: luckasz agreed to disable the negotiation. Not clear where the fix will be: ROOT or xrootd.
2) ROOT-6697: python fills some ttrees, called ntuples in LHCb. Branches are dynamically added. If the first number added is 0 the column is added as a boolean. At the second entry different from 0 or 1 an error is prompted. A fix is needed.
Both are needed soon: the release will be made by LHCb next week.
o Memory footprint: a particular application to be run in production cannot use ROOT6 as it needs 600MB VSIZE more than ROOT5.
o Longer term issues to be sorted out before november:
- memory footprint: this is coming from dictionaries, more specifically is calling interpreted functions
- Future compatibility: usual requirement. Re-run the same application 2 years later. ROOT6 for data taking must be able to run on CentOS. Future compatibility must be there. At the moment, when one moves from gcc 4.8.1 on slc6 to 4.8.2 on cc7 an incompatibility for headers
Bill:
o An IB with 6.02 is being compiled now. Two issues:
- Failures in the relvals workflows. Bill is debugging: some are missing products.
- +450 MB RSS in CMSSW workflow: cosmics, real data.
o Second fix coming to further reduce the memory
Andrea:
o It would be useful for Cool to have c++11 support in gccxml for ROOT5.
o The 2 branches will have to be maintained at least until November.