Description:
As part of the v0.4.0 initiative for Data Sovereignty, dreid-forge will no longer be responsible for generating simulation-specific input files (e.g., LAMMPS data/input scripts). Instead, the engine will focus solely on producing standardized, rigorous physical descriptions of the system (topology + parameters) via the new ISO-compliant dreid-io formats.
This architectural shift decouples the parameterization logic from execution engines, ensuring that dreid-forge remains a pure physics engine. Future conversion to LAMMPS, GROMACS, or OpenMM formats will be handled downstream by dedicated converters or the dreid-io library itself.
Tasks:
Description:
As part of the v0.4.0 initiative for Data Sovereignty,
dreid-forgewill no longer be responsible for generating simulation-specific input files (e.g., LAMMPS data/input scripts). Instead, the engine will focus solely on producing standardized, rigorous physical descriptions of the system (topology + parameters) via the new ISO-compliantdreid-ioformats.This architectural shift decouples the parameterization logic from execution engines, ensuring that
dreid-forgeremains a pure physics engine. Future conversion to LAMMPS, GROMACS, or OpenMM formats will be handled downstream by dedicated converters or thedreid-iolibrary itself.Tasks:
Phase 1: Code Removal
src/io/lammps/directory and all contained logic.mod lammps;fromsrc/io/mod.rs.lammpsfeature flags fromCargo.tomlif present.Phase 2: API Cleanup
src/lib.rsdocumentation to remove references to LAMMPS export capabilities.LammpsWriteror equivalent structs from the public API.Phase 3: Test Updates
cargo testpasses after removal.