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
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
|
.. doctest-skip-all
.. _sunpy-tutorial-acquiring-data-jsoc:
**************************************
Finding and Downloading Data from JSOC
**************************************
Joint Science Operations Center (JSOC) contains data products from the Solar Dynamics Observatory, as well as certain other missions and instruments.
These data are available from the JSOC database, which can be directly accessed by the online `JSOC interface <http://jsoc.stanford.edu/ajax/lookdata.html>`__.
sunpy's JSOC Client provides an easier interface to query for JSOC data and make export requests.
It uses `drms module <https://docs.sunpy.org/projects/drms>`__ as its backend.
There are two ways of downloading JSOC data.
One way is using sunpy's unified search interface, known as ``Fido``.
``Fido`` supplies a single, easy and consistent way to to obtain most forms of solar physics data.
An alternative way to fetch data from JSOC is by using the underlying JSOC Client.
This option can be preferred when you need to separate the staging and downloading steps, which is not supported by Fido.
The JSOC stages data before you can download it, so a JSOC query is a three stage process.
First you query the JSOC for records and a table of these records is returned.
Then you can request these records to be staged for download and then you can download them.
Fido combines the last two stages into a single call to `~sunpy.net.fido_factory.UnifiedDownloaderFactory.fetch`.
Setup
=====
sunpy's Fido module is in `sunpy.net`.
It can be imported as follows:
.. code-block:: python
>>> from sunpy.net import Fido, attrs as a
The JSOC client handles the particulars of how the data from the data provider is downloaded to your computer.
.. warning::
You must have an email address registered with JSOC before you are allowed to make a request.
`See this <http://jsoc.stanford.edu/ajax/register_email.html>`__ to register your email address.
Querying the JSOC
=================
To search for data in JSOC, your query needs at minimum, a "Series" name and a "PrimeKey".
.. code-block:: python
>>> print(a.jsoc.Series)
sunpy.net.jsoc.attrs.Series
<BLANKLINE>
The JSOC Series to Download.
<BLANKLINE>
Attribute Name Client ... Description
---------------------------------- ------ ... --------------------------------------------------------------------------------
aia_flatfield JSOC ... AIA flatfield
aia_lev1 JSOC ... AIA Level 1
aia_lev1_euv_12s JSOC ... AIA Level 1, 12 second cadence
aia_lev1_uv_24s JSOC ... AIA Level 1, 24 second cadence
aia_lev1_vis_1h JSOC ... AIA Level 1, 3600 second cadence
aia_master_pointing3h JSOC ... Master Pointing Parameters
aia_response JSOC ... AIA instrument response table
aia_temperature_summary_300s JSOC ... Temperature Statistics from AIA Housekeeping - Thermal Packet
...
Different PrimeKeys are supported by different Series, and you can find out the PrimeKeys supported in any Series by:
.. code-block:: python
>>> import drms
>>> client = drms.Client() # doctest: +REMOTE_DATA
>>> print(client.pkeys('hmi.m_720s')) # doctest: +REMOTE_DATA
['T_REC', 'CAMERA']
The most common PrimeKey, that is supported by every Series is Time, that is denoted by ``T_REC`` or ``T_OBS``.
Hence, Time can always be passed as an attribute while building a query.
Wavelength is another pre-defined attribute which is a PrimeKey.
Other PrimeKeys which need to be passed should be manually passed in `~sunpy.net.jsoc.attrs.PrimeKey`.
This will be explained later in this tutorial.
Constructing a Basic Query
--------------------------
Let's start with a very simple query.
We could ask for all "hmi.v_45s" series data between January 1st 2014 from 00:00 to 01:00:
.. code-block:: python
>>> res = Fido.search(a.Time('2014-01-01T00:00:00', '2014-01-01T01:00:00'),
... a.jsoc.Series('hmi.v_45s')) # doctest: +REMOTE_DATA
This returns an `~sunpy.net.fido_factory.UnifiedResponse` object containing information on the available online files which fit the criteria specified by the attrs objects in the above call.
It does not download the files.
To see a summary of results of our query, simply type the name of the variable set to the Fido search, in this case, ``res``:
.. code-block:: python
>>> res # doctest: +REMOTE_DATA
<sunpy.net.fido_factory.UnifiedResponse object at ...>
Results from 1 Provider:
<BLANKLINE>
81 Results from the JSOCClient:
Source: http://jsoc.stanford.edu
<BLANKLINE>
T_REC TELESCOP INSTRUME WAVELNTH CAR_ROT
----------------------- -------- ---------- -------- -------
2014.01.01_00:00:45_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:01:30_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:02:15_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:03:00_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:03:45_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:04:30_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:05:15_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:06:00_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:06:45_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:07:30_TAI SDO/HMI HMI_FRONT2 6173.0 2145
... ... ... ... ...
2014.01.01_00:54:00_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:54:45_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:55:30_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:56:15_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:57:00_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:57:45_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:58:30_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:59:15_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_01:00:00_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_01:00:45_TAI SDO/HMI HMI_FRONT2 6173.0 2145
Length = 81 rows
<BLANKLINE>
<BLANKLINE>
Now, let's break down the arguments of ``Fido.search`` to understand better what we've done.
The first argument ``a.Time('2014-01-01T00:00:00', '2014-01-01T01:00:00')`` sets the start and end times for the query (any date/time format understood by sunpy's `~sunpy.time.parse_time` can be used to specify dates and time).
The Time attribute takes UTC time, as default.
If you need to pass a Time in some other time scale, such as TAI, pass an `astropy.time.Time` object:
.. code-block:: python
>>> import astropy.time
Then, the Time attribute can be passed as:
.. code-block:: python
>>> a.Time(astropy.time.Time('2014-01-01T00:00:00', scale='tai'), astropy.time.Time('2014-01-01T01:00:00', scale='tai'))
<sunpy.net.attrs.Time(2014-01-01 00:00:00.000, 2014-01-01 01:00:00.000)>
The second argument:
.. code-block:: python
>>> a.jsoc.Series('hmi.v_45s')
<sunpy.net.jsoc.attrs.Series(hmi.v_45s: Dopplergrams with a cadence of 45 seconds) object ...>
sets the series we are looking for.
So what is going on here?
The notion is that a JSOC query has a set of attribute objects, imported as ``a.jsoc``, that are specified to construct the query.
``a.jsoc.Series()`` is compulsory to be provided in each of the jsoc queries.
Apart from this, at least one PrimeKey must be passed (generally ``a.Time()``).
Querying with other PrimeKeys
-----------------------------
Other than Time, one other PrimeKey is supported with in-built attribute.
In case of AIA series, ``a.Wavelength()`` can be passed as a PrimeKey:
.. code-block:: python
>>> import astropy.units as u
>>> res = Fido.search(a.Time('2014-01-01T00:00:00', '2014-01-01T01:00:00'),
... a.jsoc.Series('aia.lev1_euv_12s'),
... a.Wavelength(304*u.AA)) # doctest: +REMOTE_DATA
Note that, only Time and Wavelength are in-built attributes here.
If you need to pass any other PrimeKey, it should be passed like this:
.. code-block:: python
>>> a.jsoc.PrimeKey('HARPNUM', '4864')
<sunpy.net.jsoc.attrs.PrimeKey object at ...>
('HARPNUM', '4864')
If 2 or more PrimeKeys need to be passed together:
.. code-block:: python
>>> a.jsoc.PrimeKey('HARPNUM', '4864') & a.jsoc.PrimeKey('CAMERA', '2')
<AttrAnd([<sunpy.net.jsoc.attrs.PrimeKey object at ...>
('HARPNUM', '4864'), <sunpy.net.jsoc.attrs.PrimeKey object at ...>
('CAMERA', '2')])>
Also, note that the pre-defined PrimeKeys, Time and Wavelength can also be passed as above, but you need to specify the exact keyword for it:
.. code-block:: python
>>> a.Time('2014-01-01T00:00:00', '2014-01-01T01:00:00'), a.jsoc.PrimeKey('WAVELNTH', '161')
(<sunpy.net.attrs.Time(2014-01-01 00:00:00.000, 2014-01-01 01:00:00.000)>, <sunpy.net.jsoc.attrs.PrimeKey object at ...>
('WAVELNTH', '161'))
If the correct keyword is not specified, or the passed PrimeKey is not supported by the given series, a meaningful error will be thrown, which will give you the PrimeKeys supported by that series.
Hence, by looking at the error, one can easily retry building the query with correct PrimeKeys.
Another important thing to note is that, Wavelength when passed through in-built attribute, should be passed as an astropy quantity.
Specifying spectral units in arguments is necessary or an error will be raised.
For more information on units, see `~astropy.units`.
But, when the same is passed through PrimeKey attribute, it should be passed as a string.
All other PrimeKey values passed through PrimeKey attribute, must be passed as a string.
Manually specifying keyword data to fetch
-----------------------------------------
Upon doing ``Fido.search()`` as described above, only a limited set of keywords are returned in the response object.
These default keywords are ``'DATE'``, ``'TELESCOP'``, ``'INSTRUME'``, ``'T_OBS'`` and ``'WAVELNTH'``.
If you want to get a manual set of keywords in the response object, you can pass the set of keywords using :meth:`~sunpy.net.base_client.QueryResponseTable.show` method.
.. code-block:: python
>>> res = Fido.search(a.Time('2014-01-01T00:00:00', '2014-01-01T01:00:00'),
... a.jsoc.Series('hmi.v_45s')) # doctest: +REMOTE_DATA
>>> res.show('TELESCOP', 'INSTRUME', 'T_OBS') # doctest: +REMOTE_DATA
<sunpy.net.fido_factory.UnifiedResponse object at ...>
Results from 1 Provider:
<BLANKLINE>
81 Results from the JSOCClient:
Source: http://jsoc.stanford.edu
<BLANKLINE>
TELESCOP INSTRUME T_OBS
-------- ---------- -----------------------
SDO/HMI HMI_FRONT2 2014.01.01_00:00:37_TAI
SDO/HMI HMI_FRONT2 2014.01.01_00:01:22_TAI
SDO/HMI HMI_FRONT2 2014.01.01_00:02:07_TAI
SDO/HMI HMI_FRONT2 2014.01.01_00:02:52_TAI
SDO/HMI HMI_FRONT2 2014.01.01_00:03:37_TAI
SDO/HMI HMI_FRONT2 2014.01.01_00:04:22_TAI
SDO/HMI HMI_FRONT2 2014.01.01_00:05:07_TAI
SDO/HMI HMI_FRONT2 2014.01.01_00:05:52_TAI
SDO/HMI HMI_FRONT2 2014.01.01_00:06:37_TAI
SDO/HMI HMI_FRONT2 2014.01.01_00:07:22_TAI
... ... ...
SDO/HMI HMI_FRONT2 2014.01.01_00:53:52_TAI
SDO/HMI HMI_FRONT2 2014.01.01_00:54:37_TAI
SDO/HMI HMI_FRONT2 2014.01.01_00:55:22_TAI
SDO/HMI HMI_FRONT2 2014.01.01_00:56:07_TAI
SDO/HMI HMI_FRONT2 2014.01.01_00:56:52_TAI
SDO/HMI HMI_FRONT2 2014.01.01_00:57:37_TAI
SDO/HMI HMI_FRONT2 2014.01.01_00:58:22_TAI
SDO/HMI HMI_FRONT2 2014.01.01_00:59:07_TAI
SDO/HMI HMI_FRONT2 2014.01.01_00:59:52_TAI
SDO/HMI HMI_FRONT2 2014.01.01_01:00:37_TAI
Length = 81 rows
<BLANKLINE>
<BLANKLINE>
Passing an incorrect keyword won't throw an error, but the corresponding column in the table will not be displayed.
To display all of the columns, we can use ``show()`` without passing any arguments:
.. code-block:: python
>>> res.show() # doctest: +REMOTE_DATA
<sunpy.net.fido_factory.UnifiedResponse object at ...>
Results from 1 Provider:
<BLANKLINE>
81 Results from the JSOCClient:
Source: http://jsoc.stanford.edu
<BLANKLINE>
DATE DATE__OBS DATE-OBS ... CODEVER3 CALVER64
-------------------- ----------------------- ----------------------- ... ------------------------------------------------------ --------
2014-01-05T17:46:02Z 2013-12-31T23:59:39.20Z 2013-12-31T23:59:39.20Z ... $Id: polcal.c,v 1.5 2013/12/22 22:54:08 couvidat Exp $ 4370
2014-01-05T17:47:10Z 2014-01-01T00:00:24.20Z 2014-01-01T00:00:24.20Z ... $Id: polcal.c,v 1.5 2013/12/22 22:54:08 couvidat Exp $ 4370
2014-01-05T17:48:18Z 2014-01-01T00:01:09.20Z 2014-01-01T00:01:09.20Z ... $Id: polcal.c,v 1.5 2013/12/22 22:54:08 couvidat Exp $ 4370
2014-01-05T17:49:25Z 2014-01-01T00:01:54.20Z 2014-01-01T00:01:54.20Z ... $Id: polcal.c,v 1.5 2013/12/22 22:54:08 couvidat Exp $ 4370
2014-01-05T17:50:34Z 2014-01-01T00:02:39.20Z 2014-01-01T00:02:39.20Z ... $Id: polcal.c,v 1.5 2013/12/22 22:54:08 couvidat Exp $ 4370
2014-01-05T17:51:42Z 2014-01-01T00:03:24.20Z 2014-01-01T00:03:24.20Z ... $Id: polcal.c,v 1.5 2013/12/22 22:54:08 couvidat Exp $ 4370
2014-01-05T17:52:50Z 2014-01-01T00:04:09.20Z 2014-01-01T00:04:09.20Z ... $Id: polcal.c,v 1.5 2013/12/22 22:54:08 couvidat Exp $ 4370
2014-01-05T17:53:59Z 2014-01-01T00:04:54.20Z 2014-01-01T00:04:54.20Z ... $Id: polcal.c,v 1.5 2013/12/22 22:54:08 couvidat Exp $ 4370
2014-01-05T17:55:08Z 2014-01-01T00:05:39.20Z 2014-01-01T00:05:39.20Z ... $Id: polcal.c,v 1.5 2013/12/22 22:54:08 couvidat Exp $ 4370
2014-01-05T17:56:16Z 2014-01-01T00:06:24.20Z 2014-01-01T00:06:24.20Z ... $Id: polcal.c,v 1.5 2013/12/22 22:54:08 couvidat Exp $ 4370
... ... ... ... ... ...
2014-01-05T17:35:43Z 2014-01-01T00:52:54.20Z 2014-01-01T00:52:54.20Z ... $Id: polcal.c,v 1.5 2013/12/22 22:54:08 couvidat Exp $ 4370
2014-01-05T17:36:54Z 2014-01-01T00:53:39.20Z 2014-01-01T00:53:39.20Z ... $Id: polcal.c,v 1.5 2013/12/22 22:54:08 couvidat Exp $ 4370
2014-01-05T17:38:01Z 2014-01-01T00:54:24.20Z 2014-01-01T00:54:24.20Z ... $Id: polcal.c,v 1.5 2013/12/22 22:54:08 couvidat Exp $ 4370
2014-01-05T17:39:09Z 2014-01-01T00:55:09.20Z 2014-01-01T00:55:09.20Z ... $Id: polcal.c,v 1.5 2013/12/22 22:54:08 couvidat Exp $ 4370
2014-01-05T17:40:17Z 2014-01-01T00:55:54.20Z 2014-01-01T00:55:54.20Z ... $Id: polcal.c,v 1.5 2013/12/22 22:54:08 couvidat Exp $ 4370
2014-01-05T17:41:25Z 2014-01-01T00:56:39.20Z 2014-01-01T00:56:39.20Z ... $Id: polcal.c,v 1.5 2013/12/22 22:54:08 couvidat Exp $ 4370
2014-01-05T17:42:33Z 2014-01-01T00:57:24.20Z 2014-01-01T00:57:24.20Z ... $Id: polcal.c,v 1.5 2013/12/22 22:54:08 couvidat Exp $ 4370
2014-01-05T17:43:41Z 2014-01-01T00:58:09.20Z 2014-01-01T00:58:09.20Z ... $Id: polcal.c,v 1.5 2013/12/22 22:54:08 couvidat Exp $ 4370
2014-01-05T17:44:52Z 2014-01-01T00:58:54.20Z 2014-01-01T00:58:54.20Z ... $Id: polcal.c,v 1.5 2013/12/22 22:54:08 couvidat Exp $ 4370
2014-01-05T17:46:03Z 2014-01-01T00:59:39.20Z 2014-01-01T00:59:39.20Z ... $Id: polcal.c,v 1.5 2013/12/22 22:54:08 couvidat Exp $ 4370
Length = 81 rows
<BLANKLINE>
<BLANKLINE>
Using Segments
--------------
In some cases, more than 1 file are present for the same set of query.
These data are distinguished by what are called Segments.
It is necessary to specify the Segment which you need to download.
Providing a segment won't have any affect on the response object returned, but this will be required later, while making an export request.
A list of supported segments of a series, say ``hmi.sharp_720s`` can be obtained by:
.. code-block:: python
>>> client = drms.Client() # doctest: +REMOTE_DATA
>>> si = client.info('hmi.sharp_720s') # doctest: +REMOTE_DATA
>>> print(si.segments.index.values) # doctest: +REMOTE_DATA
['magnetogram' 'bitmap' 'Dopplergram' 'continuum' 'inclination' 'azimuth'
'field' 'vlos_mag' 'dop_width' 'eta_0' 'damping' 'src_continuum'
'src_grad' 'alpha_mag' 'chisq' 'conv_flag' 'info_map' 'confid_map'
'inclination_err' 'azimuth_err' 'field_err' 'vlos_err' 'alpha_err'
'field_inclination_err' 'field_az_err' 'inclin_azimuth_err'
'field_alpha_err' 'inclination_alpha_err' 'azimuth_alpha_err' 'disambig'
'conf_disambig']
Also, if you provide an incorrect segment name, it will throw a meaningful error, specifying which segment values are supported by the given series:
.. code-block:: python
>>> Fido.search(a.Time('2014-01-01T00:00:00', '2014-01-01T01:00:00'),
... a.jsoc.Series('hmi.sharp_720s'),
... a.jsoc.Segment('image')) # doctest: +REMOTE_DATA
Traceback (most recent call last):
...
ValueError: Unexpected Segments were passed. The series hmi.sharp_720s contains the following Segments ['magnetogram', 'bitmap', 'Dopplergram', 'continuum', 'inclination', 'azimuth', 'field', 'vlos_mag', 'dop_width', 'eta_0', 'damping', 'src_continuum', 'src_grad', 'alpha_mag', 'chisq', 'conv_flag', 'info_map', 'confid_map', 'inclination_err', 'azimuth_err', 'field_err', 'vlos_err', 'alpha_err', 'field_inclination_err', 'field_az_err', 'inclin_azimuth_err', 'field_alpha_err', 'inclination_alpha_err', 'azimuth_alpha_err', 'disambig', 'conf_disambig']
To get files for more than 1 segment at the same time, chain ``a.jsoc.Segment()`` using ``AND`` operator:
.. code-block:: python
>>> Fido.search(a.Time('2014-01-01T00:00:00', '2014-01-01T01:00:00'),
... a.jsoc.Series('hmi.sharp_720s'),
... a.jsoc.Segment('continuum') & a.jsoc.Segment('magnetogram')) # doctest: +REMOTE_DATA
<sunpy.net.fido_factory.UnifiedResponse object at ...>
Results from 1 Provider:
<BLANKLINE>
61 Results from the JSOCClient:
Source: http://jsoc.stanford.edu
<BLANKLINE>
T_REC TELESCOP INSTRUME WAVELNTH CAR_ROT
----------------------- -------- --------- -------- -------
2014.01.01_00:00:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:12:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:24:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:36:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:48:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_01:00:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:00:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:12:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:24:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:36:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
... ... ... ... ...
2014.01.01_00:24:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:36:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:48:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_01:00:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:00:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:12:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:24:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:36:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:48:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_01:00:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
Length = 61 rows
<BLANKLINE>
<BLANKLINE>
Using Keywords
--------------
In some cases, you might want to filter out files based on key metadata, also called keywords.
A list of supported keywords of a series, say ``hmi.sharp_720s`` can be obtained by:
.. code-block:: python
>>> client = drms.Client() # doctest: +REMOTE_DATA
>>> keywords = client.keys('hmi.sharp_720s') # doctest: +REMOTE_DATA
>>> print(keywords) # doctest: +REMOTE_DATA
['cparms_sg000', 'magnetogram_bzero', 'magnetogram_bscale', 'cparms_sg001', 'bitmap_bzero', 'bitmap_bscale', 'cparms_sg002', 'Dopplergram_bzero', 'Dopplergram_bscale', 'cparms_sg003', 'continuum_bzero', 'continuum_bscale', 'cparms_sg004', 'inclination_bzero', 'inclination_bscale', 'cparms_sg005', 'azimuth_bzero', 'azimuth_bscale', 'cparms_sg006', 'field_bzero', 'field_bscale', 'cparms_sg007', ... 'ERRJHT', 'ERRVF']
Each keyword needs to be compared to a value, e.g., ``a.jsoc.Keyword("bitmap_bzero") == 0`` or ``a.jsoc.Keyword("bitmap_bzero") > 1``.
An example of this is:
.. code-block:: python
>>> Fido.search(a.Time('2014-01-01T00:00:00', '2014-01-01T01:00:00'),
... a.jsoc.Series('hmi.sharp_720s'),a.jsoc.Keyword('bitmap_bzero') == 0) # doctest: +REMOTE_DATA
<sunpy.net.fido_factory.UnifiedResponse object at ...>
Results from 1 Provider:
<BLANKLINE>
61 Results from the JSOCClient:
Source: http://jsoc.stanford.edu
<BLANKLINE>
T_REC TELESCOP INSTRUME WAVELNTH CAR_ROT
----------------------- -------- --------- -------- -------
2014.01.01_00:00:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:12:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:24:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:36:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:48:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_01:00:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:00:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:12:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:24:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:36:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
... ... ... ... ...
2014.01.01_00:24:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:36:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:48:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_01:00:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:00:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:12:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:24:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:36:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:48:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_01:00:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
Length = 61 rows
<BLANKLINE>
<BLANKLINE>
You can pass multiple keywords and they will be chained together inside the query:
.. code-block:: python
>>> Fido.search(a.Time('2014-01-01T00:00:00', '2014-01-01T01:00:00'), a.jsoc.Series('hmi.sharp_720s'),
... a.jsoc.Keyword('bitmap_bzero') == 0, a.jsoc.Keyword('continuum_bscale') > 0) # doctest: +REMOTE_DATA
<sunpy.net.fido_factory.UnifiedResponse object at ...>
Results from 1 Provider:
<BLANKLINE>
61 Results from the JSOCClient:
Source: http://jsoc.stanford.edu
<BLANKLINE>
T_REC TELESCOP INSTRUME WAVELNTH CAR_ROT
----------------------- -------- --------- -------- -------
2014.01.01_00:00:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:12:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:24:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:36:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:48:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_01:00:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:00:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:12:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:24:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:36:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
... ... ... ... ...
2014.01.01_00:24:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:36:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:48:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_01:00:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:00:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:12:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:24:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:36:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_00:48:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
2014.01.01_01:00:00_TAI SDO/HMI HMI_SIDE1 6173.0 2145
Length = 61 rows
<BLANKLINE>
<BLANKLINE>
If you provide a keyword without a comparison it will raise an error:
.. code-block:: python
>>> Fido.search(a.Time('2014-01-01T00:00:00', '2014-01-01T01:00:00'),
... a.jsoc.Series('hmi.sharp_720s'),
... a.jsoc.Keyword('bitmap_bzero')) # doctest: +REMOTE_DATA
Traceback (most recent call last):
...
ValueError: Keyword 'bitmap_bzero' needs to have a comparison to a value.
If you provide an incorrect keyword name it will also raise a error:
.. code-block:: python
>>> Fido.search(a.Time('2014-01-01T00:00:00', '2014-01-01T01:00:00'),
... a.jsoc.Series('hmi.sharp_720s'),
... a.jsoc.Keyword('bac') == 0) # doctest: +REMOTE_DATA
Traceback (most recent call last):
...
ValueError: Keyword: 'bac' is not supported by series: hmi.sharp_720s
Using Sample
------------
In case you need to query for data, at some interval of time, say every 10 min, you can pass it using `~sunpy.net.attrs.Sample`.
In other words, if you need to query for "hmi.v_45s" series data between January 1st 2014 from 00:00 to 01:00 at 10 minute intervals, you can do:
.. code-block:: python
>>> Fido.search(a.Time('2014-01-01T00:00:00', '2014-01-01T01:00:00'),
... a.jsoc.Series('hmi.v_45s'), a.Sample(10*u.min)) # doctest: +REMOTE_DATA
<sunpy.net.fido_factory.UnifiedResponse object at ...>
Results from 1 Provider:
<BLANKLINE>
7 Results from the JSOCClient:
Source: http://jsoc.stanford.edu
<BLANKLINE>
T_REC TELESCOP INSTRUME WAVELNTH CAR_ROT
----------------------- -------- ---------- -------- -------
2014.01.01_00:00:45_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:10:30_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:20:15_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:30:00_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:39:45_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:49:30_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:59:15_TAI SDO/HMI HMI_FRONT2 6173.0 2145
<BLANKLINE>
<BLANKLINE>
Note that the argument passed in ``a.Sample()`` must be an Astropy quantity, convertible into seconds.
Constructing complex queries
----------------------------
Complex queries can be built using "OR" operators.
Let's look for 2 different series data at the same time:
.. code-block:: python
>>> Fido.search(a.Time('2014-01-01T00:00:00', '2014-01-01T01:00:00'),
... a.jsoc.Series('hmi.v_45s') | a.jsoc.Series('aia.lev1_euv_12s')) # doctest: +REMOTE_DATA
<sunpy.net.fido_factory.UnifiedResponse object at ...>
Results from 2 Providers:
<BLANKLINE>
81 Results from the JSOCClient:
Source: http://jsoc.stanford.edu
<BLANKLINE>
T_REC TELESCOP INSTRUME WAVELNTH CAR_ROT
----------------------- -------- ---------- -------- -------
2014.01.01_00:00:45_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:01:30_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:02:15_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:03:00_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:03:45_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:04:30_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:05:15_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:06:00_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:06:45_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:07:30_TAI SDO/HMI HMI_FRONT2 6173.0 2145
... ... ... ... ...
2014.01.01_00:54:00_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:54:45_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:55:30_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:56:15_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:57:00_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:57:45_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:58:30_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:59:15_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_01:00:00_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_01:00:45_TAI SDO/HMI HMI_FRONT2 6173.0 2145
Length = 81 rows
<BLANKLINE>
2107 Results from the JSOCClient:
Source: http://jsoc.stanford.edu
<BLANKLINE>
T_REC TELESCOP INSTRUME WAVELNTH CAR_ROT
-------------------- -------- -------- -------- -------
2014-01-01T00:00:01Z SDO/AIA AIA_4 94 2145
2014-01-01T00:00:01Z SDO/AIA AIA_1 131 2145
2014-01-01T00:00:01Z SDO/AIA AIA_3 171 2145
2014-01-01T00:00:01Z SDO/AIA AIA_2 193 2145
2014-01-01T00:00:01Z SDO/AIA AIA_2 211 2145
2014-01-01T00:00:01Z SDO/AIA AIA_4 304 2145
2014-01-01T00:00:01Z SDO/AIA AIA_1 335 2145
2014-01-01T00:00:13Z SDO/AIA AIA_4 94 2145
2014-01-01T00:00:13Z SDO/AIA AIA_1 131 2145
2014-01-01T00:00:13Z SDO/AIA AIA_3 171 2145
... ... ... ... ...
2014-01-01T00:59:49Z SDO/AIA AIA_2 211 2145
2014-01-01T00:59:49Z SDO/AIA AIA_4 304 2145
2014-01-01T00:59:49Z SDO/AIA AIA_1 335 2145
2014-01-01T01:00:01Z SDO/AIA AIA_4 94 2145
2014-01-01T01:00:01Z SDO/AIA AIA_1 131 2145
2014-01-01T01:00:01Z SDO/AIA AIA_3 171 2145
2014-01-01T01:00:01Z SDO/AIA AIA_2 193 2145
2014-01-01T01:00:01Z SDO/AIA AIA_2 211 2145
2014-01-01T01:00:01Z SDO/AIA AIA_4 304 2145
2014-01-01T01:00:01Z SDO/AIA AIA_1 335 2145
Length = 2107 rows
<BLANKLINE>
<BLANKLINE>
The two series names are joined together by the operator ``|``.
This is the "OR" operator.
Think of the above query as setting a set of conditions which get passed to the JSOC.
Let's say you want all the "hmi.v_45s" data from two separate days:
.. code-block:: python
>>> Fido.search(a.Time('2014-01-01T00:00:00', '2014-01-01T01:00:00') |
... a.Time('2014-01-02T00:00:00', '2014-01-02T01:00:00'),
... a.jsoc.Series('hmi.v_45s')) # doctest: +REMOTE_DATA
<sunpy.net.fido_factory.UnifiedResponse object at ...>
Results from 2 Providers:
<BLANKLINE>
81 Results from the JSOCClient:
Source: http://jsoc.stanford.edu
<BLANKLINE>
T_REC TELESCOP INSTRUME WAVELNTH CAR_ROT
----------------------- -------- ---------- -------- -------
2014.01.01_00:00:45_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:01:30_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:02:15_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:03:00_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:03:45_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:04:30_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:05:15_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:06:00_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:06:45_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:07:30_TAI SDO/HMI HMI_FRONT2 6173.0 2145
... ... ... ... ...
2014.01.01_00:54:00_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:54:45_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:55:30_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:56:15_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:57:00_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:57:45_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:58:30_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_00:59:15_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_01:00:00_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.01_01:00:45_TAI SDO/HMI HMI_FRONT2 6173.0 2145
Length = 81 rows
<BLANKLINE>
81 Results from the JSOCClient:
Source: http://jsoc.stanford.edu
<BLANKLINE>
T_REC TELESCOP INSTRUME WAVELNTH CAR_ROT
----------------------- -------- ---------- -------- -------
2014.01.02_00:00:45_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.02_00:01:30_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.02_00:02:15_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.02_00:03:00_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.02_00:03:45_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.02_00:04:30_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.02_00:05:15_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.02_00:06:00_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.02_00:06:45_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.02_00:07:30_TAI SDO/HMI HMI_FRONT2 6173.0 2145
... ... ... ... ...
2014.01.02_00:54:00_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.02_00:54:45_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.02_00:55:30_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.02_00:56:15_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.02_00:57:00_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.02_00:57:45_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.02_00:58:30_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.02_00:59:15_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.02_01:00:00_TAI SDO/HMI HMI_FRONT2 6173.0 2145
2014.01.02_01:00:45_TAI SDO/HMI HMI_FRONT2 6173.0 2145
Length = 81 rows
<BLANKLINE>
<BLANKLINE>
Each of the arguments in this query style can be thought of as setting conditions that the returned records must satisfy.
It should be noted that ``AND`` operator is supported by some of the attributes only.
The attributes which support "&" are `~sunpy.net.jsoc.attrs.PrimeKey` and `~sunpy.net.jsoc.attrs.Segment`.
Using "&" with any other attributes will throw an error.
Downloading data
================
To download the files located by `~sunpy.net.fido_factory.UnifiedDownloaderFactory.search`,
you can download them by `~sunpy.net.fido_factory.UnifiedDownloaderFactory.fetch`:
.. code-block:: python
>>> Fido.search(a.Time('2014-01-01T00:00:00', '2014-01-01T01:00:00'),
... a.jsoc.Series('hmi.v_45s') | a.jsoc.Series('aia.lev1_euv_12s'),
... a.jsoc.Notify('solar@example.com') # doctest: +SKIP
>>> downloaded_files = Fido.fetch(res) # doctest: +SKIP
To export a request for download, you must have used the `sunpy.net.jsoc.attrs.Notify` attribute at search time to specify your email address.
.. note::
**Only complete searches can be downloaded from JSOC**
This means that no slicing operations performed on the results object will affect the number of files downloaded.
Using JSOCClient for complex usage
==================================
Fido interface uses `~sunpy.net.jsoc.JSOCClient` in its backend, and combines the last 2 stages the JSOC process into one.
You can directly use the JSOC client to make queries, instead of the Fido client.
This will allow you to separate the 3 stages of the JSOC process, and perform it individually, hence allowing a greater control over the whole process.
Setup
-----
sunpy's JSOC module is in `~sunpy.net`.
It can be imported as follows:
.. code-block:: python
>>> from sunpy.net import jsoc
>>> client = jsoc.JSOCClient() # doctest: +REMOTE_DATA
This creates your client object.
Making a query
--------------
Querying JSOC using the JSOC client is very similar to what we were doing with Fido.
As above, we have to make sure we have an email address registered with JSOC before you are allowed to make a request.
`See this <http://jsoc.stanford.edu/ajax/register_email.html>`__ to register your email address.
We can add an email address to the search query with the `sunpy.net.jsoc.attrs.Notify` attribute.
Please note you can search without this but right now, you can not add the email address after the search:
.. code-block:: python
>>> res = client.search(a.Time('2014-01-01T00:00:00', '2014-01-01T01:00:00'),
... a.jsoc.Series('hmi.v_45s'),
... a.jsoc.Notify('sunpy@sunpy.org')) # doctest: +REMOTE_DATA
Apart from the function name, everything is the same.
You need to pass the same values in the `~sunpy.net.jsoc.JSOCClient.search` as you did in `~sunpy.net.fido_factory.UnifiedDownloaderFactory.search`.
Complex queries can be built in a similar way, and all other things are the same.
Staging the request
-------------------
JSOC is a 3-stage process, and after getting the query results, we need to stage a request for the data to be downloaded.
Only then, can we download them.
The download request can be staged like this:
.. code-block:: python
>>> requests = client.request_data(res) # doctest: +SKIP
>>> print(requests) # doctest: +SKIP
<ExportRequest id="JSOC_20170713_1461", status=0>
The function `~sunpy.net.jsoc.JSOCClient.request_data` stages the request.
It returns a `drms.ExportRequest` object, which has many attributes.
The most important ones are ``id`` and ``status``.
Only when the status is 0, we can move to the third step, i.e., downloading the data.
If you are making more than 1 query at a time, it will return a list of `~drms.ExportRequest` objects.
Hence, access the list elements accordingly.
You can get the id and status of the request (if it is not a list) by:
.. code-block:: python
>>> requests.id # doctest: +SKIP
JSOC_20170713_1461
>>> requests.status # doctest: +SKIP
0
Downloading data
----------------
Once the status code is 0 you can download the data using the `~sunpy.net.jsoc.JSOCClient.get_request` method:
.. code-block:: python
>>> res = client.get_request(requests) # doctest: +SKIP
This returns a Results instance which can be used to watch the progress of the download:
.. code-block:: python
>>> res.wait(progress=True) # doctest: +SKIP
|
