MOPAC force runs: normal modes are stored in MOPAC's reoriented frame, the structure in the input frame
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
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.
Written by the indexing model from the issue text.
Description
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'.
- Dominant language
- C
- Stars
- 10
- Forks
- 8
- Avg merge
- 21m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from FriendsofECCE/ECCE
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
FriendsofECCE/ECCE#336 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
FriendsofECCE/ECCE#370 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
FriendsofECCE/ECCE#368 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
FriendsofECCE/ECCE#367 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
FriendsofECCE/ECCE#366 ·
All issues in FriendsofECCE/ECCE
Similar issues
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 84/100
VirusTotal/yara#2255 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
neutralinojs/neutralinojs#1861 ·
Maintainers usually reply within 1 day
-
[BUG] Filename sequence expansion (`+`) panics on numeric values exceeding `i32::MAX`Possibly taken @muntasir-396 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
CCExtractor/ccextractor#2402 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
FujiNetWIFI/fujinet-lib#204 ·
Maintainers usually reply within 1 day
-
os:linux
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
mpv-player/mpv#18649 ·
Maintainers usually reply within 1 day