perrygreenfield
perrygreenfield
Not quite right as I recall. STSDAS and TABLES were never converted to 64-bit IRAF for various reasons, and so for us, though I don't think that prevented PyRAF from...
I agree that the equivalent of the numcodecs metadata dict should be stored that way (or allowing YAML as well). Whether it should be in the YAML header or embedded...
Yes, it should be made clear that whatever is added has to be reasonably easy to support in other languages. I agree that we don't necessarily imply all that is...
To the extent that it is supported by BLOSC, it does seem more generic since that is implemented in C. Still, that would present problems for other languages that don't...
@eslavich Any thoughts about where the metadata ought to go? If in the YAML header, it would require extending the ndarray schema to allow for such an object to aid...
Does anything prevent a second level, variable-length prefix? The id in the block header can indicate that there is a prefix to the data in the data section, the first...
I suppose, but for most uses that seems like overkill, and inefficient in that YAML parsing would be needed, even for small arrays.
Perhaps. One scheme is to have the file level configuration have some ID that can be used in the block header allowing multiple compression options within the same file. It's...
Also true for only one compression scheme though.
It probably is the most robust as well.