Open pattacini opened 1 year ago
Hi @Nicogene @mfussi66
We may consider accounting for a MVP-4.5 for:
What do you think?
cc @traversaro
Cool, thanks a lot to everyone!
Beta testing. We need to identify a bunch of testers.
To suggest someone: iRonCub mech team has been historically a long time user of simmechanics-to-urdf, I guess they may be interested in trying creo2urdf, probably we can ask to Gabriele Nava.
@Nicogene @mfussi66 @traversaro
I've just created the MVP-4.5 epic (ETA PI17) for dealing with beta testing and dissemination.
See #50 for tracking the potential activities of the iRonCub team as beta tester.
Background & Objectives
Motivated by the fact that our present pipeline for generating URDF models from CREO is broken due to an incompatibility between CREO v9 and MATLAB[^1], we decided to aim to export models bypassing the use of MATLAB and rely directly on CREO native API.
There are three essential reasons underlying this approach:
[^1]: For the time being, we're getting away with a workaround based on exporting mechanisms from CREO v9 to CREO v7 in order to be able to use the current workflow.
Outcomes
Eventually, we will deliver a SW component capable of interfacing with CREO through its native API with the goal of exporting all the necessary information to fill in a URDF model and formatted in the required files (e.g. XML, STL...).
Task Breakdown
From our preliminary brainstorming, it came out that we will tackle the feat with the following incremental deliveries.
✅ MVP-1 – ETA PI14
✅ MVP-2 – ETA PI15
✅ MVP-2.5 – ETA PI15
✅ MVP-3 – ETA PI15
✅ MVP-4 – ETA PI16
✅ MVP-4.5 – ETA PI17
⚙️ MVP-5 – ETA PI18
This is the entry-point Epic to the whole project and serves as an architectural decision record (ADR).
cc @Nicogene @mfussi66 @fiorisi @traversaro @salvi-mattia @Mick3Lozzo @maggia80 @Lawproto