Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

GROMACS: MINFF mineral force field (structure → atom types/charges → MD)

未关闭
  • 哪里不对？
#241 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
python
领域
backend, databases

调研方向

Start by reviewing the existing GROMACS MD workflow in issue #106 and the MINFF/atomipy assignment workflow described here. The issue names no ECCE implementation files or tests; its proposed tests use kaolinite and montmorillonite from minff's Systems folder and compare against atomipy output, then run grompp and a short energy minimisation. Done means the full structure-to-assignment-to-simulation workflow works in ECCE, including reported charges and untyped atoms.

由索引模型根据 Issue 内容生成。

描述

Goal

Support the MINFF force field for minerals in ECCE's GROMACS workflow: clay minerals, oxides, hydroxides and zeolites, with Si, Al, Fe, Mg, Ca, Ti, Li and F. A user should be able to take a mineral unit cell, build a simulation cell from it, have MINFF atom types and charges assigned, and run energy minimisation, equilibration and dynamics, all from ECCE.

This builds on GROMACS activation via the MD workflow (#106, in progress on wip/gromacs-md).

What MINFF consists of

  • Parameters as a GROMACS force-field directory (min.ff):

    • a general set (GMINFF) and mineral-specific sets (TMINFF, over 30 minerals);
    • each set in four angle force constants (0, 250, 500 and 1500 kJ/mol/rad²);
    • oxygen Lennard-Jones parameters taken from the OPC3 water model by default.

  • Atom-type and charge assignment, which is structure-dependent:

    • types come from nearest neighbours;
    • oxygen charges are computed per system (charge smearing after Lammers et al. 2017), e.g. around isomorphic substitutions and edge groups.

    This is implemented in atomipy (Python, PyPI, MIT licence) and in the MATLAB/Octave atom library. ECCE therefore has to run the assignment rather than only ship parameter files.

  • Example systems (unit cells, conf.mdp, topol.top) in the minff repository.

Proposed workflow in ECCE

  1. Structure:
    • import a mineral unit cell (.pdb, .gro, CIF), with the cell vectors;
    • replicate it to a supercell (n_a × n_b × n_c);
    • optionally substitute atoms with a minimum separation (e.g. Al→Mg), as atomipy does.
  2. Force-field choice:
    • general or mineral-specific MINFF (mineral list taken from min.ff);
    • angle force constant;
    • water model.
  3. Assignment:
    • ECCE runs atomipy;
    • it writes the mineral .itp, the .gro and a topol.top that includes min.ff;
    • it reports the total charge and any atoms left untyped.
  4. Show the result:
    • atoms coloured by MINFF type;
    • charges available as a property.
  5. Simulation with the GROMACS MD tasks (#106): EM → NVT/NPT → MD, with .mdp presets derived from the minff example conf.mdp.
  6. Later:
    • solvation and counter-ions (hydrated clays, e.g. Na-montmorillonite);
    • analysis (#180).

Design rules

  • The topology builder is a wx-free component with a command-line entry point and tests. The ECCE windows only collect the choices and display results.
  • Tests: kaolinite and montmorillonite from the minff Systems folder are built with ECCE's builder. They are checked against topologies produced by atomipy run directly (atom types, charges, total charge), and then go through grompp and a short EM with real GROMACS.
  • Parameter files: min.ff is fetched from the minff repository at build/test time and not copied into this repository. It can be bundled once the minff repository carries a licence.
  • Platforms: Linux and macOS (Homebrew gromacs).

Open questions for GROMACS/MINFF users

  • Which minerals and systems should come first?
  • Is the general set with k = 500 the right default?
  • Should ECCE offer CLAYFF (also supported by atomipy) alongside MINFF?
  • Which .mdp settings should the presets use: cut-offs, PME, thermostat/barostat, semi-isotropic pressure coupling for clay layers?
主要语言
C
星标
10
派生
8
平均合并
21 分钟
30 天内合并 PR
1

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

FriendsofECCE/ECCE 的其他 Issue

查看 FriendsofECCE/ECCE 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。