<?xml version="1.0" encoding="UTF-8"?>

<Spase xmlns="http://www.spase-group.org/data/schema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.spase-group.org/data/schema http://www.spase-group.org/data/schema/spase-2.4.1.xsd">
  <Version>2.4.1</Version>
  <NumericalData>
    <ResourceID>spase://CNES/NumericalData/CDPP-AMDA/Rosetta/LAP/ros-lap-efl</ResourceID>
    <ResourceHeader>
      <ResourceName>e-field component (EFL)</ResourceName>
      <AlternateName>Electric field component, calculated on ground by

taking the difference between floating probe measurements on both probes and
dividing by distance</AlternateName>

      <ReleaseDate>2019-09-02T11:02:22Z</ReleaseDate>

      <Description>

The two LAP probes could be used to measure the component of the electric field along their 
separation vector, by measuring the voltage of them, taking the difference and dividing by the 
separation distance (5.0 m). Each probe could be fed by a bias current as is typically done on 
electric field instruments in tenuous plasmas, or be disconnected from the bias circuitry to 
ensure a good zero bias current (floating probes) as is typically done on sounding rockets.  
Bias currents were used in the early part of the mission, but when the comet ionosphere 
developed, the floating mode was found to give much more consistent data. Only data from 
the floating mode have been used for providing E-field data, and only when both probes are 
sunlit.

Positive value refers to electric field  pointing in the direction from probe 1 to probe 2.
 
The booms are not equal in length (2.24 and 1.62 m) and mounted on a big spacecraft (solar 
panel wingspan 32 m), so one cannot expect LAP to provide a useful DC electric field estimate. 
A moving average of the E-field over 32 s is therefore subtracted from the data in the EFL files. 
The effective bandwidth of the data therefore is about 0.03 Hz to 20 Hz, the upper 
limit set by the analog anti-aliasing filters. Note that the filtering may distort the lowest 
frequencies. 

There are no external comparison data for assessing the absolute accuracy of the LAP E-field 
measurements. The data themselves look very clean and well behaved [Karlsson et al., 2017; 
André et al, 2017], with very little of common mode signal remaining, despite the s/c poten tial 
being both high and highly variable. The technique with floating probes is proven on numerous 
sounding rockets in the terrestrial ionosphere [Maynard, 1998].

This is a preliminary data set which will be replaced by another in a few months.
</Description>

      <Contact>
        <PersonID>spase://CNES/Person/CDPP-AMDA/Anders.Eriksson</PersonID>
        <Role>PrincipalInvestigator</Role>
      </Contact>
      <Contact>
        <PersonID>spase://CNES/Person/CDPP-AMDA/Erik.Johansson</PersonID>
        <Role>DataProducer</Role>
      </Contact>
      <InformationURL>
        <Name>RPC User Guide</Name>
        <URL>http://amda.irap.omp.eu/help/parameters/RPC_USER_GUIDE.PDF</URL>
      </InformationURL>
      <InformationURL>
        <Name>RPC LAP User Guide</Name>
        <URL>http://amda.irap.omp.eu/help/parameters/RO-IRFU-LAP-UG.PDF</URL>
      </InformationURL>
      <InformationURL>
        <Name>RPC-LAP to Planetary Science Archive Interface Control Document</Name>
        <URL>http://amda.irap.omp.eu/help/parameters/RO-IRFU-LAP-EAICD.PDF</URL>
      </InformationURL>
      <InformationURL>
        <Name>RPC-LAP Report on cross-calibration of LAP data to measurements by other RPC instruments</Name>
        <URL>http://amda.irap.omp.eu/help/parameters/RO-IRFU-LAP-XCAL_1_0_PDF_A-1b.PDF</URL>
      </InformationURL>
    </ResourceHeader>
    <AccessInformation>

      <RepositoryID>spase://SMWG/Repository/CDPP/AMDA</RepositoryID>
      <Availability>Online</Availability>
      <AccessRights>Open</AccessRights>
      <AccessURL>
        <Name>CDPP/AMDA HAPI Server</Name>

        <URL>https://amda.irap.omp.eu/service/hapi</URL>

        <Style>HAPI</Style>

        <ProductKey>ros-lap-efl</ProductKey>

        <Description>Web Service to this product using the HAPI interface.</Description>
      </AccessURL>
      <Format>CSV</Format>

      <Acknowledgement>Thank you for acknowledging the use of AMDA in publications with wording like "Data analysis was performed with the AMDA science analysis system provided by the Centre de Données de la Physique des Plasmas (CDPP) supported by CNRS, CNES, Observatoire de Paris and Université Paul Sabatier, Toulouse". See the Rules of the road at https://amda.cdpp.eu/help/policy.html . Please acknowledge the Data Providers.</Acknowledgement>

    </AccessInformation>

    <AccessInformation>

      <RepositoryID>spase://SMWG/Repository/CDPP/AMDA</RepositoryID>
      <Availability>Online</Availability>
      <AccessRights>Open</AccessRights>
      <AccessURL>
        <Name>CDPP/AMDA Web application</Name>

        <URL>https://amda.cdpp.eu</URL>

        <Description>Access to Data via CDPP/AMDA Web application.</Description>
      </AccessURL>
      <Format>CSV</Format>
      <Format>VOTable</Format>
      <Format>CDF</Format>
      <Format>PNG</Format>

      <Acknowledgement>Thank you for acknowledging the use of AMDA in publications with wording like "Data analysis was performed with the AMDA science analysis system provided by the Centre de Données de la Physique des Plasmas (CDPP) supported by CNRS, CNES, Observatoire de Paris and Université Paul Sabatier, Toulouse". See the Rules of the road at https://amda.cdpp.eu/help/policy.html . Please acknowledge the Data Providers.</Acknowledgement>

    </AccessInformation>

    <ProviderName>PSA</ProviderName>
    <ProviderResourceName>RO-C-RPCLAP-5-xxx-DERIV2-V1.0</ProviderResourceName>
    <InstrumentID>spase://CNES/Instrument/CDPP-AMDA/Rosetta/LAP</InstrumentID>
    <MeasurementType>ThermalPlasma</MeasurementType>
    <TemporalDescription>
      <TimeSpan>
        <StartDate>2015-05-20T15:17:20Z</StartDate>
        <StopDate>2016-09-30T10:30:20Z</StopDate>
      </TimeSpan>
      <CadenceMin>PT0.05S</CadenceMin>
      <CadenceMax>PT35S</CadenceMax>
    </TemporalDescription>
    <Caveats>Sampling config : Value | Averaged Samples | DownSampling Rate

           *   0  |   1    |   1
           *   1  |   2    |   1 
           *   2  |   2    |   2
           *   3  |   4    |   4
           *   4  |  64    |   4
           *   5  |  32    |  32        
           *   6  |  64    |  32
           *   7  |  64    |  64
           *   8  | 128    | 128
           *   9  | 256    | 256
           
           Quality Flag : 
           
           A quality flag is a (base 10) integer that is constructed in the two steps below:
           * Add together the constants associated with the relevant quality-related effects listed below. Note that these constants are chosen such that every digit represents up to three true/false values for the presence/absence of three specific separate quality-related effects.
           * Should the three quality-related effects be irrelevant for the given data product, then that digit is replaced by the digit “9”.
           
           Quality flag event description :
           * +1 - Low quality sweep analysis model fit
           * +2 - One of two meanings: (1) Low sample size; an average is based on fewer data points than nominal (due to filtering or otherwise) and applies to sweep steps and downsampled time series. (2) zero-padding; zeros replace lost samples for the purpose of calculating PSD.
           * +10 - One of two meanings: (1) Sweep data product and data products based on sweeps: SAA rotation of more than 0.05° during sweep. (2) Downsampled time series data product: Bias change within the 32 s downsampling period.
           * +20 - Probe in partial or full shadow
           * +100 - Rosetta wheel off-loading (WOL) or Orbit-control-maneuver (OCM)
           * +200 - One of two meanings: (1) For LAP1: LDL disturbance (LAP2 in LDL mode); (2) For LAP2: Contamination signature possibly present
           * +400 - Saturation
           
           Example: suppose that one encounters the quality flag “109”. 109 = 100 + 9 means (1) that there is an ongoing wheel off-loading (+100), and (2) that the quality-related effects associated with +1 and +2 cannot occur even in principle for the kind of data that one is looking at.                               
        </Caveats>

    <Parameter>
      <Name>e-field comp</Name>
      <ParameterKey>ros_lap_efl</ParameterKey>
      <Description>Electric field component, calculated on ground by 

                taking the difference between floating probe measurements on both probes and 
                dividing by distance, (V_P2-V_P1)/L. Positive value refers to electric field 
                pointing in the direction from probe 1 to probe 2.</Description>

      <Units>mV/m</Units>
      <RenderingHints>
        <DisplayType>TimeSeries</DisplayType>
      </RenderingHints>
      <FillValue>-1.e+09</FillValue>
      <Field>
        <Qualifier>Scalar</Qualifier>
        <FieldQuantity>Electric</FieldQuantity>
      </Field>
    </Parameter>
    <Parameter>
      <Name>sampling conf</Name>
      <ParameterKey>ros_lap_efl_s</ParameterKey>
      <Description>Number that describes the exact combination of onboard s/w averaging and downsampling. The exact values are pointers into a table 

that describes both the number of samples that are averaged over and the downsampling rate</Description>

      <RenderingHints>
        <DisplayType>TimeSeries</DisplayType>
      </RenderingHints>
      <Support>
        <SupportQuantity>Other</SupportQuantity>
      </Support>
    </Parameter>
    <Parameter>
      <Name>quality flag</Name>
      <ParameterKey>ros_lap_efl_f</ParameterKey>
      <Description>Quality flag constructed as the sum of multiple terms, depending on what quality related effects are present. Each digit is either in 

the range 0 (best) to 7 (worst), or 9 (not used).</Description>

      <RenderingHints>
        <DisplayType>TimeSeries</DisplayType>
      </RenderingHints>
      <Support>
        <SupportQuantity>Other</SupportQuantity>
      </Support>
    </Parameter>
  </NumericalData>

</Spase>