add etiquete ..

DMTN-223.tex

@@ -1,4 +1,4 @@
-\documentclass[DM,lsstdraft,authoryear,toc]{lsstdoc}
+\documentclass[DM,authoryear,toc]{lsstdoc}
 % lsstdoc documentation: https://lsst-texmf.lsst.io/lsstdoc.html
 \input{meta}
 
@@ -37,7 +37,7 @@
 % Fields: VERSION, DATE, DESCRIPTION, OWNER NAME.
 % See LPM-51 for version number policy.
 \setDocChangeRecord{%
-  \addtohist{1}{YYYY-MM-DD}{Unreleased.}{William O'Mullane}
+  \addtohist{1}{2022-12-14}{Unreleased.}{William O'Mullane}
 }
 
 

proposal.tex

@@ -51,6 +51,17 @@ \subsection{BPS Batch }\label{sec:bpsbatch}
 This BPS fronted system would meet \citeds{DMTN-202} points 1-5 (\secref{sec:requirements}). The Point 4 on catalogs can be met with Qserv.
 This would also cover DMS-REQ-0119, DMS-REQ-0125, DMS-REQ-0128, DMS-REQ-0123, DMS-REQ-0127.
 
+\subsubsection{Interactive vs Batch} \label{sec:interactivevbatch}
+User will need to consider when they should switch to batch.
+This will largely be a function how long the user is willing to wait,` how big their job is and how repeatable it is.
+Processing say a full focal plane image on RSP with interactive processing via DASK should take some minutes and should be fine.
+Should one wish to process ten focal planes (hence > 1K images)  it may become tedious and be more suited to batch. i
+That of course means  one is not tweaking the code each time.
+We will have to settle on a guide number for where switching to batch makes more sense but between 500 and 1K images would
+seem to be the point where a user is falling more in the batch realm.
+Also if one is processing 1K images it will probably soon be 2 or 3K or more.
+
+
 
 \subsubsection{Non Rubin code} \label{sec:othercode}
 Users may wish to run arbitrary code on Rubin images.