Lehman Garrison
Lehman Garrison
Just so I understand, is the 2 bytes to indicate the length of the header (i.e. up to 64K)? Or something else?
That's part of why I was leaning towards a wrapper to numcodecs as the plugin mechanism. It already has the codec ID mechanism to identify the compression algorithm for the...
I was thinking about that too. I've poked around a bit, and the only JSON field that numcodecs mandates is `id`, which is pretty uncontroversial. The rest of the JSON...
Just a thought: what about adopting @eslavich's changes, but also write the block length at the *end* of the block for the special case of streaming blocks? A special value...
I confirm the `testing` branch fixes the issue. Thanks for fixing this so quickly!
Is there a PR I can follow just to know when the fix is merged?
That's if any of `__aarch64__`, `__arm64`, and `__arm64__` are detected? Sounds good to me! Would be a fun project to try to get those undocumented vector calls to work!
Right, the `arm64` branch (PR [here](https://github.com/manodeep/Corrfunc/pull/280)) works on the M1 with both fallback and NEON kernels. So you can just use that branch instead of patching your source with the...
But isn't the particle distance with the negative offset very small, and it is thus counted, and the distance with the positive offset very large, and thus not counted? I...
Sorry, I think I confused the issue by saying "positive offset" and "negative offset". In the case of an autocorrelation, the negative offset is actually "no offset". Offsets are only...