In this case I’m using the default @validation 0.2, so there’s some in place, it’s just being banged over and over externally obviously.
I guess a validation output message would solve the use case here (I think?), where I can just check for that and call it a day once that stops improving (or whatever).
I guess in general the UX is tricky to navigate (as a non-data person) since ideally this would either be a single message thing “make it good”, with the stuff like @maxiter being more like the @zlmaxsize or @maxfftsize as an upward limit of what you may ever expect to do, but not what you intend to do or having a clearer iterative process where you can monitor the progress and decide when it’s good enough (if you know what you’re looking for).
Don’t know if there’s any overlap with the partition stuff you were talking about in this thread, but I’m a big fan of overhead being added in exchange for ease of use/better results.