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
Now, we search for the Euclid ERO images using the `astroquery` package.
154
154
Note that the Euclid ERO images are no in the cloud currently, but we access them directly from IRSA using IRSA's *Simple Image Access* (SIA) methods.
@@ -227,7 +227,7 @@ Let's check out the summary table that we have created. We see that we have all
227
227
summary_table
228
228
```
229
229
230
-
## Create Cutout Images
230
+
## 4. Create Cutout Images
231
231
232
232
Now that we have a list of data products, we can create the cutouts. This is important as the full Euclid ERO images would be too large to run extraction and photometry software on them (they would simply fail due to memory issues).
233
233
@@ -265,7 +265,7 @@ for ii,filt in tqdm(enumerate(filters)):
We now want to add the best-fit coordinates (R.A. and Decl.) to the VIS photometry catalog. For this, we have to convert the image coordinates into sky coordinates using the WCS information. We will need these coordinates because we want to use them as positional priors for the photometry measurement on the NISP images.
We now have the photometry and the position of sources on the VIS image. We can now proceed with similar steps on the NISP images. Because the NISP PSF and pixel scale are larger that those of the VIS images, we utilize the advantage of position prior-based forced photometry.
430
430
For this, we use the positions of the VIS measurements and perform PSF fitting on the NISP image using these priors.
We now load the Gaia sources at the location of the globular clusters. The goal is to compare the photometry of Gaia to the one derived above for the Euclid VIS and NISP images. This is scientifically useful, for example we can compute the colors of the stars in the Gaia optical bands and the Euclid near-IR bands.
514
514
To search for Gaia sources, we use `astroquery` again.
@@ -563,7 +563,7 @@ ax2.set_title("NISP")
563
563
plt.show()
564
564
```
565
565
566
-
## Match the Gaia Catalog to the VIS and NISP Catalogs
566
+
## 11. Match the Gaia Catalog to the VIS and NISP Catalogs
567
567
568
568
Now, we match the Gaia source positions to the extracted sources in the VIS and NISP images.
569
569
@@ -628,7 +628,7 @@ ax1.set_ylabel("I$_E$ [mag]")
628
628
plt.show()
629
629
```
630
630
631
-
## Visualization with Firefly
631
+
## 12. Visualization with Firefly
632
632
633
633
At the end of this Notebook, we demonstrate how we can visualize the images and catalogs created above in `Firefly`.
Copy file name to clipboardExpand all lines: tutorials/simulated-data/OpenUniverse2024Preview_Firefly.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -86,7 +86,7 @@ from reproject import reproject_interp
86
86
from io import BytesIO
87
87
```
88
88
89
-
## Learn where the OpenUniverse2024 data are hosted in the cloud.
89
+
## 1. Learn where the OpenUniverse2024 data are hosted in the cloud.
90
90
91
91
The OpenUniverse2024 data preview is hosted in the cloud via Amazon Web Services (AWS). To access these data, you need to create a client to read data from Amazon's Simple Storage Service (s3) buckets, and you need to know some information about those buckets. The OpenUniverse2024 data preview contains simulations of the Roman Wide-Area Survey (WAS) and the Roman Time Domain Survey (TDS). In this tutorial, we will focus on the WAS.
The Nancy Grace Roman Space Telescope will carry out a wide-area survey (WAS) in the near infrared. The OpenUniverse2024 data preview includes coadded mosaics of simulated WAS data, created with the IMCOM algorithm (Rowe et al. 2011). Bands include F184, H158, J129, K213, Y106. In this section, we define some functions that make it convenient to retrieve a given cloud-hosted simulated Roman coadd based on position and filter.
The OpenUniverse2024 data preview includes coadded mosaics in the following filters: u, g, r, i, z, y. In this section, we define some functions that make it convenient to retrieve a given cloud-hosted simulated Roman coadd based on position and filter.
## Compare simulated Roman and Rubin cutouts for a selected position
330
+
## 4. Compare simulated Roman and Rubin cutouts for a selected position
331
331
332
332
+++
333
333
@@ -366,7 +366,7 @@ fig.suptitle(f"Cutouts at ({coord.ra}, {coord.dec}) with {cutout_size} size", fo
366
366
plt.tight_layout(rect=[0, 0, 1, 0.97])
367
367
```
368
368
369
-
## Use Firefly to interactively identify a blended source
369
+
## 5. Use Firefly to interactively identify a blended source
370
370
371
371
Clearly, the simulated Roman coadd has higher spatial resolution than the Rubin simulated coadd. Let's try to locate blended objects to compare in the simulated Rubin and Roman images. We will use Firefly's interactive visualization to make this task easier.
## Use Firefly to visualize the OpenUniverse2024 data preview catalogs
504
+
## 7. Use Firefly to visualize the OpenUniverse2024 data preview catalogs
505
505
Let's inspect the properties of sources in the Rubin coadd image. For this we will use the input truth files present in S3 bucket.
506
506
507
507
The OpenUniverse2024 data preview includes the input truth files that were used to create the simulated images. These files are in Parquet and HDF5 format, and include information about the properties of galaxies, stars, and transients.
0 commit comments