search

joesinger12 / TestTicketTransfer

0 stars 0 forks source link

Vendor Support: Results Retrieval & Thermal Zone Naming #46

Open joesinger12 opened 6 years ago

joesinger12 commented 6 years ago

Can you determine the source of this error?

this is CBECC v3.0

Reported by: joesinger12

Original Ticket: cbecc-com/tickets/2582

joesinger12 commented 6 years ago

Original comment by: joesinger12

joesinger12 commented 6 years ago

12/15 NK - Initial review of the model - it is failing on the ab.xml run on BaseAirSys11 (Space is the Ground Flr MDF Rm with all the process loads) for the cooling coil sizing.

Severe Sizing: Coil:Cooling:DX:SingleSpeed "BASESYS11 COILCLG": Rated air volume flow rate per watt of rated total cooling capacity is out of range. ~~~ Min Rated Vol Flow Per Watt=[4.027E-005], Rated Vol Flow Per Watt=[2.464E-006], Max Rated Vol Flow Per Watt=[6.041E-005]. See Input Output Reference Manual for valid range. Severe For object = Coil:Cooling:DX:SingleSpeed, name = "BASESYS11 COILCLG" ~~~ Calculated outlet air relative humidity greater than 1. The combination of ~~~ rated air volume flow rate, total cooling capacity and sensible heat ratio yields coil exiting ~~~ air conditions above the saturation curve. Possible fixes are to reduce the rated total cooling ~~~ capacity, increase the rated air volume flow rate, or reduce the rated sensible heat ratio for this coil. ~~~ If autosizing, it is recommended that all three of these values be autosized. ~~~ ...Inputs used for calculating cooling coil bypass factor. ~~~ ...Inlet Air Temperature = 26.67 C ~~~ ...Outlet Air Temperature = -297.28 C ~~~ ...Inlet Air Humidity Ratio = 1.125000E-002 kgWater/kgDryAir ~~~ ...Outlet Air Humidity Ratio = 1.000000E-005 kgWater/kgDryAir ~~~ ...Total Cooling Capacity used in calculation = 3704.95 W ~~~ ...Air Mass Flow Rate used in calculation = 1.046026E-002 kg/s ~~~ ...Air Volume Flow Rate used in calculation = 9.132183E-003 m3/s ~~~ ...Air Volume Flow Rate per Watt of Rated Cooling Capacity is also out of bounds at = 2.4648627E-006 m3/s/W ~~~ During Warmup, Environment=LOS-ANGELES-DOWNTOWN-USC ANN CLG 0.4% CONDNS DB=>MCWB, at Simulation time=07/21 00:00 - 00:15 Fatal Check and revise the input data for this coil before rerunning the simulation.

Original comment by: joesinger12

joesinger12 commented 6 years ago

2/15/17 DR - I'm debugging a model form EnergyPro. The ab simulation is failing because the air flow for ab system BASEAIRSYS11 is out of range for a DX system. This is a single-zone system serving ThrmlZn '4-[Grd Flr] MDF Room'. I reviewed the zb sizing results in the SQL file, and I for the zone there is a cooling design flow, but that doesn't seem to be making it in to the PostSim zb model. Can you run this through our debugger to see if there is an issue with the results retrieval for this zone? Here are the SQL file values (in SI units, CalcDesFlow should be the ). Also attached are the the PostSim air flow sizing values.

Original comment by: joesinger12

joesinger12 commented 6 years ago

Original comment by: joesinger12

joesinger12 commented 6 years ago

12/17/17 SC - the workaround is to rename the ThrmlZn. I found that the calls to retrieve the sizing results for this zone look fine - it just returns no result when called with this Zone name, but returns a valid result when run with the same inputs but just this one zone name changed.

We are using the openstudio::SqlFile for all E+ results retrieval and calling the function execAndReturnFirstDouble() with a formatted SQL string (w/ all object names enclosed in double quotes) to retrieve the result.

I just did a little more looking @ the zb.ibd-detail-PostSim file and am finding that NONE of the zone cooling flows or loads are getting retrieved. Perhaps this is related to something that all/many of the zone names have in common, such as data enclosed in square brackets?

I did a second renaming run w/ more similar names but covering the first four zones and found that each renamed zone fixed the cooling load & flow results retrieval, using: 1-[Grd Flr] Retail -> 1-(Grd Flr) Retail 2-[Grd Flr] Dog Spa -> 2-|Grd Flr| Dog Spa 3-[Grd Flr] Lobby -> 3-Grd Flr Lobby 4-[Grd Flr] MDF Room -> Grd Flr MDF Room (4)

Next steps would be trying additional Zone renaming options to see if we can further isolate what about these zone names is causing the problem - perhaps presence of square brackets.

Another thing to do is to ask NREL if they are aware of anything that might explain these results retrieval errors.

Original comment by: joesinger12

joesinger12 commented 6 years ago

Original comment by: joesinger12

joesinger12 commented 5 years ago

Original comment by: joesinger12

joesinger12 commented 5 years ago

Original comment by: joesinger12

joesinger12 commented 1 year ago

Original comment by: joesinger12