Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixing NNPInput to allow us to write torch script models #295

Merged
merged 5 commits into from
Oct 22, 2024

Commits on Oct 21, 2024

  1. Making NNPInput is imported directly from modelforge.utils.prop (it w…

    …as imported into dataset.__init__.py and then being imported from dataset in several place which could be confusing)
    chrisiacovella committed Oct 21, 2024
    Configuration menu
    Copy the full SHA
    2a9eb88 View commit details
    Browse the repository at this point in the history

Commits on Oct 22, 2024

  1. to allow for us to export torchscript to file, we cannot use None in …

    …NNPInput. This revises NNPInput and changes the logic used to check if, e.g., pair_list data has been precomputed in the neighborlist for training.
    chrisiacovella committed Oct 22, 2024
    Configuration menu
    Copy the full SHA
    b15aa82 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    8beae3b View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    7a9f6f4 View commit details
    Browse the repository at this point in the history
  4. fix one test that seemed to have been rolled back or missed in terms …

    …of writing to a temp dir, not test dir.
    chrisiacovella committed Oct 22, 2024
    Configuration menu
    Copy the full SHA
    9b51137 View commit details
    Browse the repository at this point in the history