search

kbenne / cbecc

Automatically exported from code.google.com/p/cbecc
0 stars 0 forks source link

Equipment Summary:Cooling Coils:Design Coil Load reporting #334

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Describe the translation issue or enhancement:
The 00700-bz model (attached) includes SDD ZnSys:Type = FPFC 
(ZoneHVAC:FourPipeFanCoil) systems.  

The values in table
Equipment Summary:Cooling Coils, Column: Design Coil Load [W]

for all FPFC cooling coils (named BASESYS2 COILCLG-XX) is 0, and there are no 
results in the eio file for these cooling coils. 

This is a critical issue because we are retrieving this value to properly size 
BASELINE systems.  Kyle, can you review this issue and see why these values are 
not reported for these cooling coils?

Original issue reported on code.google.com by da...@360-analytics.com on 10 Nov 2013 at 9:45

Attachments:

GoogleCodeExporter commented 9 years ago 
This is almost certainly a bug in the tabular output, the data in the eio file 
is non zero, but the data in the html table is in fact zero.  See attached 
screenshots.

Original comment by kbe...@gmail.com on 12 Nov 2013 at 11:05

Attachments:

GoogleCodeExporter commented 9 years ago 
That's strange; I did a search for BASESYS2 in the eio file previously and 
didn't get any hits, but your are right, the results are in the eio file.

So... any way to fix this in the near term, other than retrieving results from 
the eio file?

Original comment by da...@360-analytics.com on 13 Nov 2013 at 12:59

GoogleCodeExporter commented 9 years ago 
It looks like the sqlite table named ComponentSizes has what you need.  Scott 
can work up a query along the lines of 

select * from ComponentSizes where CompType = 'Coil:Heating:Water' and CompName 
like 'BASESYS%';

Notice the columns of the CompnentSizes table are

CompType
CompName
Description
Value
Units

See the OutputDetailsAndExamples.pdf document for more information about that 
table.

Original comment by kbe...@gmail.com on 13 Nov 2013 at 2:10

GoogleCodeExporter commented 9 years ago 
In the 00700-bz model that I am testing on, the SQL db only appears to include 
the system and reheat heating coils.  We need the desing coil load for the FPFC 
cooling coils, which I don't see in this report.  Am I missing something?

Original comment by da...@360-analytics.com on 13 Nov 2013 at 5:36

GoogleCodeExporter commented 9 years ago 
Never mind, found them.

Original comment by da...@360-analytics.com on 13 Nov 2013 at 5:37

GoogleCodeExporter commented 9 years ago 
I think this will work.  Scott, I'll go through and make sure all the values we 
want to retrieve are in ComponentSizes, as opposed to the 
TabularDataWithStrings -> Equipment Summary table.

Original comment by da...@360-analytics.com on 13 Nov 2013 at 5:57

GoogleCodeExporter commented 9 years ago 
I reviewed the ComponentSizes data and found that we can't get all of the 
information we need on different components.  I've updated the Google Drive 
spreadsheet that summarizes retrieved values with what information we want is 
available in this sql report:

https://docs.google.com/spreadsheet/ccc?key=0AqAYyX2ggNyBdHBoVGRuaDc5RzhQazJxVXR
0SVR3eWc&usp=sharing

Basically, the only change needed at this time is to retrieve the value "Design 
Coil Load" for CoilHtg:Type = HotWater and all CoilClg:Type = ChilledWater 
coils. This value is mapped to the SDD property FluidLdDsgn.

Scott, we need this update to complete testing of the residential baseline 
prototypes with FPFC; please let me know if you have questions.

Kyle, is there a place to submit E+ bugs, or have you already submitted one?

Original comment by da...@360-analytics.com on 14 Nov 2013 at 1:18

GoogleCodeExporter commented 9 years ago 
I have not submitted a bug.  Normally things come in through the help desk.  If 
a bug is confirmed by a developer a change request is filed in their source 
control system which is StartTeam. 

http://energyplus.helpserve.com

This of course is all going to change, as Luigi will be taking over management 
role.  The code will be on GitHub just like OpenStudio.  I think he wants to 
use GitHub's issue tracker too.

Original comment by kbe...@gmail.com on 14 Nov 2013 at 2:59

GoogleCodeExporter commented 9 years ago 
How critical (timeframe-wise) is the bug report being discussed here?
Between the E+ team's focus on Fortran->C++ & management change and 
our/OpenStudio's relatively slow adoption of new E+ versions, it seems like a 
bug reported now would not be made available for 6-12 months.
If what we need is on our critical path, is there another way to access the 
information?

Original comment by scriswel...@gmail.com on 14 Nov 2013 at 4:18

GoogleCodeExporter commented 9 years ago 
Hey Scott, I just meant we should file a bug report in parallel to revising our 
results retrieval target for "Design Coil Load".  The property we need, as Kyle 
pointed out, is in the ComponentSizes report.  I was hoping everything else we 
wanted was in that report, for consistency, but I didn't find that was the case.

Comment #7 describes the CBECC change needed.

Original comment by da...@360-analytics.com on 14 Nov 2013 at 4:29

GoogleCodeExporter commented 9 years ago 
Hey Scott, I just meant we should file a bug report in parallel to revising our 
results retrieval target for "Design Coil Load".  The property we need, as Kyle 
pointed out, is in the ComponentSizes report.  I was hoping everything else we 
wanted was in that report, for consistency, but I didn't find that was the case.

Comment #7 describes the CBECC change needed.

Original comment by da...@360-analytics.com on 14 Nov 2013 at 4:29

GoogleCodeExporter commented 9 years ago 
Changing ownership to Scott for implementation of resolution per #7

Original comment by da...@360-analytics.com on 18 Nov 2013 at 10:17

GoogleCodeExporter commented 9 years ago 
Looks like "Design Coil Load" for Coil:Cooling:Water components in FPFC systems 
are not included in the ComponentSizes report either.  This doesn't make much 
sense, but is inline with the fact that the eio and sql database output don't 
have these values; definitely a bug.

So, here is the revised strategy:

Instead of retrieving the design load (on the water side of the coil), we 
retrieve the water flow rate and calculate the load from that value.  Here is a 
mapping of SDD to the value in the ComponentSizes report; note they differ 
based on whether they are heating or cooling coils: 

CoilClg:FluidFlowRtDsgnSim (gpm) = ComponentSizes:Design Water Flow Rate (m3/s)
CoilHtg:FluidFlowRtDsgnSim (gpm) = ComponentSizes:Maximum Water Flow Rate (m3/s)

Scott, I have rules revised that can be used for testing, just give me a call 
to coordinate how you want to get them.

Original comment by da...@360-analytics.com on 19 Nov 2013 at 12:59

GoogleCodeExporter commented 9 years ago 
Hi Scott,
Now that we have the package posted, are you available to coordinate on this?

Original comment by da...@360-analytics.com on 25 Nov 2013 at 9:59

GoogleCodeExporter commented 9 years ago 
Confirmation for Scott:
In parallel to the adding retrieval of the values outlined in comment #13, 
eliminate retrieval for the following SDD properties
CoilHtg:FluidLdDsgn
CoilClg:FluidLdDsgn

Original comment by da...@360-analytics.com on 26 Nov 2013 at 10:55

GoogleCodeExporter commented 9 years ago 
OpenStudio update including CoilHtg/CoilClg results retrieval as described in 
comment #13 has been committed to GC SVN @ rev 1192.

Original comment by scriswel...@gmail.com on 27 Nov 2013 at 10:13

GoogleCodeExporter commented 9 years ago 
Now getting results for all water coils, including FPFC systems that instigated 
this issue.  Closing.

Original comment by da...@360-analytics.com on 12 Dec 2013 at 5:58

GoogleCodeExporter commented 9 years ago

Original comment by da...@360-analytics.com on 12 Dec 2013 at 5:58