B2OC: add Hlt2B2OC_B_SigmaNet_Run3.json for the B2OC Hlt2 generic B hadron NN

to be in place for testing:

lhcb/Moore!1414 (merged)

approved this merge request

unapproved this merge request

assigned to @msaur

mentioned in merge request lhcb/Moore!1414 (merged)

changed the description

• [2022-03-08 15:17] Validation started with lhcb-master-mr#3904
• [2022-03-10 09:31] Validation started with lhcb-master-mr#3926
• [2022-03-10 16:47] Validation started with lhcb-master-mr#3935

mentioned in commit be245b67

merged

A very general question, not actually for this MR, but triggered by the filename added in this MR, and much more generally:

There are several files in ParamFiles/data which have eg. 'run3' in their name -- but isn't it quite optimistic to think that those files will be 'valid' for the entire run3? Would it not be better to have an explicit version in the name, and perhaps plan ahead for what to do if another version will be needed?

Ideally we would replace doing 'plain I/O' on $PARAMFILES/data/somename_Vversion.ext with accessing a git repo through a tiny 'ParamFiles' service which provides an interface with only two methods : one to access a filename without version 'embedded' in the name), and an explicit tag, and one method without an explicit tag, where the service would substitute the value of a property for the tag. And it would have one more property, namely the URL for the git repository to use...

Anyway, this comment is intended to resolved into an issue ;-)

mentioned in issue lhcb/Moore#411 (closed)