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

Scalars stored in sequences in single timestep optimisation #693

Closed
joroeder opened this issue Mar 24, 2020 · 2 comments
Closed

Scalars stored in sequences in single timestep optimisation #693

joroeder opened this issue Mar 24, 2020 · 2 comments
Assignees
Labels
Milestone

Comments

@joroeder
Copy link
Member

If an optimisation with one timestep is performed, the outputlib stores the scalars of the results in the dict of the sequences.

So, I guess in outputlib.processing.results(om), the following condition must be somehow adapted:

https://github.com/oemof/oemof/blob/8640ea712da8db4227979d06ed12aedfab9c7c66/oemof/outputlib/processing.py#L131

If there is a scalar, at 2 and more timesteps, there will be a NaN at the second timestep at all scalars without the need of knowing the attributes name. This must be replaced. Any ideas?

@joroeder joroeder added the bug label Mar 24, 2020
@joroeder joroeder added this to the v0.4.1 milestone Jun 4, 2020
@p-snft p-snft modified the milestones: v0.4.3, v0.4.4 May 26, 2021
@p-snft p-snft modified the milestones: v0.4.5, v0.5.0 Nov 10, 2022
@uvchik
Copy link
Member

uvchik commented Feb 2, 2023

I am not sure if this is still valid. I tried to reproduce it but maybe I did not got the idea.

@joroeder Could you check and add an example or better a failing test?

@p-snft
Copy link
Member

p-snft commented Feb 3, 2023

I will move this to v0.5.1. If it's not triaged when that version is about to be released, I'd consider this bug not existing.

@p-snft p-snft modified the milestones: v0.5.0, v0.5.1 Feb 3, 2023
@p-snft p-snft closed this as completed Aug 8, 2023
@p-snft p-snft closed this as not planned Won't fix, can't repro, duplicate, stale Aug 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants