Skip to content

[Bug]: Invalid eigenvalues #317

Closed

Description

@ioanaapapa

Bug Report

When running a calculation with the current version of CodeEntropy on main, a lot of invalid eigenvalues are identified. This was not the case with an earlier version of CodeEntropy 2.1.1.


To Reproduce

YAML configuration

│ top_traj_file │ ['ramp2.prmtop', 'ramp2_1_500fr_imaged.nc']
│ force_file │ None │
│ file_format │ None │
│ kcal_force_units │ False │
│ selection_string │ all │
│ start │ 0 │
│ end │ -1 │
│ step │ 1 │
│ bin_width │ 30 │
│ temperature │ 298.0 │
│ verbose │ False │
│ grouping │ molecules │
│ combined_forcetorque │ False │
│ customised_axes │ False │
│ search_type │ RAD |

CLI command used

CodeEntropy --top_traj_file ramp2.prmtop ramp2_1_500fr_imaged.nc --combined_forcetorque False --customised_axes False --end -1

Actual output

program_output.txt

Expected output

Output was expected to be similar to that from a previous version, such as the one below.
program_output_prev.txt

Environment and Versions

Additional Context

Issue appears with flag --customised_axes set either True or False.

Activity

  1. jimboid commented on Apr 21, 2026

    @jimboid
    Member

    Thanks Ioana. @skfegan @harryswift01 we should check if this shows up in the systems used for testing and make sure we are testing for this. If it does not then we need to write a new set of tests to validate against this type of bug.

  2. skfegan commented on Apr 21, 2026

    @skfegan
    Member

    Does this also happen with combined_forcetorque set to True?

  3. ioanaapapa commented on Apr 21, 2026

    @ioanaapapa
    CollaboratorAuthor

    It still happens with combined_forcetorque True

    program_output.txt

  4. skfegan commented on Apr 22, 2026

    @skfegan
    Member

    @jimboid @harryswift01 The regression tests [frame-window case] will catch this if it comes back, but this bug crept in when I was changing the trajectory slicing which affected the conformational and orientational results, so the regression baselines were updated with the wrong vibrational results for cases with more than one frame.

  5. linked a pull request that will close this issueFixing #317 Invalid Eigenvalues #318on Apr 22, 2026
  6. added a commit that references this issue on Apr 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions