My apologies if this is not the right place for these questions.
Does your program provide "under-constrained", "fully-constrained" and "over-constrained" feedback?
If so what technique/algorithm is used to determine those conditions?
Thanks.
I have pushed some cosmetic self() to getHandle() renaming for coherence, but you may have to rebase before pushing or there is chance the repo does not compile (if you used self() in the meantime).DeepSOIC wrote:...
No, not yet. That's what that scary diagnose does. It's not yet implemented in ConstraintSolver.Mark Szlazak wrote: ↑Wed Mar 25, 2020 3:17 pmDoes your program provide "under-constrained", "fully-constrained" and "over-constrained" feedback?
If so what technique/algorithm is used to determine those conditions?
There are some requirements:Mark Szlazak wrote: ↑Wed Mar 25, 2020 3:17 pmMy apologies if this is not the right place for these questions.
Does your program provide "under-constrained", "fully-constrained" and "over-constrained" feedback?
If so what technique/algorithm is used to determine those conditions?
Thanks.
I know DeepSonic has been re-implementing things with (dual?) quaternions and i got interested in them with regards to screw-displacement theory. I do not know if that is the direction this could evolve with regards to 3d-constrains in sketches and assemblies. In any case, i found a paper on this topic of screw-theory and reciprocal screws but not in terms of quaternions. I suspect it could be modified for quaternions. It does claim very fast real-time constraint evaluation (under, over, full).
ConstraintSolver has nothing to do with screw theory right now. I was using something from it to implement placement interpolation (SCLERP) in FreeCAD.