Retroffiting Manual in FAQ

[jimenofonseca]

@amraladdin please include the details here, thanks!

[amraladdin]

According to our last discussion, a small restructuring of the presentations will take place, as follows:

• Presentation on "How to ensure you have a correct main (aka baseline) scenario?"

Regarding the retrofitting set of presentations, the following changes should take place:

• Create a general presentation on "How to edit databases?"
• Create 3 sub-presentations that tackle the retrofitting topic: a) HVAC, b) Appliances, and c) Envelope.

For that to happen, we need to:

• Create/adapt a case study with a few number of buildings, and upload it on the Website/GitHub.
• Each case results should show the variation in results in % (post processing using Excel).

@jimenofonseca feel free to edit in case I forgot/misunderstood one or more of the above-mentioned points.

[jimenofonseca]

@amraladdin i think it is not necessary to adapt a casee study. the HQ should be sufficient in this matter. the analysis should take the same time in any case study. Making another one is nice to have but troublesome timewise for the goal of this milestone

[jimenofonseca]

@martin-mosteiro is the case study in the server up to date to do the study?

[martin-mosteiro]

@jimenofonseca no, it's still waiting to be merged
https://github.com/architecture-building-systems/cea-reference-case/pull/13

[jimenofonseca]

done! thanks!

…

________________________________ From: martin-mosteiro [notifications@github.com] Sent: Tuesday, May 23, 2017 4:47 PM To: architecture-building-systems/CEAforArcGIS Cc: Jimeno Fonseca; Mention Subject: Re: [architecture-building-systems/CEAforArcGIS] Retroffiting Manual in FAQ (#643) @jimenofonseca<https://github.com/jimenofonseca> no, it's still waiting to be merged architecture-building-systems/cea-reference-case#13<architecture-building-systems/cea-reference-case#13> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#643 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AIjrglK87sJRU0Et_8I0964R9oyClBkRks5r8p01gaJpZM4NcCki>.

[jimenofonseca]

@daren-thomas hi Daren, would you mind giving me an extra hand to the interface of this tool? you helped me about two weeks ago, but there is some help i need, @skype?

I am talking about branch i643

[daren-thomas]

@jimenofonseca check out the newest commit: It includes an interface. Instead of checkboxes it works like this: if there is a value in the input field, then that criteria is to be used. if the field is empty, then ignore that criterium. i think that works quite well.

as always, use cea install-toolbox to update the arcgis plugin...

[jimenofonseca]

Great! Thanks for this. The only thing is that it would be good to keep default values there. (They are like rules of thumb, and they are good to guide the user). In this context, it would be good to have checkboxes too. the checkboxes should enable or disable charging the default values. On 12 Jun 2017, at 22:33, Daren Thomas <notifications@github.com<mailto:notifications@github.com>> wrote: @jimenofonseca<https://github.com/jimenofonseca> check out the newest commit: It includes an interface. Instead of checkboxes it works like this: if there is a value in the input field, then that criteria is to be used. if the field is empty, then ignore that criterium. i think that works quite well. [image]<https://user-images.githubusercontent.com/2969564/27038952-c26129f2-4f8c-11e7-9c1d-4289f9e93572.png> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#643 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AIjrguV5UWNwB-Jziiz93GUGFLrMIdibks5sDUwPgaJpZM4NcCki>.

[daren-thomas]

We can do that, at the expense of cluttering the UI. An alternative would be to add example values to the labels. What would you prefer?

[jimenofonseca]

From my side, i would prefer the tick boxes that enable each field. In addition, it would be good to create subcategories in the interface so it is easy to read the Filters . It would avoid cluttering a bit. what do you think? On 13 Jun 2017, at 3:28 pm, Daren Thomas <notifications@github.com<mailto:notifications@github.com>> wrote: We can do that, at the expense of cluttering the UI. An alternative would be to add example values to the labels. What would you prefer? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#643 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AIjrgn3oGnk1FMuRGmw09He7-ME25F7Iks5sDjoXgaJpZM4NcCki>.

[jimenofonseca]

[daren-thomas]

@jimenofonseca you happen to know what those are called? that could be a good way to do it... still include checkboxes? i have a checkbox version coming up next. still ironing out some bugs...

[jimenofonseca]

Mm no idea about the name. Looking forward to seeing the version with the checkboxes. Best, Jimeno On 13 Jun 2017, at 18:57, Daren Thomas <notifications@github.com<mailto:notifications@github.com>> wrote: @jimenofonseca<https://github.com/jimenofonseca> you happen to know what those are called? that could be a good way to do it... still include checkboxes? i have a checkbox version coming up next. still ironing out some bugs... — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#643 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AIjrgil1RGuDcFOexiwepq972b5zRn49ks5sDmsTgaJpZM4NcCki>.

[daren-thomas]

If only I can get it to work!!

[daren-thomas]

OK. Check out the perfected interface combining the checkboxes as well as grouping the options by category.

[amraladdin]

#1 ERRORS AND ISSUES RELATED TO i643

After conducting a successful simulation using the Building Retrofit Potential Feature, I could not locate the "potentials" folder, which contains the retrofit_filters.csv file. Neither in the original scenario, i.e. "baseline", nor the created retrofitting case, i.e. "age_HVAC". Below are the screenshots of the simulation run:

(Inputs)

(Successful run)

(No "potentials" folder or "retrofit_filers.csv" files created)

While in the documentation created by Jimeno, the .csv file is successfully generated:

[amraladdin]

#2 ERRORS AND ISSUES RELATED TO i643

While testing branch i643, I found an issue:

• When using the cost criteria, an error occurs as seen in the following images:

(In this example I chose age and costs, however, even when I use the costs alone, the feature does not work.)

(Here's a snapshot of the error)

(and of course, the expected new scenario, i.e. "baseline_HVAC" is not created)

Here's a copy of the error text:

Executing: RetrofitPotentialTool C:\reference-case\baseline 2020 false retrofit_HVAC false 15 false 50 false 50 false 4 false 20 false 30 true 2 false 2 false 2 false 2 false 15 false 15 false 15
Start Time: Thu Jun 15 09:28:15 2017
Running script RetrofitPotentialTool...
['C:\Users\aelesawy\Anaconda2\envs\cea\python.exe', '-u', '-m', 'cea.cli', '--scenario', u'C:\reference-case\baseline', 'retrofit-potential', '--retrofit-target-date', '2020', '--name', 'retrofit_HVAC', '--heating-costs-threshold', '2']
Traceback (most recent call last):
File "C:\Users\aelesawy\Anaconda2\envs\cea\lib\runpy.py", line 174, in _run_module_as_main
"main", fname, loader, pkg_name)
File "C:\Users\aelesawy\Anaconda2\envs\cea\lib\runpy.py", line 72, in _run_code
exec code in run_globals
File "c:\users\aelesawy\documents\github\ceaforarcgis\cea\cli.py", line 449, in
main()
File "c:\users\aelesawy\documents\github\ceaforarcgis\cea\cli.py", line 445, in main
parsed_args.func(parsed_args)
File "c:\users\aelesawy\documents\github\ceaforarcgis\cea\cli.py", line 274, in retrofit_potential
emissions_operation_criteria=args.emissions_operation_threshold)
File "c:\users\aelesawy\documents\github\ceaforarcgis\cea\analysis\retrofit\retrofit_potential.py", line 96, in retrofit_main
costs_totals = pd.read_csv(locator_baseline.get_costs_operation_file(criteria_name))
File "C:\Users\aelesawy\Anaconda2\envs\cea\lib\site-packages\pandas\io\parsers.py", line 646, in parser_f
return _read(filepath_or_buffer, kwds)
File "C:\Users\aelesawy\Anaconda2\envs\cea\lib\site-packages\pandas\io\parsers.py", line 389, in _read
parser = TextFileReader(filepath_or_buffer, **kwds)
File "C:\Users\aelesawy\Anaconda2\envs\cea\lib\site-packages\pandas\io\parsers.py", line 730, in init
self._make_engine(self.engine)
File "C:\Users\aelesawy\Anaconda2\envs\cea\lib\site-packages\pandas\io\parsers.py", line 923, in _make_engine
self._engine = CParserWrapper(self.f, **self.options)
File "C:\Users\aelesawy\Anaconda2\envs\cea\lib\site-packages\pandas\io\parsers.py", line 1390, in init
self._reader = _parser.TextReader(src, **kwds)
File "pandas\parser.pyx", line 373, in pandas.parser.TextReader.cinit (pandas\parser.c:4184)
File "pandas\parser.pyx", line 667, in pandas.parser.TextReader._setup_parser_source (pandas\parser.c:8449)
IOError: File C:\reference-case\baseline\outputs\data\costs\Qhsf_cost_operation.csv does not exist

Completed script RetrofitPotentialTool...
Succeeded at Thu Jun 15 09:28:17 2017 (Elapsed Time: 1.29 seconds)

[jimenofonseca]

@amraladdin fixed. please check the guidelines. Now i included the interface. there is not need of the retrofit_potential file. Only buildings that comply with the criteria are kept in the new scenario. Would you mind complementing and modifying the presentation? thanks!!!

[amraladdin]

Great! Thanks! I will sync the new version, test it and report if I find any errors.

[jimenofonseca]

@amraladdin could we try to finish this? :-)

[amraladdin]

Not any time soon to be honest. This semester, my work schedule is more than full. I will also need someone who knows how this tool works to guide me through it. Otherwise, I can have time to explore the tool myself after December. I've already tried this before but the tool was still buggy, so I ended up spending a lot of time trying to make it work with no outcome.

[jimenofonseca]

@martin-mosteiro @amraladdin this feature will not be anymore supported in CEA so we will not create a tutorial. Check PR #1677