Justin Gerber
Justin Gerber
This issue raises 2 issues. 1. Right now the changelog is only visible in the source code. We should make the changelog viewable in the online documentation. This is especially...
There has been considerable discussion about how comparisons operators should behave on `UFloat`. See #295 most recently. In that discussion it was agreed that `` should all be dropped for...
I came across this formatting bug "in the wild": ``` from uncertainties import ufloat from importlib import metadata print(f'version : {metadata.version("uncertainties")}') a = ufloat(9.994, 0.002)*1e-1 b = ufloat(9.997, 0.002)*1e-1 c...
This is a subtle problem that has been an Achilles heel of #262. On master branch we have ``` from uncertainties import ufloat zero = ufloat(0, 0) p = ufloat(0.3,...
The user guide already calls out this strange behavior ``` >>> a = ufloat(25, 10) >>> b = ufloat(25, 8) >>> a >= b False >>> a > b False...
A few ideas have been identified that would be useful helper functions we could consider adding to `uncertainties`. It may be appropriate to collect these helpers into a single module,...
- [x] Closes #99 - [x] Executed `pre-commit run --all-files` with no errors - [x] The change is fully covered by automated unit tests - [x] Documented in docs/ as...
#262 makes changes to the backend for some core functionality and also has some API changes. As a result it comes with decently large changes to the test suite. That...
Right now the `std_score` function raises a `ValueError` if it is called on an `AffineScalarFunc` with zero standard deviation. Should it return `nan`, possibly with a warning instead? https://github.com/lmfit/uncertainties/blob/969324dcbe01dc933888c2540f3b097c99b350f6/uncertainties/core.py#L591
In `3.x` the `AffineScalarFunc` class has two attributes that tell users about the contribution of other `Variable`s to the uncertainty: the `derivatives` property and the `error_component` method. ``` x =...