Hi @taylor13 and @davidhassell, Regarding the `computational_precision` attribute, it appears that we currently have two proposals: Either an optional attribute with a default value or a mandatory attribute.
I have written two versions of the new section 8.3.8, one for each of the two proposals. I hope that will help deciding! Anders **Optional attribute version:** **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 with which the interpolation method is applied. 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 by setting the interpolation variable’s `computational_precision` attribute to one of the following values: (table) 32: 32-bit floating-point arithmetic (default) 64: 64-bit floating-point arithmetic For the coordinate reconstitution process, the floating-point arithmetic precision should (or shall?) 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. **Mandatory attribute version:** **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 with which the interpolation method is applied. To ensure that the results of the coordinate reconstitution process are reproducible and of predictable accuracy, the creator of the compressed dataset must specify the floating-point arithmetic precision by setting the interpolation variable’s `computational_precision` attribute to one of the following values: (table) "32": 32-bit floating-point arithmetic "64": 64-bit floating-point arithmetic For the coordinate reconstitution process, the floating-point arithmetic precision should (or shall?) match or exceed the precision specified by `computational_precision` attribute. -- 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-858807540__;Iw!!G2kpM7uM-TzIFchu!gtrT1ATM4i1MruwBLI8QC6A-7qNj82V3hO7OSg6QSAd5_un8FRNyoZP1kDDwPaLTAqErhmDq_7E$ 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.
