<div dir="ltr">I suggest asking the question: What FITS library cannot handle 16-bit and 128-bit floats? We know that half-precision is supported in C/C++ and FORTRAN, which means that it is potentially available in FITSIO, CFITSIO, and Python/numpy that depend on these languages. It is also available in Java and Julia. This leaves languages such as IDL, Matlab, and R that may not be supported, unless the maintainers decide to eventually add those types. My feeling is that those who use those languages are a small percentage (<1 %) of the user base. It does not seem reasonable to me that such a small percentage of users have such a large influence on the development of our community. It has always been my opinion that a data format should not control what and how software is developed. It places an unnecessary constraint on the development of high quality, high performance software.<div><br></div><div> -- Paul</div><div><br></div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Thu, Jul 24, 2025 at 5:01 AM jaffe via fitsbits <<a href="mailto:fitsbits@listmgr.nrao.edu">fitsbits@listmgr.nrao.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Whether a FITS storage format is supported by any programming language, <br>
or even any machine processor architecture is irrelevant, FITS is a <br>
transport standard. If half-precision FP is accepted into the FITS <br>
standard, this implies that the FITS reader/writers for any language or <br>
architecture have to be adapted to convert the FITS data into a locally <br>
functional format, e.g. 32-bit FP if local 16-bit FP is not supported.<br>
<br>
Walter<br>
<br>
On 2025-07-23 20:11, Lucio Chiappetti via fitsbits wrote:<br>
> On Wed, 23 Jul 2025, Barrett, Paul via fitsbits wrote:<br>
> <br>
>> Yes, definitely. I have been advocating for half-precision (16-bit) <br>
>> floating point for several years now for radio astronomy. In addition, <br>
>> 128-bit floats<br>
> <br>
> Are these formats supported by any major programming language ?<br>
> <br>
> Is it worth supporting "exotic" formats, which might be suitable for <br>
> some niche application, when most data producers often use improperly <br>
> 64-bit all the times, even when overshoot ?<br>
> <br>
> Historically FITS went the other way round (concentrating on 16 and 32, <br>
> later 64, when mainframres with 36 or 60 bits were around).<br>
> <br>
> _______________________________________________<br>
> fitsbits mailing list<br>
> <a href="mailto:fitsbits@listmgr.nrao.edu" target="_blank">fitsbits@listmgr.nrao.edu</a><br>
> <a href="https://listmgr.nrao.edu/mailman/listinfo/fitsbits" rel="noreferrer" target="_blank">https://listmgr.nrao.edu/mailman/listinfo/fitsbits</a><br>
<br>
_______________________________________________<br>
fitsbits mailing list<br>
<a href="mailto:fitsbits@listmgr.nrao.edu" target="_blank">fitsbits@listmgr.nrao.edu</a><br>
<a href="https://listmgr.nrao.edu/mailman/listinfo/fitsbits" rel="noreferrer" target="_blank">https://listmgr.nrao.edu/mailman/listinfo/fitsbits</a><br>
</blockquote></div>