EOVSA Data Products: Difference between revisions

From EOVSA Wiki
Jump to navigation Jump to search
 
(55 intermediate revisions by 4 users not shown)
Line 1: Line 1:
EOVSA observes the full disk of the Sun at all times when the Sun is >10 degrees above the local horizon (season dependent and ranges from 7-12 hours duration centered on 20 UT). EOVSA records data at 451 science frequency channels each second, in four polarization products, as well as additional total flux measurements from each individual antenna. Raw data in the visibility domain are processed through a pipeline processing system to produce images and spectrograms in the time- and frequency-dependent image plane (the block diagram in Figure 1 shows the data flow in the pipeline).  
=Introduction=
EOVSA observes the full disk of the Sun at all times when the Sun is >10 degrees above the local horizon (season dependent and ranges from 7-12 hours duration centered on 20 UT). EOVSA records data at 451 science frequency channels each second, in four polarization products, as well as additional total flux measurements from each individual antenna. Figure 1 summarizes the different levels of data we produce. The later sections will give a more detailed description and usage examples.
[[File:pipeline_flowchart.jpg|center|600px|EOVSA pipeline block diagram/flow chart ]]
[[File:pipeline_flowchart.jpg|center|600px|EOVSA pipeline block diagram/flow chart ]]
We deliver the radio interferometry data on the following three levels:


=Level 0 - Raw visibility data from the instrument=
=Level 0 - Raw visibility data from the instrument=
Line 10: Line 8:


==Raw "Interim" Database (IDB) visibility data==
==Raw "Interim" Database (IDB) visibility data==
Full-resolution raw "Interim" Database (IDB) visibility data. They are stored in Miriad format, and hence may not be that useful for most people. Be patient after clicking the link--this is a very long list of directories, one for each available date. These data can be retrieved from the following page:
Full-resolution raw "Interim" Database (IDB) visibility data. They are stored in Miriad format, and hence may not be that useful for most people. Be patient after clicking the link--this is a very long list of directories, one for each available date. Recent data (latest few months) can be retrieved from the following page:
 
https://www.ovsa.njit.edu/fits/IDB/
 
For older data, visit the UC/Berkeley hosting page:


http://www.ovsa.njit.edu/fits/IDB/
https://research.ssl.berkeley.edu/data/eovsa/IDB/


==Raw 1-min-averaged visibility data==
==Raw 1-min-averaged visibility data==
Line 20: Line 22:


=Level 0.5 - Calibrated visibility data=
=Level 0.5 - Calibrated visibility data=
After applying calibration and other preliminary processing to the raw (level 0) data, we create the CASA ms’s in the second column in Figure 1 (labeled "level 0.5"). These visibility data are in the Fourier domain of the true images in the plane of the sky and are not immediately ready for spectral imaging analysis yet. However, they have all of the required content to produce images and spectrogram data in standard FITS format (level 1.0).  We provide a set of standard ms’s for each day (red boxes in Figure 1), for use by researchers who know how to deal with visibility data.  
After applying calibration and other preliminary processing to the raw (level 0) data, we create the CASA ms’s in the second column in Figure 1 (labeled "level 0.5"). These visibility data are in the Fourier domain of the true images in the plane of the sky and are not immediately ready for spectral imaging analysis yet. However, they have all of the required content to produce images and spectrogram data in standard FITS format (level 1.0).  We provide a set of standard ms’s for each day (red boxes in Figure 1), for use by researchers who know how to deal with visibility data. These data are more suitable for experienced users to exploit the full potential of EOVSA data, such as spatially resolved spectral analysis. Processing these data requires CASA or sunCASA (https://github.com/suncasa/suncasa-src). Please refer to our tutorial at [[EOVSA_Data_Analysis_Tutorial]].


==Calibrated full-resolution visibility data for flare events==
==Calibrated full-resolution visibility data for flare events==
Calibrated and self-calibrated visibility data for flare events (purple boxes in Figure 1) will typically be available within 7 days after they are taken. They will be
Calibrated and self-calibrated visibility data for flare events (purple boxes in Figure 1) will typically be available within 7 days after they are taken. They will be released at our flare list site soon: https://ovsa.njit.edu/flarelist


==Self-calibrated 1-min-averaged visibility data==
==Self-calibrated 1-min-averaged visibility data==
Line 32: Line 34:
=Level 1.0 - Images and spectrogram data in standard FITS format =
=Level 1.0 - Images and spectrogram data in standard FITS format =


Most users, however, will prefer to work with spectrogram (frequency-time) and image data, which are also outputs of the pipeline system shown in Figure 1 (orange boxes). Spectrograms are provided as standard FITS tables containing the frequency list, list of times, and data in both total power (TP) and a sum of amplitudes over intermediate-length baselines (cross power or XP). Likewise, image data products are in FITS format with standard keywords and are converted into the Helioprojective Cartesian coordinate system compatible with the World Coordinate System (WCS) convention, along with correct registration for the spatial, spectral, and temporal coordinates. Both the spectrogram and image data products are calibrated properly and have physical radio intensity units (sfu for spectrograms and brightness temperature for radio images).
Level 1.0 data are for users who prefer to work with spectrogram (frequency-time) and image data directly, which are also outputs of the pipeline system shown in Figure 1 (orange boxes). They are perfectly suitable to be used as context data for comparison with other multi-wavelength observations but are not (yet) intended for quantitative spatially resolved spectral analysis.  


We provide the following data products:
Spectrograms are provided as standard FITS tables containing the frequency list, list of times, and data in both total power (TP) and a sum of amplitudes over intermediate-length baselines (cross power or XP). Likewise, image data products are in FITS format with standard keywords and are converted into the Helioprojective Cartesian coordinate system compatible with the World Coordinate System (WCS) convention, along with correct registration for the spatial, spectral, and temporal coordinates. Both the spectrogram and image data products are calibrated and have physical radio intensity units (sfu for spectrograms and brightness temperature for radio images).
 
We provide the following level 1 data products:
* Synoptic products:
* Synoptic products:
** All-day total-power spectrograms:
** '''All-day spectrograms''': Full-day total-power (TP) and cross-power (XP) spectrograms (i.e., no spatial resolution) at full spectral and time resolution in FITS format. One file per day.
** All-day cross-power spectrograms:
** '''All-day synoptic images''': Full disk images at 7 selected frequency bands centered at 1.4, 3.0, 4.5, 6.8, 10.2, 13.9 and 17.0 GHz are produced once per day utilizing the earth-rotation synthesis, calibrated in brightness temperature. This is because EOVSA has a limited number of baselines and we need a long integration to fill up the uv domain in order to make full-disk images.
** All-day synoptic images:
* Event-based products:  
* Event-based products:  
** Flare spectrograms: These are full time and frequency resolution spectrograms produced from the median of calibrated cross-power visibilities in FITS format, cropped to cover the flare duration. Pre-flare background is also subtracted. Compared to total-power spectrograms, these spectrograms have the advantage of revealing details of the flare evolution by "filtering out" the large-scale, continuous background from the visibilities (as they are poorly correlated by baselines with intermediate lengths). Note that for flares that have a large source size, the flux shown by the cross-power spectrograms can be lower than its true flux (as a fraction of the flux will be "resolved out"). In this case, one might compare the spectrograms with our total-power spectrogram products.  
** '''Flare spectrograms''': These are full time and frequency resolution spectrograms produced from the median of calibrated cross-power visibilities in FITS format, cropped to cover the flare duration. Preflare background is also subtracted. Since mid-October 2024, we offer both total- and cross-power spectrograms for flare events. Cross-power spectrograms, compared to total-power spectrograms, have the advantage of revealing details of the flare evolution by "filtering out" the large-scale, continuous background from the visibilities. Note that for certain flares that have a large source size, the flux can be lower than its true values (as a fraction of the flux will be "resolved out").
** Pipeline-produced spectral images: We also have a semi-automated flare imaging pipeline to produce calibrated (and self-calibrated) images at 12-s cadence in up to 10 frequency bands. They are saved  
** '''Pipeline-produced spectral images''': We also have a semi-automated flare imaging pipeline to produce calibrated (and self-calibrated) images at 12-s cadence at up to 10 frequency bands. They are saved in standard FITS format and have been registered into Helioprojective coordinates. They can be read by SSWIDL or astropy/sunpy. These data have already been calibrated to physical units and are usually good to be compared with context data. But please be cautious when using them for quantitative spectral analysis.


'''List of Level 1 data products'''
{| class="wikitable"
{| class="wikitable"
|+ Summary of EOVSA Level 1 Data Products
|-
|-
! scope="col"| Category
! scope="col"| Category
! scope="col"| Data Product
! scope="col"| Data Product
! scope="col"| Naming Convention
! scope="col"| Naming Convention
! scope="col"| Download Link
|-
|-
! rowspan="2" | Synoptic Spectrogram
! rowspan="2" | Synoptic Spectrograms
| All-day TP Spectrogram
| All-day TP Spectrograms
| EOVSA_TPall_yyyymmdd.fts
| EOVSA_TPall_yyyymmdd.fts
!rowspan="9" | https://ovsa.njit.edu/browser
|-
|-
| All-day XP Spectrogram
| All-day XP Spectrograms
| EOVSA_XPall_yyyymmdd.fts
| EOVSA_XPall_yyyymmdd.fts
|-
|-
! rowspan="7" | Synoptic Image
! rowspan="7" | Synoptic Images
|-
| Synoptic 1.4 GHz images
| Synoptic 1.4 GHz image
| eovsa_yyyymmdd.spw00-01.tb.disk.fits
| eovsa_yyyymmdd.spw00-01.tb.disk.fits
|-
|-
| Synoptic 3.0 GHz image
| Synoptic 3.0 GHz images
| eovsa_yyyymmdd.spw02-05.tb.disk.fits
| eovsa_yyyymmdd.spw02-05.tb.disk.fits
|-
|-
| Synoptic 4.5 GHz image
| Synoptic 4.5 GHz images
| eovsa_yyyymmdd.spw06-10.tb.disk.fits
| eovsa_yyyymmdd.spw06-10.tb.disk.fits
|-
|-
| Synoptic 6.8 GHz image
| Synoptic 6.8 GHz images
| eovsa_yyyymmdd.spw11-20.tb.disk.fits
| eovsa_yyyymmdd.spw11-20.tb.disk.fits
|-
|-
| Synoptic 10.2 GHz image
| Synoptic 10.2 GHz images
| eovsa_yyyymmdd.spw21-30.tb.disk.fits
| eovsa_yyyymmdd.spw21-30.tb.disk.fits
|-
|-
| Synoptic 13.9 GHz image
| Synoptic 13.9 GHz images
| eovsa_yyyymmdd.spw31-43.tb.disk.fits
| eovsa_yyyymmdd.spw31-43.tb.disk.fits
|-
|-
! rowspan="1" | Flare Spectrogram
| Synoptic 17.0 GHz images
| Full-resolution cross-power Spectrogram
| eovsa_yyyymmdd.spw44-49.tb.disk.fits
| eovsa.spec.flare_id_YYYYMMDDHHMMSS.fits
|-
! rowspan="2" | Flare Spectrograms
| Flare TP Spectrogram
| eovsa.spec_tp.flare_id_YYYYMMDDHHMM.fits
!rowspan="3" | https://ovsa.njit.edu/flarelist
|-
|-
! rowspan="1" | Flare Spectral Image
| Flare XP Spectrogram
| eovsa.spec_xp.flare_id_YYYYMMDDHHMM.fits
|-
! rowspan="1" | Flare Spectral Images
| Pipeline-produced spectral images
| Pipeline-produced spectral images
| eovsa.lev1_mbd_12s.YYYY-MM-DDTHHMMSSZ.image.fits
| eovsa.lev1_mbd_12s.YYYY-MM-DDTHHMMSSZ.image.fits
Line 87: Line 98:
|}
|}


==Getting level 1 data==  
==Browsing and Downloading level 1 data==  
[[File:eovsa_browser.jpg|right|thumb|EOVSA Browser]]
[[file:EOVSA_flarelist.jpg|right|thumb|EOVSA Flare List]]
===Synoptic level 1 data===  
===Synoptic level 1 data===  
EOVSA Level 1 synoptic data products can be retrieved with the following steps:
EOVSA Level 1 synoptic data products can be retrieved with the following steps:
Line 94: Line 107:
* Click "synoptic fits" button next to the calendar tool.
* Click "synoptic fits" button next to the calendar tool.
* Select the data product based on the names listed in the table above.
* Select the data product based on the names listed in the table above.
[[File:eovsa_browser.jpg|800px|center]]
===Flare level 1 data===


==Reading level 1 data==
===Software===
We have developed a package for EOVSA data processing and analysis:
[https://github.com/suncasa/suncasa SunCASA] A wrapper around [https://casa.nrao.edu/ CASA (the Common Astronomy Software Applications package)] for synthesis imaging and visualizing solar spectral imaging data. CASA is one of the leading software tools for "supporting the data post-processing needs of the next generation of radio astronomical telescopes such as ALMA and VLA", an international effort led by the [https://public.nrao.edu/ National Radio Astronomy Observatory]. The current version of CASA uses Python (2.7) interface. More information about CASA can be found on [https://casa.nrao.edu/ NRAO's CASA website ]. Note, CASA is available ONLY on UNIX-BASED PLATFORMS (and therefore, so is SunCASA). We are developing a new version of SunCASA based on CASA 6 (which offers a modular approach) so that users have the flexibility to build CASA tools and tasks in their Python environment.


Please [http://www.ovsa.njit.edu/wiki/index.php/SunCASA_Installation follow this link] for details regarding the installation of SunCASA on your own machine (only available on Unix-bases OS). This will take you to another page.
===Flare level 1 data===
EOVSA flare list with spectrograms and spectral images can be queried and downloaded at https://ovsa.njit.edu/flarelist. Users can use the top box to select a time range of interest and query our flare list. The results are displayed in the dropdown box. An interactive plot of the flare light curves will be shown at the bottom of the page once an event is highlighted (by clicking on the flare ID). Quicklook plots and FITS files of the spectrograms and flare movies can be accessed by clicking the icons in each flare record.


===Flare Spectrograms and Multi-Frequency Images ===
==Reading and Using level 1 data==
EOVSA flare list with spectrograms and spectral images can be queried and downloaded at https://ovsa.njit.edu/flarelist.
===Introduction===
All our level 1 data products are in FITS format. All the images have standard, WCS-compatible coordinates. Users can use their favorite method to read these files. In the following, we provide minimal examples to read them with Astropy and Sunpy.


* An example of how to read and plot these FITS data in Python (with Astropy and SunPy) can be accessed at [https://colab.research.google.com/drive/1Y3ONWCxLPYvWda5_LqFNxafJtwZDNJBD?usp=sharing#scrollTo=ueiMoHbdxfo- this Google Colab Jupyter notebook].
===Event-Based Data Products===
* We are working on an example with SSWIDL and will release it soon.
* An example of how to read and plot the flare spectrograms and images in Python (with [https://www.astropy.org/ Astropy] and [https://sunpy.org/ SunPy]) can be accessed at [https://colab.research.google.com/drive/1wMvuxuNip5cJJHMoTOLT6u_OdWobpBY0?usp=sharing this Google Colab Jupyter notebook].
* We are working on an example with SSWIDL and will post it soon.


===All-day TP spectrum===
===Synoptic Data Products===
Daily total power full-Sun-integrated spectrogram calibrated in solar flux units are provided at 451 frequencies (134 frequencies prior to 2019 Feb 22) and 1 s time resolution.
* An example of how to read and plot the flare spectrograms and images in Python (with [https://www.astropy.org/ Astropy], [https://sunpy.org/ SunPy], and optionally, [https://docs.sunpy.org/projects/radiospectra/en/latest/ radiospectra]) can be accessed at [https://colab.research.google.com/drive/1bF_WjKRk51Hb3h10EzcGaBCw9QFjWwqW?usp=sharing this Google Colab Jupyter notebook].


To read a spectrogram file in Python using the suncasa library:
<pre style="background-color: #FCEBD9;">
from suncasa.eovsa import eovsa_dspec as ds
from astropy.time import Time
from matplotlib.colors import LogNorm
## Read EOVSA Dynamic Spectrum FITS file <filename>
filename = 'EOVSA_TPall_20170713.fts'
s = ds.get_dspec(filename, doplot=True, cmap='gist_heat', norm=LogNorm(vmax=2.1e3, vmin=40))
## To access the data in the spectrogram object, use
spec = s['spectrogram']                    ## (Array of amplitudes in SFU, of size nfreq,ntimes)
fghz = s['spectrum_axis']                  ## (Array of frequencies in GHz, of size nfreq)
tim = Time(s['time_axis'], format='mjd')  ## (Array of UT times in astropy.time object, of size ntimes)
</pre>
The '''get_dspec''' function is accessible on [https://github.com/suncasa/suncasa-src/blob/master/suncasa/eovsa/eovsa_dspec.py GitHub]. For comprehensive guidance, please refer to suncasa's [https://suncasa-src.readthedocs.io/en/latest/autoapi/suncasa/eovsa/eovsa_dspec/index.html ReadtheDocs page].
[[File:TPSP.jpeg|center|500px]]
The following code will read the spectrogram file in IDL:


Additional examples for IDL users. For spectrograms:
<pre style="background-color: #FCEBD9;">
<pre style="background-color: #FCEBD9;">
function dspec,filename,doplot=doplot
function dspec,filename,doplot=doplot
Line 171: Line 161:
[[File:IDL_TPSP.png|center|500px]]
[[File:IDL_TPSP.png|center|500px]]


===Synoptic 6-band Images===
Full disk images at 6 selected frequency bands centered at 1.4, 3.0, 4.5, 6.8, 10.2, and 13.9 GHz are provided once per day, calibrated in brightness temperature. [[File:synoptic_image.jpg| center |400px]]
The EOVSA full disk image FITS files are compressed with the RICE algorithm implemented in the FITS file handling module (astropy.io.fits) in Astropy. EOVSA FITS files are very similar to the compressed SDO/AIA FITS files from JSOC. Popular coding languages can easily read compressed images directly.
In IDL, you can use read_sdo in the ONTOLOGY package, which should be installed by default in SolarSoftWare (SSW), to read compressed EOVSA FITS files. The following code will read the EOVSA image FITS file in SSWIDL:


For synoptic images:
<pre style="background-color: #FCEBD9;">
<pre style="background-color: #FCEBD9;">
read_sdo,'eovsa_20191225.spw11-20.tb.disk.fits',header,data,/UNCOMP_DELETE
read_sdo,'eovsa_20191225.spw11-20.tb.disk.fits',header,data,/UNCOMP_DELETE
Line 186: Line 171:
[[File:eovsa_20191225_image_sswidl.jpg| center |250px]]
[[File:eovsa_20191225_image_sswidl.jpg| center |250px]]


In Python, you can use SunPy map module to read EOVAS FITS files. SunPy is an open solar data analysis environment for Python. The installation instruction can be found at [https://sunpy.org/ SunPy official website].
=Requesting EOVSA Data or Analysis Assistance=
<pre style="background-color: #FCEBD9;">
The pipeline-processed synoptic and flare event data (level 1.0) are science-ready and usually sufficient for many purposes. However, the list may not be complete, and the pipeline-processed data do not have the full-time and frequency resolution necessary for certain in-depth quantitative spectral analyses. If you are interested in (1) working on events that are not currently included in our level 1.0 database and/or (2) needing assistance from an EOVSA team member in detailed or quantitative analysis that requires EOVSA data processing beyond that offered by the level 1.0 products, please use the following Data Request Form to submit such requests.  
import matplotlib.pyplot as plt
from sunpy import map as smap
eofile='eovsa_20191225.spw11-20.tb.disk.fits'
eomap = smap.Map(eofile)
eomap.plot()
plt.show()
</pre>
[[File:eovsa_20191225_image_py.jpg| center |250px]]


Although the Sunpy Python package already exists for doing analysis of solar data, it has a significant learning curve and lacks the generality of the Mapping routines written by Dominic Zarro for the IDL-based Solarsoft (SSW). We provided IDL Mapping routines available in Python that may help those IDL users who have been avoiding learning Python. '''The mapping routines work equally well in both Python 2.7 and Python 3'''.
[https://forms.gle/xPo7G3fwGwQhEmdLA EOVSA data request form]
Get the [http://www.ovsa.njit.edu/wiki/index.php/Mapping_Software Mapping routines]
The following code will read the EOVSA image FITS file in python:
<pre style="background-color: #FCEBD9;">
from mapping.plot_map import plot_map
from mapping.fits2map import fits2map
eofile='eovsa_20191225.spw11-20.tb.disk.fits'
eomap, h = fits2map(eofile,header=True)
plot_map(eomap, grid=15, limb=True,cmap='gray')
</pre>
[[File:eovsa_20191225_image_py_ssw-mapping.jpg| center |250px]]


===10-min 6-band Images===
We will normally respond to your request within 2-3 working days. Note that for (1), standard acknowledgments and reference citations would be sufficient. For (2), the EOVSA team member who helped with the data analysis/interpretation needs to be included as a co-author for publications that utilize the relevant EOVSA data. Please refer to https://ovsa.njit.edu//wiki/index.php/EOVSA_Data_Policy for details of our data policy.
===Event images===

Latest revision as of 18:39, 11 November 2024

Introduction

EOVSA observes the full disk of the Sun at all times when the Sun is >10 degrees above the local horizon (season dependent and ranges from 7-12 hours duration centered on 20 UT). EOVSA records data at 451 science frequency channels each second, in four polarization products, as well as additional total flux measurements from each individual antenna. Figure 1 summarizes the different levels of data we produce. The later sections will give a more detailed description and usage examples.

EOVSA pipeline block diagram/flow chart

Level 0 - Raw visibility data from the instrument

As outlined in Figure 1, EOVSA creates raw data products in the left-hand column (labeled Level 0). This includes observations of cosmic sources for phase calibration, and gain and pointing observations required for total power calibration.

Raw "Interim" Database (IDB) visibility data

Full-resolution raw "Interim" Database (IDB) visibility data. They are stored in Miriad format, and hence may not be that useful for most people. Be patient after clicking the link--this is a very long list of directories, one for each available date. Recent data (latest few months) can be retrieved from the following page:

https://www.ovsa.njit.edu/fits/IDB/

For older data, visit the UC/Berkeley hosting page:

https://research.ssl.berkeley.edu/data/eovsa/IDB/

Raw 1-min-averaged visibility data

This is the same as for the IDB data, except with 1-minute time integration applied. This is typically not useful for flares, but is perfectly fine for imaging active regions and full Sun. These data can be retrieved from the following page:

http://www.ovsa.njit.edu/fits/UDB/

Level 0.5 - Calibrated visibility data

After applying calibration and other preliminary processing to the raw (level 0) data, we create the CASA ms’s in the second column in Figure 1 (labeled "level 0.5"). These visibility data are in the Fourier domain of the true images in the plane of the sky and are not immediately ready for spectral imaging analysis yet. However, they have all of the required content to produce images and spectrogram data in standard FITS format (level 1.0). We provide a set of standard ms’s for each day (red boxes in Figure 1), for use by researchers who know how to deal with visibility data. These data are more suitable for experienced users to exploit the full potential of EOVSA data, such as spatially resolved spectral analysis. Processing these data requires CASA or sunCASA (https://github.com/suncasa/suncasa-src). Please refer to our tutorial at EOVSA_Data_Analysis_Tutorial.

Calibrated full-resolution visibility data for flare events

Calibrated and self-calibrated visibility data for flare events (purple boxes in Figure 1) will typically be available within 7 days after they are taken. They will be released at our flare list site soon: https://ovsa.njit.edu/flarelist

Self-calibrated 1-min-averaged visibility data

EOVSA 1-min averaged visibility data in CASA ms format can be retrieved from the following page:

http://www.ovsa.njit.edu/fits/UDBms_slfcaled

Level 1.0 - Images and spectrogram data in standard FITS format

Level 1.0 data are for users who prefer to work with spectrogram (frequency-time) and image data directly, which are also outputs of the pipeline system shown in Figure 1 (orange boxes). They are perfectly suitable to be used as context data for comparison with other multi-wavelength observations but are not (yet) intended for quantitative spatially resolved spectral analysis.

Spectrograms are provided as standard FITS tables containing the frequency list, list of times, and data in both total power (TP) and a sum of amplitudes over intermediate-length baselines (cross power or XP). Likewise, image data products are in FITS format with standard keywords and are converted into the Helioprojective Cartesian coordinate system compatible with the World Coordinate System (WCS) convention, along with correct registration for the spatial, spectral, and temporal coordinates. Both the spectrogram and image data products are calibrated and have physical radio intensity units (sfu for spectrograms and brightness temperature for radio images).

We provide the following level 1 data products:

  • Synoptic products:
    • All-day spectrograms: Full-day total-power (TP) and cross-power (XP) spectrograms (i.e., no spatial resolution) at full spectral and time resolution in FITS format. One file per day.
    • All-day synoptic images: Full disk images at 7 selected frequency bands centered at 1.4, 3.0, 4.5, 6.8, 10.2, 13.9 and 17.0 GHz are produced once per day utilizing the earth-rotation synthesis, calibrated in brightness temperature. This is because EOVSA has a limited number of baselines and we need a long integration to fill up the uv domain in order to make full-disk images.
  • Event-based products:
    • Flare spectrograms: These are full time and frequency resolution spectrograms produced from the median of calibrated cross-power visibilities in FITS format, cropped to cover the flare duration. Preflare background is also subtracted. Since mid-October 2024, we offer both total- and cross-power spectrograms for flare events. Cross-power spectrograms, compared to total-power spectrograms, have the advantage of revealing details of the flare evolution by "filtering out" the large-scale, continuous background from the visibilities. Note that for certain flares that have a large source size, the flux can be lower than its true values (as a fraction of the flux will be "resolved out").
    • Pipeline-produced spectral images: We also have a semi-automated flare imaging pipeline to produce calibrated (and self-calibrated) images at 12-s cadence at up to 10 frequency bands. They are saved in standard FITS format and have been registered into Helioprojective coordinates. They can be read by SSWIDL or astropy/sunpy. These data have already been calibrated to physical units and are usually good to be compared with context data. But please be cautious when using them for quantitative spectral analysis.
Summary of EOVSA Level 1 Data Products
Category Data Product Naming Convention Download Link
Synoptic Spectrograms All-day TP Spectrograms EOVSA_TPall_yyyymmdd.fts https://ovsa.njit.edu/browser
All-day XP Spectrograms EOVSA_XPall_yyyymmdd.fts
Synoptic Images Synoptic 1.4 GHz images eovsa_yyyymmdd.spw00-01.tb.disk.fits
Synoptic 3.0 GHz images eovsa_yyyymmdd.spw02-05.tb.disk.fits
Synoptic 4.5 GHz images eovsa_yyyymmdd.spw06-10.tb.disk.fits
Synoptic 6.8 GHz images eovsa_yyyymmdd.spw11-20.tb.disk.fits
Synoptic 10.2 GHz images eovsa_yyyymmdd.spw21-30.tb.disk.fits
Synoptic 13.9 GHz images eovsa_yyyymmdd.spw31-43.tb.disk.fits
Synoptic 17.0 GHz images eovsa_yyyymmdd.spw44-49.tb.disk.fits
Flare Spectrograms Flare TP Spectrogram eovsa.spec_tp.flare_id_YYYYMMDDHHMM.fits https://ovsa.njit.edu/flarelist
Flare XP Spectrogram eovsa.spec_xp.flare_id_YYYYMMDDHHMM.fits
Flare Spectral Images Pipeline-produced spectral images eovsa.lev1_mbd_12s.YYYY-MM-DDTHHMMSSZ.image.fits

Browsing and Downloading level 1 data

EOVSA Browser
EOVSA Flare List

Synoptic level 1 data

EOVSA Level 1 synoptic data products can be retrieved with the following steps:

  • Go to EOVSA browser page.
  • Browse to the date of interest.
  • Click "synoptic fits" button next to the calendar tool.
  • Select the data product based on the names listed in the table above.


Flare level 1 data

EOVSA flare list with spectrograms and spectral images can be queried and downloaded at https://ovsa.njit.edu/flarelist. Users can use the top box to select a time range of interest and query our flare list. The results are displayed in the dropdown box. An interactive plot of the flare light curves will be shown at the bottom of the page once an event is highlighted (by clicking on the flare ID). Quicklook plots and FITS files of the spectrograms and flare movies can be accessed by clicking the icons in each flare record.

Reading and Using level 1 data

Introduction

All our level 1 data products are in FITS format. All the images have standard, WCS-compatible coordinates. Users can use their favorite method to read these files. In the following, we provide minimal examples to read them with Astropy and Sunpy.

Event-Based Data Products

Synoptic Data Products


Additional examples for IDL users. For spectrograms:

function dspec,filename,doplot=doplot
  ; Read EOVSA Dynamic Spectrum FITS file <filename> and return a spectrogram object.
  ; Optionally show an overview plot if doplot switch is set
  ; 
  ; Usage:
  ;    s = dspec(<filename>)            ; Returns spectrogram object
  ;    s = dspec(<filename>,/doplot)    ; Plots spectrum and returns spectrogram object
  ;
  ; To access the data in the spectrogram object, use
  ;    spec = s.get(/spectrogram)    (Array of amplitudes in SFU, of size ntimes, nfreq)
  ;    fghz = s.get(/spectrum_axis)  (Array of frequencies in GHz, of size nfreq)
  ;    ut = s.get(/time_axis)        (Array of UT times in anytim format, of size ntimes)
  
  default,doplot,0
  spec = mrdfits(filename,0)
  freq = mrdfits(filename,1)
  time = mrdfits(filename,2)
  fghz = freq.sfreq
  ut = anytim(time)
  s = spectrogram(spec,ut,fghz)
  if doplot then begin
    window,/free,xsiz=1024,ysiz=600
    ; Find min and max of data from 5% to 95% of sorted array (eliminates outliers)
    sarr = sort(spec)
    dlim = minmax(spec[sarr[n_elements(sarr)*0.05:n_elements(sarr)*0.95]])
    ; Set drange with margin factor of 2 on low end and 5 on high end
    s.set,drange=dlim*[0.5,5]
    loadct,3
    s.plot,/log,/xsty,/ysty,ytitle='Frequency [GHz]',charsize=1.5
  endif
return,s
end
IDL TPSP.png


For synoptic images:

read_sdo,'eovsa_20191225.spw11-20.tb.disk.fits',header,data,/UNCOMP_DELETE
index2map,header,data,eomap
plot_map,eomap
Eovsa 20191225 image sswidl.jpg

Requesting EOVSA Data or Analysis Assistance

The pipeline-processed synoptic and flare event data (level 1.0) are science-ready and usually sufficient for many purposes. However, the list may not be complete, and the pipeline-processed data do not have the full-time and frequency resolution necessary for certain in-depth quantitative spectral analyses. If you are interested in (1) working on events that are not currently included in our level 1.0 database and/or (2) needing assistance from an EOVSA team member in detailed or quantitative analysis that requires EOVSA data processing beyond that offered by the level 1.0 products, please use the following Data Request Form to submit such requests.

EOVSA data request form

We will normally respond to your request within 2-3 working days. Note that for (1), standard acknowledgments and reference citations would be sufficient. For (2), the EOVSA team member who helped with the data analysis/interpretation needs to be included as a co-author for publications that utilize the relevant EOVSA data. Please refer to https://ovsa.njit.edu//wiki/index.php/EOVSA_Data_Policy for details of our data policy.