As part of my PhD dissertation, I wrote an "interval valued" constraint solver and a Python internal DSL based originally on miniKanren, that ran it. The inter

As part of my PhD dissertation, I wrote an "interval valued" constraint solver and a Python internal DSL based originally on miniKanren, that ran it. The intervals handle the floating point in interval chunks, allowing for set-like reasoning and relational constraint programming atop floating point. I used it to operate on a design space as a single entity, or sliced into finite chunks, and to cut out sub-spaces of infeasible designs by constraint propagation. I think interval valued relational constraint programming could be extended (and probably already has) for mechanical modeling, and 3D animation, yes. But the utility of a purely discrete constraint solver, such as the one posted here, is maybe less for these types of cases. Interval systems methods (for solving nonlinear equations) have a long history in optimization and motion planning. No reason a constraint solver couldn't be applied there. Similarly, if you have a specific use case, I could try and offer more about constraint solving for it. I should also note that constraint solving with real or and especially interval data goes back to at least the 80s. I just made use of some low hanging fruit!