Hi Ray,
I'm fine with most of the app framework libraries moving into
middleware/pipeline/appframework. They were placed in framework so that
other pipelines could make use of them.
I revise the structure to:
> >
middleware
pipeline
framework
policy
image handling
collection handling
> > <other general support libraries>
> > applications
> > pipeline
> > imageProcessing
> > <app modules/libraries>
> > <validation>
> > <scripts>
> > <docs>
> > movingObjectDetection
> > ....
>
> While we set up is not intended to be set in stone, I'll note that it was
> our intention that the part you call "framework" would go into
> middleware/pipeline/appframework. I think this reflects the UML model
> more (although perhaps the image handling stuff might be argued to be more
> application related). Comments?
>
We don't have any examples at the moment, but I'm assuming that there
will be non-pipeline applications to warrant the second level under
applications.
Robyn
_______________________________________________
LSST-data mailing list
[email protected]
http://www.lsstmail.org/mailman/listinfo/lsst-data
