Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inaccurate dates when RunPeriod starts later than Jan 1st #42

Open
asparke2 opened this issue Nov 25, 2017 · 1 comment
Open

Inaccurate dates when RunPeriod starts later than Jan 1st #42

asparke2 opened this issue Nov 25, 2017 · 1 comment

Comments

@asparke2
Copy link
Member

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.

@olawhr
Copy link

olawhr commented Jul 19, 2024

@shorowit this is still a problem, as reported in this Unmet Hours post. Could you please help re-open the issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants