02. Explore a SNIa Lightcurve (intermediate)¶
Contact authors: Melissa Graham and Greg Madejski
Last verified to run: 2022-06-26
Targeted learning level: intermediate
Introduction: This tutorial explores the data for a Type Ia supernova (SNIa) lightcurve: the i-band photometry, the seeing for each i-band epoch, and the astrometric scatter of the i-band observations. The scientific motivation here is that a user knows the coordinates of a low-redshift SNIa (67.4579, -44.0802), and now wants to find an i-band epoch in which this SNIa was bright and the seeing was good. The user also wants to get a sense of the scatter in the astrometry for the coordinates in the DiaObject catalog. For example, perhaps the user knows there is pre-explosion JWST imaging of the host galaxy, and is looking for the best image from Rubin Observatory with which to co-register with the JWST image in order to characterize the underlying stellar population at the SNIa’s location. (Note that typically, laser adaptive optics is necessary to obtain ground-based images of SNe that have high enough astrometric precision to co-register with a space-based image and identify a progenitor star, so this use-case is a bit contrived).
This tutorial assumes a basic working knowledge of the Portal interface (e.g., the successful completion of the first Portal tutorial). This tutorial uses the Astronomy Data Query Language (ADQL) to query and retrieve data from the DP0.2 catalogs. ADQL is similar to SQL (Structured Query Language), and the documentation for ADQL includes more information about syntax and keywords. For more information about the DP0.2 catalogs, visit the DP0.2 Data Products Definition Document (DPDD) or the DP0.2 Catalog Schema Browser.
WARNING: In this tutorial, the difference-image fluxes are converted to magnitudes in the TAP query. This is usually safe to do, because supernovae fluxes should never be negative in a difference image – unless the supernova also appears in the template image. In the case of DP0.2, due to how the template images were built, some of the template images are contaminated with supernova flux, potentially up to 40% of DC2 SNIa. This leads to negative-flux difference-image detections that are significant (SNR>5), and thus an overall offset in the SNIa lightcurves. Work is ongoing to evaluate this issue and recommend a robust correction method (see Images). Note that this offset is not discoverable in the following tutorial.
1. Determine the DiaObject Id¶
1.1. Log in to the Portal Aspect.
1.2. Leave the TAP Service and Query Type as their default, and select the dp02_dc2_catalogs.DiaObject table.
1.3. Check the box for spatial constraints, and use ra and decl as the longitude and latitude columns. Leave the shape type as Cone and enter the coordinates
67.4579, -44.0802. Set the radius to 2 arcsec.
1.4. In the table at right, select columns ra, decl, and diaObjectId to be returned.
1.5. Click “Search” and view the results: there is only one DiaObject within 2 arcsec, with coordinates
67.4579634, -44.080243 and DiaObjectId “1252220598734556212”.
This is definitely the SNIa of interest to the user.
2. Query the DiaSource table¶
2.1. Clear the previous search and return to the main Portal interface (use the “RSP TAP Search” button at upper left).
2.2. Select Query Type as “Edit ADQL (advanced)”, enter the following ADQL query. This query will retrieve all of the DiaSource table entries (i.e., all of the individual measurements on the difference images) for this DiaObject. This query also uses the ccdVisitId to join to the CcdVisit table and obtain the mean seeing measurement for the visit.
SELECT diasrc.ra, diasrc.decl, diasrc.diaObjectId, diasrc.diaSourceId, diasrc.filterName, diasrc.midPointTai, scisql_nanojanskyToAbMag(diasrc.psFlux) AS psAbMag, ccdvis.seeing FROM dp02_dc2_catalogs.DiaSource AS diasrc JOIN dp02_dc2_catalogs.CcdVisit AS ccdvis ON diasrc.ccdVisitId = ccdvis.ccdVisitId WHERE diasrc.diaObjectId = 1252220598734556212 AND diasrc.filterName = 'i'
2.3. Click “Search”.
3. Make the three plots¶
3.1. If the Results view is showing three panels including a sky image at upper left, switch to the “xy-tbl” view using the buttons at upper right. Use the settings icon (two gears at upper right) to open the plot parameters pop-up window, match those shown below, then click “Apply” and “Close”.
3.2. View the i-band lightcurve for this SNIa.
3.3. To add a plot of seeing versus time: use the settings icon, choose “Add New Chart” and match the parameters shown below, then click “OK”.
3.4. To add a plot to visualize the astrometric scatter: use the settings icon, choose “Add New Chart” and match the parameters shown below, then click “OK”.
Note that in both the X and Y parameters, the difference between the DiaSource coordinate and the DiaObject coordinate are multiplied by 3600, so that the plot axes are in arcseconds:
3.5. View all three plots together. Plots might appear in a different order than as shown in the figure below. In the plot labeled “seeing”, click on the i-band epoch with the best seeing (0.75 arcsec). Notice how the point turns orange in all three plots, and that the corresponding table row will be highlighted.
In the lightcurve plot, notice that for this “best-seeing” epoch the SNIa had an apparent magnitude near its peak (around 22nd mag). That makes it a suitable choice for the scientific use-case outlined in the Introduction.
In the plot showing the astrometric scatter, notice that for this “bright / best-seeing” epoch the measured sky coordinates of the DiaSource are very close to those reported for the DiaObject. This does not necessarily mean that the coordinates for the “best-seeing” epoch are more accurate, because the coordinates of DiaObjects are derived from the individual DiaSources. The point of this plot is more that the overall scatter is less than 0.3 arcsec, and that selecting the “bright / best-seeing” epoch image for co-registration with images from other facilities is a wise choice.
4. Exercise for the learner¶
4.1. Obtain the visitId. At this point, the user is ready to obtain the “bright / best seeing” epoch’s images. The simplest way to do that is with the visitId, but the ADQL query did not request that from the CcdVisit table. Return to the ADQL query and add ccdvis.ccdVisitId and ccdvis.visitId to the query.
4.2. Add magnitude error bars.
To retrieve magnitude errors from the DiaSource catalog, return to step 2.2 and add to the ADQL statement:
scisql_nanojanskyToAbMagSigma(diasrc.psFlux, diasrc.psFluxErr) AS psAbMagErr.
When you get to step 3.1, for the Y error choose “Symm” from the drop-down menu, and then in the new box that appears to the right, enter “psAbMagErr”.
When you click “Apply” to create the plot, the points will have error bars.