Hi Nina,

the green and the black lines are two possibilities to go through the
workflow. In the pdf the workflow has to be read from bottom to top
(more or less). Everything starts with some prediction application (e.g.
ToxPredict or a ValidationService,...) that needs descriptors to be
recalculated for prediction. I added the third variant in red arrows and
made 3 out of the one slide to make it easier readable.

In version 1 (black) no descriptor recalculation service is needed and
every model service has to delegate the descriptor recalculation to all
descriptor calculation services.
In version 2 (green) the descriptor recalculation service is called by
the model service. The recalc service delegates the necessary descriptor
calculations. In both cases the model service gets a dataset that has
not all the descriptors needed to use the model for predicting the
dataset.
In version 3 (red) the descriptor recalculation service is called
directly by the application, delegates the descriptor calculations at
updates the dataset. This updated dataset is the submitted by the
application itself to the model service.

I hope this clarifies my rough sketch from last week.

regards,
Tobias

On Tue, 2010-04-20 at 14:42 +0300, Nina Jeliazkova wrote: 
> Hi Tobias,
> 
> Could you tell what's the difference between black and green lines in
> your schema?
> 
> I would suggest starting a new wiki page under API to discuss descriptor
> calculator and its API.
> 
> Best regards,
> Nina
> 
> Tobias Girschick wrote:
> > Hi All,
> >
> > I attached one slide which illustrates the problem from my point of
> > view. The green and the black lines are the two possibilities. Note that
> > the "descriptor recalculator" has to be implemented only once (if it is
> > generic). Otherwise, every new algorithm that learns models has to
> > provide the whole functionality of calling all the different descriptor
> > calculation services. 
> >
> > I think that wrapping the distribution to the different descriptor
> > calculation services makes things a lot easier. 
> >
> > Just to again kick-off the discussion.
> > regards,
> > Tobias
> >
> >   
> 


-- 
Dipl.-Bioinf. Tobias Girschick

Technische Universität München
Institut für Informatik
Lehrstuhl I12 - Bioinformatik
Bolzmannstr. 3
85748 Garching b. München, Germany

Room: MI 01.09.042
Phone: +49 (89) 289-18002
Email: tobias.girschick at in.tum.de
Web: http://wwwkramer.in.tum.de/girschick
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenTox_descriptorRecalc_Prob.pdf
Type: application/pdf
Size: 33238 bytes
Desc: not available
URL: <http://lists.opentox.org/pipermail/development/attachments/20100420/28f15ffd/attachment.pdf>