Hi, I’m working on an early RFC-stage open-source CAE application-layer initiative.
The proposed first public MVP is MBD-first, and Chrono is one possible backend through a solver-adapter layer. The goal is not to replace Chrono, build a new MBD solver, or create a thin GUI wrapper around Chrono. The goal is to define a solver-independent application layer that could eventually connect CAD/geometry, assemblies, MBD, FEA, CFD-ready workflows, meshing, visualization, results, and automation. For the Chrono side, I’m trying to define the correct boundary between: - a solver-independent Core Model - an Application / Command Layer - a Chrono MBD Adapter - Simulation Cases - time-based Results - visualization / replay The key question I’d appreciate feedback on is: What is the biggest mistake to avoid when designing a solver-independent application model and adapter boundary around Chrono? Repository: https://github.com/Shlomo365/open-cae-application-layer Main RFC discussion: https://github.com/Shlomo365/open-cae-application-layer/discussions Thanks, Shlomo -- You received this message because you are subscribed to the Google Groups "ProjectChrono" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/projectchrono/b1f4a84e-17e6-4ae9-a35c-d220e03f731an%40googlegroups.com.
