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

MOPAC force runs: normal modes are stored in MOPAC's reoriented frame, the structure in the input frame

未关闭
#369 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
c
领域
data

调研方向

Start with scripts/parsers/mopac.desc and the MOPAC FORCE output section labeled “ORIENTATION OF MOLECULE IN FORCE CALCULATION”; compare the stored geometry and normal modes in the ch4_force, ch4_geovib, and ch4_force_nothermo fixtures. Adjust the vibration-step data so the geometry and modes share a frame, then check Builder arrows for CH4, H2O, and NH3 MOPAC runs against other codes.

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

描述

A MOPAC FORCE calculation reorients the molecule ("ORIENTATION OF MOLECULE IN FORCE CALCULATION") and prints its normal modes in that frame, while [GEOMTRACE] in scripts/parsers/mopac.desc stores the input-orientation geometry. The modes ECCE stores therefore belong to a different orientation than the structure they are drawn on.

Found while implementing #367: for CH4 in all three MOPAC fixtures (ch4_force, ch4_geovib, ch4_force_nothermo) the stored modes are not orthogonal to the stored structure's rotations. With the force-orientation geometry the mode symmetries come out right (E, T2, T2, A1, equal to MOPAC's own labels).

Likely effect: the displacement arrows and animation of a MOPAC vibration in the Builder point in the wrong directions (not yet checked by eye). The vibrations table shows MOPAC's own symmetry labels and no Mode description for these runs: #367's analysis detects the mismatch and refuses rather than guess.

Fix: store the geometry the modes belong to, i.e. read MOPAC's force-calculation orientation for the vibration step, or rotate the modes back into the input frame. Then check the Builder's arrows for CH4, H2O and NH3 MOPAC runs against the other codes'.

主要语言
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 摘要。