Difference: RCF (1 vs. 39)

SN Siblings

Status: in preparation at https://www.overleaf.com/read/fdwjbnmtmsxp

Cosmology with Type II-P distances: Expanding photosphere method

Leads: Jakob Nordin, Peter Nugent, Sarafina Nance, Suhail Dhawan, Ariel Goobar

Brief Description: Type II-P supernovae using the expanding photosphere method give absolute distances, independent of the Cepheid distance ladder, hence, are a novel probe to resolve the cause of the Hubble tension. This project has two related motivations. Firstly, for SN II-Ps that exploded in galaxies with an SN Ia, the II-P distance can be used to calibrate the absolute luminosity of (nearby, z < 0.03) Type Ia supernovae and hence, measure H0. Secondly, SNII-P's can themselves be used to make a Hubble diagram extending the redshift range to z ~ 0.07. Since the largest degeneracy in measuring the distance is a precise explosion date, the ZTF sample with early coverage would be ideal for this study.

Observations: P48 g,r,i lightcurves, SEDm spectra for nearby Type II-Ps, Gemini/8-m class for SNe 19.5 mag and fainter

Status: in prep.

• Check for duplicates: sometimes the same transient (or non-transient!) is given two separate identifiers. A note will be present below the identifier name on the Marshal (at the top of the page) if there is another ZTF source within about 3 arcseconds. If you see such a note, check the other object to see if it's actually the same source and if so, make sure follow-up is only triggered for at most one of them.

• Currently we trigger every genuine transient that is <19 mag (so everything that passed for the day and was not bogus, stars (CVs), or known AGN).
• When triggering SEDM use "Followup" = "IFU" (the rest are only photometry). Anything <18.5 or that is rising such that a reasonable extrapolation suggests it will reach <18.5 within a few days should be P3. Fainter objects that appear to be rising can be set at P2. Set P1 for objects whose reality is very questionable, or objects that are close to 19 mag and not rising.

Brief Description : Statistics on most strangely behaving SNe

Status : Sharma & Fremling, in prep

Various timescale analysis: long-duration Ic's and link to SLSNe, distinction between IIP/IIL, statistics on double-peaked light curves, rates of very short and very long transients, photometric classification

Large-scale host galaxy papers: various subtypes (Ibn vs IIb vs Ib vs Ic vs Ic-BL, etc.), correlations with duration and luminosity, morphology studies, IFU studies, spectroscopic studies

BTS Sample Selection and Public Portal

Brief Description: Describes sample selection in practice and the use of coverage criteria to establish a statistical high-completeness sample. Shows a few science highlights: initial duration-luminosity plot, aggregate rates, host color/luminosity statistics.

Leads: Perley & Fremling

ZTF RCF Sample: supernovae as tracers of the Large Scale Structure

Leads: Eleni Tsaprazi (PhD student), Ariel Goobar, Jens Jasche, Hiranya Peiris (OKC)

Objects: all SNe in RCF sample

Observations: ZTF SN coordinates and classifications

Brief Description:

We explore the underlying LSS properties at the locations of SN hosts, and explore possible correlations and the ability to use SNe as tracers of LSS properties at higher redshifts

Status: in prep.

Characterization of the SNIa Population using ZTF RCF

Leads: Rahul Biswas, Ariel Goobar, Hiranya Peiris, Daniel Mortlock

Brief Description: We propose a method to study rates of low redshift SNIa and the distribution of their parameters simultaneously, assuming a fixed cosmology. The method explores the use of simulations (via simsurvey) to incorporate the impact of selection efficiency in place of control times.

Observations: Selected sample (coordinates, redshifts) + Forced photometry

Status: in prep.

Berkeley: Modak, Hoffman, Patra

Fremling, Ulf Christoffer (Christoffer) <fremling@caltech.edu>; Adam Miller <amiller@northwestern.edu>; Alison Dugas <adugas@hawaii.edu>; Jesper Sollerman <jesper@astro.su.se>; Daniel Perley <D.A.Perley@ljmu.ac.uk>; Sharma, Yashvi <yssharma@astro.caltech.edu>; Taggart, Kirsty <K.L.Taggart@2016.ljmu.ac.uk>; Suhail Dhawan <suhail.dhawan@fysik.su.se>; Rahul Biswas <rbiswas4@gmail.com>; Melissa Graham <melissalynngraham@gmail.com>; Jakob Nordin <jnordin@physik.hu-berlin.de>; Ariel Goobar <ariel@fysik.su.se>; Neill, James D. (Don) <neill@srl.caltech.edu>; Rachel Bruch <rachel.bruch@weizmann.ac.il>; Rauch, Ludwig <ludwig.rauch@desy.de>; Steve Schulze <steve.schulze@weizmann.ac.il>; Ido Irani <ido.irani@weizmann.ac.il>; Kulkarni, Shrinivas R. (Shri) <srk@astro.caltech.edu>; Jannis Necker <necker@physik.hu-berlin.de>; Kishore Patra <kcpatra@berkeley.edu>; Samantha Goldwasser <samantha.goldwasser@weizmann.ac.il>; Shaunak Modak <shaunakmodak@berkeley.edu>; Andrew Hoffman <andrewmh@berkeley.edu>; Erez Zimmerman <erez.zimmerman@weizmann.ac.il>; yafshar0673@sdsu.edu <yafshar0673@sdsu.edu>; Hall, Xander J. <xhall@caltech.edu>

Brief Description: Spectroscopic Classification of the 2019 RCF sample; SN subtype statistics

Status: Fremling, Dahiwale, Miller, Hall, Perley Sharma, and others. Need results from SNID, Superfit (ppython version), DASH, Ia LC fits.

Brief Description: ML Classification of SEDM spectra

Status: Fremling +, some testiing of the models still needed before deployment

Brief Description: Spectroscopic Classification and the Redshift Completeness of Local Galaxy Catalogs

Status: (Fremling et al. 2020, ApJ accepted)

• RCF July 2018:
  

  ---

Filter History

• Check (on Lasair) whether the light curve and/or position is consistent with a nova or supernova. If not - in particular, if the object looks like an obvious AGN (nuclear, complex vaiability, MILLIQUAS match), CV (hostless or blue pointlike host, no rise), or variable star - close the tab. Note that there may be genuine transients in nearby galaxies (e.g. M31), please keep these!
• Compile a list of all the transients (candidate novae/supernovae) that remain.

• If a link for today does not appear by noon Pacific Time, or if the table is empty, and the weather was not poor last night, AMPEL may not have generated a list (you can check with Dan if this is the case). If so, the events will simply be incorporated into tomorrow's cross-check.

• If using the age-sorted scan, there will usually be a few "stale" alerts at the top (age=none), followed by some real SNe (age = 0 - 25 days), followed by a large number of AGN and variable stars with a few SNe mixed in (age >> 25 days).
• If there is only one night of detections, be sure the candidate is not an asteroid especially if it has a red color. If you save an asteroid by accident be sure to remove it since these should not ever be sent to TNS. (Note: catalogued asteroids are now flagged in the avro packets and are removed by the filter, so it is now very rare to see asteroids.)
• If the rise time is very fast (i.e. less than the 3-day cadence so that it is fading from the first epoch) and the object is hostless or has a faint point-source host exactly coincident with the transients, it is probably a CV. If it additionally has an old "age" parameter it is definitely a CV. These need not be saved.

• Check TNS: are there previous reports at this position from well before the first ZTF detection (can be a strong indicator of a CV, or AGN)

• If the transient already has an SEDM spectrum that has been taken under a private program: if the type is not obvious from that spectrum, retrigger under RCF as normal, possibly setting the start date a few days into the future to allow for some evolution. If the type is obvious, check if a classification report has been sent to TNS (from any group). If not, re-trigger under RCF.

• Go to http://www.astro.caltech.edu/too/rcf/complete/directory.html and select today's date. (Note that the check is not run until 10:15 AM Pacific time, so the link will not appear until then.)
• If there are any items in the table, open the corresponding "Lasair" link for each of them in a new tab.
• Check whether the light curve and/or position is consistent with a nova or supernova. If not - in particular, if the object looks like an obvious AGN (nuclear, complex vaiability, MILLIQUAS match), CV (hostless or blue pointlike host, no rise), or variable star - close the tab. Note that there may be genuine transients in nearby galaxies (e.g. M31), please keep these!
• For now, send the list of missing transients to Aishwarya for Marshal ingestion and RCF transfer. ACTUAL INSTRUCTIONS HERE
• Once ingested and saved to RCF, follow the same procedure for SEDM as in #4.
• If a link for today does not appear by noon PDT, or if the table is empty, and the weather was not poor last night, AMPEL may not have generated a list (you can check with Dan if this is the case). If so, the events will simply be incorporated into tomorrow's cross-check.

Redshift Completeness Factor - Papers in Progress

Title of your Paper

Leads:

Brief Description: A one line description of your paper

Status: in preparation/submitted etc.

• If using the age-sorted scan, there will usually be a few "stale" alerts at the top (age=none), followed by a few asteroids (age < 1 day), followed by some real SNe (age = 0 - 25 days), followed by a large number of AGN and variable stars (age >> 25 days) with a few SNe mixed in.
• If there is only one night of detections, be sure the candidate is not an asteroid especially if it has a red color (check ssdistnr and ssnamenr: if distance is small/zero and there is a name number it is an asteroid). If you save an asteroid by accident be sure to remove it since these should not ever be sent to TNS.
• If the rise time is very fast (i.e. less than the 3-day cadence so that it is fading from the first epoch) and the object is hostless or has a faint point-source host, it is probably a CV. If it additionally has an old "age" parameter it is definitely a CV. These should not be saved.
• If the object is merely hostless, and not an asteroid and not clearly a CV, it should be saved. (Could be a hostless Ia, or even possibly a GRB afterglow.)
• Be sure to scan all the way to the bottom of the page, including old (age > 25 day) transients. Objects that have been previously classified/removed as AGNs/stars can be ignored, as can anything with continuous variability over the past month. However anything with a clear rising light curve that is not a star/AGN should be saved, especially if it is in a galaxy.

• A short-cut page with links to scan the current night, ordered by transient age, is available here: http://www.astro.caltech.edu/too/rcf/rcf.php

• If using the age-sorted scan, most new SNe will be near the top of the page with an age parameter between 0-20 days. However occasionally new SNe do appear with old "age" values (>100), so be sure to scan all the way to the bottom. Anything with a rising light curve should be considered a viable candidate if not a known AGN.

• When triggering SEDM use "Followup" = "IFU" (the rest are only photometry). The priority should generally be set to 2 or 3 if the candidate does not already have an active SEDM IFU request. Anything <18.5 or that is rising such that a reasonable extrapolation suggests it will reach <18.5 within a few days should be P3. Fainter objects can be set at P2. (Set P1 only for objects whose reality is very questionable.)

• If the transient already has an SEDM spectrum that has been taken... [policy here?]

• When triggering SEDM use "Followup" = "IFU" (the rest are only photometry), and set the priority to at least 2 (but most things worth saving should be a 3, and only low-priority backups should be 1, as they might not be observed).
• If you want to trigger something with an existing SEDM request for CLU, Orphan Afterglows, Red Transients, etc, you should replace the original request with one for RCF, keeping at least the original group's priority and duration (i.e., these could be priority >3). This will allow for the spectrum to be shared.

• On days with a lot of candidates, it may be a good idea to wait until a few hours after the sun has come up in case processing takes a while.
• The sun sets as early as 4:40pm PST (0:40 UTC) in the winter, so be mindful of submitting requests by soon after that.

• We still save candidates if there is no visible counterpart but the field looks like the candidate is very likely a CV

• Here it is very helpful to look at PS1 or Gaia before saving, to determine if there is a star at the position of the transient that sgscore is unable to classify
• Note that if there is no visible counterpart but the field looks like the candidate is very likely a CV, we still do save these candidates
• Note that known AGN will now be already flagged on the scanning page
• We do save all nuclear transients that are not known AGN

• Look for and add SDSS redshift when available
• Check the LCs, (detections interspersed with non-detections can indicate a bogus candidate, especially for nuclear candidates)
• Check TNS: are there previous reporting on the position (can be a strong indicator of a CV, or AGN)

• Currently we trigger everything that is <19 mag (so everything that passed for the day and was not bogus, stars (CVs), or known AGN).
• When triggering SEDM use "Followup" = "IFU" (the rest are only photometry), and set the priority to at least 2 (but most things worth saving should be a 3).
• If you want to trigger something with an existing SEDM request for CLU, Orphan Afterglows, Red Transients, etc, you should replace the original request with one for RCF, keeping at least the original group's priority and duration.

• Go through the program report -- look for transients that SEDM has been unable to classify, and assign for followup at P200 (or other)

Classification and TNS reporting

• Adjust classifications for all targets when possible. Especially make sure to classify any known AGN as AGN.
• If you found that one target was bogus after saving to the program, transfer this target to the garbage dump program. Clear stars/CVs that don't need spectra can also be transferred to garbage dump. We keep all AGN, and Nuclear events on the program, even if we do not get spectra.

ATel guidelines

RCF Scripts

• RCF July 2018:
  

if (dt = 0.0 and candidate["magpsf"] < 99){ if (candidate["jd"] > t_slope and candidate["fid"] == fid_now) { t_slope = candidate["jd"]; slope = (m_now - candidate["magpsf"]) / dt; } } } }

NOTE

We do not send classifications of AGN, or TDEs to TNS.

filteron latitude and bright and noPointUnderneath and (not mover) and real and positiveSubtraction and (not brightStar);

RCF Filter (Before 2018-09-04): bright = False; noPointUnderneath = True; mover = True; real = False; slope = 0.0; t_slope = 0.0; rb = 0.0; positiveSubtraction = False; brightstar = False; scorr = 0.0; latitude = True;

prevCandidates = observation["prv_candidates"]; m_now = observation["candidate"]["magpsf"]; m_app = observation["candidate"]["magap"]; t_now = observation["candidate"]["jd"]; fid_now = observation["candidate"]["fid"]; sgscore = observation["candidate"]["sgscore1"]; sgscore2 = observation["candidate"]["sgscore2"]; sgscore3 = observation["candidate"]["sgscore3"]; srmag = observation["candidate"]["srmag1"]; srmag2 = observation["candidate"]["srmag2"]; srmag3 = observation["candidate"]["srmag3"]; sgmag = observation["candidate"]["sgmag1"]; simag = observation["candidate"]["simag1"]; rbscore = observation["candidate"]["rb"]; magnr = observation["candidate"]["magnr"]; distnr = observation["candidate"]["distnr"]; distpsnr1=observation["candidate"]["distpsnr1"]; distpsnr2=observation["candidate"]["distpsnr2"]; distpsnr3=observation["candidate"]["distpsnr3"]; scorr = observation["candidate"]["scorr"]; fwhm = observation["candidate"]["fwhm"]; elong = observation["candidate"]["elong"]; nbad = observation["candidate"]["nbad"]; chipsf = observation["candidate"]["chipsf"]; gal_lat = observation["candidate"]["gal_lat"];

bright = m_now < 19.0;

if (gal_lat and gal_lat < 7 and gal_lat > -7) { latitude = False; }

if (observation["candidate"]["isdiffpos"] and (observation["candidate"]["isdiffpos"] = "t" or observation["candidate"]["isdiffpos"] = "1")){ positiveSubtraction = True; } if (rbscore and rbscore > 0.2) { real = True; }

if (sgscore and distpsnr1 and sgscore > 0.76 and distpsnr1<2) { noPointUnderneath = False; }

if ((distpsnr1 and srmag and distpsnr1 < 20 and srmag < 16.0 and srmag>0 and sgscore > 0.49) or (distpsnr2 and srmag2 and distpsnr2 < 20 and srmag2 < 16.0 and srmag2>0 and sgscore2 > 0.49) or (distpsnr3 and srmag3 and distpsnr3 < 20 and srmag3 < 16.0 and srmag3>0 and sgscore3 > 0.49) ) { brightStar = True; }

for candidate in prevCandidates{ if (candidate["jd"] and candidate["magpsf"] and candidate["fid"] and candidate["isdiffpos"] and (candidate["isdiffpos"] = "t" or candidate["isdiffpos"] = "1")) {

dt = t_now - candidate["jd"]; if (dt > 0.02 and candidate["magpsf"] < 99) { mover = False; }

if (dt = 0.0 and candidate["magpsf"] < 99){ if (candidate["jd"] > t_slope and candidate["fid"] == fid_now) { t_slope = candidate["jd"]; slope = (m_now - candidate["magpsf"]) / dt; } } } }

annotate "magnitude" m_now; annotate "sgscore" sgscore; annotate "slope" slope; annotate "rbscore" rbscore; annotate "mover" mover; annotate "real" real; annotate "positiveSubtraction" positiveSubtraction; annotate "brightStar" brightStar; annotate "magnr" magnr; annotate "distnr" distnr; annotate "scorr" scorr; annotate "gal_lat" gal_lat;

filteron latitude and bright and noPointUnderneath and (not mover) and real and positiveSubtraction and (not brightStar);

• RCF July 2018:
  

- I f you found that one target was bogus after saving to the program, transfer this target to the garbage dump program. Clear stars/CVs that don't need spectra can also be transferred to garbage dump. We keep all AGN, and Nuclear events on the program, even if we do not get spectra.

3. Any new classifications that have been made that do not have a [TNS_upload_date]: 2018-MM-DD auto annotation should be reported to TNS (we have a python script for this, see below)

NOTE

We do not send classifications of AGN, or TDEs to TNS.

Scanning and triggering guidelines

- Note that if there is no visible counterpart, and the field looks like the candidate is very likely a CV, we still do save these candidates

- Note that known AGN will now be already flagged on the scanning page

- We do save all nuclear transients that are not known AGN

3. After scanning, look through the saved transients for the day on the program report page and their view source pages

- Look for and add SDSS redshift when available

- Check the LCs, (detections interspersed with non-detections can indicate a bogus candidate, especially for nuclear candidates)

4. Trigger SEDM

- Currently, we trigger everything that is <19 mag (so everything that passed for the day, and was not bogus, stars, or known AGN).

(5.) If there is an upcoming run at P200 (or other larger telescopes)

- Go through the program report -- look for transients that SEDM has been unable to classify, and assign for followup at P200 (or other)

Classification and TNS reporting

2. Go through the program report, look for new spectra, run them through SNID and classify.

3. Any new classifications that has been made that do not have a [TNS_upload_date]: 2018-08-09 auto annotation should be reported to TNS (we have a python script for this, see below)

ATel guidelines

1. Check the redshifts. If it comes from host galaxy lines or narrow SN lines, use 3 decimals. If it comes from a SNID fit to broad SN features (use 2 decimal points)

2. Check TNS, and ATels for what other groups have done on the objects in our ATel (put this info in notes).

RCF Scripts

https://github.com/Yashvi-Sharma/RCF_scripts

tns_upload_spec.py is used to send TNS classification reports get_source_tnsuploadinfo.py is used to generate a rough ATel table

RCF webpage (for host redshift determination)

RCF webpage

I have some preliminary RCF pages running on skipper. As with the marshal, you'll need to register for an account here (to avoid letting just anyone potentially make changes to the data):

http://skipper.caltech.edu:8083/redcomp/register.html

I'd recommend just using the same username and password you've set up with the growth marshal. Once you've activated your accounts, you will be able to access a bare bones search page (just names for now, more will be added later as useful):

http://skipper.caltech.edu:8083/cgi-bin/redcomp/find_tns_sources.cgi

And you will be able to access source summary pages (also linked to by the results of the search page), e.g.:

http://skipper.caltech.edu:8083/cgi-bin/redcomp/source_summary.cgi?name=2016aaj

The source summary is currently non-interactive, but I will start adding interactivity today.

http://adsabs.harvard.edu/abs/2017arXiv171004223K

https://www.dropbox.com/s/nhd3qxnhdxwqjyd/WP_SEDM.pdf?dl=0

Date of next telecon

Apr. 2 - Apr. 9?

People

S. Kulkarni, C. Fremling (CIT lead)
N. Blagorodnova (CIT)
D. Perley (LJMU)
A. Miller (NU)
P. Nugent (LBL)
D. Goldstein (LBNL)
M. Graham?


SN Ia cosmology
A. Goobar (OKC)
S. Dhawan (OKC)
R. Biswas (OKC)
J. Nordin (Berlin)


Students:

Christopher Cannella (CIT)
Yashvi Sharma (IIT Bombay)
Kirsty Taggart (LJMU)

-- ChristofferFremling - 21 Mar 2018