Repository navigation
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1071 +/- ##
==========================================
+ Coverage 67.09% 67.12% +0.02%
==========================================
Files 123 123
Lines 43675 43691 +16
Branches 11153 11156 +3
==========================================
+ Hits 29303 29326 +23
+ Misses 11223 11221 -2
+ Partials 3149 3144 -5
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
The fit can still abort when frequency outputs are missing or all ZPE values are unavailable, causing FileNotFoundError or ZeroDivisionError instead of handling an unsuccessful fit.
2 open issues
What changed in this PR
This PR enables frequency scale-factor fitting for ASE levels by recognizing renamed YAML outputs and deriving zero-point energies from their frequencies.
Changes:
- Detect ARC YAML outputs by content and compute missing harmonic ZPEs from positive frequencies.
- Handle missing parsed ZPE values and correct the species error message.
- Standardize ASE Hessian output to Hartree/Ų and add regression tests.
| File | Description |
|---|---|
arc/utils/scale.py |
Preserve unavailable ZPEs as None and fix error-message formatting. |
arc/parser/parser.py |
Recognize ARC YAML output regardless of extension. |
arc/parser/parser_test.py |
Test YAML detection and frequency-derived ZPEs. |
arc/parser/adapters/yaml.py |
Compute harmonic ZPE when no stored value exists. |
arc/job/adapters/scripts/ase_script.py |
Convert returned Hessians to Hartree/Ų. |
arc/job/adapters/ase_test.py |
Verify returned Hessian units against ORCA data. |
Review effort: Balanced
Comment on lines
+111
to
+113
| zpe = parse_zpe_correction(os.path.join(project_directory, 'output', 'Species', spc.label, | ||
| 'geometry', 'freq.out')) | ||
| zpe_dict[spc.label] = zpe * 1000 if zpe is not None else None # convert to J/mol |
| 'geometry', 'freq.out')) * 1000 # convert to J/mol | ||
| zpe = parse_zpe_correction(os.path.join(project_directory, 'output', 'Species', spc.label, | ||
| 'geometry', 'freq.out')) | ||
| zpe_dict[spc.label] = zpe * 1000 if zpe is not None else None # convert to J/mol |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

What
With an ASE level (e.g., UMA) and no
freq_scale_factor, ARC runs its 15-species scale-factor project. Every job finishes, but the fit then crashes:ARC copies an ASE job's
output.ymltogeometry/freq.out.determine_ess()recognized YAML only by its.ymlextension, andYAMLParser.parse_zpe_correction()returned a ZPE only if one was stored, which ASE outputs don't do. Any parse of an ASE job'sfreq.outfailed the same way, not just the ZPE.Changes
determine_ess()recognizes ARC's YAML output by its content when no ESS marker matches (is_arc_yaml_output()).YAMLParser.parse_zpe_correction()computes the harmonic ZPE from the frequencies,sum(h·c·ν)/2over the real ones (imaginary ones excluded, as an ESS does). A storedzpestill takes precedence.scale.py:fprefix.ase_script.py: it wrote the Hessian in eV/Ų for UMA and finite-difference frequencies, but in Hartree/Ų for TorchANI (torchani.unitsworks in Hartree). It now writes Hartree/Ų for every calculator. Frequencies were in cm⁻¹ either way and are unchanged. Nothing in ARC reads this Hessian today:parser_evidencetakes Hessians only from Gaussian and ORCA.Checks
scale.pyto 0–6% for 14 of the 15 species. F₂ is the outlier at +21%.Tests
test_determine_ess_recognizes_arc_yaml_output_by_content: an ASEoutput.ymlcopied tofreq.outis read as YAML, and an unrelated YAML mapping is not.test_parse_zpe_correction_from_yaml_frequencies: the ZPE is the harmonic sum, an imaginary frequency doesn't count, and a stored ZPE takes precedence.test_numpy_vibrational_analysis: the returned Hessian is in Hartree/Ų, checked against an ORCA Hessian.arc/parser,ase_test.py,scale_test.py,parser_evidence_test.pyandscheduler_test.pypass: 396 tests, run serially.