spase://CNES/NumericalData/CDPP-Archive/Cluster-4/RAPID/CLU_PP_C4_RAP

This data set contains the Cluster 4 RAPID Prime Parameters (spin averaged) : omni-directional particle fluxes in two energy ranges for 4 species, plus field-aligned anisotropies for protons and electrons. Caveats The calibration data applied are the most reasonable for a quick and standardised calculation of the particle fluxes. They do not attempt to include cross-calibrations among the spacecraft, since these are extremely complicated, requiring case-by-case analysis. Thus the same geometry factors are applied to all 4 RAPID units. However, the energy thresholds are slightly different, but a spectral analysis correction brings them all to a uniform set of values. Since this correction is applied automatically, it is prone to error. The restrictions on the interpretation of the anisotropy values have already been mentioned. Furthermore, due to a programming error in the RAPID on-board computer, the magnetic field was incorrectly processed during the first months of operations. This problem was corrected on April 26, 2001 on spacecraft 3, and on May 18, 2001 on the other spacecraft. Up until these times, the anisotropies contain only fill values. It must be pointed out that the helium and heavy ion fluxes are measured and read out every 4 spins, and not every spin as for protons and electrons. This is consistent with their expected lower count rates. However, since the PPDB deliver data for every spin, it has been decided to fill in the intervening spins with repeated helium and heavy ion data. This accurately reflects the true situation, since the delivered fluxes are indeed averages over these four spins. Due to another programming bug, the helium and heavy ion fluxes were in fact only measured every 8 spins: every second set of 4-spin data simply repeated the previous measurement. This too was corrected at the same time as the anisotropy bug mentioned above. During operations it has been discovered that the RAPID DPU can be spontaneously reset, for reasons which are still unclear. This in itself is not harmful, however it does mean that the high voltage supply is turned off (resulting in a loss of ion data) and that the program patches of April 26 and May 18, 2001, are no longer activated. After this was discovered (February 2001) a procedure was built into the standard commanding sequences to regularly correct both these problems. A caveat is written into the CDF files to indicate when this happens. A more serious problem is the corruption of the new patches when RAPID is temporarily turned off. This corruption becomes noticeable on the next turn-on and results in the immediate deactivation of the patches. The high voltage supply remains on, so ion data are accumulated, however the problems with the anisotropy and helium/heavy ion sampling return. Furthermore, the electron energy thresholds revert to default values that are totally unrealistic, resulting in loss of these data. This situation remains in effect until the patches are manually reloaded by Operations, which can be several days later. Caveats are written to the CDF files to indicate this. The central ion detector head has been badly hit by sunlight. For details on this and any other caveat information, please consult the RAPID home page (http://www2.mps.mpg.de/dokumente/projekte/cluster/rapid/Rapid_Userguide.pdf).