About 4 years ago, I introduced the context manager class "deepsuppression" as a way to ensure that sections of DAQInterface code which had Popen calls to verbose processes (e.g., an artdaq process) could suppress the output to the terminal in which DAQInterface was running. While useful in preventing lots of "noise" from obscuring more important messages (such as whether a transition was successful), sometimes for debugging purposes it's desirable to remove deepsuppression. I've modified the code so that in every place where deepsuppression occurs, there's a "debug level" which can be set in the boot file which will disable the suppression.
This issue has been migrated from https://cdcvs.fnal.gov/redmine/issues/21189 (FNAL account required) Originally created by @jcfreeman2 on 2018-10-19 15:40:56
About 4 years ago, I introduced the context manager class "deepsuppression" as a way to ensure that sections of DAQInterface code which had Popen calls to verbose processes (e.g., an artdaq process) could suppress the output to the terminal in which DAQInterface was running. While useful in preventing lots of "noise" from obscuring more important messages (such as whether a transition was successful), sometimes for debugging purposes it's desirable to remove deepsuppression. I've modified the code so that in every place where deepsuppression occurs, there's a "debug level" which can be set in the boot file which will disable the suppression.