Leaving out "base-2" is fine. Shortening the description further as you suggest would also be fine with me.
I am wondering if we could change the wording to: "The floating-point arithmetic precision should match or exceed the precision specified by `computational_precision `attribute. The allowed values of `computational_precision ` attribute are: (table) `"32":` 32-bit floating-point arithmetic `"64"`: 64-bit floating-point arithmetic If the `computational_precision `attribute has not been set, then the default value "32" applies." That would ensure that we can assume a minimum precision on the user side, which would be important. Practically speaking, high level languages that support 16-bit floating-point variables, typically use 32-bit floating-point arithmetic for the 16-bit floating-point variables (CPU design). -- 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-842138566__;Iw!!G2kpM7uM-TzIFchu!gfbyhFC3RCWGePZYqKGDBp0A08A-7cKwm-xNyE1iOpYdCukBwdL1ehtXly3L8hNRpq9rvz-RKAU$ 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.
