ReactionMechanismGenerator / ReactionMechanismGenerator/ARC
logging
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 51
- Forks
- 25
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 15
Description
We should improve logging in ARC.
We should have two major log files, a comprehensive one (as we currently have), and a more compact one with only essential info.
We should also save a log file created independently for each species (saved in the respective output folder).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by tracing ARC's current logging setup and how output folders are created for each species; done means retaining the comprehensive log, adding a compact log with essential information, and writing an independent log in each species' output folder.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100