solo-mag-8s.xml
10.4 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
<?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/Solar_Orbiter/MAG/solo-mag-8s</ResourceID>
<ResourceHeader>
<ResourceName>LL (Low Latency)</ResourceName>
<AlternateName>Low Latency Magnetic Field : Not for Publication</AlternateName>
<DOI>10.1026/1234567</DOI>
<ReleaseDate>2023-02-14T04:25:04Z</ReleaseDate>
<Description>LL02 : Level 2 Low Latency Data : Not For Publication
The MAG Low Latency data are a useful resource but should be used with caution:
they contain many artificial signals, are not of a high enough quality to undertake
science analysis and results derived from them should not submitted for publication.
Routine processing of the MAG data on the ground removes the vast majority of these signals but the
automated nature of the pipeline at ESA/ESAC means that this cannot be applied to the Low Latency data stream.
The MAG team intends to provide a cleaned version of the MAG data in the near future which should be used in
preference to the Low Latency data. We also expect to release full science-quality level 2 data products to the
ESA archive from September 2020.</Description>
<Contact>
<PersonID>spase://CNES/Person/CDPP-AMDA/Tim.Horbury</PersonID>
<Role>PrincipalInvestigator</Role>
</Contact>
<InformationURL>
<Name>Low Latency Data</Name>
<URL>https://www.cosmos.esa.int/web/solar-orbiter/access-to-solar-orbiter-low-latency-data</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>http://amda.irap.omp.eu/service/hapi</URL>
<Style>HAPI</Style>
<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 http://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>http://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 http://amda.cdpp.eu/help/policy.html. Please acknowledge the Data Providers.</Acknowledgement>
</AccessInformation>
<ProviderName>http://soar.esac.esa.int/soar</ProviderName>
<ProviderResourceName>SOLO_LL02_mag</ProviderResourceName>
<InstrumentID>spase://CNES/Instrument/CDPP-AMDA/Solar_Orbiter/MAG</InstrumentID>
<MeasurementType>MagneticField</MeasurementType>
<TemporalDescription>
<TimeSpan>
<StartDate>2020-06-03T14:28:15Z</StartDate>
<StopDate>2023-02-13T20:49:37Z</StopDate>
</TimeSpan>
<Cadence>PT8S</Cadence>
</TemporalDescription>
<ObservedRegion>Heliosphere.Inner</ObservedRegion>
<ObservedRegion>Sun.Corona</ObservedRegion>
<Caveats>The MAG team has not had the opportunity to assess the reliability of the data
processing pipeline for Low Latency flight data, so we cannot vouch for the reliability or accuracy of this processing.
In addition, the MAG data contain artificial signals covering a wide range of timescales and magnitudes, none of which
are predictable at this time:
* MAG heater signal up to 1nT in amplitude, typically lasts one minute and occurs every 10-20 minutes. This is the most visible signature in the data.
* Varying spacecraft offsets spacecraft fields can vary over long timescales (weeks or more) by up to several nT. Since these can only be determined after the fact, that are not corrected in the Low Latency data. Some changes can also be rapid, such as those due to solar array movements.
* Spacecraft-operated heaters over 50 heaters operate on the spacecraft and switch off and on unpredictably to keep various components within their required temperature range. Their total contribution to the field at the sensor location is around 0.5 nT but variations due to the total field are more common at around the 0.1 nT level.
* Thruster firings these occur up to once a day, last up to several minutes, and have amplitudes up to 0.2 nT.
* Operation of other instruments fields due to the currents from other instruments, and sharper variations due to mechanism movements, can also be present in the data. The MAG team are still quantifying these fields but the total field due to the operation of the payload is around 0.5 nT. Note that the majority of the power is consumed by remote sensing instruments, which are not operated continuously, so these fields can vary.
* Operation of SWA/EAS we have evidence that operation of the electron sensor at the end of the instrument boom introduces signals into the MAG data at the 0.1 nT level but these have not yet been quantified in detail.</Caveats>
<Parameter>
<Name>b_rtn</Name>
<ParameterKey>solo_b_rtn_8s</ParameterKey>
<UCD>phys.magField</UCD>
<Units>nT</Units>
<UnitsConversion>1e-9>T</UnitsConversion>
<CoordinateSystem>
<CoordinateRepresentation>Cartesian</CoordinateRepresentation>
<CoordinateSystemName>RTN</CoordinateSystemName>
</CoordinateSystem>
<RenderingHints>
<DisplayType>TimeSeries</DisplayType>
</RenderingHints>
<Structure>
<Size>3</Size>
<Element>
<Name>br</Name>
<Qualifier>Component.I</Qualifier>
<Index>1</Index>
<ParameterKey>solo_b_rtn_8s(0)</ParameterKey>
</Element>
<Element>
<Name>bt</Name>
<Qualifier>Component.J</Qualifier>
<Index>2</Index>
<ParameterKey>solo_b_rtn_8s(1)</ParameterKey>
</Element>
<Element>
<Name>bn</Name>
<Qualifier>Component.K</Qualifier>
<Index>3</Index>
<ParameterKey>solo_b_rtn_8s(2)</ParameterKey>
</Element>
</Structure>
<Field>
<Qualifier>Vector</Qualifier>
<Qualifier>Component.I</Qualifier>
<Qualifier>Component.J</Qualifier>
<Qualifier>Component.K</Qualifier>
<FieldQuantity>Magnetic</FieldQuantity>
</Field>
</Parameter>
<Parameter>
<Name>b_srf</Name>
<ParameterKey>solo_b_srf_8s</ParameterKey>
<UCD>phys.magField</UCD>
<Units>nT</Units>
<UnitsConversion>1e-9>T</UnitsConversion>
<RenderingHints>
<DisplayType>TimeSeries</DisplayType>
</RenderingHints>
<Structure>
<Size>3</Size>
<Element>
<Name>bx</Name>
<Qualifier>Component.I</Qualifier>
<Index>1</Index>
<ParameterKey>solo_b_srf_8s(0)</ParameterKey>
</Element>
<Element>
<Name>by</Name>
<Qualifier>Component.J</Qualifier>
<Index>2</Index>
<ParameterKey>solo_b_srf_8s(1)</ParameterKey>
</Element>
<Element>
<Name>bz</Name>
<Qualifier>Component.K</Qualifier>
<Index>3</Index>
<ParameterKey>solo_b_sr_8s(2)</ParameterKey>
</Element>
</Structure>
<Field>
<Qualifier>Vector</Qualifier>
<Qualifier>Component.I</Qualifier>
<Qualifier>Component.J</Qualifier>
<Qualifier>Component.K</Qualifier>
<FieldQuantity>Magnetic</FieldQuantity>
</Field>
</Parameter>
<Parameter>
<Name>|b|</Name>
<ParameterKey>solo_b_tot_8s</ParameterKey>
<Description>Magnetic field magnitude</Description>
<UCD>phys.magField</UCD>
<Units>nT</Units>
<UnitsConversion>1e-9>T</UnitsConversion>
<RenderingHints>
<DisplayType>TimeSeries</DisplayType>
</RenderingHints>
<Structure>
<Size>1</Size>
</Structure>
<Field>
<FieldQuantity>Magnetic</FieldQuantity>
</Field>
</Parameter>
<Parameter>
<Name>phi</Name>
<ParameterKey>solo_b_rtn_8s_phi</ParameterKey>
<Description>Magnetic field phi angle</Description>
<UCD>phys.magField</UCD>
<Units>degrees</Units>
<UnitsConversion>1e-9&gt;T</UnitsConversion>
<RenderingHints>
<DisplayType>TimeSeries</DisplayType>
</RenderingHints>
<Structure>
<Size>1</Size>
</Structure>
<Field>
<FieldQuantity>Magnetic</FieldQuantity>
</Field>
</Parameter>
<Parameter>
<Name>theta</Name>
<ParameterKey>solo_b_rtn_8s_theta</ParameterKey>
<Description>Magnetic field theta angle</Description>
<UCD>phys.magField</UCD>
<Units>degrees</Units>
<UnitsConversion>1e-9&gt;T</UnitsConversion>
<RenderingHints>
<DisplayType>TimeSeries</DisplayType>
</RenderingHints>
<Structure>
<Size>1</Size>
</Structure>
<Field>
<FieldQuantity>Magnetic</FieldQuantity>
</Field>
</Parameter>
</NumericalData>
</Spase>