You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, the command-line arguments that are passed to daqconf_multiru_gen are stored in an "info" file that is created in the top directory of the generated configuration.
It would be really great to also have copies of the input daqconf.json and hw_map.txt files that were used in generating the configuration stored somewhere for future reference.
If this functionality already exists, we can simple make a note in this Issue and mark it as unneeded...
The text was updated successfully, but these errors were encountered:
This is a good idea however the fact that the hardware map isn't a json file complicates things. All the files are uploaded to a mongodb in case the user wants to run a k8s run, and txt file won't work. I have another issue in dfmodules (I think) about this, the hardware map should be added to the dataflow configuration rather than in a standalone file.
@plasorak , your temporary fix sounds reasonable to me, so I vote for going ahead with it, at least on develop branch(es).
My sense from our earlier discussion was A) we weren't sure whether it should go into v3.2.x or v3.3.0, and B) we would discuss possible implementations as part of a wider discussion about HWMap files, but in neither case did I imagine that we would "not fix" this, but rather reassign it to v3.3.0.
At the moment, the command-line arguments that are passed to daqconf_multiru_gen are stored in an "info" file that is created in the top directory of the generated configuration.
It would be really great to also have copies of the input
daqconf.json
andhw_map.txt
files that were used in generating the configuration stored somewhere for future reference.If this functionality already exists, we can simple make a note in this Issue and mark it as unneeded...
The text was updated successfully, but these errors were encountered: