dima

Hi. I have a scenario that's slightly different than the usual mtf-mapper case, and am wondering what the right way to approach it is. I have A low-resolution sensor: 640x480 With a VERY wide lens: 160deg corner-corner Focused at infinity I want to measure lens acuity. Normally I would use the lensgrid chart, and "mtf_mapper --annotate --lensprofile", but with the wide lens this doesn't work right. A sample image of the lensgrid chart placed chart squarely in front of the camera is attached in wide-headon.png....

Hi. The mtf_mapper manpage says that the ‘loess’ algorithm is recommended for --esf-model. However mtf_mapper_gui defaults to "kernel". Should the gui default be changed to follow the manpage recommendation? Thanks

Hi. I'm trying to use the new mtfmapper Debian package, and I'm seeing it crash with every image I give it. This happens: $ mtf_mapper .... .... mtf_mapper: .../src/mtf_core.cc:628: double Mtf_core::compute_mtf(Edge_model&, const std::map<int, scanline="">&, double&, double&, std::vector<double, std::allocator\<double=""> >&, std::vector<double, std::allocator\<double=""> >&, Snr&, bool): Assertion `fabs(magnitude[0] - 1.0) < 1e-6' failed.</double,></double,></int,> I see this in every image I tried....

Oh. OK. I understand what it's doing now, but I guess it just feels like a very strange thing to be doing. The output window is xy. The autoscaler untimately decides on xrange and yrange. So the xy data is what it should be using to make that decision. It sounds like it makes sense to you, so then yeah, there's no bug. Thanks for explaining.

Hold on! I've been busy, and haven't had time to reply. I've read your comments multiple times, and I'm sure it makes sense to you, but it doesn't make sense to me. First, the regression. I check out the "5.4" git tag, and I see the old behavior. The breaking commit is linked above. I cannot say if it does the right thing. Next, the intent was not to limit the input (as rrange would do) but to limit the output (as yrange should do). The autoscaling logic, as I always understood it, should select...

Hello. This plot is autoscaled on the x (where the data appears in a very small range), but the yrange is locked to [-5:5]. The data outside this yrange shouldn't affect this, and it didn't previously. I just did a bisection. 5.4 worked properly, 5.5 does not. The specific commit that broke it is: https://github.com/gnuplot/gnuplot/commit/6d3c518a5bdd0da34d7e7ba40e88d7e7576c41b2

Incorrect autoscale regression in polar plots

Hi. I don't think this is the case. I have this script: set yrange [10:0] set y2range [0:10] set link y2 via y inverse y set y2tics plot x If I remove one of "set yrange/y2range" commands, then the remaining one IS respected, despite the "set link" coming after. I.e. the "set link" doesn't override the existing setting. If I leave both "set yrange/y2range" in there, it's impossible to respect them both, and the "set y2range" is ignored.