-
Notifications
You must be signed in to change notification settings - Fork 1.1k
clarify units for U1 and Uv temperature model coeff #960
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
Conversation
* closes pvlib#945 * group denominator together, same way it was done for U0 and Uc, ie: `W/(m^2 C)` instead of `(W/m^2 C)` which is ambiguous because it could mean `W/m^2 * C = W * C / m^2` which is not the same thing * add missing division symbol before 2nd denominator `(m/s)` to get `W / (m^2 C) / (m/s)` instead of `(W/m^2 C) (m/s)` which looks like `WmC/ (m^2 s)` so it's ambiguous * pvsyst help docs (https://www.pvsyst.com/help/thermal_loss.htm) say `W/m²·k / m/s` which is also ambiguous but you can't win em all
Everywhere? what about units that are simpler to parse? Probably best to be consistent, right? pvlib-python/pvlib/temperature.py Line 46 in 3ce8e1a
I'm okay with making the shift to use |
Perhaps in the few instances where the unit involves a compound fraction. I'm -1 for using :math: for units otherwise. |
Could we do:
This would be more easily associated with the variables going in. |
I'm fine with
which looks like this: But this makes me wonder if the What do y'all think? |
Also should we be using Kelvin instead of Celsius? |
Sure, but I'd also be ok with the plain text: |
+1 |
* update what's new for v0.8.0 * use textrm for units Signed-off-by: Mark Mikofski <[email protected]>
sorry stickler but inline math don't render if it's on two lines 😕 |
What do you think @CameronTStark? Is this good? |
LGTM @mikofski, thanks! |
W/(m^2 C)
instead of(W/m^2 C)
which is ambiguous because it could meanW/m^2 * C = W * C / m^2
which is not the same thing(m/s)
to getW / (m^2 C) / (m/s)
instead of(W/m^2 C) (m/s)
which looks likeWmC/ (m^2 s)
so it's ambiguousW/m²·k / m/s
which is also ambiguous but you can't win em allTests addedUpdates entries todocs/sphinx/source/api.rst
for API changes.docs/sphinx/source/whatsnew
for all changes. Includes link to the GitHub Issue with:issue:`num`
or this Pull Request with:pull:`num`
. Includes contributor name and/or GitHub username (link with:ghuser:`user`
).New code is fully documented. Includes numpydoc compliant docstrings, examples, and comments where necessary.