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
and then Energy uses those values as lower_frequency.to(units.m).value when sending to the service.
If a value (rather than a Quantity) is sent to Energy (ie no units) then Energy can assume they are in m or through an error, but for backwards friendly it should accept this as unit.m by default and cast the value to a unit.m Quantity
The text was updated successfully, but these errors were encountered:
Making use of astropy.units would add tremendous power to caom2
this extra power is worth the burden of astropy as a dependency (it already is anyhow, implicitly)
caom2.plane.Energy(bounds=[lower_frequencyunits.GHz, upper_frequencyunits.GHz])
and then Energy uses those values as lower_frequency.to(units.m).value when sending to the service.
If a value (rather than a Quantity) is sent to Energy (ie no units) then Energy can assume they are in m or through an error, but for backwards friendly it should accept this as unit.m by default and cast the value to a unit.m Quantity
The text was updated successfully, but these errors were encountered: