search

kbenne / cbecc

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

Translation - Importing SDD Model (.xml) into OpenStudio #832

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Kyle and Dan,

We are unable to import an SDD Model (.xml) using the OpenStudio plugin for 
Sketchup.

Sketchup terminates with a "bug splat".

The termination occurs even when we try to import a .xml that is unedited from 
the OS Plugin export.

OS Version: 1.4.0.4cd6ad08de
Sketchup Version: 8.0.16846

Noah

Original issue reported on code.google.com by ncz...@archenergy.com on 23 Oct 2014 at 8:36

GoogleCodeExporter commented 9 years ago 
This would certainly be odd, OS 1.4.0 and SketchUp have been tested and working 
together for a while.  What operating system are you using, Mac or Windows?  If 
Mac, which version of Mac OS?  Can you attach the problem ?

Original comment by dan.macu...@gmail.com on 24 Oct 2014 at 4:52

GoogleCodeExporter commented 9 years ago

Original comment by dan.macu...@gmail.com on 24 Oct 2014 at 4:52

GoogleCodeExporter commented 9 years ago 
I am using Windows 7 Professional.

We had the same problem in our most recent CBECC-Com v3 training.  Roger 
Hedrick also saw the same results.

I've attached a .osm file that we use in the training as well as the .xml file 
that is created when exported.  Importing this .xml file produces the "bug 
splat".

Noah

Original comment by ncz...@archenergy.com on 24 Oct 2014 at 2:51

Attachments:

GoogleCodeExporter commented 9 years ago 
This issue is really a side effect of something we talked about today.  
OpenStudio exports input SDD XML, then OpenStudio imports sim SDD XML.  
Exporting to SDD and directly reimporting into OpenStudio (without cleaning up 
in CBECC) is not currently a supported workflow.  This file has a problem 
because there are no zones and the door and window constructions don't have 
performance data.  If I recall correctly (I have not dug around in the backlog 
of issues) it was requested that OpenStudio not write some of this information 
to the input XML.  This may all have to get revisited as we improve the 
OpenStudio to SDD translation.

Original comment by dan.macu...@gmail.com on 27 Oct 2014 at 8:22

GoogleCodeExporter commented 9 years ago 
I changed this to won't fix for the near future.  We may have to revisit this.

Original comment by dan.macu...@gmail.com on 27 Oct 2014 at 8:23

GoogleCodeExporter commented 9 years ago 
Scott, it would help us in this case to have a flag that signified sim or input 
XML.  That way our translator could exit more gracefully if users try to import 
an input XML (before we actually implement that).  Is there any element we can 
use to test whether an XML is sim or input SDD?

Original comment by dan.macu...@gmail.com on 5 Nov 2014 at 5:52

GoogleCodeExporter commented 9 years ago 
My audio wasn't working yesterday when I tried to as the question: What are the 
pros/cons of using an element in the XMl file vs separate file extensions? The 
file extension would be more clear to users, so that would be my vote.

Original comment by da...@360-analytics.com on 5 Nov 2014 at 6:43

GoogleCodeExporter commented 9 years ago 
File extension change would be great to me, I would suggest changing the sim 
file as this one is not generally exposed to users.  We may still want 
something in the file to be explicit.  Also, heuristics to support past 
versions (e.g. if there is an exceptional conditions element then it is not a 
sim xml).

Original comment by dan.macu...@gmail.com on 5 Nov 2014 at 6:48

GoogleCodeExporter commented 9 years ago 
Happy to go with BOTH unique file extension and a data model property 
identifying sim SDD XML files.
So ... extension of sim SDD XML files -> .sddsimx  or  .sddsx   ???

And additional flag IN the file further identifying SIM SDD XML files:
   Proj:SimInput  /  SimulationInput
   set to '1' for sim SDD and not present in input SDD ?

Original comment by scriswel...@gmail.com on 5 Nov 2014 at 7:08

GoogleCodeExporter commented 9 years ago 
We do have a existing property (among a few others), Proj:SimFlag, that is 
classified as 'NotInput', meaning it will not be written to an Input SDD XML 
file -and- it will be stripped out by CBECC-Com if the user has it in their 
file. However, this flag is always written to the SIM XML file be 0 or 1.  Is 
just the presence of an element enough, or is it important that it also be set 
to 1?  I guess I could see down the road a possibility we would revise this to 
an Optional property for some applications, and if we want to plan for this, 
adding a designated property makes sense.

As far as heuristics, I'd say that the presence of Proj:AnalysisType and/or 
Proj:CompType are the two most reliable indicators that the XML file is an 
input file.  These are likely going to be required or defaulted inputs for all 
rulesets.

Re: file extensions, I like the shorter one.  If we did opt to revise the input 
file extension, it would be sddix?

Original comment by da...@360-analytics.com on 5 Nov 2014 at 7:26

GoogleCodeExporter commented 9 years ago 
That is great David, thanks.  The element is all we need, maybe it would be 
simplest to skip changing the file extension unless that is something you guys 
want for something else.

Original comment by dan.macu...@gmail.com on 5 Nov 2014 at 7:43

GoogleCodeExporter commented 9 years ago 
Proj:SimFlag could indeed be used.  I had not noticed that that flag is set for 
simulation output.  That, along w/ the fact that it is classified as NotInput 
are the key factors.  It can be set to 0 or 1, but when it is set to 0 it is 
not passed into OpenStudio for processing (since a value of 0 is an indicator 
that the model is not to be simulated).
I won't add any new property unless subsequent comments request it.

Re: file extensions - new wrinkle - there are separate res & com versions of 
"SDD", so my new proposal is .csddsx for com-sim and .csddix for com-input
I like the idea of having a unique input extension as well to enable file 
extension registration and display of these files in File-Open listing w/out 
having to specify the input extension (both cibd & csddix files would be 
displayed by default).
We would still allow users to open .xml files in CBECC-Com though, for backward 
compatbility.

Original comment by scriswel...@gmail.com on 5 Nov 2014 at 7:58

GoogleCodeExporter commented 9 years ago 
Proj:SimFlag works for us, no need to change file extensions from us, just let 
us know what you decide

Original comment by dan.macu...@gmail.com on 5 Nov 2014 at 10:43

GoogleCodeExporter commented 9 years ago 
Crash on import fixed via 
https://github.com/NREL/OpenStudio/commit/16a0b30769b2bd8213c972a4ffd6bb362b5819
f9

Original comment by dan.macu...@gmail.com on 5 Nov 2014 at 10:48