I was recently introduced to a new and free (as in beer) stacking program and have been testing it. The program is called AviStack and it is written in a language called IDL. I’ve been programming in IDL since 1981 and have considered writing an image stacking/processing application with it for some time. Someone has beaten my to the punch and done a very good job in the process. One particular thing of interest is that there are free IDL virtual machines for most operating systems and so AviStack will run on just about anything. So the question is: Is it better than what is out there already?
We’ll see in a moment, but first, What is Stacking? Stacking is pretty much what it sounds like. Multiple images of the same thing are aligned and averaged together to improve the result. Averaging multiple images allows you to increase the signal-to-noise ratio of the image and overcome geometric distortions due to atmospheric turbulence (aka Seeing). See this post for a glimpse at the magic of stacking. The stacking process is comprised of a number of algorithms. The individual frames of the AVI have to be graded for quality and then aligned with a master image. When imaging a large object such as the Moon, the stacking process is done on several pieces of the image separately and then combined into the full frame. The reason for this is that atmospheric turbulence causes regions of the images to move relative to one another as well as warp and blur. Therefore, the stacking program has to look at every frame of the AVI and decide what, if any, parts of it are usable. Since the part of the image the program wants to use is probably warped/distorted geometrically, the alignment algorithm is another important task that has to be done well. Finally, the program has to keep track of what part goes where during the stacking/averaging process.
The image above is a side by side comparison of images produced by the “Industry Standard” – RegiStax (Left) and the new comer – AviStack (Right). Click the (or any) image to get the full resolution image to get the full impact of the comparison.
RegiStax has been around for a long time and is probably the single reason why amateur astronomy has made huge strides in the last several years. It is also free (as in beer) and is under active development. It works on just about any type of object and has a lot of controls to learn. The manual is borderline useful (being a translation to my native language) and so learning what each control does is more or less trial and error. Nevertheless, it is easy to learn. One of the most powerful aspects of RegiStax is its post-processing capabilities. It has a sophisticated sharpening tool based on Wavelets that is simply a must have for me. This comparison is based on RegiStax version 188.8.131.52.
In my comparison, the RegiStax result (Left side) was produced using the Human grading algorithm and 20 alignment points. The stack is the best 200 out of 1300 frames. The image was sharpened with Wavelets in RegiStax and a modest Adaptive Richardson-Lucy Deconvolution (RLD) in ImagesPlus. I applied a Gamma correction of 1.30 in PhotoShop.
The AviStack result (Right side) used a 32 pixel grading grid and had about 1700 alignment points. The TIFF output file was converted to RGB in PhotoShop so that RegiStax would read the file for subsequent wavelet sharpening. As with the other image, a mild 5-iteration RLD with a 3×3 Gaussian PSF was applied in ImagesPlus and the gamma adjusted in PhotoShop.
As you have probably already concluded for yourself, the AviStack result is clearly superior. The overall resolution increase is striking. Let’s dig into the details of the good, bad, and ugly and try to uncover what is behind the differences. To do so, I’d like to discuss the differences between the way each program approaches the problem. The steps I’ll consider are ‘Setup’, ‘Grading’, ‘Alignment’, ‘Stacking’, and ‘Post-Processing’.
RegiStax requires that you select features in the image you wish to use for grading and alignment by placing square regions of various sizes manually with the mouse on a single frame from the AVI. You need to be careful placing alignment points near the edge of the frame since in most cases the image drifts during the length of the AVI. Having an alignment point drift out of the frame is a bad thing in RegiStax. In my test case I placed 20 alignment points/squares (128×128) and then saved my settings. RegiStax does have an automatic mode to place alignment points, but I have never really gotten satisfactory results with that and always place my points manually. The maximum number of alignment points in RegiStax is 99.
AviStack first needs to determine the drift in the image over the course of the AVI. To do this the user selects two features in a frame and places small squares on them with the mouse. The program then runs through each frame of the AVI to calculate the direction and rate of image drift. AviStack also estimates the amount of distortion due to seeing. When completed the user then sets a few controls that will determine how the alignment points are placed. There are two controls that identify regions that are too dark (space is dark after all) or too bright (overexposed) where there is no need to try to recover information by doing an alignment.
Once the controls are set, a press of a button will generate many alignment points automatically. The program generated 1688 alignment points for my test case. Points can be added or removed manually if needed.
Pros and Cons: AviStack is certainly easier to setup primarily because the automatic alignment point selection works well. I don’t have to worry about image drift with AviStack either. Both have the ability to save the point placement information for easier reprocessing. I’ll give AviStack a slight advantage in the Setup category.
Having performed the Setup, hitting RegiStax’s Align button performs an initial alignment and quality estimation or Grading of the areas around each alignment point (within the specified box). RegiStax reads the AVI file multiple times, once for each alignment point. Using FFT-based algorithms to calculate rough integral pixel alignment and image quality, it chugs through all of the alignment points. This process is not fast, but it does allow the user to monitor the process and correct problems. The problems encountered most often are an alignment box drifting off of the edge of the frame and losing the ‘lock’ on a feature. The former is not a frequent problem if you place your alignment boxes carefully to begin with, but the latter is a problem I frequently encounter. This initial alignment and grading step is not a fast process.
The approach to grading taken by AviStack is very different. The user selects a grid size and the program divides each frame into blocks of that size. The AVI is read once and a quality grade is calculated for each box. During this step the user also selects how ‘Deep’ the final stack will be (i.e., how many frames to stack). This process is as fast as it is for RegiStax to grade one alignment point.
Pros and Cons: RegiStax is very flexible in how the image is graded. I have found that different grading methods work best depending upon the type of object (Moon vs a planet like Saturn) or the seeing conditions (poor vs good). AviStack is very fast at this step of the process, but you have to decide how deep your stack is up front and regrade the AVI if you decide to change your mind. This is not a problem since you do not have to go back to the very beginning (as with RegiStax). In RegiStax, the stack depth is set after grading so the user can look at the frames going into the stack before choosing the depth. The Grading step is a toss up between the two as a winner will be determined by whether the user values flexibility vs speed.
After the frames have been graded, the RegiStax user needs to decide on the depth of the final stack by setting a slider to the last frame (for the first alignment point) and hitting the Limit button. At that point two new tabs become active and I usually create a reference frame. This is an important step in the process as the reference frame is used for final alignment. The reference frame is created by quickly stacking some small number (like 50) of the best images (based on the first alignment point). This is a single point alignment. Stacking based on a single point alignment averages out the warping due to seeing, but does not produce the optimal image quality over the whole image. I almost always set my first alignment point to be a prominent feature in the middle of the frame. The user is allowed to slightly sharpen the reference frame with wavelets. Once again many options are available during the alignment step. Once set, alignment commences with a press of the Optimize button. Then you can go off and read a book, get something to drink, something else to kill some time while RegiStax reads the AVI several times (again) once for each alignment point. Alignment is done to sub-pixel precision by calculating the position of the maximum of the local correlation matrix. Again things can go wrong here as it is possible to lose lock on an alignment feature. RegiStax does have a few options to predict the track of features as the images drifts over the duration of the AVI, but it is not apparent that this prediction is remembered from alignment point to point. It could be used to help maintain lock.
AviStack reads the AVI file once during the alignment step. For each frame, it uses the quality estimates for each quality grid box to determine which, if any, alignment points fall in a box that is good enough to be used in the stack. Those that do are aligned with respect to the feature found in a reference frame which is simply the average of all frames in the AVI. As the alignment is proceeding, the user sees the location of the original alignment points along with the location of the feature (both indicated by colored crosses on the image). Under all but the worst seeing conditions, the pattern of deviations should be reasonably smooth (correlated within a small area). Random fluctuations in the pattern of deviations indicates a problem which is correctable and reasonably well addressed in the manual. AviStack can track very low contrast features exceedingly well. As a result it can extract features in regions that you would otherwise think are featureless.
Pros and Cons: AviStack is a bit faster at this step in the process as well. It is also a very robust process. RegiStax is more likely to lose lock on a feature (although occurrences are not very common). In the lower left corner of the test comparison image at the top of this article you will notice that RegiStax had a problem locking onto the craters in the darker regions which resulted in faint displaced doubles. If you change your mind on the stack depth in RegiStax (or anywhere else in the work flow) you pretty much have to go back to the beginning. In some cases you should probably exit the program and restart it. The manual clearly states that canceling an operation can leave the program in an unpredictable state and that has certainly been my experience. The winner in the Alignment stage is clearly AviStack due to its speed and accuracy. Once again RegiStax does offer more flexibility, but I personally rarely use it.
RegiStax uses the location of the alignment points to divide the whole image area into polygonal regions with one alignment point inside each region. Using the best frames determined for each region it then interpolates the image (yes this means a potential loss of resolution for undersampled images) to the destination grid at each point in the region’s polygon and averages the frames together. Again in the usual RegiStax way there are many options to control and tailor this process to the user’s needs. One that is particularly useful is the degree to which adjacent regions are feathered to blend across polygon boundaries. The polygons can be significantly larger than the alignment box and so the quality of the region of the frames outside the box can be poor. At least with the real world seeing that I have where I live, there is significant smearing during stacking due to image warping within the large polygons.
Here is where all of those alignment points ultimately pay off. Like RegiStax, AviStack stacks the interpolated sub-frame data into little polygon regions with a single alignment point in each one. The polygons are so small, however, that the blurring due to warpage from seeing is minimal. The result is that very fine detail is preserved and enhanced by uniformly accurate alignment.
Pros and Cons: Simply because of the sheer number of alignment points and the corresponding smallness of the polygonal sub-regions, AviStack will produce a more uniformly resolved result with a higher average resolution than you get from RegiStax. There is no aspect of RegiStax’s performance or flexibility that can outweigh this. AviStack wins hands down.
You will need RegiStax simply because of its Post-Processing tools. The Wavelet sharpening process has to be seen to be believed. It is very powerful and a little goes a long way. It is very easy to over sharpen and produce an unrealistic image. This is very much a learn by doing process and it took me over a year to get it to do what I want. It was time very well spent.
AviStack has no Post Processing capabilities. The TIFF format you can save the image to is not compatible with RegiStax, at least for gray-scale, monochrome images. I usually convert it to RGB in PhotoShop before going to RegiStax for the Wavelets.
Pros and Cons: RegiStax wins by default and would put up an excellent fight had AviStack offered any tools.
You will have to have both programs. AviStack is a fabulous new stacking program that produces astounding results and at breakneck speed. Although I have not covered it here, AviStack does not work for me with planetary images (at least on my system where I’m not using a V7.0 IDLVM, but rather IDLDE V6.3). The author assures me that it does indeed work, so I must be doing something wrong. I’ll update this once I get it working. RegiStax has a wavelet sharpening tool that you simply must use. RegiStax V5 is due out in the near future and I will certainly try that out as soon as I can and revisit this comparison. I have reprocessed and compared a lot of images with RegiStax and AviStack. A few of them from nights of excellent seeing and of detailed terrain produced close if not indistinguishable images. I have not seen a case where RegiStax produced a better image, at best it was just as good, but often AviStack’s result was superior (especially when it came to the uniformity of quality).
The current trend among the top tier lunar imagers is to stack only a few images. They will stack only the best 20 out of thousands to make sure they get the best of the best. I think AviStack is going to change that – a lot. Because of the very small regions it uses for alignment and stacking, users of AviStack can and will stack more frames. There is no penalty for doing so.
AviStack has a bright future. I would like to see the author publish an API and provide hooks where 3rd party IDL gurus like myself can add tools to the program. I’d like to add a mosaic tool, for example, and I’m sure someone would generate a host of post-processing tools like Wavelets or RLD or …
Both programs have features and short-comings that I have not covered that others will deem essential or show-stopping. I do encourage you to give both of these programs a try and let me know what you think.