erykoff

I don't believe so, though I don't know exactly how cross-python works. But in general, we just have compiler flags set that are ignored when that env variable is set...

An additional public interface to `observed_e1` and `observed_e2` would also be nice. And the current return for `observed_shape` should probably use the optimized `_Shape` rather than `Shape`.

I haven't done anything about this because I didn't want to deal with writing the tests. 😞

Reading the docs https://numpy.org/doc/stable/reference/generated/numpy.sort.html, it seems that the mention of `datatype` for `stable` is whether `timsort` is used (I think for floats, etc) or `radix sort` (for ints, strings, etc)...

This is what I have used (based on a different stack overflow which I didn't link to, sorry): https://github.com/lsst/pipe_tasks/blob/main/python/lsst/pipe/tasks/reserveIsolatedStars.py#L81-L84

The most interesting aspect for my work is the fact that (on average) the QE as a function of wavelength is different for each detector. The sub-detector variations are also...

Before running imsim or galsim you must set all the num threads vars. I thought this would be put into imsim (galsim wants to keep the flexibility of implicit multithreading...

https://github.com/lsst/utils/blob/main/python/lsst/utils/threads.py#L38-L57 It may be that @cwwalter is waiting for my standalone shut-it-all-down package which I'll put together during the break.

Implicit multithreading takes more resources and only occasionally improves runtime. Often it greatly increases the runtime by x10 or in some cases x100. I hates it.

Not just oversubscribing. Weird cache contention issues maybe. Unclear but it’s broken everywhere and should never be used.