90.1 Climate Zones - Githubissues

GoogleCodeExporter commented 9 years ago

Rule Writing Team,

Are there any ideas on how to handle climate zones for 90.1?

Currently in CBECC-Com there are 16 climate zones.

Proj:CliZn = ClimateZone1... ClimateZone16
Proj:CliZnNum = 1... 16

Within the rules we have been using CliZnNum for logic similar to this:
if( CliZnNum > 3 ) then x else y endif

90.1 has 17 climate zones.
Proj:CliZn = 1A, 1B, 2A, 2B, 3A, 3B, 3C, 4A, 4B, 4C, 5A, 5B, 5C, 6A, 6B, 7, 8
Proj:CliZnNum = does not translate for all conditions because some 90.1 logic 
is humidity dependent so we need to have the A, B and C for each respective 
climate zones.

Should we create a CliZnNum for S901G_2010 that is just the climate numbers, 
and then it is the rule authors responsibility to find the rules that are 
climate zone letter specific?  Or we could change 1A to 1.1, and 1B to 1.2 ?

Noah

Original issue reported on code.google.com by ncz...@archenergy.com on 11 Sep 2014 at 6:15

GoogleCodeExporter commented 9 years ago

I think we should keep ClimZnNum unchanged as an integer value (1-8 for 90.1).  
There are not that many PRM requirements dependent on the A, B, C designations, 
so we can handle those cases separately in those rules.

Original comment by da...@360-analytics.com on 11 Sep 2014 at 6:22

Changed state: Discussion

GoogleCodeExporter commented 9 years ago

Maybe we could make CliZnNum a float and then use 5.1, 5.2 and 5.3 for 5A, 5B 
and 5C.  If we are only interested in the 1 through 8 part, use TRUNC(CliZnNum)?

Original comment by rhedr...@archenergy.com on 11 Sep 2014 at 6:59

kbenne / cbecc

90.1 Climate Zones #778