Closed bieryAtFnal closed 2 months ago
Unfortunately, as things stand now, this is because some environment variables are used to key the configuration: so https://github.com/DUNE-DAQ/appmodel/blob/kbiery/second_session_example/test/config/test-session.data.xml#L431 and https://github.com/DUNE-DAQ/appmodel/blob/kbiery/second_session_example/test/config/test-session.data.xml#L436 would need to be replicated too and hold swtest-session
. That's the quick fix for this particular problem. The underlying problem should be fixed differently: https://github.com/DUNE-DAQ/confmodel/issues/44
I have created a second session in my local OKS database, but when I try to use it from the
drunc
"boot" command, it does not seem to get used. This second session is named "swtest-session", and the only difference between it and the usual "test-session" is in the value for the operational environment config param (op_env
). For thetest-session
, I have changed theop_env
to "test2", and for theswtest-session
, I have specified anop_env
value of "swtest". One easy way to check which op_env value is being used is to check the prefix for HDF5 files that are created.Here are steps to demonstrate this behavior: