I'm sure you still have loads to solve and a lot of quite human decisions to make (because bRep is one thing; contemporary CAD 'default solutions' strike me as likely to be full of human compromises), but I can see that having an LLM on the team to help with the maths must help.
Your performance table is treating brep-conformance like it's some kind of backend server that processes x requests per n seconds, but that's now how geometry kernels work. How does this enable faster/smoother workflow than solidcore? Can you demonstrate that with a side-by-side video? No one, not even people who work with CAD all day can understand any benefits this has from a table.
Most of springrep's lead comes from the scoring rules. Any operation that doesn't match springrep's API counts as a failure for the other kernels, even if the other kernels can combine operations to output the same result.
Also "no dependencies" isn't really a brag when Solidcore's only two dependencies are serde and thiserror. I'm sure the author had good intentions but this does seem like another case of marketing hype getting ahead of the real engineering.
Good callout, we don’t want to unfairly punish a kernel that supports an operation as two individual steps. However, it’s an explicit goal [1] that the adapter code isn’t acting as a compatibility layer that a user of the library wouldn’t get. As the suite evolves, we may add alternate operation types, in the case of chamfers being done differently for example.
> so I wrote
No you didn't, you asked an LLM to write it.
Anything that makes this better suited to designing robot parts than other CAD software?
Now this is a great application of an LLM.
I'm sure you still have loads to solve and a lot of quite human decisions to make (because bRep is one thing; contemporary CAD 'default solutions' strike me as likely to be full of human compromises), but I can see that having an LLM on the team to help with the maths must help.
Best of luck with it :-)
Thanks! This has been an exciting project so far, and lots more to come.
Why this instead of extending/supporting solidcore? (also in Rust)
https://github.com/tangency-labs/solidcore
Your performance table is treating brep-conformance like it's some kind of backend server that processes x requests per n seconds, but that's now how geometry kernels work. How does this enable faster/smoother workflow than solidcore? Can you demonstrate that with a side-by-side video? No one, not even people who work with CAD all day can understand any benefits this has from a table.
See their benchmark why. Solidcore fails much more tests and is dramatically slower.
https://springcraft-ai.github.io/brep-conformance/
Most of springrep's lead comes from the scoring rules. Any operation that doesn't match springrep's API counts as a failure for the other kernels, even if the other kernels can combine operations to output the same result.
Also "no dependencies" isn't really a brag when Solidcore's only two dependencies are serde and thiserror. I'm sure the author had good intentions but this does seem like another case of marketing hype getting ahead of the real engineering.
Good callout, we don’t want to unfairly punish a kernel that supports an operation as two individual steps. However, it’s an explicit goal [1] that the adapter code isn’t acting as a compatibility layer that a user of the library wouldn’t get. As the suite evolves, we may add alternate operation types, in the case of chamfers being done differently for example.
[1] https://springcraft-ai.github.io/brep-conformance/docs/#the-...
Differing philosophies - Solidcore is a rust port of C++ SMLib. In comparison, springrep is a bottom up Rust implementation of a new kernel.
When it comes to timing, we run extensive build steps and assembly checks on our designed parts for which speed is a real bottleneck.