Notebooks protobuildings#447
Conversation
|
@nllong @JieXiong9119 , I have some cleaning up to do on that. Can you verify the code part and kindly ignore the text for the moment? I have some descriptions to write near the end of the document and some section numbers to verify. |
|
@laurenliz22 , the text has been updated! I think it is ready for review |
laurenliz22
left a comment
There was a problem hiding this comment.
@ThibaultMarzullo This is awesome, thank you for all of your hard work. I added in a few comments - do you mind looking through and letting me know if you have any questions. Thank you!!
Updated the XML examples. Removed older markdown file.
|
@laurenliz22 Thank you, I have committed the corrected version following your review. I have not added a ReadMe file as Jie already created a single ReadMe for the whole bsync_examples folder that mentions the primary school example. |
laurenliz22
left a comment
There was a problem hiding this comment.
Looks great! Thanks Thibault!
nllong
left a comment
There was a problem hiding this comment.
this is great. There are some orthographic updates, but they aren't required to merge.
I do think one item that we need to solve is how to make these new BuildingSync files cover more than just Level 1 and Level 2 Use Cases (as seen by the Validation Tool)? Will these files upload to Audit Template, if not, what is missing? How can we make these work with SEED (looks like that use case was also a red X)?
Good work diving in and dealing with very detailed models!
|
|
||
| ## 4. Setting up the root of the BuildingSync file | ||
|
|
||
| We are going to define the basic building blocks (ha!) of our representation of the primary school prototype building. For that, we need to define a buiding, which belongs to a site, which belongs to a facility, which belongs to the highest-level of our BuildingSync file: the BuildingSync root. It will look like this: |
|
|
||
| # xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance" | ||
| # xsi:SchemaLocation = "http://buildingsync.net/schemas/bedes-auc/2019 ../../../BuildingSync.xsd" | ||
| root = bsync.BuildingSync()#**kwargs=xmlargs) |
There was a problem hiding this comment.
| root = bsync.BuildingSync()#**kwargs=xmlargs) |
| 'xsi:SchemaLocation' : "http://buildingsync.net/schemas/bedes-auc/2019 ../../../BuildingSync.xsd" | ||
| } | ||
|
|
||
| # xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance" |
There was a problem hiding this comment.
| # xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance" |
| ```python | ||
| # create a new section | ||
| gym_sec = bsync.Sections.Section(ID="Gym") | ||
| gym_sec += bsync.SectionType('Space function') |
There was a problem hiding this comment.
| gym_sec += bsync.SectionType('Space function') | |
| gym_sec += bsync.SectionType("Space function") |
this repeats...
| # Let us automate the task this time | ||
| # We first create a list of dictionaries that contains information on space IDs and the appropriate plug load. The plug load is taken from the Primary School Prototype ASHRAE Standard 90.1-2016 model | ||
| # We take the IDs from the sections we created earlier | ||
| plugloads = [{'spaceid' : lobby_sec["ID"], 'plugload' : 4.0}, |
There was a problem hiding this comment.
good job on the space functions! I'm wondering if in the future we can create a dict or something that we store all the space function data in first, then just iterate? Similar to your space plugloads here.
There was a problem hiding this comment.
Yes, agreed. I'll also do the same for schedules, it's a bit too dense right now IMHO.
No functional changes.
Any background context you want to provide?
The Documentation contains Jupyter Notebooks that walk users through the creation of a BSync XML using bsyncpy.
The existing example of a L100 audit in a DOE Prototype small office building was expanded to include a L200 audit of the same building, and both a L100 and L200 audit of the DOE Prototype primary school building.
What does this PR do?
It adds the L100 and L200 examples for the DOE Prototype primary school building
How should this be manually tested?
Review the notebook. Generate the two .xml files. Replace the XML headers to specify the correct namespaces. Upload them to the Schema Validator.
What are the relevant tickets?
Reference implementations of 2 DOE prototype buildings in BuildingSync 2.4
Screenshots (if appropriate)