Skip to content

Evaluating on second GPU gives weird numbers after some number of evaluations #13

Description

@Alexsp32

Example: GPU 0

Example: GPU 0

Example: GPU 1

Example: GPU 1

Energies and forces evaluated by MACEModels eventually become garbage values after some number of structure evaluations.

This is probably not related to using PythonCall/PyCall, nor to premature garbage collection due to multithreading. (Tested both)

MACE doesn't offer support for running on a specific GPU by default, and now I think I know why.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions