We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I think Scalar(1, "m") should compare equal to Scalar(100, "cm"). This would allow us to write more natural code like:
Scalar(1, "m")
Scalar(100, "cm")
if current_tubing_end <= current_open_hole_position:
Instead of being forced to write:
if current_tubing_end.GetValue('m') <= current_open_hole_position.GetValue('m'):
pint works this way:
>>> import pint >>> ureg = pint.UnitRegistry() >>> 1* ureg.meter == 100 * ureg.centimeter True
From this discussion: https://eden.esss.com.br/stash/projects/ESSS/repos/alfasim/pull-requests/1690/overview?commentId=120265
The text was updated successfully, but these errors were encountered:
Another annoying side-effect:
>>> {Scalar(1,'m'), Scalar(100, 'cm')} {Scalar(1.0, 'm', 'length'), Scalar(100.0, 'cm', 'length')}
This should have returned:
>>> {Scalar(1,'m'), Scalar(100, 'cm')} {Scalar(1.0, 'm', 'length')}
Sorry, something went wrong.
and
>>> {Scalar(100, 'cm'), Scalar(1,'m')} {Scalar(100.0, 'cm', 'length')} >>> {Scalar(100.0, 'cm', 'length')} == {Scalar(1.0, 'm', 'length')} True
?
This will make the scalar hash being a bit slower.
Successfully merging a pull request may close this issue.
I think
Scalar(1, "m")
should compare equal toScalar(100, "cm")
. This would allow us to write more natural code like:Instead of being forced to write:
pint works this way:
From this discussion: https://eden.esss.com.br/stash/projects/ESSS/repos/alfasim/pull-requests/1690/overview?commentId=120265
The text was updated successfully, but these errors were encountered: