Martin Kuemmel

Yes, I agree. Clipping + a warning message is the way to go! *No* flagging necessary. People will specify astrophysically meaningful absolute limits, so objects with outside starting values will...

Not to my knowledge.

I can run a test to see whether this still happens.

I am running now with gsl. There is tons of: > 2021-12-06T14:04:09CET ModelFitting WARN : WorldToEngine ExpSigmoidConverter: world values outside of possible range > 2021-12-06T14:04:09CET ModelFitting WARN : WorldToEngine ExpSigmoidConverter:...

Okay, but I did not change the boundaries or so in the python configuration files. So it is not clear why they show up now.

Just to give the scale of that, in the levmar runs that warning appears 2 times, in gsl, 1/3 through the processing, it appeared 41000 time (same dataset of course).

I checked into this. The error values are almost all filled now. If they are not filled then `fmf_flags` is in almost all cases 1024, which is a general error...

Fine with me. levmar is behaving well, no reason to emphasize this for 0.16.

It is strange that: * the positional offset goes to the same direction; * there is this line at ~-1000. Maybe more effort is necessary in the parameterization, I only...

Yepp, the objects at -1000. are black holes in the residuals. But the failures are signaled in the stop reason. They all have stop-reason=11 (but there are also good stop-reson=11...