ECALELF  d6718b6cc30d69f18fde9018c5ae12f9d80bd7a5
Name conventions in ECALELF

For book-keeping it's important to respect a naming convention.

The full name of a json file is too long to be retained. Ntuples are produced using a json file, so to keep track of the used json file, the ntuples are stored under a directory having the short name of the json file.

The convention is the following:

{runMin}-{runMax}_{rerecoName|Prompt}_v{versionID} 

For example, for the json file:

 /afs/cern.ch/cms/CAF/CMSCOMM/COMM_DQM/certification/Collisions12/8TeV/Reprocessing/Cert_190456-208686_8TeV_22Jan2013ReReco_Collisions12_JSON.txt

the jsonName should be: 190456-208686_22Jan_v1