Open GoogleCodeExporter opened 9 years ago
Original comment by f.le...@gmail.com
on 30 Dec 2014 at 8:23
Attachments:
I'm not sure what version of CBECC they are trying to use. In v2b, I get file
read errors when attempting to open the file. In v3 and v3a, when I attempt to
simulate the process jumps very quickly to "ab - Annual Translation(s) . . ."
and the progress bar indicates 87% complete, and at that point CBECC stops
working and has to be closed. I am unable to figure out what is happening.
Annual translations should be happening much earlier than 87% complete. This
is an ExistingAlteration project.
Transferring ownership to Scott.
Original comment by rhedr...@archenergy.com
on 2 Jan 2015 at 8:50
When tested in the latest development version (SVN r3040) a number of warnings
and errors are reported when analyzing this project. Some initial ones fixed
in the input file attached to this comment:
- model included 2 objects with the following duplicate Names (which is not
allowed): "2013 External Window" & "Air segment" - manually edited in XML input
- Range check failure on WtrHtr:StdbyLossFrac of WaterHeater 'Water heater' -
value updated from 0 to 0.001 in XML input
Reran analysis and got more errors:
- ZoneSystems 'FC-1' & 'FC-2' is Type = PTAC, but has no heating coil. This is
currently not supported. If the system has no heating coil, model an
appropriate Type heating coil with 1 Btu/hr capacity, or use the AirSystem
object. - fixed by creating HeatingCoil objects as described in error message.
Reran analysis and got many more errors - the first of which was: Division by
zero evaluating rule: Set SIZING_PROPOSED WtrHtr:TankOffCycleLossCoef
(83:'WaterHeater.rule' line 3630)
This highlights a ruleset problem - any denominators should be checked for
value = 0 prior to performing division, in which case logic must avoid the
division (or perhaps a range check or CHECKSIM/CODE expression needs to prevent
the user input from being analyzed.
Switching issue owner to NC to address WtrHtr rule fix.
Original comment by scriswel...@gmail.com
on 10 Feb 2015 at 7:58
Attachments:
Original issue reported on code.google.com by
f.le...@gmail.com
on 30 Dec 2014 at 8:21