Control verbosity in `GeomQueryTool`
Issue #166
resolved
A DAGMC user recently requested an option to suppress some output when initializing a DAGMC instance.
https://github.com/svalinn/DAGMC/issues/856
Many of the lines shown in that issue originate in DAGMC, but some come from the GeomQueryTool class here in MOAB as well (our own doing, I believe).
A path of low resistance would be to add a verbose flag/attribute to the class that can be set to skip over these output lines, but we’re curious if there might be a more general approach that would be of benefit to the library as a whole.
Comments (2)
-
-
- changed status to resolved
A PR was submitted to enable verbosity control in GeomQueryTool
- Log in to comment
Ideally, the long-term solution would be to add the infrastructure to read command-line arguments and make them available globally in MOAB. This has been on my TODO list for some time, and I will be implementing this soon as we will add a dependency to Kokkos to enable GPU computations. When that happens, the main driver will need to invoke something like a
MOABInitialize(argc,argv), which will internally parse arguments, etc, and create a database of options.In the short term, as you said, please go ahead and add a verbosity flag for GeomQueryTool. We will simplify the usage in the next iteration.