Opened 6 years ago

Last modified 9 months ago

#178 assigned enhancement

How to deal with the frequent revisions of natural constants.

Reported by: Gunther Schadow Owned by: Governance/Process
Priority: minor Milestone: Version 2.2
Component: help Keywords:


Since UCUM was first published in 1997/1998, natural constants such as the Planck Constant were modified, and modified rather frequently.

1986 6.626 075 5(40) ×10−34 J.s
1998 6.626 068 76(52) ×10−34J.s
2002 6.626 0693(11) ×10−34 J.s
2006 6.626 068 96(33) ×10−34J.s
2010 6.626 069 57(29) ×10−34J.s
today 6.626 070 040(81) ×10−34J.s

And similar alterations happen to other constants.

The question becomes what UCUM should do about these alterations?

  1. Should we track them and maintain UCUM up to date?
  2. Should we change the values silently?
  3. Should we maintain the history of the prior values?
    • e.g., the prior values could be maintained by adding a year index to the unit symbol

The pros and cons of these decisions need to be considered.

  • if we update, then past conversions may no longer be the same, i.e., they may seem to be errors in numbers saved over time.
  • if we don't update, then those same "errors" persist undetected.
  • if we come up with something very complicated, such as indexing everything by version or year, etc. it just becomes hard for the users to deal with.

My proposal would be to just update these constants from time to time and not provide any special way of tracking them. If it turns out that only few of these constants change, we might preserve older versions with year subscript index.

Change History (2)

comment:1 Changed 4 years ago by Gunther Schadow

Milestone: Version 2.1Version 2.2

Ticket retargeted after milestone closed

comment:2 Changed 9 months ago by Brenée Mitchell

Component: help
Owner: set to Governance/Process
Status: newassigned
Note: See TracTickets for help on using tickets.