Skip to content
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

Use Logging for info and warning printouts #103

Merged
merged 3 commits into from
Jul 25, 2023
Merged

Use Logging for info and warning printouts #103

merged 3 commits into from
Jul 25, 2023

Conversation

kbarros
Copy link
Member

@kbarros kbarros commented Jul 25, 2023

UPDATED

Only the first 5 site or pair coupling override warnings will be printed to the terminal. After that, the warnings will be suppressed.

Convert some println statements to Logging.@info and @warn statements. This is appropriate for providing a warning that the user wasn't expecting. Some functions, of the form print_* explicitly promise to print something, and here the println() statements seem appropriate.

@kbarros kbarros requested a review from Lazersmoke July 25, 2023 15:56
@Lazersmoke
Copy link
Contributor

Something strange with git happening here, be careful when you merge!

But these changes look great. I think the default behavior should be to warn the user if they try to override an interaction, especially with the new way biquad is handled.

@Lazersmoke
Copy link
Contributor

There's a few more in https://github.com/search?q=repo%3ASunnySuite%2FSunny.jl%20println&type=code

but this is probably an update-as-needed situation

@kbarros kbarros merged commit 1988b18 into main Jul 25, 2023
3 checks passed
@kbarros kbarros deleted the logging branch July 25, 2023 21:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants