-
Notifications
You must be signed in to change notification settings - Fork 9
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
Feature critical demand #166
Conversation
Release Offgridders v.4.4
Prepare release V4.5
Release v4.6
Release/v4.6.1
…tical", "demand_dc_critical" to the excel input file
…e_demand_dc_non_critical and title_demand_dc_critical in the excel, and define constants in
…TICAL and DEMAND_PROFILE_DC_CRITICAL
Co-authored-by: smartie2076 <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure about the last commit!
Hi @adnanalakori! I am not sure from the title and text what you are planning in this PR, and will have to check this from the code. You should try to use a title that is different from #165, that directly tells me what you do. Also, "fix"/"close" are github-specific words that imply an action that github will take. They are used to close issues, ie. to adress and solve an issue. Used here, I am not sure what it will do with the other PR.
I think you created a new PR, because you pushed to a different branch name. The other branch is Should I then even look at this? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cbc.exe
and coin-license.txt
should not be pushed to the repo. I am not clear what you are planning to do...
DEMAND_AC = "demand_ac_non_critical" | ||
DEMAND_AC = "demand_ac_critical" | ||
DEMAND_DC = "demand_dc_non_critical" | ||
DEMAND_DC = "demand_dc_critical" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You now have redefined DEMAND_AC
and DEMAND_DC
directly after you defined it. Variables have to be unique.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, got it, w'll correct it -> hoppfully it runs w/o errors
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will run without errors, but not nesessarily run as intended :D
TITLE_DEMAND_AC = "title_demand_ac_non_critical" | ||
TITLE_DEMAND_AC = "title_demand_ac_critical" | ||
TITLE_DEMAND_DC = "title_demand_dc_non_critical" | ||
TITLE_DEMAND_DC = "title_demand_dc_critical" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TITLE_DEMAND_AC
and TITLE_DEMAND_DC
are defined twice, this does not work.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cbc.exe
andcoin-license.txt
should not be pushed to the repo. I am not clear what you are planning to do...
I don't know how cbc.exe
was pushed, weird...! I just received this error message "Error: No executable found for solver 'cbc'", then I copied it again to offgridders folder and re-run it.
Do you know this always why this happening ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@@ -709,7 +709,7 @@ def distribution_grid_ac( | |||
return distribution | |||
|
|||
|
|||
def demand_ac(micro_grid_system, bus_electricity_ac, demand_profile): | |||
def demand_ac(micro_grid_system, bus_electricity_ac, demand_profile, demand_name): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What are you planning to do with demand_name
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now I understand it is correct.
@@ -721,10 +721,11 @@ def demand_ac(micro_grid_system, bus_electricity_ac, demand_profile): | |||
) | |||
|
|||
micro_grid_system.add(sink_demand_ac) | |||
demand_name.add(sink_demand_ac) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do not understand what you use demand_name
for, and why you use add()
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was just planning just to merge the functions generate.demand_ac
and generate.demand_dc
to function generate.demand
, but not sure about the structure of this function below:
def demand_ac(micro_grid_system, bus_electricity_ac, demand_profile): |
Also, just trying to reach your goal mentioned in the #162, that the new demand shall be like that :
sink_demand_ac_critical = generate.demand(
micro_grid_system, bus_electricity_ac, experiment[DEMAND_PROFILE_AC_CRITICAL], demand_name=DEMAND_AC_CRITICAL
)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was just planning just to merge the functions generate.demand_ac and generate.demand_dc to function generate.demand, but not sure about the structure of this function below
Yeah, that is a good idea! You will have to change
def demand(micro_grid_system, bus_electricity_ac, demand_profile, demand_name):
Also, just trying to reach your goal mentioned in the #162, that the new demand shall be like that :
[Code]
This is correct :)
Hi @smartie2076, sorry it just a mistake that a slash |
Just re-define constants..
Fixes #165
By the way: once I made a PR, it shows with a new number #166 -> should be a way to keep this PR within the previous one #165?