ReactionMechanismGenerator / ReactionMechanismGenerator/RMG-database
import/export: collision efficiency formatting
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 127
- Forks
- 160
- Avg merge
- 6d 2h
- Merged PRs (30d)
- 2
Description
The e formatting loses some precision and makes it harder to read. Could we use g?
Also, there's trailing whitespace, lots of spaces, and some pretty long lines (one is 161 characters long).
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 import/export formatting code and identify where collision values use e formatting. Check the surrounding output for trailing whitespace, excessive spaces, and the reported 161-character line. Done means using g formatting without the precision loss and correcting the specified formatting issues, with any relevant tests or import/export checks passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- database
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100