add bold headings

sec_req.tex

@@ -2,12 +2,12 @@ \section{Requirements Related to Special Programs}\label{sec:req}
 % \lsrreq, \ossreq, \dmreq
 % \reqparam
 
-This section proves a summary of the requirements related to Special Programs.
-A more detailed list is provided in Appendix~\ref{sec:docrev}.
-
+Appendix~\ref{sec:docrev} provides a full description of the requirements 
+on the Data Management System related to Special Programs, which are summarized here.
 
 \subsection{Data Products}\label{ssec:req_dp}
 
+\textbf{Produce unique and special (and joinable) data products when possible --}
 Rubin Observatory and the LSST system (the observatory and the data 
 management systems) are required to process Special Programs data to 
 produce unique and separate data products ``whenever possible" 
@@ -25,64 +25,65 @@ \subsection{Data Products}\label{ssec:req_dp}
 images, difference images, and catalogs of sources and objects for those 
 images).
 
-It is a requirement that the cumulative size of the Special Programs data 
-products generated by Rubin Observatory be no more than $\sim$10\% the 
-size of the Data Release data products (i.e., proportional to the fraction 
-of survey time spent; LSR-REQ-0121).
-
 It is a requirement that these Special Programs data products be distinct, 
 and joinable with (in other words, they can be federated or cross-matched 
 with) the Prompt and Data Release data products (DMS-REQ-0322).
 
+\textbf{The data products' size should be about 10\% of the WFD programs' --}
+It is a requirement that the cumulative size of the Special Programs data 
+products generated by Rubin Observatory be no more than $\sim$10\% the 
+size of the Data Release data products (LSR-REQ-0121).
+The spirit of this requirement is that the size be proportional to the fraction 
+of survey time spent on Special Programs.
+
 The derivation of value-added data products, such as HiPS or MOC maps, for 
-Special Programs remains an open question (DMS-REQ-0379, 0383).
+Special Programs remains an open question (DMS-REQ-0379, 0383), and is not required.
+However, they are suggested to be produced with Special Processing where
+appropriate (Section~\ref{ssec:proc_special}).
 
 
 \subsection{Metadata}\label{ssec:req_meta}
 
+\textbf{Store metadata sufficient to trigger Special Processing -- }
 In order to support Special Programs processing, the LSST system is 
 required to store metadata that includes program information for every raw 
 image, such as identifiers for images obtained as part of the Main Survey 
 or a Special Program (DMS-REQ-0068).
-
 It is required that this metadata be sufficient for Special Programs to 
 trigger their own real-time data processing recipes ``whenever possible" 
 (DMS-REQ-0320), and be included in alert packets (DMS-REQ-0274).
 
 
 \subsection{Processing}\label{ssec:req_proc}
 
+\textbf{Latency requirements apply to alerts from Special Programs images --}
 It is a requirement that any Special Programs processing done with the 
 Prompt pipeline (or a reconfigured version of it) is subject to the same 
 timescales and latency constraints of 24 hours for the release of Prompt 
 data products and 1 minute for the transmission of Alert packets 
 (DMS-REQ-0344).
 
+\textbf{Intermediate timescales should be used to enable science --}
 It is also a requirement that Special Programs processing be done on 
 timescales intermediate to the Prompt and Data Release processing, 
 ``whenever possible" and whenever necessary to enable the intended science 
 goals of the Special Program (LSR-REQ-0032).
 
+\textbf{Exposure times of 1 second must be processable -- }
 It is a requirement that the LSST system be able to process non-standard 
 visits with short exposure times as low as 1 second, with a discussion 
 note that such short exposures might have degraded image quality 
 (LSR-REQ-0111).
 
-Processing for Special Programs by Rubin Observatory is expected to use no 
-more than $\sim$10\% of computational and storage capacity of the Rubin 
-data processing cluster (i.e., proportional to the fraction of survey time 
-spent and the size of the Rubin-processed Special Programs data products; 
-Section 6 of the DPDD).
+It is not a requirement, but processing for Special Programs by Rubin Observatory is expected to use no 
+more than $\sim$10\% of computational and storage capacity of the Rubin data processing cluster 
+(i.e., proportional to the fraction of survey time spent; Section 6 of LSE-163).
 
 
 \subsection{User Processing}\label{ssec:req_ug}
 
-In cases where the science goals of a Special Program require that new 
-algorithms or software be developed, User-Generated pipelines and data 
-products will be needed.
-
 The 10\% of the total data processing capacity that Rubin Observatory is 
-required to reserve for all User-Generated processing includes that 
-applied by users to Special Programs data -- in other words, there is no 
-additional capacity {\it for users} that will be reserved only for Special 
+required to reserve for \emph{all} User-Generated Processing includes that 
+applied by users to Special Programs data.
+There is no additional capacity {\it for users} that will be reserved only for Special 
 Programs data (LSR-REQ-0041).