melix
Suggestion for jagged edges correction enhancement
As I understand the current jagged edges experimental feature, it makes a noisemap of the ellipse and adjusts the pixels accordingly.
In my case with a mount that has some harmonic shakes, the jagged edges are caused by a shift in "time" during the scan. For instance the telescope tube is shaking up and down and hits the slit too low or too high in a rhythmic fashion while scanning.
My suggestion would be to make a new function where we use the noisemap to interpolate the frames of the .ser file so that it becomes a smooth ellipse in the time dimension, either by dropping frames or interpolating.
Does it make sense?
I'm extremely unclear what you mean. In particular, there's no such thing as a "noise map". The whole system is based on detection of the solar edges, nothing more than a geometric correction on each line. See https://melix.github.io/blog/2025/05-02-jsolex-3-1-0.html
I am sorry if it was unclear. I meant to write not noise map but "distortion map" as you mention in the blogpost.
The experimental idea I try to explain is meant for cases where the telescope itself is moving because of wind or vibration of the mount and slew errors as you mention. The turbulence and bad seeing is corrected by the current system you have made, but it will not help as much for telescope shake.
To try to make my point I can give an example: Lets say a gust of wind is making the whole telescope rig move slightly back and forth while scanning accross the sun. In the scan this will show up as a "smear" (many of the same slitscans of the same point of the sun being copied in a row) when the telescope moves one direction and then as a contraction when moving the other. This is very similar as slitscan effects used as effects in experimental photos. If I follow a person waking with a slitscan camera they will look elongated in that direction.
Ok, that is my whole point, that this type of error has to do with "time" in this sense. Your jagged edges algorithm corrects for movement in the "slit direction", but not in the direction perpendicular to it. So to avoid it if the .ser file has enough frames one could perhaps counteract the effect by calculating the error and build a better image image by dropping frames where they are smearing.
It might be too complex to do. Just a very experimental idea that would help a lot! Thanks again for your great software :-)