NatLabRockies / NatLabRockies/SAM
DView timestamp misleading
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 486
- Forks
- 219
- Avg merge
- 10h 10m
- Merged PRs (30d)
- 2
Description
Hello SAM team,
I was working with field data in 15-minute intervals in SAM format, for 2019. I noticed that the data of 2019 when copied from the clipboard results, the year is being rewritten to 2020. Below I show how I found this maybe bug. ~~
File loaded for 2019. 15-min data in SAM format. Data is originally from SRRL for Golden CO.
This is how the input file looks like in Excel.
Data gives some warnings that show that the year is being read correctly to 2019.
From the dashboard you cant tell that there's anything wrong with the Year. The DHI Values match the input data too which is great:
But if you copy to clipboard:
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
No source file or test is identified in the issue. Reproduce the clipboard copy using the attached 2019, 15-minute SAM-format data and compare the exported timestamp with the input and dashboard values. Done means clipboard output preserves the source year instead of rewriting it to 2020.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100