movements of resources from ready to stocks is not INFO1 importance #625
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Build Status Report - 6460766 - 2024-10-02 22:15:01 +0000Build
|
|
This seems reasonable - let me know when it's ready for review. |
gonuke
approved these changes
Oct 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The only thing that shows up in my terminal when I run simulations with verbosity 2 is the time step... and a single logging function in Storage,
Storage prototype() moved resources from ready to stocks at t=->time().Moving resources between ResBufs is not a
LEV_INFO1level of logging, and most (all?) other archetypes don't log anything aboveLEV_INFO3. Changed to a level commensurate with the logging of other ResBuf moves in Storage