-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Modifying Variables" section has inconsistencies #22
Comments
Good point. I'll make this more consistent. |
This may be related to #17... Perhaps allowing suffixes while some parameter names already include the suffixes (e.g. |
What do you think about this slightly changed order of modifications: -- For example, one application might be to compare simulated and measured maximum-power-point power. In this case, the base variable pmp can be modified into pmp_sim and pmp_meas. In order to standardize some common naming modifications, we have chosen a common order.
For simplicity, it is not necessary to use all modifications for a particular variable. Some examples:
|
I think this is now consistent. From a parsing perspective, it may be simpler to always have |
My idea was to place |
The Modifying Variables section of the docs (https://duramat.github.io/pv-terms/guide.html ) has some inconsistencies. The way in which to apply the preferred order is not clear. For example,
temperature_module_12
andtemperature_module_meas
appear to apply the preferences in opposite order.The text was updated successfully, but these errors were encountered: