spectral range for VIRGO data

[rick]

In the registry there are several spectral ranges for VIRGO data. It is not completely clear to me, but it looks like the multispectral data are bundled together in FITS tables. Thus, each data record should in principle match all of the spectral ranges listed in the registry. But it looks like the VIRGO data do not much any selected spectral range. They all say N/A for minimum and maximum wavelength.

[joe]

I think this is another one of the artifacts from how the SOHO data is cataloged in our database:

SQL> select count(*),wavemin,wavemax,id_wave_unit from observation
where id_instrume=12 group by wavemin,wavemax,id_wave_unit;

  COUNT(*)    WAVEMIN    WAVEMAX ID_WAVE_UNIT
---------- ---------- ---------- ------------
     18084                                  8

I'll talk to Joe and George about what types of queries should match the VIRGO data, and either fix the entries in the database, or provide a hack like I did for the LASCO data, so it'll override the database's rules for matching.

[gurman]

VIRGO has (in addition to housekeeping and helioseismology) three kinds of irradiance data: two from total solar irradiance (TSI) detectors (DIARAD and PMO) and one from a spectral irradiance data instrument (SPM). I'm not certain how we characterize TSI in terms of wavelength in our current or any future data model; indeed, for something that integrates all radiant energy at all wavelengths from the visible hemisphere of the Sun, perhaps there shouldn't be a response to searches on wavelength. Rick?

The SPM FITS files indicate wavelength ranges called 862, 500, and 402 (those are in nm, Joe, so they correspond to 8620, 5000, and 4020 ?). The instrument homepage refers to an unpublished document for further reference, but does state that each filter is about 5 nm (50 ?) wide, apparently centere don those reference wavelengths.