EOVSA Data and Database System J. McTiernan EOVSA CoDR 25-April-2011

EOVSA data processing: Processes Interim DB (from DPP) L0-L1 (Archive) Process Application DB File DB L1-L2 (Spectro) Process Qlook Spectrogram The L0 Process takes the IDB; does time-dependent calibration, time and frequency averaging and creates the Application database. The L1 Process takes the ADB files, and creates spectrograms for browsing purposes and for use by the data analysis SW. The L2 Process creates an event list of Solar radio Bursts. L2-L3 (Burst) Process Event List

EOVSA data processing: Products Interim DB (from DPP) L0-L1 (Archive) Process Application DB File DB L1-L2 (Spectro) Process Qlook Spectrogram The Application database is the archived database; “Science” data, binned in time and frequency for use by the Data Analysis SW - in MIRIAD format (can also do FITS format if people want to use non-MIRIAD SW). We expect at least three types of datasets, magnetography, bursts, and utility. The File database is a set of files containing information about the time range covered by each Application dataset. L2-L3 (Burst) Process Event List (Not sure if it’s possible to create an event list in an automated process, will start with RHESSI-like process.)

EOVSA data processing: Calibration? Interim DB (from DPP) L0-L1 (Archive) Process Application DB File DB L1-L2 (Spectro) Process Qlook Spectrogram Partial calibration happens in the DPP process, the data are calibrated using a time-independent gain factors. It is expected that this will be useful for simple tasks like spectral generation, but not for maps. The L0 process will analyze calibrator data, then apply or add time-dependent calibration. Post-imaging, more calibration might occur (maybe from “self-cal” or “closure phase output”) and added back into the ADB. L2-L3 (Burst) Process Event List Extra Calibration

EOVSA data processing: Maps Interim DB (from DPP) L0-L1 (Archive) Process Application DB File DB L1-L2 (Spectro) Process Qlook Spectrogram Once we have good calibrations, we can make maps of the Sun. Given a flare list, we can create flare images in some standard frequency bands. Also we will image active regions. Full Sun imaging may also be an option. L2-L3 (Burst) Process Event List Extra Calibration L3-L4 (Image) Process Radio Maps of the Sun,

EOVSA data analysis SW: The EOVSA GUI is an IDL wrapper that will create MIRIAD scripts, which can be run locally or on a dedicated EOVSA server. On initialization, the user chooses an observation time interval, and the dynamic spectrum for that time range is displayed. (Sample is not radio.) The user will have the option of choosing time and frequency ranges graphically, or via pop-up widgets. Other settings, e.g., frequency binning, baseline choices, or frequency masks, are handled by selection widgets. Once the image process is set up, the user presses a button.

EOVSA data analysis SW: Once the “Process” button is clicked, the IDL program generates a series of MIRIAD commands, which are written to a file. If the user has MIRIAD on his system, a process is spawned, and maps are created. If the user has no MIRIAD, then there is an option to upload the command file to our server, which will queue and then run the process. The user can choose to be notified via that his process has been run, or the IDL shell can be configured to automatically look for results. Image maps are saved in (FITS, MIRIAD or FITS or both) format. The EOVSA program will be able to read and display the image files.