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

better place to store temp. generator data #41

Closed
nesnoj opened this issue Sep 14, 2017 · 1 comment
Closed

better place to store temp. generator data #41

nesnoj opened this issue Sep 14, 2017 · 1 comment

Comments

@nesnoj
Copy link
Member

nesnoj commented Sep 14, 2017

The data of agg. genos are currently stored in Network's attribute _dingo_import_data (written by dingo importer, read by geno importer) #21. To avoid spamming our main class, I need a better location here..

EDIT: If we had something like run_edisgo(), the dingo importer could return the data and pass it to the generator importer.

@nesnoj nesnoj self-assigned this Sep 14, 2017
@nesnoj nesnoj added this to the Release v0.0.2 milestone Nov 28, 2017
@gplssm gplssm modified the milestones: Release v0.0.3, Release v0.0.4 Feb 28, 2018
@birgits
Copy link
Collaborator

birgits commented Jul 9, 2021

Handling of generators in aggregated areas has changed completely. They are now exported in ding0 the same way as other generators. We can therefore close this issue.

@birgits birgits closed this as completed Jul 9, 2021
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

3 participants