Skip to content

Commit

Permalink
Update sec_sci.tex
Browse files Browse the repository at this point in the history
  • Loading branch information
MelissaGraham committed Mar 1, 2024
1 parent 7f0c713 commit 689c73c
Showing 1 changed file with 14 additions and 7 deletions.
21 changes: 14 additions & 7 deletions sec_sci.tex
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ \section{Recommendations to Enable Science from Special Programs}\label{sec:sci}

\subsection{Region and Observing Mode Labels}\label{ssec:sci_labels}

\textbf{All visits should have a region label \textit{and} an observing mode
\textbf{All visits should have at least one region label \textit{and} one observing mode
label, and these labels should be propagated to processed images and catalog data.}

\textbf{Region Labels -- }
Expand All @@ -15,18 +15,25 @@ \subsection{Region and Observing Mode Labels}\label{ssec:sci_labels}
Region labels would include, e.g., WFD low-dust, Galactic Plane, Galactic
Bulge, SCP, NES, or Virgo; DDF fieldname; mini-survey region name.
Region labels should be propagated to processed images (visit,
difference, and deep coadds), catalog sources, and catalog static-sky objects.
difference, and deep coadds), catalog sources, and catalog static-sky objects.
A given image might have more than one region label due to overlaping regions,
but they could be, e.g., held in a single string as a CSV.

\textbf{Observing Mode Labels -- }
Based on the scheduler mode at the time of the observation
(i.e., survey cadence or strategy).
To be applied by the Survey Scheduler team via the observations scheduler.
Observing mode labels might include, e.g., WFD, DDF, TOO, mini-survey name, or other
options like engineering, commissioning, and director's discretionary.
Observing mode labels should be propagated to single-visit processed and
Observing mode labels should be propagated to single-visit processed and
difference images and catalog sources.
It would not make sense to propagate observing mode labels to deep coadds or
object tables, as these data products could be a mix of modes.
It is left to the discretion of the Survey Scheduler team whether more than one
observing mode labels might be applied at a time and, e.g., held in a single string as a CSV.

A given image would probably only have one observing mode label


There are three main motivations for this recommendation.

Expand All @@ -38,10 +45,10 @@ \subsection{Region and Observing Mode Labels}\label{ssec:sci_labels}

\item To enable users to query and retrieve processed image and catalog
data associated with a specific Special Program, and meet the science goals
of that Special Program, when regular processing as been applied
of that Special Program, when standard processing as been applied
(e.g., Prompt Processing, Section~\ref{ssec:sci_pproc}).

\item To enable provenance when Special Programs data in included in regular
\item To enable provenance when Special Programs data in included in standard
processing and the Main Survey's data products (e.g., if used to improve the
all-sky coadd).

Expand All @@ -58,7 +65,7 @@ \subsection{Special Processing}\label{ssec:sci_sproc}
or significant additional computational resources, are needed.

\textbf{Necessary -- } When the primary science goal for a Special Program
cannot be met by including the data in regular processing (e.g., Prompt processing),
cannot be met by including the data in standard processing (e.g., Prompt processing),
or where doing so would compromise the Main Survey data products (e.g., introduce additional non-uniformity beyond what would be expected based on the survey strategy).

There are two main motivations for this recommendation.
Expand Down Expand Up @@ -99,7 +106,7 @@ \subsection{Prompt Processing}\label{ssec:sci_pproc}
enhanced by any and all additional observations, even if they are not
optimized for the science (as the WFD area's cadence is being optimized).

Further discussion of regular Prompt processing of Special Programs data, with
Further discussion of standard Prompt processing of Special Programs data, with
examples and a discussion of a few challenges,
is provided in Section~\ref{sssec:proc_reg_prompt}.

Expand Down

0 comments on commit 689c73c

Please sign in to comment.