When track-stacking multiple cameras or multiple nights, the initial canvas may be too small, leading to cropping of the final image. This arises because to estimate the size required, the code calculates the angular separations of each frame from the refernce. Normally, this will be at a maximum with the latest or earliest image. However, in the scenarios above, the angular separation does not behave in the same way, leading to canvases that are too small.
This fix adds a --scalefactor parameter that scales the canvas up by the specified amount. This increases the amount of memory required by scalefactor squared, which could cause issues on low-memory machines. Hence its an optional parameter and the default is to keep the original size.
Example attached showing the cropped and uncropped images created by stacking four colocated cameras for the night of 5/Feb with no scalefactor, and with --scalefactor 2
When track-stacking multiple cameras or multiple nights, the initial canvas may be too small, leading to cropping of the final image. This arises because to estimate the size required, the code calculates the angular separations of each frame from the refernce. Normally, this will be at a maximum with the latest or earliest image. However, in the scenarios above, the angular separation does not behave in the same way, leading to canvases that are too small.
This fix adds a --scalefactor parameter that scales the canvas up by the specified amount. This increases the amount of memory required by scalefactor squared, which could cause issues on low-memory machines. Hence its an optional parameter and the default is to keep the original size. Example attached showing the cropped and uncropped images created by stacking four colocated cameras for the night of 5/Feb with no scalefactor, and with --scalefactor 2
