[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[UDUNITS #VLT-428101]: Passing in numbers as units strings has some odd effects

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [UDUNITS #VLT-428101]: Passing in numbers as units strings has some odd effects
  • Date: Fri, 30 Nov 2012 14:09:24 -0700
Jim,

> Fair enough.  We had this debate at the office, and I initially took
> your position here.  However, if I can't convert dimensionless units by
> offset as well it just feels weirdly incomplete.  I think it reduces the
> chances that someone would do this on purpose, and therefore it only
> serves as a trap for the unaware.
> 
> It may not be worth modifying your code over. I'm planning to modify
> mine to catch this case.

One could always use specifications like "1@10" or "1/10". They're well-defined 
and consistent with the dimensionless unit "1".

> Jim

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: VLT-428101
Department: Support UDUNITS
Priority: Normal
Status: Closed