NatLabRockies / NatLabRockies/H2Integrate
Allow time step and bounds to be specified in "HH:MM:SS" format
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 26
- Forks
- 44
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 16
Description
Allow time step and bounds to be specified in "HH:MM:SS" format
The current seconds integer timestep input format is hard to read. The "HH:MM:SS" format is easy to read.
Proposed solution
datetime already has a converter from "HH:MM:SS" format to seconds, or we can make the individual model compatible.
Alternatives considered
Additional context
Contributor guide
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 time-step and bounds inputs and the existing datetime converter mentioned in the issue, then trace how those values reach the individual model. Check how current seconds-integer inputs are validated and used. Done means both inputs accept "HH:MM:SS" while preserving existing seconds behavior, with relevant tests passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100