-
Notifications
You must be signed in to change notification settings - Fork 9
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
Added switch to replace simple pyramids and snouts with boxes and cyl… #66
base: master
Are you sure you want to change the base?
Conversation
This should not have any effect on reveal pipeline, since we already do this in CadRevealComposer |
Added missing box detection for facet groups. Tested on few thousand objects. Automated tests need to be written. Class needs some clean-up. Suggestion for shared algebra functions? Maybe it is time to move them in RvmSharp out of CadRevealComposer |
HDA: |
Investigating the failing builds on WS1611 its related to the uploader having issues. I'll revert the Uploading code to the slow and semi reliable variant. |
Yeah, they could to go into RvmSharp in my mind. Most of the Math/Algebra utils have test coverage already so the quality is OK, and it should be relatively easy to move them into RvmSharp afaik. |
Note: the PR is not tested by current build pipeline, since the feature is opt-in (either by -z|-optimize flag to RvmSharp.Exe or by passing options to RvmParser class). The benefit to CadRevealComposer is small (since CRC already do instancing on CRC's side), however it will reduce number of facetgroups considerably, that needs to go through facet group matcher. I can temporarily activate the code path in CRC to see the effect |
Timings for HDA: time increase is probably attributed to import analysis. NOTE: interesting to see -2 reduction in templates. That means that facet group matcher might not manage some corner cases. |
MEL before 19m12s |
…inders
This is Part 1, I am still working on tests for part 2 to cover all test cases and transforms.