You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When reading data into the primap2 interchange format rules are more lenient than for the native pm2 format, leading to errors on conversion from IF to native format. Examples:
Entity names can contain characters confusing pint (e.g. HFC-32, where the '-' is interpreted as 'minus')
More examples to be added
Describe the solution you'd like
Check for consistency with native format to make sure conversion is possible. Currently a validity check is only implemented for the native format.
Describe alternatives you've considered
Keep as is to have less restrictions int he interchange format.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When reading data into the primap2 interchange format rules are more lenient than for the native pm2 format, leading to errors on conversion from IF to native format. Examples:
Describe the solution you'd like
Check for consistency with native format to make sure conversion is possible. Currently a validity check is only implemented for the native format.
Describe alternatives you've considered
Keep as is to have less restrictions int he interchange format.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: