-
Notifications
You must be signed in to change notification settings - Fork 4
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
Comments
Will there be more years in a future version? Now there is only data for 2030. @imilinkovic1 |
There will be no more years in the future version. We are analyzing only one year in CS 5. @Ludee |
The output file is now included in the adapter. Did you already tested the adapter yourself? @imilinkovic1 |
The four new data files are updated and imported to the database. I am currently writing a Jupyter Notebook to visualise these first two data versions. |
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 Thanks in advance! |
As @imilinkovic1 reported there were several new version that hasn't been uploaded yet. @4lm, please repeat the OEP exchange for PLEXOS tables. |
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 Thanks in advance! CC: @Ludee |
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 Thanks in advance! CC: @Ludee |
Hi @imilinkovic1, what's the status about this? CC: @Ludee |
I've checked the new data in the database and everything seems OK. Thanks! |
Thanks for the info! I would keep it for historical reasons! @Ludee, what do you think? |
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! |
modeller: @imilinkovic1
The text was updated successfully, but these errors were encountered: