-
Notifications
You must be signed in to change notification settings - Fork 2
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
Build mock objects #51
Comments
I don't think so. We might need to update our mock objects. They probably don't handle profiles |
MockScenario can handle profiles just fine, via MockAnalyze: https://github.com/Breakthrough-Energy/PowerSimData/blob/develop/powersimdata/tests/mock_analyze.py#L25 |
Based on my most recent experience using mock objects, they could take mock profiles in the current structure. To be specific, mock scenario could take mock profiles and mock grid attributes. Example use case here. |
Is |
We will need to re-process the time-series inputs so that they have the proper index and columns for the Scenario object to use when calculating things like curtailment. |
Here's the status of everything I think we need for a 'full' MockScenario object representing the Switch solution:
EDIT: Besides what we are already saving in the Switch project folder, it seems that we also need as inputs:
If we begin to save these files in the folder when we generate the Switch inputs (i.e. within |
As discussed elsewhere, there may be two different use cases that the user wants. Either:
The former is implemented via #107, the latter seems to be desired by @YifanLi86. I think this could be an option that the user selects from the main user-facing function when they pass the Switch project folder, once we have backend logic for the latter feature. |
We need to instantiate a
MockGrid
andMockScenario
objects to hopefully used modules in PostREISEThe text was updated successfully, but these errors were encountered: