Skip to content

Strange behavior when HMX.BNC file exceeds 1500 binary parameter sets #758

@ThukeS

Description

@ThukeS

I'm logging this issue simply to inform other users of this maximum number of parameter sets that your HMX.BNC file can have and still reliably load mixtures. I've read in documentation that there is a maximum of 40 permissible #MXM excess Helmholtz free energy functions possible before REFPROP's behavior gets funky; however, I wasn't aware of a max on binary parameter sets.

I've noticed that when you exceed 1500 sets, REFPROP may not effectively load certain binary parameter sets, both when you define new mixtures and attempt to SETMIX with MIX files. Programmatically I don't know at what stage this failure happens, but it happens both in the GUI and through the Python wrapper.

*As a related side note, I've noticed somewhat similar behavior, where REFPROP v10 will not load estimated parameters when a mixture includes a FLD file that has been developed by the user (a FLD file that does not come with REFPROP). For what it's worth, if the user updates the DLL files to the latest beta version, this is resolved. https://nist-srd.s3.amazonaws.com/SRD23/10.0.0.98/REFPROP.HTM

**I apologize for not providing specific examples of these behaviors as I haven't been able to replicate these without proprietary models. I just hope that this helps anyone else that experiences this issue.

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