A separate ESYS-Particle xml element is needed #223
Labels
bug
third party
Related to third party software
watch out!
Things to watch out for (bug/non-bug weird behavior)
Milestone
Problem
Because of my lazy naming, we ended up with a
<RemoteForceInterface>
element which both runs the Remote Force Interface (RFI) and executes (or connects to) ESYS-Particle code. This naming doesn't make sens and has to be changed.Proposed solution
Separate elements should be available. The
<RemoteForceInterface integrator="...">
should run RFI and connect to a selected integrator. A separate<ESYSParticle>
element should run the ESYS-Particle code, and there should be different elements for other DEM codes (LAMMPS in near future).Comments
This change is not backwards compatible. Old xml files involving RemoteForceInterface would have to be changed.
The text was updated successfully, but these errors were encountered: