Closed gabriel-happle closed 6 years ago
@daren-thomas this issue seems to have many aspects.
one of them seems to be that the ArcGIS interface of optimization
and thermal networks
does not modify/change and save the config
file in the right way.
I.e., changes in the ArcGIS window are only partly transferred to the config file
@gabriel-happle they're not saved to the config file at all...
@gabriel-happle I think I see the problem now. Or at least, suspect what is happening: I assume, the "changes in the config file" you're talking about are the parameters to running the script. The main
function of the script accepts a config
parameter which contains the configuration. If, however, you decide to create your own instance of cea.config.Configuration
further down in the script, these parameters will not be picked up. This is by design! Also, don't do that! Pass down the config
object from the main function as intended.
Here are problematic instances of creating a cea.config.Configuration
instances done by searching all the files in the project:
weather_file = cea.config.Configuration().weather
self.config = cea.config.Configuration()self.config = cea.config.Configuration()
Checking for uses of gv.config
:
furnace_cost_data = pd.read_excel(locator.get_supply_systems(gv.config.region), sheetname="Furnace")
cea.config
has a different region than what the script usespump_cost_data = pd.read_excel(locator.get_supply_systems(gv.config.region), sheetname="Pump")
@daren-thomas in this case, I'm just the first tester who found this problem and therefore created the issue. I think @BhargavaKrishnaSreepathi 's help is needed here to fix this.
@gabriel-happle @BhargavaKrishnaSreepathi what is the current status of this issue?
@gabriel-happle @BhargavaKrishnaSreepathi what is the current status of this issue?
I think this is no longer an issue. I think this got fixed in one of PRs in the past two weeks