Closed jmbhughes closed 8 months ago
It would be good to figure out how to use astropy to identify planets and the moon proximity in this build.
Note https://sohoftp.nascom.nasa.gov/solarsoft/packages/pdl/auto/gen/images/processing/zspike.pdl and we should see Craig for code and ideas.
Also look at how polarization could help inform us
@mwest007 is going to start brainstorming and implement a basic module that identifies easy targets like planets and the Moon.
I discussed this with Craig some. We are going to get some test data with clouds to experiment with. ZSPIKE might do just the trick we're looking for. We'll have to think about making that work in the pipeline properly though.
Also, Craig mentioned that we should track comets/small bodies in addition to planets/moon.
Module L2BS identifies bright structures in the data products.
Diffuse bright structures over and above the background F-corona are identified and marked in the data using in-band “bad value” marking (which is supported by the FITS standard). Data marking uses the existing ZSPIKE temporal despiking algorithm to identify auroral transients. ZSPIKE was originally used to identify cosmic rays, and was adopted on STEREO for on-board despiking during exposure accumulation. For this application ZSPIKE is ideal because it does not rely on the spatial structure of spikes, only their temporal structure. Both cosmic rays and, if present, high-altitude aurora are transient and easily detected with ZSPIKE. The algorithm assembles “votes” from the images surrounding each one in a stream, to determine whether a particular pixel is a good candidate for a temporal spike. If the pixel is sufficiently bright compared to its neighbors in time, it is marked bad. “Bad values” are stored in the DRP for file quality marking outlined in Module Quality Marking.