kbenne / cbecc

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

Translation issue from .xml to .idf regarding Material ThrmlCndct #258

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Describe the translation issue or enhancement:

It looks like there is a issue with the translation from .xml to .idf regarding 
Material Thermal Conductivity.

If issue occurs during translation, describe what steps reproduce the
problem:
1. In CBECC simulate any of the CBECC Prototype Models.
2. In the Proposed.xml file that is produced search for a material's ThrmlCndct.
3. Compare the .xml material ThrmlCndct to the same material's ThrmlCndct in 
the Proposed.idf file.
4. The ThrmlCndct in the Proposed.xml is the correct value in IP units 
(Btu*in/ft2*F*hr).

Noah

What version of OpenStudio are you using? On what operating system?

Please provide any additional information below.

Original issue reported on code.google.com by ncz...@archenergy.com on 1 Aug 2013 at 3:54

GoogleCodeExporter commented 9 years ago
The units proposed for ThrmlCndct (Btu*in/ft2*F*hr) are not same units listed 
in the ACM (Btu/ft*F*hr).  The ruleset units defined in BEMBase are inline with 
the ACM, so before revisions to the translator are made, I suggest we reconcile 
the difference within the ruleset/ACM first.  At the very least, if the 
decision is to leave the MaterialData table and BEMBase units unchanged, the 
rule that populates this property needs to be revised.

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

GoogleCodeExporter commented 9 years ago
Issue - Fixed

I updated ThrmlCndct units from (Btu*in/ft2*F*hr) to (Btu/ft*F*hr) in 
MaterialData.csv and MaterialDataAndMetalInsFrameLayers.xlsx.  CBECC lookup 
table now matches the existing unit translation from .xml to .idf

Noah

Original comment by ncz...@archenergy.com on 1 Aug 2013 at 7:02

GoogleCodeExporter commented 9 years ago
Revising to DoneVerified to remove from action item list.  If rule updates need 
to be tracked, I suggest we create a new issue for it.

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