STEREO-A beacon images

[helioshk]

It would be great if STEREO-A beacon images (particularly COR2) were available in helioviewer, as they are available with low latency (within minutes) compared to the full resolution images.

[wafels]

The beacon data is in FITS format; existing processing tools use FITS format and SSWIDL, so this is probably do-able. I'll contact the people on the STEREO team to find out more.

[dzarro]

Is the Beacon data available via VSO? Is so, it would easy to search and process.

On 4/4/2022 5:40 PM, Jack Ireland wrote: The beacon data is in FITS format; existing processing tools use FITS format and SSWIDL, so this is probably do-able. I'll contact the people on the STEREO team to find out more. — Reply to this email directly, view it on GitHub <#41>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA5DDNKS5MLTI652J5CTKGDVDNOUTANCNFSM5SLDKKQA>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

-- Dominic Zarro Heliophysics Group Manager/Principal Support Scientist ADNET Systems, Inc. 240-463-4461 (cell) ***@***.*** http://www.adnet-sys.com

[dgarciabriseno]

@dzarro Have you had a chance to work on this yet?

[wafels]

The basic code is in https://heliodocs.com/xdoc/xdoc_print.php?file=$SSW/gen/idl/atest/hv_beacon.pro . A couple of things come to mind for this.

1. Need to test it as is.
2. Will probably need a wrapper around hv_beacon.pro to continually search for new data. This is not a big deal - there are other examples in JP2Gen.
3. The current code uses the HVS_EUVI_A and HVS_EUVI_B helioviewer structure files. The beacon data should probably have their own structure files so that the filenames and the compression can be defined independently.
4. Not sure if COR1 and COR2 beacon images will be written out by this code

There is also some discussion on how these data should be included in the data selector hierarchy in helioviewer.org. For example, we could have

STEREO-A > SECCHI > EUVI beacon > (wavelength)

or

STEREO-A > SECCHI beacon > EUVI > (wavelength)

This second one might be more sensible if COR1 and COR2 also have writeable beacon data.

A request we've had in the past is to make the EUVI wavelet-processed data available. This would be included as

STEREO-A > SECCHI > EUVI wavelet enhanced > (wavelength)

Since wavelet enhanced data has also been requested maybe it is best to distinguish different types of data from the source instrument at the detector level, i.e., EUVI beacon and EUVI wavelet enhanced.