Martin Kuemmel
Martin Kuemmel
Looks like in 0.21 and the current develop *requires* partition-multithreshold switched off, and the default, which is on, leads to errors as discussed in #575 . I consider this as...
In the dataset discussed in #554, one way to avoid getting stuck would be using gsl instead of levmar. I checked that. While indeed the program runs through, a comparison...
When using the gsl minimizer. There are some cases when the error values are all NAN (blank in the pic) and sometimes the error values are all 0.0, which also...
FITS keywords are currently stored in structs "boost::variant". "boost::variant" allows a set of types, and when reading the value the correct type **must** be known and addressed. This results in...
Since we are using the ONNX runtime for the ML detection we suffer from a problem between ONNX and slurm: https://github.com/microsoft/onnxruntime/issues/10736 Some comments from Alejandro: It seems to be C++...
When fitting on a multi-band data, it is not clear what happens at empty spots (data=weight=0.0) in one band. While the auto_flux is 0.0 in that band the fitted flux...
Looks like when there is an exception in a thread, SE++ does not know what to do. The SE++ just hangs around. That behavior showed up in #442 and #438...
When fitting a bulge+disk model to VIS coadded data the comparison between auto_mag (== TU mags) and the fitted mags looks like this:  The PSF is a bit naive...
I ran some Euclid test data with single image fitting (3 bands, ~4 images per band per pixels) using different number of cores to test the scaling of the multi-threading....
The output-properties _AperturePhotometry_ and _AutoPhotometry_ are treated differently: * _AperturePhotometry_ is **only** applied to the measurement image(s). In case that the _AperturePhotometry_ of the detection image is wanted, a python...