Skip to content

Coexistence of multiple CUTEst models #440

Open
@amontoison

Description

@amontoison

Each CUTEstModel is, in theory, independent, and we can create as many models as we want; however, there is a corner case.
If all CUTEstModel instances are based on different problems, this is not an issue.
If all CUTEstModel instances are based on the same problem but with different precisions, this is not an issue either.
However, if we have CUTEstModel instances for the same problem and precision, but with variable parameters (such as size), we encounter an issue.

This is because the shared library generated after decoding the problem is suffixed only with the name of the problem and its precision.
The user must define the names of the decoded SIF files and shared libraries so that they do not conflict.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions