Logging Design and Improvements #1812
Replies: 3 comments
-
I'd generally agree to this and can see how this would be interpreted as a documentation gap. At a quick glance, it looks like this is all there is in the dev manual for logs. |
Beta Was this translation helpful? Give feedback.
-
Hi @andfranklin - Do you have a simple example of how this run log choice makes it difficult to work with? This is the best video / documentation I've found on pythons logging - https://youtu.be/9L77QExPmI0?si=TbFYHYvZX6MtHkvB |
Beta Was this translation helpful? Give feedback.
-
I have a PR open for this: #1810 (I can't MERGE that PR right now, because we are in a merge freeze. But soon.)
As Jake said, what is your specific feature request? |
Beta Was this translation helpful? Give feedback.
-
This is a spin-off of the conversation started in issue #1807. A brief overview of my view:
The big concern seems to be the amount of effort required to implement the changes, and the unknown consequences of making changes. Admittedly I don't have a complete perspective on all of ARMI's use cases, and I hope that starting a discussion will unsurface other people's perspectives. My hope is that we can trim-down the ARMI's
runLog
requirements to the bare essential, the design can be simplified, and guidance can be provided to developers and analysts.Beta Was this translation helpful? Give feedback.
All reactions