-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
8 changed files
with
1,131 additions
and
51 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,6 @@ | ||
| [submodule "lsst-texmf"] | ||
| path = lsst-texmf | ||
| url = git@github.com:lsst/lsst-texmf | ||
| url = https://github.com/lsst/lsst-texmf | ||
| [submodule "images"] | ||
| path = images | ||
| url = git@github.com:lsst-dm/images | ||
| url = https://github.com/lsst-dm/images |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,57 @@ | ||
| \addtocounter{table}{-1} | ||
| \begin{longtable}{|p{0.145\textwidth}|p{0.8\textwidth}|}\hline | ||
| \textbf{Acronym} & \textbf{Description} \\\hline | ||
|
|
||
| ATM & Adaptavist Test Management \\\hline | ||
| Archive & 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. \\\hline | ||
| CC & Change Control \\\hline | ||
| CI & Cyber Infrastructure \\\hline | ||
| Center & An entity managed by AURA that is responsible for execution of a federally funded project \\\hline | ||
| Change Control & The systematic approach to managing all changes to the LSST system, including technical data and policy documentation. The purpose is to ensure that no unnecessary changes are made, all changes are documented, and resources are used efficiently and appropriately. \\\hline | ||
| DAC & Data Access Center \\\hline | ||
| DM & Data Management \\\hline | ||
| DMS & Data Management Subsystem \\\hline | ||
| DR & Data Release \\\hline | ||
| DRP & Data Release Production \\\hline | ||
| Data Access Center & Part of the LSST Data Management System, the US and Chilean DACs will provide authorized access to the released LSST data products, software such as the Science Platform, and computational resources for data analysis. The US DAC also includes a service for distributing bulk data on daily and annual (Data Release) timescales to partner institutions, collaborations, and LSST Education and Public Outreach (EPO). \\\hline | ||
| Data Management & 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. \\\hline | ||
| Data Management Subsystem & 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'"." \\\hline | ||
| Data Management System & 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. \\\hline | ||
| Data Release & 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. \\\hline | ||
| DocuShare & The trade name for the enterprise management software used by LSST to archive and manage documents \\\hline | ||
| Document & 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 \\\hline | ||
| EPO & Education and Public Outreach \\\hline | ||
| ForcedSource & DRP table resulting from forced photometry. \\\hline | ||
| HSC & Hyper Suprime-Cam \\\hline | ||
| Handle & The unique identifier assigned to a document uploaded to DocuShare \\\hline | ||
| IRSA & Infrared Science Archive \\\hline | ||
| LDM & LSST Data Management (Document Handle) \\\hline | ||
| LSST & Large Synoptic Survey Telescope \\\hline | ||
| NCSA & National Center for Supercomputing Applications \\\hline | ||
| Object & 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. \\\hline | ||
| PDAC & Prototype Data Access Center \\\hline | ||
| QA & Quality Assurance \\\hline | ||
| Qserv & LSST's distributed parallel database. This database server is used for collecting, storing, and serving LSST Data Release Catalogs and Project metadata, and is part of the Software Stack. \\\hline | ||
| RAM & Random Access Memory \\\hline | ||
| SDSS & Sloan Digital Sky Survey \\\hline | ||
| Science Platform & 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. \\\hline | ||
| Scope & The work needed to be accomplished in order to deliver the product, service, or result with the specified features and functions \\\hline | ||
| Sloan Digital Sky Survey & is a digital survey of roughly 10,000 square degrees of sky around the north Galactic pole, plus a ~300 square degree stripe along the celestial equator. \\\hline | ||
| Software Stack & 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. \\\hline | ||
| Solar System Object & 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. \\\hline | ||
| Source & 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.) \\\hline | ||
| Specification & One or more performance parameter(s) being established by a requirement that the delivered system or subsystem must meet \\\hline | ||
| Stripe 82 & A 2.5° wide equatorial band of sky covering roughly 300 square degrees that was observed repeatedly in 5 passbands during the course of the SDSS, In part for calibration purposes. \\\hline | ||
| Subsystem & A set of elements comprising a system within the larger LSST system that is responsible for a key technical deliverable of the project. \\\hline | ||
| Subsystem Manager & 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 \\\hline | ||
| TB & TeraByte \\\hline | ||
| US & United States \\\hline | ||
| Validation & A process of confirming that the delivered system will provide its desired functionality; overall, a validation process includes the evaluation, integration, and test activities carried out at the system level to ensure that the final developed system satisfies the intent and performance of that system in operations \\\hline | ||
| Verification & The process of evaluating the design, including hardware and software - to ensure the requirements have been met; verification (of requirements) is performed by test, analysis, inspection, and/or demonstration \\\hline | ||
| astronomical object & A star, galaxy, asteroid, or other physical object of astronomical interest. Beware: in non-LSST usage, these are often known as sources. \\\hline | ||
| calibration & The process of translating signals produced by a measuring instrument such as a telescope and camera into physical units such as flux, which are used for scientific analysis. Calibration removes most of the contributions to the signal from environmental and instrumental factors, such that only the astronomical component remains. \\\hline | ||
| forced photometry & A measurement of the photometric properties of a source, or expected source, with one or more parameters held fixed. Most often this means fixing the location of the center of the brightness profile (which may be known or predicted in advance), and measuring other properties such as total brightness, shape, and orientation. Forced photometry will be done for all Objects in the Data Release Production. \\\hline | ||
| metadata & 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). \\\hline | ||
| monitoring & In DM QA, this refers to the process of collecting, storing, aggregating and visualizing metrics. \\\hline | ||
| stack & a grouping, usually in layers (hence stack), of software packages and services to achieve a common goal. Often providing a higher level set of end user oriented services and tools \\\hline | ||
| \end{longtable} |
Oops, something went wrong.