Our college days have taught us that there is a difference between 'accurate' and 'precise'.
OffTopic#2 [But not way off since the following relates to both one of the 7 units of measure and NIST]:
The US Department of Commerce's National Institute of Standards and Technology (NIST) [has] launched the new atomic clock, called NIST-F2, to serve as a new US civilian time and frequency standard, along with the current NIST-F1 standard. NIST-F2 would neither gain nor lose one second in about 300 million years, making it about three times as accurate as NIST-F1, which has served as the standard since 1999, NIST said. NIST-F2 is now the world's most accurate time standard, NIST said in a statement. For now, NIST plans to simultaneously operate both NIST-F1 and NIST-F2.
"If we've learned anything in the last 60 years of building atomic clocks, we've learned that every time we build a better clock, somebody comes up with a use for it that you couldn't have foreseen," said NIST physicist Steven Jefferts, lead designer of NIST-F2.
Both clocks use a "fountain" of cesium atoms to determine the exact length of a second. Both NIST-F1 and NIST-F2 measure the frequency of a particular transition in the cesium atom - which is 9,192,631,770 vibrations per second, and is used to define the second, the international (SI) unit of time.
The reason why "kilogram" is the name of a base unit of the SI is an artefact of history.
Louis XVI charged a group of savants to develop a new system of measurement. Their work laid the foundation for the "decimal metric system", which has evolved into the modern SI. The original idea of the king's commission (which included such notables as Lavoisier) was to create a unit of mass that would be known as the "grave". By definition it would be the mass of a litre of water at the ice point (i.e. essentially1 kg). The definition was to be embodied in an artefact mass standard.
After the Revolution, the new Republican government took over the idea of the metric system but made some significant changes. For example, since many mass measurements of the time concerned masses much smaller than the kilogram, they decided that the unit of mass should be the "gramme". However, since a one-gramme standard would have been difficult to use as well as to establish, they also decided that the new definition should be embodied in a one-kilogramme artefact. This artefact became known as the "kilogram of the archives". By 1875 the unit of mass had been redefined as the "kilogram", embodied by a new artefact whose mass was essentially the same as the kilogram of the archives.
The decision of the Republican government may have been politically motivated; after all, these were the same people who condemned Lavoisier to the guillotine. In any case, we are now stuck with the infelicity of a base unit whose name has a "prefix".
OffTopic >> Thank you for the link but I find it quite odd that NIST (old NBS) calls out the unit of mass as being the Kilogram (kg) rather than a gram (g).
Wikipedia provides the following historical perspective:
In 1921 the Convention of the Metre was revised and the mandate of the CGPM (Conférence générale des poids et mesures) was extended to provide standards for all units of measure, not just mass and length. In the ensuing years the CGPM took on responsibility for providing standards of electric current (1946), luminosity (1946), temperature (1948), time (1956) and molar mass (1971). Those are not too far away in the rear view mirror!
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.