ReactionMechanismGenerator / ReactionMechanismGenerator/T3
Report iteration number next to unconverged species
Open
Nobody has claimed this yet.
Type: Feature
- Dominant language
- Python
- Stars
- 14
- Forks
- 7
- Avg merge
- 22h 36m
- Merged PRs (30d)
- 22
Description
So that users can go back to the iteration folder and see what happened
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
Start by locating the code that handles unconverged species and writes iteration folders. Trace how the current iteration is known, then identify where its number should be reported beside each unconverged species. Done means users can identify the relevant iteration folder from the report.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100