Skip to content

Potential licensing constraints when using PyPrimeMesh in another tool #1014

@germa89

Description

@germa89

Hi Mike, thanks again for the quick and helpful reply.

We’ve been looking into PyPrimeMesh, and it definitely seems promising. That said, we’re a bit concerned about potential licensing constraints, especially when it comes to using PyPrimeMesh inside a project like ours.

Specifically, we're building a lightweight FEA automation tool aimed at students and small teams. We'd love to use PyPrimeMesh for .cdb generation, but we’re unsure if it’s intended to be used only within the full Ansys ecosystem, or if there’s any way to use it externally (e.g., as part of a standalone conversion script) without running into redistribution or commercial usage issues.

Would you happen to know how Ansys handles this, or if there’s any flexibility for tools like ours?

Originally posted by @AltoAuto in ansys/pymapdl#3888 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions