Good idea David.

Should we perhaps use _computation_ instead of _calculation_ to match the 
attribute name? Here I have updated the first two paragraphs and added an 
example:

**8.3.8 Computational Precision**

"The accuracy of the reconstituted coordinates will depend on the degree of 
subsampling, the choice of interpolation method and the choice of the 
floating-point arithmetic precision used in the interpolation method 
computations.

To ensure that the results of the coordinate reconstitution process are 
reproducible and of predictable accuracy, the creator of the compressed dataset 
may specify the floating-point arithmetic precision to be used in the 
interpolation method computations by setting the interpolation variable’s 
`computational_precision` attribute to one of the following values:

(table)
"32": 32-bit floating-point arithmetic (default), comparable to the binary32 
standard in [IEEE_754]
"64": 64-bit floating-point arithmetic, comparable to the binary64 standard in 
[IEEE_754]

For the coordinate reconstitution process, the floating-point arithmetic 
precision should match or exceed the precision specified by 
`computational_precision `attribute, or match or exceed 32-bit floating-point 
arithmetic if the `computational_precision` attribute has not been set.

As an example, `computational_precision = "64"` would specify that the 
floating-point arithmetic precision should match or exceed  64-bit 
floating-point arithmetic.


**Bibliography**
**References**

[IEEE_754] "IEEE Standard for Floating-Point Arithmetic," in IEEE Std 754-2019 
(Revision of IEEE 754-2008) , vol., no., pp.1-84, 22 July 2019, doi: 
10.1109/IEEESTD.2019.8766229.



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/327*issuecomment-863211066__;Iw!!G2kpM7uM-TzIFchu!i0wYeRWjS2nDJDLdSy5CWBpzLE2atsGcqTyGc-nvFovozpXj1keEpoxqVaUjWoApPKX5PicW2FY$
 
This list forwards relevant notifications from Github.  It is distinct from 
cf-metad...@cgd.ucar.edu, although if you do nothing, a subscription to the 
UCAR list will result in a subscription to this list.
To unsubscribe from this list only, send a message to 
cf-metadata-unsubscribe-requ...@listserv.llnl.gov.

Reply via email to