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

Use scenario object to call engine #28

Merged
merged 52 commits into from
Jul 18, 2019
Merged

Use scenario object to call engine #28

merged 52 commits into from
Jul 18, 2019

Conversation

rouille
Copy link
Collaborator

@rouille rouille commented Jul 12, 2019

Changes that have been done:

  • in module call: use scenario object (in powersimdata.scenario.scenario) to pass information to Matlab script in REISE (start date, end date, interval, ...). Update monitoring files on server (status and runtime).
  • in module gather: use the Grid object (in powersimdata.input.grid) to query wind speed and solar irradiance to build profile.
  • Update Docstrings throughout the package.
  • Update README. Remove documentation on the WesternInterconnectNetwork and modify information on how to start simulation using the call module.

@@ -30,24 +32,25 @@ def ll2ij(lon_origin, lat_origin, lon, lat):


def to_reise(data):
Copy link
Contributor

Choose a reason for hiding this comment

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

@rouille Do you remember if this formatting is still necessary with the scenario object?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yes it is. We still need to create base profile for the scenario object. And I need to reformat the information I query from NREL and NOAA to a data frame with UTC timestamp as index and plant id as columns.

@kasparm kasparm force-pushed the callForScenarioObject branch from 2760bc5 to e7f6289 Compare July 13, 2019 00:08
@kasparm kasparm self-requested a review July 18, 2019 23:03
@kasparm kasparm merged commit 5d5881a into develop Jul 18, 2019
@rouille rouille deleted the callForScenarioObject branch June 15, 2020 18:45
@ahurli ahurli mentioned this pull request Mar 16, 2021
@rouille rouille changed the title Call for scenario object Use scenario object to call engine Mar 16, 2021
jmbott pushed a commit to SEL-Columbia/PreREISE that referenced this pull request May 26, 2022
* add 2019 fuel data

* style: restructure area_scale_res

* chore: add 2018 column to area_scale_com

* feat: update model fitting to all for any input base_year with necessary fitting data

* feat: update puma_fuel

* chore: move frac_target_sh_res.csv location

* fix: scaling from gbs areas corrected

* fix: update blob storage temp referencing

* chore: minor comment cleanup

* refactor: clean up code through testing

* chore: code style cleanup

* fix: correct blob reference for puma_temps

* fix: correct temp_ref_it defining

* fix: uncomment data_dir definition within functions

* fix: strike commented redundant data column

* fix: area scaling syntax cleanup

* style: basic cleanup

* style: linting fix

Co-authored-by: Daniel Olsen <[email protected]>
BainanXia pushed a commit to SEL-Columbia/PreREISE that referenced this pull request Feb 21, 2023
* add 2019 fuel data

* style: restructure area_scale_res

* chore: add 2018 column to area_scale_com

* feat: update model fitting to all for any input base_year with necessary fitting data

* feat: update puma_fuel

* chore: move frac_target_sh_res.csv location

* fix: scaling from gbs areas corrected

* fix: update blob storage temp referencing

* chore: minor comment cleanup

* refactor: clean up code through testing

* chore: code style cleanup

* fix: correct blob reference for puma_temps

* fix: correct temp_ref_it defining

* fix: uncomment data_dir definition within functions

* fix: strike commented redundant data column

* fix: area scaling syntax cleanup

* style: basic cleanup

* style: linting fix

Co-authored-by: Daniel Olsen <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants