@@ -22,7 +22,6 @@ supports object and region based querying and data staging and retrieval.
22
22
You can get interactive help to find out what keywords to query for:
23
23
24
24
.. code-block :: python
25
- .. doctest-remote-data ::
26
25
>> > from astroquery.alma import Alma
27
26
>> > Alma.help()
28
27
< BLANKLINE >
@@ -92,7 +91,6 @@ Users can log in to acquire proprietary data products. Login is performed
92
91
via the ALMA CAS (central authentication server).
93
92
94
93
.. code- block:: python
95
- .. doctest-remote-data ::
96
94
>> > from astroquery.alma import Alma
97
95
>> > alma = Alma()
98
96
>> > # First example: TEST is not a valid username, it will fail
@@ -145,15 +143,8 @@ You can query by object name or by circular region:
145
143
' scientific_category' , ' lastModified' ]
146
144
147
145
148
- Please note that some of the column names are duplicated. First group of names
149
- (the ones containing "_") are column names as they appear in the ALMA ObsCore
150
- model while the second group are copies created to maintain backwards
151
- compatibility with previous version of the library.
152
-
153
-
154
146
Region queries are just like any other in astroquery:
155
147
156
-
157
148
.. code- block:: python
158
149
.. doctest- remote- data::
159
150
>> > from astropy import coordinates
@@ -171,14 +162,14 @@ As of version 0.3.4, you can also query other fields by keyword. For example,
171
162
if you want to find all projects with a particular PI , you could do:
172
163
173
164
.. code- block:: python
174
- .. doctest-remote-data ::
175
- >>> rslt = Alma.query_object(' W51' , pi_name = ' *Ginsburg*' , public = False )
165
+
166
+ >> > rslt = Alma.query_object(' W51' , pi_name = ' *Ginsburg*' , public = False ) # doctest: +REMOTE_DATA
176
167
177
168
The ' ' query_sia' ' method offers another way to query ALMA using the IVOA SIA
178
169
subset of keywords returning results in ' ObsCore' format .
179
170
180
171
.. code- block:: python
181
- .. doctest-remote-data ::
172
+
182
173
>> > # Alma.query_sia(pol='XX')
183
174
184
175
Finally, the ' ' query_tap' ' method is the most general way of querying the ALMA
@@ -195,8 +186,7 @@ Use the ''help_tap'' method to learn about the ALMA 'ObsCore' keywords and
195
186
their types.
196
187
197
188
.. code- block:: python
198
- .. doctest-remote-data ::
199
- >>> Alma.help_tap()
189
+ >> > Alma.help_tap() # doctest: +REMOTE_DATA
200
190
Table to query is " voa.ObsCore" .
201
191
For example: " select top 1 * from ivoa.ObsCore"
202
192
The scheme of the table is as follows.
@@ -277,12 +267,12 @@ cycle 1 data sets tend to be >100 GB!
277
267
.. code- block:: python
278
268
.. doctest- remote- data::
279
269
>> > import numpy as np
280
- >>> uids = np.unique(m83_data[' Member ous id ' ])
281
- >>> print (uids)
282
- Member ous id
270
+ >> > uids = np.unique(m83_data[' member_ous_uid ' ])
271
+ >> > print (uids) # doctest: +IGNORE_OUTPUT
272
+ member_ous_uid
283
273
---------------------- -
284
- uid://A002/X3216af/X31
285
- uid://A002/X5a9a13/X689
274
+ uid:// A001 / X11f / X30
275
+ uid:// A001 / X122 / Xf3
286
276
287
277
New to most recent versions of the library is that data does not need to be
288
278
staged any longer. The ```stage_data``` method has been deprecated, but the
@@ -360,7 +350,8 @@ You might want to look at the READMEs from a bunch of files so you know what kin
360
350
361
351
.. code- block:: python
362
352
.. doctest- remote- data::
363
- >>> filelist = Alma.download_and_extract_files(uid_url_table[' URL' ], regex = ' .*README$' )
353
+
354
+ >> > filelist = Alma.download_and_extract_files(uid_url_table[' URL' ], regex = ' .*README$' ) # doctest: +IGNORE_OUTPUT
364
355
365
356
366
357
Further Examples
0 commit comments