- Timestamp:
- Apr 4, 2017, 12:28:13 PM (9 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/release.2015/ps1.datasystem/datasystem.tex
r40004 r40009 177 177 178 178 \section{Overview of Pan-STARRS Data Processing} 179 \label{sec:overview} 179 180 180 181 The Pan-STARRS Data Analysis system contains many features to support … … 291 292 292 293 \subsection{Processing Database} 293 \label{sec: database}294 \label{sec:processing.database} 294 295 295 296 A critical element in the Pan-STARRS IPP infrastructure is the … … 1022 1023 1023 1024 \section{Post-Processing : Database Ingest \& Calibration} 1025 \label{sec:postprocessing} 1024 1026 1025 1027 \subsection{DVO} … … 1395 1397 \subsection{Pantasks \& Parallel Processing} 1396 1398 \label{sec:pantasks} 1399 1400 Sections~\ref{sec:subsystesm} \& \ref{sec:postprocessing} describe the 1401 analysis steps which take place in the Pan-STARRS data analysis 1402 systems. Individually, these steps appear as commands which could be 1403 run by a user within the UNIX environment of the PS1 data system. The 1404 processing database (Section~\ref{sec:processing.database}) provides 1405 the logical links to relate the results of one analysis stage to 1406 another. In order to make a complete system which can run 1407 automatically, it is necessary to have a process which can use the 1408 contents of the processing database to generate the commands 1409 corresponding to the analysis stages. This system needs to (1) 1410 regularly examine the database to find items from stages which are 1411 ready to be processed, (2) to have rules which define how to construct 1412 the appropriate commands, (3) to cause those commands to be executed 1413 within the processing system, (4) to monitor the active processing 1414 jobs for completion, and (5) to check on the results of those 1415 commands and update the processing database as needed. Within the 1416 Pan-STARRS IPP, the top-level management of these operations is 1417 performed with the program called \ippprog{pantasks}. 1418 1419 The core capability of the \ippprog{pantasks} program is to take a 1420 collection of ``tasks'' which describe the concept of a command which 1421 might be run and to regularly generate new commands based on that 1422 concept. These commands may the be run by the pantasks program 1423 directly, or they may be passed to another program which 1424 1425 * task vs job 1397 1426 1398 1427 \note{this section needs to be re-written : pclient vs pcontrol vs pantasks}
Note:
See TracChangeset
for help on using the changeset viewer.
