-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Physical_Engine: Make physical surfaces return material and volume of all content #3008
Physical_Engine: Make physical surfaces return material and volume of all content #3008
Conversation
Method could potentially be versioned over to the methods in Matter_Engine, which does the same thing, but wanted to change as little across engines as possible.
…f method Method could potentially be versioned over to the methods in Matter_Engine, which does the same thing, but wanted to change as little across engines as possible.
@enarhi if you want this to make the Beta, we need it reviewed kind of ASAP. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, tested test file along with a few other use cases and results are consistent and as expected per compliance with other similar calc methods.
@BHoMBot check compliance |
@IsakNaslundBh to confirm, the following actions are now queued:
There are 69 requests in the queue ahead of you. |
The check |
@BHoMBot check compliance |
@IsakNaslundBh to confirm, the following actions are now queued:
There are 4 requests in the queue ahead of you. |
@enarhi had some silly description mistakes I had to fix. Do you mind re-approving? |
@IsakNaslundBh to confirm, the following actions are now queued:
There are 4 requests in the queue ahead of you. |
The check |
The check |
Please be advised that the check with reference 11883804830 has more than 50 annotations of notes. API limitations restrict annotations to 50. You may need to rerun this check to obtain the next set when you make changes. At the time of reporting this check, there are 70 additional annotations waiting, made up of 70 errors and 0 warnings. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, functionality all there as expected as per previous review.
@FraserGreenroyd to confirm, the following actions are now queued:
There are 5 requests in the queue ahead of you. |
@BHoMBot check unit-tests |
1 similar comment
@BHoMBot check unit-tests |
@FraserGreenroyd to confirm, the following actions are now queued:
|
@BHoMBot check compliance |
@FraserGreenroyd to confirm, the following actions are now queued:
There are 40 requests in the queue ahead of you. |
@FraserGreenroyd to confirm, the following actions are now queued:
There are 2 requests in the queue ahead of you. |
@BHoMBot check installer |
1 similar comment
@BHoMBot check installer |
@IsakNaslundBh to confirm, the following actions are now queued:
There are 7 requests in the queue ahead of you. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Last commit is minor and not sufficiently changes @enarhi review following bot reports to reapproving for merge.
@BHoMBot check ready-to-merge |
@IsakNaslundBh to confirm, the following actions are now queued:
There are 4 requests in the queue ahead of you. |
Issues addressed by this PR
Closes #2895
Updates so that Physical ISurface objects account for inner opening type objects, such as doors and walls, for computation of SolidVolume as well as MaterialComposition.
Important that this is changing behaviour, and would impact workflows like LCA, but should be to the better. Important that people using the tools are aware of this. @enarhi when review/merged would you be able to help spread this?
Also, smaller change, is I removed all errors/warnings regarding Void type openings, as imo, it is safe to simply return 0 volume/empty material composition for this type of object, given it by definition is meant to model nothingness.
Test files
Testfile from issue:
Test File
Also good ofc if this can be tested through a few cases.
Changelog
Additional comments