-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
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
nephelometric turbidity units #220
Comments
Interesting stuff. I recently reckoned that you distinguish a solution from a suspension or emulsion by measuring turbidity (vs. clearness). Seems like it's actually a thing. What are the mathematic properties of these units that would allow them to be part of a system of units? This might actually bring up a more general consideration. It touches on "procedure defined units" but that is a term of jargon to begin with, because all units that are actually defined are necessarily defined by some procedure. I think what's going on here is that some phenomena we make accessible to measurement developing a comparable unit standard, are great, but they do not interact with other units in a system. I think this is where the crux really lies. You may be a unit, and that is great. But do you have any systematic relationships with other units that are not just intrinsic but extrinsically useful? By "just intrinsic" I mean of course to the extent that the new unit 's definition depends on standard units, it is systematically related. My example is always to measure hairfall as the mass of of hair falling off someone's head in a week. Those use "day" and "mg" units of measure. Sure, but the resulting unit cannot be used much in computing anything else with them. They are just there. And of course, someone could make a derived unit from it, but no derivation ever brings this unit back into contact with other units and kinds of quantities. It always produces more ideosyncratic kinds of quantities. I think this is a very fundamental property of systematic units, perhaps one can call those oddball unit "ideosyncratic" units. We need not deny that they are units, but they don't communicate outside of their own ideosyncratic lineage. |
How can I merge these 3 tickets so only one is left? This has been open for a long time. We were promised that somehow the new approach to everything would bring proposals forward faster. But it seems like there is no way to act on any of them. #246 badly needs some attention. |
I don't know of any way to formally merge Issues. |
https://en.wikipedia.org/wiki/Turbidity I would propose:
There is a remaining argument though where it is alleged that NPUs do not signify comparable results, in other words that the USEPA Method 180.1 does not lead to reproducible results? |
Good afternoon,
I concur with Gunther’s proposal.
Thanks,
Bill
***@***.***
From: Gunther Schadow ***@***.***>
Sent: Tuesday, July 25, 2023 4:25 PM
To: ucum-org/ucum ***@***.***>
Cc: Hess, William A ***@***.***>; Assign ***@***.***>
Subject: [EXTERNAL] Re: [ucum-org/ucum] nephelometric turbidity units (Issue #220)
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
https://en.wikipedia.org/wiki/Turbidity
I would propose:
* [FNU] - Formazin Nephelometric Units (FNU) from ISO 7027
* [NPU] - Nephelometric Turbidity Units (NTU) from USEPA Method 180.1<https://www.epa.gov/sites/default/files/2015-08/documents/method_180-1_1993.pdf>
* [JTU] - Apparently this is really old and unreliable
There is a remaining argument though where it is alleged that NPUs do not signify comparable results, in other words that the USEPA Method 180.1 does not lead to reproducible results?
—
Reply to this email directly, view it on GitHub<#220 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AY6AYAIV6HVY2LBZWWW4CDDXSATSDANCNFSM6AAAAAAQ3WIUCA>.
You are receiving this because you were assigned.Message ID: ***@***.******@***.***>>
|
Included in v2.2 release |
Issue migrated from trac ticket # 5822
component: organization | priority: minor | keywords: NTU
2022-06-07 20:46:00: william.hess@fda.hhs.gov created the issue
The text was updated successfully, but these errors were encountered: