1) TEA (CAPE-OPEN 1.1) is configured as the Property Package Manager. The capeOpenFlashPropList function lists the extensive properties of "enthalpyF" and "gibbsEnergy" for the property package used.
In the code with the error,The first function successfully used gibbsEnergy, a valid propNames argument, with the capeOpenEquilibriumProp function. The second function fails to use propNames as prop1 for the capeOpenEquilibrium function. The problem as defined is that the functions work for enthalpyF, code section with No error, but not for gibbsEnergy, code section with Error.
If gibbsEnergy is not supported, then why is it listed for TEA (CAPE-OPEN 1.1)? Question: How does one check version 1.1 packages for supported extensive properties?
Since the capeOpenFlashPropList function calls the handle of the property package used, why is the returned list of properties not specific to that package? Why not call an empty function parameter list, e.g., functionList(), instead if the list is not relevant to the specified package handle? Then what use is the returned list?
2) The Example for capeOpenEquilibriumProp shows '0' in the parameter list for type. This statement is not true. The type parameter is optional so it was omitted from the parameter list of the example. The '0' appeared as the value of prop2, val2,--"vaporFraction",0), not as the value of type. The example is correct as written.Statistics: Posted by nrgeng — 23 January 2018, 22:09
]]>