[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Introduction and some comments ;-)
--- Mark Pitts <PITTS@shands.ufl.edu> wrote:
> Greetings all,
>
><SNIP>
> Bottom line: the first thing you need is a project plan. With a
> good plan, we could farm out the work to those most qualified to
> perform each task. Collaboratively, we could get the data reduction
> flowing toward some usable results.
>
> Thoughts?
>
> Mark
Here is one person's opinion:
Our problem is a little easier. The data reduction that needs to
be done is well understood. We are by far not the first to do this.
We are more like a group of people sitting on a ton
of iron oar wishing we had steel. The process itself is known
but who builds the steel plant? where? do we want to use coal or
gas? one big plant or ten smaller ones. and so on and so on.
The big problems are all logistical and political. Yes there are
technical details but really they are just that, details. In our
case we know the data formats for the images, we know what object
lists look like and many of us can point to multiple examples of
software that get you from images to lists.
The current state of the art with TASS is that data reduction is a
"craft" that is done by a few people by hand, each using his own
methods and bits of borrowed code. What we need is a modern
"lights out" factory. The technical work required to go from the
"18th century arts and craft" stage to "21st century lights out
automation" mostly involves editing a pile of small scripts and
configuration files. Nothing like heavy duty software engineering
is needed. I think because everyone knows it is not a huge
engineering job is what makes not having it done so frustrating.
=====
Chris Albertson
Home: 310-376-1029 chrisalbertson90278@yahoo.com
Cell: 310-990-7550
Office: 310-336-5189 Christopher.J.Albertson@aero.org
__________________________________________________
Do You Yahoo!?
Great stuff seeking new owners in Yahoo! Auctions!
http://auctions.yahoo.com