Conversation
Co-authored-by: Sam Wolk <szvsw@users.noreply.github.com>
Co-authored-by: Sam Wolk <szvsw@users.noreply.github.com>
|
Cursor Agent can help with this pull request. Just |
|
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #60 +/- ##
=======================================
+ Coverage 63.3% 66.8% +3.4%
=======================================
Files 34 42 +8
Lines 4907 5472 +565
Branches 443 495 +52
=======================================
+ Hits 3110 3656 +546
Misses 1651 1651
- Partials 146 165 +19 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Co-authored-by: Sam Wolk <szvsw@users.noreply.github.com>
Co-authored-by: Sam Wolk <szvsw@users.noreply.github.com>
Co-authored-by: Sam Wolk <szvsw@users.noreply.github.com>
Co-authored-by: Sam Wolk <szvsw@users.noreply.github.com>
Co-authored-by: Sam Wolk <szvsw@users.noreply.github.com>
Co-authored-by: Sam Wolk <szvsw@users.noreply.github.com>
Co-authored-by: Sam Wolk <szvsw@users.noreply.github.com>
Co-authored-by: Sam Wolk <szvsw@users.noreply.github.com>
Co-authored-by: Sam Wolk <szvsw@users.noreply.github.com>
| EnvelopeAssemblyComponent, | ||
| ) | ||
| from epinterface.sbem.flat_constructions.materials import ( | ||
| CEMENT_MORTAR, |
There was a problem hiding this comment.
I wonder if the materials and their quantities can still be part of the configurations an inputs as well, unless we are collectively exhaustive here
There was a problem hiding this comment.
Part of the goal is for the abstraction to be sufficient that users are not defining materials, only assemblies of materials. And yes, there should be sufficient options in the library to express what is needed. I think that there are probably sufficient options in there now, but we can add more on an as needed basis.
|
|
||
|
|
||
| def build_partition_assembly( | ||
| *, name: str = "Partition" |
There was a problem hiding this comment.
I think this needs to be more flexible/handle the boundaries of E+ constructions / what is possible to model in E+. I can test the boundaries a bit!
There was a problem hiding this comment.
Not sure I follow here. currently the assumption is that (a) partition construction does not really matter for the most part and (b) it's fine to use a uniform partition for all buildings.
| for structural_system, template in WALL_STRUCTURAL_TEMPLATES.items(): | ||
| if template.supports_cavity_insulation and template.cavity_depth_m is not None: | ||
| max_cavity_r = template.cavity_depth_m / FIBERGLASS_BATTS.Conductivity | ||
| audit_cavity_r = min(2.0, max_cavity_r * 0.9) |
There was a problem hiding this comment.
where does the 0.9 come from?
There was a problem hiding this comment.
The goal of this test is really to check that the entire assembly comes out reasonably when a reasonable set of user inputs for e.g. cavity insulation, external insulation etc are used; as such, we need to make some sort of choice as to what the user might set for the cavity insulation; for now, it says : "We won't go above RSI-2/R10ish, but otherwise, let's set it to 90% of what the maximum nominal r-value that the cavity could support would be. In other words, if it's 2x4 studs, then the cavity depth is something like 3.x" and so we would use 0.9 * 3.x" of insulation in this test. We could do multiple tests in fact using several different cavity insulation levels; for now though it is just doing one. The goal here is not to test the behavior when the user provides extreme values in excess of what the cavity supports - instead we are trying to test that what we think should be a reasonable layup is in fact a reasonable layup.
Add a semi-flat wall construction representation for improved expressivity and ML-friendly feature generation.