MINFF Prepare: gaps found rebuilding a real clay/ion/water system

未關閉
#363 4 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
55/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
c
領域
desktop, tooling

研究方向

Start with ECCE's Prepare editor and Run settings, then trace the genion options, MINFF ion-parameter selection, restraint generation, angle parameter handling, and vacuum-gap logic. The launch dialog's warning classification and harmless-warning display are a separate UI path. Reproduction uses a three-layer TMINFF Cu2+/water system; validate each gap against the rebuilt topology and step-0 energies.

由索引模型根據 Issue 內容生成。

描述

Rebuilding an existing MINFF system (three TMINFF layers, Cu2+ interlayer ions, water) through ECCE's Prepare editor and Run settings reproduced its topology atom for atom and its step-0 energies (9.3 work, wip/930-small). Remaining gaps:

  1. Thin interlayer water: genion fails with "No more replaceable solvent" for a 1.22 nm interlayer slab. Its default -rmin 0.6 leaves almost no replaceable water, and the Prepare editor does not expose it. Offer -rmin (or lower it automatically for thin slabs, with a warning).
  2. Ion parameter sets: ECCE writes OPC3_HFE_LM; the other common choice, OPC3_IOD_LM, cannot be selected.
  3. Position restraints without hydrogens: some MINFF workflows use -DPOSRES_noH; ECCE's min.itp has no such block.
  4. Angle equilibrium values: atomipy's equilibrium angles differ from an independently built topology by up to 0.53°, giving angle energy 1191 vs 1248 kJ/mol at step 0. Check which parameter version is right.
  5. Bare mineral cell: a cell needs about 0.3 nm of vacuum, or atomipy bonds the layer to its own periodic image. Warn, or add the gap automatically.
  6. Launch dialog: the launch check now classifies grompp warnings as harmless or stopping, but when it passes, the list of harmless warnings is not shown in the GUI; show it as information.
主要語言
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 摘要。