Skip to content

Conversation

@staudtMarius
Copy link
Member

Resolves #543
Resolves #572

@staudtMarius staudtMarius added the enhancement New feature or request label Apr 8, 2024
@staudtMarius staudtMarius self-assigned this Apr 8, 2024
@danielfeismann danielfeismann added this to the Version 6.0 milestone Jun 4, 2024
Copy link
Member

@danielfeismann danielfeismann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Another question from my side, the rest looks fine for me :)

Copy link
Member

@sebastian-peter sebastian-peter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just some remarks and questions

@sebastian-peter
Copy link
Member

sebastian-peter commented Jun 24, 2024

Note to myself: Does it make sense to only retrieve the next tick after the current instead?

Edit: Considering the principle of discrete-event simulations, we only need the very next tick. But since a tick as a Long only takes 8 bytes of memory, we only have ~ 70 kbytes for a whole year of hourly-spaced ticks (for one time series). This does not seem like a problem (currently).

Copy link
Member

@sebastian-peter sebastian-peter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks all good, thanks @staudtMarius!

@sebastian-peter sebastian-peter merged commit 0fa4219 into dev Aug 22, 2024
@sebastian-peter sebastian-peter deleted the ms/#543-enhance-timeseriesSources-with-future-activation-call branch August 22, 2024 15:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

WeatherSource: get activation ticks TimeSeriesSource: get activation ticks

4 participants