Feature Request
It would be desirable to support units across the board in the core framework. Unit support should be optional, not mandatory, and it should not affect the API, ie. should be in the style of gradual typing-ish, that if used as input, it should produce unit-aware results, but if not used, regular numeric results should be returned.
The data sub-system (encoders/decoders) should also be extended to support. Support for numpy data should also be included.
As a secondary feature, it would be ideal to support uncertainties when using values, e.g. 0.20+/-0.01.
The steps to tackle this would be to:
- Analyze the impact and reach of this change, potential side effects, etc.
- Draft a concrete proposal for technical implementation, potentially,
pint and uncertainties as concrete python packages to rely on for unit/uncertainty descriptors/calculation
- Draft diagrams if needed, and any other supporting documentation useful to decide on whether this change is green-light or not
After all these are sorted out, we can start a draft implementation.
Feature Request
It would be desirable to support units across the board in the core framework. Unit support should be optional, not mandatory, and it should not affect the API, ie. should be in the style of gradual typing-ish, that if used as input, it should produce unit-aware results, but if not used, regular numeric results should be returned.
The data sub-system (encoders/decoders) should also be extended to support. Support for numpy data should also be included.
As a secondary feature, it would be ideal to support uncertainties when using values, e.g.
0.20+/-0.01.The steps to tackle this would be to:
pintanduncertaintiesas concrete python packages to rely on for unit/uncertainty descriptors/calculationAfter all these are sorted out, we can start a draft implementation.