docs: explain how ecalc handles time #639
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
olelod
force-pushed
the
docs-how-ecalc-handles-time
branch
from
b9b7cd7 to
d65fb04
Compare
TeeeJay
reviewed
Nov 29, 2024
| # Time periods in eCalc™ | ||
| eCalc™ does calculations between a global start date and a global end date. This global time period will be split into | ||
| many smaller time periods, where each of them follow immediately after each other, based on other dates encountered in | ||
| the YAML file and in the various time series resource files. |
There was a problem hiding this comment.
Give/illustrate with some examples?
TeeeJay
reviewed
Nov 29, 2024
| date, respectively. | ||
|
|
||
| :::note | ||
| Any dates defined in the YAML file (e.g. in [ENERGY_USAGE_MODEL](/about/references/ENERGY_USAGE_MODEL.md)) will not |
There was a problem hiding this comment.
I assume we check this, do we give warning or error if this is the case?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thought it would be a good idea to add some information about how eCalc interprets what is given as input.
Will add more text and probably some plots to give examples.
Have you remembered and considered?
docs/docs/changelog/next.md)docs/docs/migration_guides/)BREAKING:in footer or!in header, if breakingECALC-XXXX)Why is this pull request needed?
This pull request is needed because of....
What does this pull request change?
Write summary of what this pull request changes if needed.
Issues related to this change: