From suyong@fnal.gov Thu May  6 09:42:34 2004
Date: Wed, 05 May 2004 23:14:23 -0500
From: Suyong Choi <suyong@fnal.gov>
To: Gordon Watts <gwatts@fnal.gov>
Cc: d0dfwg@fnal.gov
Subject: Re: summary of answers to Dfwg survey

    [ The following text is in the "ISO-8859-1" character set. ]
    [ Your display is set for the "US-ASCII" character set.  ]
    [ Some characters may be displayed incorrectly. ]

Hi,

I don't think DFWG has a long enough lifetime to address this.

We all know it's hard to get things developed for the framework and there's
no simple fix. Slow d0 environment is something we'll have to tackle.
It's one of the problems, but certainly not the only one.

Ideally, it'd be important to teach people about good design practices,
and that's more than
simply learning the syntax of C++. Patterns anyone? I don't think
anybody's going to pay for that.

I think the next algorithmic development  will be based on TMB++.
We're opening a pandora box with this format and we'll have to deal with it.
Who knows what people will think of with all the detector information
available.
People will take the path of least resistance and somebody will put the
hits in whatever root format we decide upon.

Human behavior factors are something that we cannot ignore in these matters,
since we have no control over what people do.
Especially, in cases where we don't have good tools. We don't have good
code/class browsers,
debuggers, profilers and class designers. All of which, I think, are
necessary to do
serious development these days.

So what will people do? They'll work with root-tuples and develop algorithms
based on that. I don't think people will use edmROOT, unless a good
code/interface browser is
provided. Nobody's patient enough to look up header files.

So then the question becomes which code would be easier to convert to
framework..

Suyong

>
>
>
>>Due to the slowness of working in d0 environment (linking, running, and
>>debugging),
>>algorithm development outside the framework is unavoidable.
>>However, algorithm development (using ROOT) should be done carefully,
>>especially the design of classes and packages, with assistance from
>>true software experts to make it  simple and portable.
>>It can be written so that it is not tied to any specific format.
>>
>>
>
>You are one of the people that is responsible for putting together reco.
>Have you given some thought to how one might solve this problem? If so,
>could you share any ideas you've had? :-)
>
>       Cheers,
>               Gordon.
>
>
>
>
>
>