Skip to content

EoS fitting routines don't fail gracefully #474

@bobmyhill

Description

@bobmyhill

It's really common for there to be insufficient data to constrain an EoS. In such circumstances, lsq procedures drive the parameters outside the range of validity of the EoS and some bit of the EoS fails (often due to very low K').

BurnMan should deal with this more gracefully than it currently does. To do: add try/except to the PTp and XPTp functions in eos_fitting to catch exceptions and print a better message

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