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
Hello,
In some situations, units should not cancel out in division. For example, soil erodibility is measured in t * ha * hr / (ha * MJ * mm). By convention the hectares are left on the top and bottom, to emphasize that it measures soil loss (in t) per unit area (in ha) per unit of storm erosivity (in MJ * mm / (ha * hr)).
The option to instantiate a pint.Unit that evaluates without canceling would be useful in this situation. Something like:
I would love to make tons of things non-cancellable. When computing emissions intensity, it would be great if t CO2 / t Steel did not cancel to CO2 / Steel. PLEASE!
I'm more than OK when t CO2 / t CO2 becomes dimensionless. It's just when substances are different I don't want the mass unit to disappear.
Hello,
In some situations, units should not cancel out in division. For example, soil erodibility is measured in
t * ha * hr / (ha * MJ * mm)
. By convention the hectares are left on the top and bottom, to emphasize that it measures soil loss (int
) per unit area (inha
) per unit of storm erosivity (inMJ * mm / (ha * hr)
).The option to instantiate a
pint.Unit
that evaluates without canceling would be useful in this situation. Something like:The text was updated successfully, but these errors were encountered: