ReactionMechanismGenerator / ReactionMechanismGenerator/RMG-database
treatment of multiple (conflicting) rules needs fixing
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 127
- Forks
- 160
- Avg merge
- 6d 2h
- Merged PRs (30d)
- 2
Description
In RMG-java it looks at the "rank" column (I think) and/or chooses the first (or last?). Perhaps a design decision is needed here.
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 identified. Start by tracing how RMG-java handles multiple conflicting rules and determine whether selection uses the rank column or rule order; done requires an agreed, documented rule-selection policy and corresponding behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100