An AI diagnosis IDE for a very narrow Abaqus pain point
Jacobi-IDE aims to reduce pain when writing Abaqus Fortran subroutines. In Abaqus, UMAT handles mechanical material behavior, while UMATHT handles heat, , and related physics. These subroutines are used to simulate how materials fail under high or during manufacturing processes.
In practice, 80% to 90% of the work can go into making Abaqus CAE run a physics model that is already known on paper, or into finding the right subroutines and to use. A large amount of time also goes into reading .sta/.msg files to understand why a failed. General IDEs such as VS Code are built for software engineering, not computational physics or mechanics, so they may not explain why a run hit a error or warn that a fully damaged variable can lead to division by zero.
Silent mistakes can spread through the and make the physics wrong, including cases where the result still looks believable.
Key points
- Abaqus Fortran subroutine work can be slowed more by setup, , and than by the physics idea itself.
- The claimed time sink is large: 80% to 90% of effort can go into making Abaqus CAE behave as expected.
- Failed runs often require manual inspection of .sta/.msg files.
- General IDEs do not give enough help for computational physics and mechanics errors.
- Jacobi-IDE combines analytical tests and AI for this specialized workflow.