NatLabRockies / NatLabRockies/wex
Inaccurate dates when RunPeriod starts later than Jan 1st
Open
Nobody has claimed this yet.
bug
dview
- Dominant language
- C
- Stars
- 66
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Description
From unmet hours. If your simulation RunPeriod starts later than Jan 1st, DView still shows the data starting on Jan 1st.
Solution: Check the start date of the simulation when reading in the data from a SQL file.
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 at DView's path for reading simulation data from a SQL file. Check how the simulation RunPeriod start date is obtained and used when displaying dates. Done means a RunPeriod beginning after January 1 displays data from its actual start date.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- databases, desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100