Closed MtoLStoN closed 10 months ago
Attention: 21 lines
in your changes are missing coverage. Please review.
Comparison is base (
305eb7a
) 69.81% compared to head (c8fafbb
) 69.79%.
Files | Patch % | Lines |
---|---|---|
test/test_write_turbomole.f90 | 56.09% | 0 Missing and 18 partials :warning: |
src/mctc/io/write/turbomole.f90 | 78.57% | 2 Missing and 1 partial :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
You are right, I thought about that too. However, there are a few additional things that differ between writing a normal coord and a coord file in angstrom form, other than just the conversion ($coord angs, and $lattice angs). This could be of course easily done with if clauses, but this would make the code a little bit harder to read. I therefore opted to do it this way in favor of code clarity.
But we can also do it with fewer lines, if you prefer that.
At the moment, mctc-lib allows reading of coord files in angstrom format (
$coord angs
), but can not write these files. With this PR, mctc-lib will write$coord angs
files if specified in the input.