Hi Russ, This maps quite well. The only reason to not combine Pipeline Exec and Pipeline Construction is that we currently have two different groups of folks working on each one.
Jeff > From: Russell E Owen <[EMAIL PROTECTED]> > Reply-To: LSST Data Management <[email protected]> > Date: Fri, 14 Jul 2006 16:04:34 -0700 > To: LSST-data mailing list <[email protected]> > Subject: [LSST-data] svn applictions dir [Software Standards] > > Also, the applications dir in the svn repository could have sublevels > to match the EA model. This may be premature for DC1, but here's a > suggested layout in case we should do it now. > > applications > alert (Alert Processing) > associate (Association) > calibrate (Calibration) > classify (Classification) > community (Community Science) > deepdet (Deep Detection) > imageproc (Image Processing) > movingobj (Moving Object) > > As a reminder, the suggested middleware layout was as follows (since > a consistent level if abbreviation is desirable): > > middleware > das (data access services) > catalog (catalog construction) > query (querying) > ingest (data ingest) > dps (distributed processing services) > control (Control and Management) > pipeconst (Pipeline Construction) > pipeexec (Pipeline Execution) > (or pipeline if we can consolidate the previous two) > security > sysadmin (Sys Admin and Opns Services) > ui (User Interface Services) > > -- Russell > _______________________________________________ > LSST-data mailing list > [email protected] > http://www.lsstmail.org/mailman/listinfo/lsst-data > _______________________________________________ LSST-data mailing list [email protected] http://www.lsstmail.org/mailman/listinfo/lsst-data
