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

Database Adapter - PLEXOS #14

Open
5 tasks done
Ludee opened this issue Nov 8, 2017 · 12 comments
Open
5 tasks done

Database Adapter - PLEXOS #14

Ludee opened this issue Nov 8, 2017 · 12 comments
Assignees
Milestone

Comments

@Ludee
Copy link
Member

Ludee commented Nov 8, 2017

modeller: @imilinkovic1

@Ludee Ludee added this to the v0.1.0 milestone Nov 8, 2017
@Ludee Ludee self-assigned this Nov 8, 2017
Ludee added a commit that referenced this issue Nov 20, 2017
Ludee added a commit that referenced this issue Nov 20, 2017
@Ludee
Copy link
Member Author

Ludee commented Nov 20, 2017

Will there be more years in a future version? Now there is only data for 2030. @imilinkovic1

Ludee added a commit that referenced this issue Nov 20, 2017
@imilinkovic1
Copy link

There will be no more years in the future version. We are analyzing only one year in CS 5. @Ludee

Ludee added a commit that referenced this issue Nov 22, 2017
@Ludee
Copy link
Member Author

Ludee commented Nov 22, 2017

The output file is now included in the adapter.
Since the structure is slightly different between the two files (column "source") there are two functions used: input and output.

Did you already tested the adapter yourself? @imilinkovic1
If not I am waiting for your feedback or call for help.
Don't hesitate to contact me if you have problems or questions.

Ludee added a commit that referenced this issue Dec 4, 2017
Ludee added a commit that referenced this issue Aug 9, 2018
@Ludee
Copy link
Member Author

Ludee commented Aug 9, 2018

The four new data files are updated and imported to the database.
The metadata (see: https://github.com/ReeemProject/reeem_db/blob/master/database_setup/reeem_db_setup_plexos.sql#L50-L96) is still missing a lot of information. E.g. no license is given yet.

I am currently writing a Jupyter Notebook to visualise these first two data versions.

Ludee added a commit that referenced this issue Aug 9, 2018
@Ludee Ludee modified the milestones: v0.1.0, v0.2.0 Oct 1, 2018
Ludee added a commit that referenced this issue Oct 8, 2018
Ludee added a commit that referenced this issue Oct 29, 2018
Ludee added a commit that referenced this issue Nov 5, 2018
4lm added a commit that referenced this issue Nov 29, 2018
Ludee added a commit that referenced this issue Jun 11, 2019
4lm pushed a commit that referenced this issue Jun 19, 2019
4lm pushed a commit that referenced this issue Jun 19, 2019
4lm added a commit that referenced this issue Jul 2, 2019
4lm added a commit that referenced this issue Jul 2, 2019
4lm added a commit that referenced this issue Jul 2, 2019
@4lm
Copy link
Member

4lm commented Jul 11, 2019

IMPORTANT: Request for OEP-Publishing

Hi @imilinkovic1,

you licensed reeem_plexos_input and reeem_plexos_output as CC-BY-4.0 and therefore suitable for publishing on the Open Energy Platform (OEP). We now pre-staged the data on OEP and are ready to hit the button :) Nevertheless we want to ask for your final OK!

If you want to have a look at the data, you find it in the REEEM DB in:

model_draft.reeem_plexos_input
model_draft.reeem_plexos_output

Thanks in advance!

@Ludee
Copy link
Member Author

Ludee commented Jul 15, 2019

As @imilinkovic1 reported there were several new version that hasn't been uploaded yet.
I just included them in the adapter and run the upload.

@4lm, please repeat the OEP exchange for PLEXOS tables.

Ludee added a commit that referenced this issue Jul 15, 2019
Ludee added a commit that referenced this issue Jul 15, 2019
4lm added a commit that referenced this issue Jul 16, 2019
@4lm
Copy link
Member

4lm commented Jul 16, 2019

Hi @imilinkovic1,

thanks for the hint! I imported the 12 files, updated the tagging and exported the tagged data from REEEM DB to OEP DB. Please have a look again (to give your OK for OEP publication), you find it in the REEEM DB in:

model_draft.reeem_plexos_input
model_draft.reeem_plexos_output

Thanks in advance!

CC: @Ludee

@4lm
Copy link
Member

4lm commented Aug 1, 2019

Hi @imilinkovic1,

as requested via email, I updated the changed data (and tagged it). Before I export the tagged data from REEEM DB to OEP DB for publishing, please have a look (to give your OK for OEP publication), you find it in the REEEM DB in:

model_draft.reeem_plexos_input
model_draft.reeem_plexos_output

Thanks in advance!

CC: @Ludee

@4lm
Copy link
Member

4lm commented Aug 6, 2019

Hi @imilinkovic1,

as requested via email, I updated the changed data (and tagged it). Before I export the tagged data from REEEM DB to OEP DB for publishing, please have a look (to give your OK for OEP publication), you find it in the REEEM DB in:

model_draft.reeem_plexos_input
model_draft.reeem_plexos_output

Thanks in advance!

CC: @Ludee

Hi @imilinkovic1, what's the status about this?

CC: @Ludee

@imilinkovic1
Copy link

Hi @4lm and @Ludee,

I've checked the new data in the database and everything seems OK.
I've noticed that the input/output data for "Base" scenario are also in the database. That scenario was relevant in the first phase of our modelling activities and it is not relevant for final results. So should that data be removed from the database? Or we are keeping all versions?

Thanks!

@4lm
Copy link
Member

4lm commented Aug 6, 2019

Thanks for the info!

I would keep it for historical reasons!

@Ludee, what do you think?

@4lm
Copy link
Member

4lm commented Aug 6, 2019

Hi @imilinkovic1,

I talked to @Ludee, we leave "Base" in. We also kept all the data (incl. "Base") in all the other models, so it makes sense to also keep "Base" in PLEXOS.

Have a nice vacation!

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