SHG (spectroheliography) software release version 3.2

The place for all your solar software; capture, stacking, post processing, ancillaries etc. It's all up for discussion here!
Post Reply
thesmiths
Almost There...
Almost There...
Posts: 1053
Joined: Mon Jun 04, 2012 8:13 pm
Location: London, England
Has thanked: 42 times
Been thanked: 1485 times

SHG (spectroheliography) software release version 3.2

Post by thesmiths »

We just published a new release of our spectroheliography software , version 3.2:
https://github.com/thelondonsmiths/Sole ... s/tag/v3.2

The major changes/ improvements to the last version:

The height of the image output files is now set to always be the same as the width of the video input file. So, for example, if the ROI is 1600x100 pixels, we assume the final image should have a height of 1600 pixels. There was previously a slight variability in the image size due to the ellipse to circle geometric correction.

The last used states of the three user interface check boxes are now saved in the SHG.ini settings file.

The geometric correction graphic is now always saved (unless "save clahe.png only" is chosen). This graphic box is quite useful to recognise issues of geometric distortion. I find it is also helpful for setting the exposure since it produces an image of +10 pixel shift that may show sunspots. If it is completely washed out, probably the exposure is too high.

The radius of the black disk in the protus.png can now be adjusted by entering a positive or negative integer into a box below pixel shift. Generally, something like +5 to +10 will bring the black disk right to the edge and -5 to -10 will shrink it so there is a large bright ring. See examples below.

protus adjustment = 0
protus adjustment = 0
14195_protus 0.jpg (26.42 KiB) Viewed 1277 times
protus adjustment = +10
protus adjustment = +10
141958_protus +10.jpg (22.66 KiB) Viewed 1277 times
protus adjustment = -10
protus adjustment = -10
141958_protus -10.jpg (29.73 KiB) Viewed 1277 times

There is an infrequent failure mode in the border detection function. When this happens, the program would stop. The "bad lines" and "transversallium correction" use the border detection function. If the border detection fails, we now flag the failure and do not perform "bad lines" and "transversallium correction" and the processing continues without these corrections.


Post Reply