Skip to content

Conversation

@flora-hofmann-frequenz
Copy link
Collaborator

As identified by Noah if there is no data we should get nan instead of 0.0

@github-actions github-actions bot added the part:docs Affects the documentation label Oct 1, 2024
@flora-hofmann-frequenz flora-hofmann-frequenz self-assigned this Oct 1, 2024
Copy link
Contributor

@cwasicki cwasicki left a comment

Choose a reason for hiding this comment

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

LGTM.

I realized some unrelated things though:

  • We rely on the data being sorted in the sum. This is currently usually the case but it's not guaranteed by the service.
  • If we have missing data this can be really off, depending on the cause of the missing data. We currently effectively treat NaNs as zeroes and forward-fill gaps in case we use raw data. This is inconsistent and I think we should just forbid resolution of Nones (although this wouldn't really fill gaps in the current version of the service, but in future only).
  • I think the start time of the CumulativeEnergy should be the timestamp of the first sample. The end time I think is fine if we always assume resampled data, otherwise we would need to adjust it too.

@flora-hofmann-frequenz
Copy link
Collaborator Author

I realized some unrelated things though:

I have opened a new issue for these points

@flora-hofmann-frequenz flora-hofmann-frequenz added this pull request to the merge queue Oct 2, 2024
Merged via the queue into frequenz-floss:v0.x.x with commit 6a2ab86 Oct 2, 2024
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

part:docs Affects the documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants