You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: documentation/spherex_data_access.md
+20-6Lines changed: 20 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,15 +5,15 @@ IRSA provides layered access to these data to support a variety of use cases and
5
5
These layers include:
6
6
7
7
***Browsable Directories:** SPHEREx on-premises data products are laid out in directories that can be navigated with standard web browsers.
8
-
***Application Program Interfaces:** IRSA provides SPHEREx data access APIs that are compliant with International Virtual Observatory Alliance (IVOA) standards.
8
+
***Application Program Interfaces:** IRSA provides SPHEREx data access APIs, most of which are compliant with International Virtual Observatory Alliance (IVOA) standards.
9
9
***Python Packages:** SPHEREx data at IRSA are accessible via the Python packages pyvo and astroquery
10
10
***SPHEREx Data Explorer:** IRSA provides a web-based Graphical User Interface (GUI) that makes it easy to search for, visualize, and download SPHEREx data.
11
11
12
12
Each of these data access layers is described in greater detail in the subsections below.
13
13
14
14
## Browsable Directories
15
15
SPHEREx data products are laid out in directories that can be navigated with standard web browsers.
16
-
This is convenient for users to get a quick sense of the types of data products that are available, to quickly download some examples by clicking through the directory tree, and to script bulk downloads using wget or curl.
16
+
This is convenient for users to get a quick sense of the types of data products that are available, to quickly download some examples by clicking through the directory tree, and to script bulk downloads using `wget` or `curl`.
17
17
18
18
The root of the SPHEREx data quick release data directories is:
19
19
https://irsa.ipac.caltech.edu/ibe/data/spherex/qr
@@ -35,6 +35,8 @@ The content of each subdirectory is described in greater detail in the Data Prod
35
35
36
36
## Application Program Interfaces (APIs)
37
37
38
+
### SPHEREx Spectral Image MEFs and Calibration Files are available through the IVOA Simple Image Access Protocol
39
+
38
40
IRSA provides API access to SPHEREx Spectral Images through version 2 of the VO Simple Image Access (SIA2) protocol.
39
41
SIA2 allows users to query for a list of images that satisfy constraints based on position(s) on the sky, band, time, ID, and instrument.
40
42
The list returned by the service includes data access URLs, which can be used to retrieve some or all of the images in the list using wget or curl.
@@ -47,12 +49,12 @@ Due to the nature of the ingestion process, new SPHEREx data will first be avail
47
49
Availability via SIA2 and Python libraries like Astroquery and PyVO will lag on the order of a day.
48
50
:::
49
51
50
-
IRSA's generric SIA2 endpoint is:
52
+
IRSA's generic SIA2 endpoint is:
51
53
52
54
`https://irsa.ipac.caltech.edu/SIA?`
53
55
54
56
Users must add a `COLLECTION` parameter to this endpoint to specify which dataset to search.
55
-
There are three SPHEREx-related SIA2 collections:
57
+
There are three SPHEREx-related SIA2 collections:
56
58
57
59
* SPHEREx Quick Release Spectral Image MEFs that are part of the SPHEREx **Wide Survey** can be accessed with: `COLLECTION=spherex_qr`
58
60
@@ -63,9 +65,21 @@ Users must add a `COLLECTION` parameter to this endpoint to specify which datase
63
65
You can use `wget` or `curl` to submit SIA2 queries from the command line.
See the section on Python packages to learn how to use Python wrappers around IRSA’s SIA2 service.
71
+
72
+
### Cutouts of SPHEREx Spectral Image MEFs
73
+
74
+
SPHEREx Spectral Image MEFs are available on premises at IPAC and on the cloud.
75
+
76
+
If you have identified the access URL for an on-premises Spectral Image, you can request a cutout of this MEF by appending a query string containing the center and size parameters. The parameters are described in more detail here:
77
+
78
+
`https://irsa.ipac.caltech.edu/ibe/cutouts.html`
79
+
80
+
**Example:**
67
81
68
-
See the next section to learn how to use Python wrappers around IRSA’s SIA2 service.
Copy file name to clipboardExpand all lines: documentation/spherex_data_products.md
+33-4Lines changed: 33 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
#SPHEREx Data Products Available at IRSA
1
+
SPHEREx Data Products Available at IRSA
2
2
3
3
A detailed description of SPHEREx data products available to the public is provided in the [SPHEREx Explanatory Supplement](https://irsa.ipac.caltech.edu/data/SPHEREx/docs/SPHEREx_Expsupp_QR.pdf).
4
4
Here we provide a concise summary of the science, calibration, and additional data products available at IRSA.
@@ -7,7 +7,10 @@ This summary includes filenaming conventions, for which we adopt the following d
7
7
-`Planning Period` designates the survey plan uploaded to the spacecraft, e.g. `2025W18_2B`.
8
8
Each planning period covers approximately 3.5 days of operation.
9
9
10
-
-`Observation ID` includes the survey planning period and the large and small slew counters, e.g. `2025W18_2B_0001_1`.
10
+
-`Observation ID` includes the survey planning period and the large and small slew counters.
11
+
For example, `2025W18_2B_0001_1` contains the planning period (`2025W18_2B`), the large slew counter (`0001`), and the small slew counter (`1`).
12
+
Each large slew has a maximum of 4 small slews, so the allowed small slew counter range is 1 to 4.
13
+
Some large slews will have fewer than 4 small slews.
11
14
12
15
-`Detector` is an integer from 1 through 6.
13
16
@@ -18,8 +21,10 @@ Each planning period covers approximately 3.5 days of operation.
18
21
19
22
## Main Science Data Product: Spectral Image Multi-Extension FITS Files (MEF)
20
23
21
-
The main Quick Release data product is the Level 2 Spectral Image MEF.
24
+
The main Quick Release data product is the Level 2 Spectral Image MEF,as described in Section 2.1 of the [Explanatory Supplement](https://irsa.ipac.caltech.edu/data/SPHEREx/docs/SPHEREx_Expsupp_QR.pdf).
25
+
22
26
There are 6 Spectral MEFs (one for each detector) for each sky pointing.
27
+
Because data quality assessments are evaluated per spectral image band, some observations will not include all 6 bands in the archive.
23
28
Each Spectral MEF is approximately 70 MB and contains 6 extensions:
24
29
25
30
HDU 1: IMAGE
@@ -40,7 +45,7 @@ HDU 1: IMAGE
40
45
41
46
HDU 2: FLAGS
42
47
: Bitmap of per-pixel status and processing flags, stored as a 2040 x 2040 image.
43
-
The definition of the flags are provided in Table 8 of the [SPHEREx Explanatory Supplement](https://irsa.ipac.caltech.edu/data/SPHEREx/docs/SPHEREx_Expsupp_QR.pdf).
48
+
The definition of the flags are provided in Table 10 of the [SPHEREx Explanatory Supplement](https://irsa.ipac.caltech.edu/data/SPHEREx/docs/SPHEREx_Expsupp_QR.pdf).
44
49
45
50
HDU 3: VARIANCE
46
51
: Variance of calibrated surface brightness flux in units of (MJy/sr)^2, stored as a 2,040 x 2,040 image.
IRSA enables users to access rectangular cutouts of a SPHEREx Spectral Image MEF by simply appending a [query string](https://irsa.ipac.caltech.edu/ibe/cutouts.html) containing center and size parameters to the image URL.
89
+
These cutout MEFs contain the same HDUs as the original Spectral Images (IMAGE, FLAGS, VARIANCE, ZODI, PSF, WCS-WAVE). However, the IMAGE, FLAGS, VARIANCE, AND ZODI HDUs have been modified to include only those pixels within the specified cutout size.
90
+
The WCS-WAVE HDU has also modified to provide the correct mapping between the pixels in the cutout to wavelength.
91
+
The PSF HDU from the original spectral image is included unmodified in the cutout MEF.
92
+
93
+
The spatially-varying PSF is represented as an image cube with 121 planes.
94
+
Each plane is a 101x101 pixel image representing a PSF for a different region of the detector. Users interested in performing photometry on a cutout using the information in the cutout PSF HDU will need to understand how to find the most applicable PSF cube plane for each pixel in the cutout.
95
+
The basic steps are described below, and a [Python notebook tutorial](https://caltech-ipac.github.io/irsa-tutorials/) is provided to help users get started with a simple implementation.
96
+
97
+
1. Determine the 0-based pixel coordinates of the position of interest in the IMAGE HDU of the cutout.
98
+
99
+
2. Determine the 0-based pixel coordinates of the position of interest in the IMAGE HDU of the original Spectral Image.
100
+
101
+
```
102
+
xpix_orig = 1 + xpix_cutout - CRPIX1A
103
+
ypix_orig = 1 + ypix_cutout - CRPIX2A
104
+
```
105
+
106
+
3. Examine the header of the PSF HDU of the cutout to determine the PSF zone and cube plane corresponding to the pixel of interest in the original Spectral Image.
107
+
108
+
The PSF HDU has a header containing the keywords `XCTR_*`, `YCTR_*`, `XWID_*`, and `YWID_*`, where * goes from [1 to 121].
109
+
To determine if a pixel in the original Spectral Image falls within a PSF zone, simply find the closest `XCTR_*` and `YCTR_*` to determine the cube plane that contains the corresponding PSF for this zone.
0 commit comments