Yanzhao Wang （王彦昭）

Maybe set the expID at compile time is a bad idea. Doing so will bind all binary files of R3BRoot to a specific experiment. It is very bad both for...

Ok, but do you think it's a good idea to store it in JSON file (in R3BParam repo), which is human readable. The ROOT parameter file could then be generated...

Yes, JSON file is pretty much the standard file format for storing metadata. [nlohmann/json](https://github.com/nlohmann/json) has been already included in FairSoft. The problem for text based file([CalibPar_522.par](https://github.com/R3BRootGroup/R3BParams_s091_s118/blob/dev/parameters/CalibPar_522.par)) is human readable but...

I have one question though. Why do we create R3BParams for each experiment instead of just one repository?

Hi, @hapol I see. But Jose Luis also mentioned we also have some metadata files in text format which specifies some geometrical and triggering information. To transform those metadata files...

I see. If I understand you correctly, the generation scripts of root file parameters from text files should be independent of each experiment. If so, it's also ok to put...

> For NeuLAND we work directly with Root files because the calibration of the TDCs requires a lot of information and it makes no sense to produce ASCII files. If...

I'm not sure about this. From the NeuLAND calibration process, the relation between the fine time value (in ns) and fine time channels (0~4086?) is determined during the calibration process...

Hi, @igasparic Yes, that' right. But isn't NeuLAND tcal par calculated during the calibration process (actually we have a task class called R3BNeulandMapped2CalPar to do this job)? I think our...

> We run Mapped2CalPar class to produce calibration parameters and we store them into files. Yes, that's what I was saying. We create the tcal parameter file by running this...