-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Simple logger #876
Simple logger #876
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for these improvements @gonuke! 🙌🏻
Just a few tidying comments and a typo fix from me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll give this another few hours, but I'm ready to merge @gonuke. Thanks for fixing that CI issue!
It appears that there is an error in building the |
This is working for our tests. Can you provide more build log info about your failure? |
Sure.
I am assumeing |
Is it possible that you're finding an old header file in your system? The |
I meant to make an issue for this. I believe DAGMC (even prior to this PR) will include the headers in the installed location if they exist (i.e. if DAGMC has been installed in that location previously). |
Yes. I've recently performed a clean install (delete previous versions of DAGMC) and haven't encountered any problems so far. However, the issue still needs to be resolved and I'm not sure how to go about fixing it. I need to do some research. |
This is an attempt to streamline and add code re-use to @pshriwise's PR #872.
Per @pshriwise: This is a step toward improved console logging in some of our classes. As described in #856, DAGMC and other classes in MOAB always write some output, which can conflict with output in downstream applications and cause confusion.
A
DagMC_Logger
object is added to theDagMC
class and thedagmcmetadata
class. TheDagMC_Logger
has methodsmessage
,warning
, anderror
. The first two write tostd::cout
and the third tostd::cerr
. Warnings and errors will always be written.Also borrowed from @pshriwise: The message will either be written to screen or not depending on the verbosity level set on the class instance. I've specified two levels of verbosity for now, but I'm open to a more fine grain set of verbosity levels down the line.