HMI_Logo HMI Ring Diagrams
Processing Status

Observables processing status


The following test data series (unarchived, and with all SUMS data now aged off the disc cache) have been removed:
There are sufficient definitive data to allow for the synoptic processing of data for Carrington times 2099:110 – 2104:005. Ring-diagrams synoptic data sets are nearly complete for the period 2100:030 – 2102:005 (3 Sep – 30 Oct). The 15° cfits are missing for 2102:015, and there are two periods when the duty cycle was too low for the 5° charts (see below).

In addition, I have processed the data for the period 2100:360 – 2100:275 (Aug 9–16), corresponding to part of the time when the targte active regions for the next LoHCo workshop were on the disc, and plan to extend the coverage backward in time, following resolution of problems with the data averaging that have come to light.

Note that much of the October data include gaps due to the daily eclipses; duty cycles as low as 80% for some of the 9-hour 5° tiles occur frequently. There was one 9-hour period centered on 2102:230 (12 Oct) during which the duty cycle was below 40%, due to spacecraft rolls. Much of the data from this period could be recovered with special processing, however any period with a duty cycle below 70% is rejected by the normal pipeline. Consequently there will be no 5° data for that period. Other 9-hour periods for which the duty cycle is below the acceptable threshold are 2102:050 (26 Oct) and 2103:290 (4 Nov). The 27-hour duty cycle for 2103:285 (5 Nov) is 68%, slightly below the automatic rejection threshold. Forcing of the 15° processing for that period may be in order.


Definitive processing status

The following series have been processed with archiving of the data products:
hmi.rdV*_fd*
Series# / CRoldestnewestcompletepartial
5° synoptic72 2100:360 (2010.08.10)2102:005 (2010.10.30) 1660
15° synoptic24 2100:360 (2010.08.10)2102:015 (2010.10.29) 551
30° synoptic12 2100:360 (2010.08.10)2102:030 (2010.10.28) 280


Definitive synoptic data products: SUMS Unit Sizes

All of the definitive ring-diagram series have now been published and are available for public (non-team) export from JSOC and also for mirroring by any NetDRMS sites. As discussed before, the data segments for all of these series are archived for various reasons, either the quantity of input data (for averages and tracked data), the computing resources (for ring fits) that would be required to reproduce them, or the expected demand for repeated access (spectra, inversions).

Because of the way the data are processed, it is impossible (or at least useless) to set a unit size of more than 1 for the rdVfitsc*, rdVflows*, and averaged data series, even though the typical segment sizes are very small. Likewise, it is impractical to set a unit size of more than 1 or 2 for the 15° and 30° cubes and tracked spectra because of their large size. The unit sizes I propose are as follows:

In the multi-unit series the records in a given storage directory correspond to the regions in one or a few latitude strips at a given time.

Test processing status

The following series were processed from an earlier test version of the Doppler data. They have been removed and will be replaced with products of test scripts or modules processing definitive Doppler data.
hmi.rdV*_fd*
Series# / CRoldestnewest completepartialnotes
5° synoptic72 2095:170 (2010.04.10)2100:035 (2010.09.03) 28820
15° synoptic24 2095:150 (2010.04.11)2100:045 (2010.09.02) 10313
30° synoptic12 2095:150 (2010.04.11)2100:060 (2010.09.01) 485

Notes on Individual Series

N.B.: none of the listed series are archived. Records from incomplete mosaics for a given analysis time are likely to be removed to make disk cache space. Current usage is about 18 TB for hmi_test.rdVtrack_fd* and 12 TB for hmi_test.rdVpspec_fd*. The fits use a negligible amount of disk space, but may be cleaned to provide consistent and complete record samples (This information has not been updated since the last report)
hmi_test.rdVtrack_fd05
complete: 2098:090–2100:255, 2100:245–2100:035
2100:250 contains only 1524 records
2099:090–2100:315 may be replaced by hmi_test.rdV2pspec_fd05
hmi_test.rdVpspec_fd05
complete: 2098:090–2100:035
missing links: 2100:250 (some)
2099:090–2100:315 may be replaced by hmi_test.rdV2pspec_fd05
hmi_test.rdVfitsf_fd05
complete: 2098:090–065, 2098:055–025, 2098:015–2099:350, 2099:340–2100:255, 2100:245–035
missing links: 2100:250 (some)
incomplete segments: 2098:060, 2098:020, 2099:345 (2747 / 2748 present)
2099:090–2100:340 may be replaced by hmi_test.rdV2fitsf_fd05
hmi_test.rdVfitsc_fd05
complete: 2098:090–065, 2098:055–2100:120, 2100:110–040
missing links: 2100:250 (some)
2100:115 contains only 538 records
2100:035 contains only 1653 records
2099:090, 2099:025–2100:360, and 2100:345 may be replaced by hmi_test.rdV2fitsc_fd05
hmi_test.rdVtrack_fd15
complete: 2098:165–015, 2099:345–2100:045
2099:090–015, and 2100:345 may be replaced by hmi_test.rdV2track_fd15
hmi_test.rdVpspec_fd15
complete: 2098:165–015, 2099:345–2100:045
2099:090–2100:345 may be replaced by hmi_test.rdV2pspec_fd15
hmi_test.rdVfitsf_fd15
complete: 2098:165–015, 2099:345–2100:045
missing links: 2098:180
2099:090–015, and 2100:345 may be replaced by hmi_test.rdV2fitsf_fd15
hmi_test.rdVfitsc_fd15
complete: 2098:165–015, 2099:345–2100:135, 2100:105–045
2099:090, 2099:030–015, and 2100:345 may be replaced by hmi_test.rdV2fitsc_fd15
hmi_test.rdVtrack_fd30
complete: 2099:210–2100:060
2099:090–015, and 2100:345 may be replaced by hmi_test.rdV2track_fd30
hmi_test.rdVpspec_fd30
complete: 2099:210–2100:060
2099:090–2100:360 may be replaced by hmi_test.rdV2pspec_fd30
hmi_test.rdVfitsf_fd30
complete: 2099:210–2100:060
2099:090–2100:360 may be replaced by hmi_test.rdV2fitsf_fd30
hmi_test.rdVfitsc_fd30
complete: 2099:210–2100:150, 2100:090–060

Valid HTML 4.01 Transitional 11 Jan 2011, 09:35-0800
previous report