Skip to content

Commit

Permalink
Merge pull request #6 from lsst/tickets/RFC-598
Browse files Browse the repository at this point in the history
Merge to master - but as draft
  • Loading branch information
womullan committed Jun 3, 2019
2 parents 51cf81a + 66862d0 commit b20fdcc
Show file tree
Hide file tree
Showing 4 changed files with 35 additions and 8 deletions.
Binary file added LDM-702.pdf
Binary file not shown.
7 changes: 4 additions & 3 deletions LDM-702.tex
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@
% \setDocSubtitle{A subtitle}

\author{%
Willliam O'Mullane
William O'Mullane
}

\setDocRef{LDM-702}
Expand All @@ -40,7 +40,7 @@
% Fields: VERSION, DATE, DESCRIPTION, OWNER NAME.
% See LPM-51 for version number policy.
\setDocChangeRecord{%
\addtohist{1}{YYYY-MM-DD}{Unreleased.}{Willliam O'Mullane}
\addtohist{1}{2019-06-03}{First Issue.}{William O'Mullane}
}

\begin{document}
Expand All @@ -57,7 +57,8 @@
\appendix
% Include all the relevant bib files.
% https://lsst-texmf.lsst.io/lsstdoc.html#bibliographies
\section{References} \label{sec:bib}
\section{References } \label{sec:bib}
\renewcommand{\refname}{}
\bibliography{lsst,lsst-dm,refs_ads,refs,books}

%Make sure lsst-texmf/bin/generateAcronyms.py is in your path
Expand Down
26 changes: 26 additions & 0 deletions aglossary.tex
Original file line number Diff line number Diff line change
@@ -1,31 +1,57 @@
% DO NOT EDIT - generated by /Users/womullan/LSSTgit/lsst-texmf/bin/generateAcronyms.py from https://lsst-texmf.lsst.io/.
\newglossaryentry{Alert} {name={Alert}, description={A packet of information for each source detected with signal-to-noise ratio > 5 in a difference image during Prompt Processing, containing measurement and characterization parameters based on the past 12 months of LSST observations plus small cutouts of the single-visit, template, and difference images, distributed via the internet.}}
\newglossaryentry{Alert Production} {name={Alert Production}, description={The principal component of Prompt Processing that processes and calibrates incoming images, performs Difference Image Analysis to identify DIASources and DIAObjects, packages and distributes the resulting Alerts, and runs the Moving Object Processing System.}}
\newglossaryentry{Archive} {name={Archive}, description={The repository for documents required by the NSF to be kept. These include documents related to design and development, construction, integration, test, and operations of the LSST observatory system. The archive is maintained using the enterprise content management system DocuShare, which is accessible through a link on the project website www.project.lsst.org.}}
\newglossaryentry{Archive Center} {name={Archive Center}, description={Part of the LSST Data Management System, the LSST archive center is a data center at NCSA that hosts the LSST Archive, which includes released science data and metadata, observatory and engineering data, and supporting software such as the LSST Software Stack.}}
\newglossaryentry{Association Pipeline} {name={Association Pipeline}, description={An application that matches detected Sources or DIASources or generated Objects to an existing catalog of Objects, producing a (possibly many-to-many) set of associations and a list of unassociated inputs. Association Pipelines are used in Prompt Processing after DIASource generation and in the final stages of Data Release processing to ensure continuity of Object identifiers.}}
\newglossaryentry{Center} {name={Center}, description={An entity managed by AURA that is responsible for execution of a federally funded project}}
\newglossaryentry{DIASource} {name={DIASource}, description={A DIASource is a detection with signal-to-noise ratio greater than 5 in a difference image.}}
\newacronym{DM} {DM} {\gls{Data Management}}
\newglossaryentry{DMLT} {name={DMLT}, description={DM Leadership Team}}
\newacronym{DMS} {DMS} {Data Management Subsystem}
\newglossaryentry{DMTN} {name={DMTN}, description={DM Technical Note}}
\newacronym{DR} {DR} {Data Release}
\newacronym{DRP} {DRP} {Data Release Production}
\newglossaryentry{Data Management} {name={Data Management}, description={The LSST Subsystem responsible for the Data Management System (DMS), which will capture, store, catalog, and serve the LSST dataset to the scientific community and public. The DM team is responsible for the DMS architecture, applications, middleware, infrastructure, algorithms, and Observatory Network Design. DM is a distributed team working at LSST and partner institutions, with the DM Subsystem Manager located at LSST headquarters in Tucson.}}
\newglossaryentry{Data Management Subsystem} {name={Data Management Subsystem}, description={The subsystems within Data Management may contain a defined combination of hardware, a software stack, a set of running processes, and the people who manage them: they are a major component of the DM System operations. Examples include the 'Archive Operations Subsystem' and the 'Data Processing Subsystem'"."}}
\newglossaryentry{Data Management System} {name={Data Management System}, description={The computing infrastructure, middleware, and applications that process, store, and enable information extraction from the LSST dataset; the DMS will process peta-scale data volume, convert raw images into a faithful representation of the universe, and archive the results in a useful form. The infrastructure layer consists of the computing, storage, networking hardware, and system software. The middleware layer handles distributed processing, data access, user interface, and system operations services. The applications layer includes the data pipelines and the science data archives' products and services.}}
\newglossaryentry{Data Release} {name={Data Release}, description={The approximately annual reprocessing of all LSST data, and the installation of the resulting data products in the LSST Data Access Centers, which marks the start of the two-year proprietary period.}}
\newglossaryentry{Data Release Production} {name={Data Release Production}, description={An episode of (re)processing all of the accumulated LSST images, during which all output DR data products are generated. These episodes are planned to occur annually during the LSST survey, and the processing will be executed at the Archive Center. This includes Difference Imaging Analysis, generating deep Coadd Images, Source detection and association, creating Object and Solar System Object catalogs, and related metadata.}}
\newglossaryentry{Difference Image} {name={Difference Image}, description={Refers to the result formed from the pixel-by-pixel difference of two images of the sky, after warping to the same pixel grid, scaling to the same photometric response, matching to the same PSF shape, and applying a correction for Differential Chromatic Refraction. The pixels in a difference thus formed should be zero (apart from noise) except for sources that are new, or have changed in brightness or position. In the LSST context, the difference is generally taken between a visit image and template. }}
\newglossaryentry{Difference Image Analysis} {name={Difference Image Analysis}, description={The detection and characterization of sources in the Difference Image that are above a configurable threshold, done as part of Alert Generation Pipeline.}}
\newglossaryentry{DocuShare} {name={DocuShare}, description={The trade name for the enterprise management software used by LSST to archive and manage documents}}
\newglossaryentry{Document} {name={Document}, description={Any object (in any application supported by DocuShare or design archives such as PDMWorks or GIT) that supports project management or records milestones and deliverables of the LSST Project}}
\newacronym{FITS} {FITS} {\gls{Flexible Image Transport System}}
\newglossaryentry{Firefly} {name={Firefly}, description={A framework of software components written by IPAC for building web-based user interfaces to astronomical archives, through which data may be searched and retrieved, and viewed as \gls{FITS} images, catalogs, and/or plots. Firefly tools will be integrated into the Science Platform.}}
\newglossaryentry{Flexible Image Transport System} {name={Flexible Image Transport System}, description={an international standard in astronomy for storing images, tables, and metadata in disk files. See the IAU FITS Standard for details.}}
\newglossaryentry{Handle} {name={Handle}, description={The unique identifier assigned to a document uploaded to DocuShare}}
\newacronym{IAU} {IAU} {International Astronomical Union}
\newglossaryentry{IPAC} {name={IPAC}, description={No longer an acronym; science and data center at Caltech}}
\newglossaryentry{LDM} {name={LDM}, description={LSST Data Management (Document Handle)}}
\newacronym{LSP} {LSP} {LSST Science Platform}
\newacronym{LSST} {LSST} {Large Synoptic Survey Telescope}
\newacronym{MOPS} {MOPS} {Moving Object Processing System}
\newglossaryentry{Moving Object Processing System} {name={Moving Object Processing System}, description={The Moving Object Processing System (MOPS) identifies new SSObjects using unassociated DIASources. MOPS is part of the Science Pipelines.}}
\newglossaryentry{NCSA} {name={NCSA}, description={National Center for Supercomputing Applications}}
\newacronym{NSF} {NSF} {\gls{National Science Foundation}}
\newglossaryentry{Object} {name={Object}, description={In LSST nomenclature this refers to an astronomical object, such as a star, galaxy, or other physical entity. E.g., comets, asteroids are also Objects but typically called a Moving Object or a Solar System Object (SSObject). One of the DRP data products is a table of Objects detected by LSST which can be static, or change brightness or position with time.}}
\newglossaryentry{Operations} {name={Operations}, description={The 10-year period following construction and commissioning during which the LSST Observatory conducts its survey}}
\newglossaryentry{Project Manager} {name={Project Manager}, description={The person responsible for exercising leadership and oversight over the entire LSST project; he or she controls schedule, budget, and all contingency funds}}
\newglossaryentry{Prompt Processing} {name={Prompt Processing}, description={The processing that occurs at the Archive Center on the nightly stream of raw images coming from the telescope, including Difference Imaging Analysis, Alert Production, and the Moving Object Processing System. This processing generates Prompt Data Products.}}
\newacronym{QA} {QA} {Quality Assurance}
\newglossaryentry{Science Pipelines} {name={Science Pipelines}, description={The library of software components and the algorithms and processing pipelines assembled from them that are being developed by DM to generate science-ready data products from LSST images. The Pipelines may be executed at scale as part of LSST Prompt or Data Release processing, or pieces of them may be used in a standalone mode or executed through the LSST Science Platform. The Science Pipelines are one component of the LSST Software Stack.}}
\newglossaryentry{Science Platform} {name={Science Platform}, description={A set of integrated web applications and services deployed at the LSST Data Access Centers (DACs) through which the scientific community will access, visualize, and perform next-to-the-data analysis of the LSST data products.}}
\newglossaryentry{Scope} {name={Scope}, description={The work needed to be accomplished in order to deliver the product, service, or result with the specified features and functions}}
\newglossaryentry{Software Stack} {name={Software Stack}, description={Often referred to as the LSST Stack, or just The Stack, it is the collection of software written by the LSST Data Management Team to process, generate, and serve LSST images, transient alerts, and catalogs. The Stack includes the LSST Science Pipelines, as well as packages upon which the DM software depends. It is open source and publicly available.}}
\newglossaryentry{Solar System Object} {name={Solar System Object}, description={A solar system object is an astrophysical object that is identified as part of the Solar System: planets and their satellites, asteroids, comets, etc. This class of object had historically been referred to within the LSST Project as Moving Objects.}}
\newglossaryentry{Source} {name={Source}, description={A single detection of an astrophysical object in an image, the characteristics for which are stored in the Source Catalog of the DRP database. The association of Sources that are non-moving lead to Objects; the association of moving Sources leads to Solar System Objects. (Note that in non-LSST usage "source" is often used for what LSST calls an Object.)}}
\newglossaryentry{Subsystem} {name={Subsystem}, description={A set of elements comprising a system within the larger LSST system that is responsible for a key technical deliverable of the project.}}
\newglossaryentry{Subsystem Manager} {name={Subsystem Manager}, description={responsible manager for an LSST subsystem; he or she exercises authority, within prescribed limits and under scrutiny of the Project Manager, over the relevant subsystem's cost, schedule, and work plans}}
\newacronym{TOR} {TOR} {Terms Of Refference}
\newacronym{WG} {WG} {Working Group}
\newglossaryentry{astronomical object} {name={astronomical object}, description={A star, galaxy, asteroid, or other physical object of astronomical interest. Beware: in non-LSST usage, these are often known as sources.}}
\newglossaryentry{camera} {name={camera}, description={An imaging device mounted at a telescope focal plane, composed of optics, a shutter, a set of filters, and one or more sensors arranged in a focal plane array.}}
\newglossaryentry{metadata} {name={metadata}, description={General term for data about data, e.g., attributes of astronomical objects (e.g. images, sources, astroObjects, etc.) that are characteristics of the objects themselves, and facilitate the organization, preservation, and query of data sets. (E.g., a FITS header contains metadata).}}
\newglossaryentry{pipeline} {name={pipeline}, description={A configured sequence of software tasks (Stages) to process data and generate data products. Example: Association Pipeline.}}
\newglossaryentry{stack} {name={stack}, description={A record of all versions of a document uploaded to a particular DocuShare handle}}
\newglossaryentry{transient} {name={transient}, description={A transient source is one that has been detected on a difference image, but has not been associated with either an astronomical object or a solar system body.}}
10 changes: 5 additions & 5 deletions body.tex
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
\section{Scope}

This Working Group is to look into image display for pipeline developers as well as \gls{QA} and commissioning staff.
It should start by June 1$^{st}$ 2019 and conclude by the Project and Community Workshop in August 2019 with an interim report at \gls{DMLT} in July.
It should start by June 1$^{st}$ 2019 and conclude by the Project and Community Workshop in August 2019 with an interim report to the \gls{DMLT} in July.


\section{Responsibilities}
Expand All @@ -17,16 +17,16 @@ \section{Responsibilities}
\item Consider if Firefly is sufficient for portal use cases.
\item The \gls{WG} Chair shall convene meetings on a regular basis.
\item The \gls{WG} will make a recommendation on minimum and desirable image display functionality, potentially identifying tools (not necessarily a single tool) which could be used in each case, and identifying use cases where the existing tools are not sufficient.
\item The \gls{WG} will draft a report with some recommendations for the consideration of \gls{DMLT}.
\item The \gls{WG} will draft a report (DMTN) with some recommendations for the consideration of \gls{DMLT}.
\end{itemize}


\section{Specific tasks}

\subsection{Draft use case/requirements document(s)}
Consolidate and classify use cases for image display in a single document. This is not just for the \gls{LSP} but rather a cross cutting document. This should clearly identify \gls{DM} requirements and \gls{DM} desirable functionality and like wise for what may be considered non \gls{DM} requirement.
Consolidate and classify use cases for image display in a single document. This is not just for the \gls{LSP} but rather a cross cutting document. This should clearly identify \gls{DM} requirements and \gls{DM} desirable functionality and like wise for what may be considered non \gls{DM} requirements.
The group should decide if they wish to spend a little time on understanding the camera diagnostic display requirements, care should be taken to not spend a lot of effort to scope non \gls{DM} work however. It may be preferable to spend time consulting with camera when a consolidated list is available.
In general cost and scope should be considered.
In general cost and scope should be considered - a cash amount has been held specifically for this task, should it be needed it this. There is about 900k there, of which $\approx600K$ was intended for the portal revamp in 2022/23 leaving about 300K for the image display needs. \footnote{\url{https://project.lsst.org/groups/ccb/node/2930}}.


\section{Membership}
Expand All @@ -38,7 +38,7 @@ \section{Membership}
\item John Swinbank (as custodian of \citeds{DMTN-085}),
\item Lauren MacArthur
\item Simon Krughoff
\item Gregory Dubois Felsmann
\item Gregory Dubois-Felsmann
\end{itemize}

\section{Reporting}
Expand Down

0 comments on commit b20fdcc

Please sign in to comment.