From: rasure@snidley.eece.unm.edu (John Rasure)
Newsgroups: comp.soft-sys.khoros
Subject: Re: Preparing for K2 (LONGish)
Date: 16 Oct 92 20:48:30 GMT
Article-I.D.: pprg.41032


In "Preparing for K2 (LONGish)", Patrick Haggard writes:
+ 
+ Hi.  I've just been reading some of the documentation about khoros2.0.
+ It looks like a powerful and well-thought-out system.  The new VIFF
+ seems to be very powerful, and the use of a common format for 
+ 1D thru' 4D signals will be really helpful.

I just updated the Khoros 2.0 Overview document - it now has a pretty
picture to go with all of the fancy words.
(ftp pprg.eece.unm.edu, then cd pub/khoros/khoros_2.0 and get overview.ps.Z)

I should remind or inform everyone that in Khoros 2.0 you won't program
to the VIFF at all.  It just represents an implementation of one possible
way to store data that is in the abstract data model at the "Abstract
Data Services" layer of the "Distributed Data Services Toolkit".

The Khoros Group spent about 4 years evolving and developing Khoros
1.0 Patch 5.  We have done a complete redesign and new implementation
for Khoros 2.0.  It is really pretty exciting to us .... I hope that it
will be to you.  We have managed to take most of the experience and 
knowledge gained in creating Khoros 1.0 and put it into Khoros 2.0.
In general terms, we have carefully defined new layers of abstraction
and developed libraries to support the layer, then we have grouped
similar libraries into programming toolkits.  The goal being that we
want to create a very powerful software development environment.

+ 
+ So, I'm really looking forward to using k2.  However, it would help
+ us plan our research strategy to know more about how it is
+ progressing.  The overview documents suggest that k2 alpha will be
+ distributed to the consortium this month.  Is this still on schedule?

We are behind schedule.  What always seems to happen to us is that as
we develop something new, we aren't afraid of taking risks and trying
new things.  Well, in this case, too many good ideas have panned out, and
they are taking a lot of time to finalize.
(I will be more specific about our schedule when we have determined new
 release dates).

+ If so, would it be possible/fair/helpful for the consortium members
+ to comment in this group about their impressions of k2, and to make
+ public general information about how to use k2?  In particular, it 

One of the motivations of joining the consortium is to get early releases
of the software and to participate in the goals of the project.

+ would be very useful to have reports of evaluation of k2 for
+ particular applications such as 2D and 3D imaging, signal processing
+ etc, from the consortium so that other users can prepare for the new
+ capabilities.  For example, the new VIFF will support 3D and 4D, and I
+ would be very interested to know what sort of routines for working with
+ volumes and sequences will come with k2?
+ Are the khoros group happy about this idea about diffusing k2
+ information?  If so, could some people from the consortium volunteer
+ to answer questions and post updates on their experiences on evaluating k2?

The consortium members will have a separate mailing list to use to
get support on and discuss Alpha.  Remember, we are supplying Khoros at
no cost - the funding generated from the Consortium is what is making
the Open Distribution of Khoros possible.

+ 
+ Second, will the beta release, originally scheduled for February 93,
+ be a public release, available on the same basis as k1?  The reason
+ I ask is that I am about to apply for funding for a project beginning
+ in early 93 which will require 3D imaging, work with isosurfaces etc.
+ I would like to do this work in k2 if possible.  But if k2 is unlikely
+ to be available when the project starts, then I will need to consider
+ other software (though I would rather not, because I like khoros).
+ 
+ Third, will the initial releases of k2 have all the functionality of
+ k1?  Will existing k1 toolboxes work under k2 without major
+ alteration?  If so, then we will be able to get using k2 much faster.

The strongest desire of the consortium members for the Alpha release is
that they be able to begin to port old toolboxes and applications to the
new system.  So the emphasis is the Core Toolbox as described in the
document mentioned earlier.  As we move to the public release, we will
bring on line the other toolboxes.

+ 
+ *FINALLY* I would just like to point out that I do *NOT* want to
+ hassle the khoros group.  I really appreciate that they must be
+ working flat out on k2, and I would like to thank them for their

Thanks.

+ great efforts.  I don't want to push them any harder, but it would
+ be useful to have brief information about the progress of the k2 
+ project, so users can plan ahead.  Further, I'ld like to ask if 
+ there is anything that *WE* can do to help the khoros group in the

Mail of this nature is useful and participation with the newsgroup
will help relive us from "maintaining" it (I should add that I think the
community is doing a great job).

But most importantly, we need help in building the Khoros Consortium.
We have not very actively marketed the Consortium yet, we will be in
the best position to do this with the technology that Khoros 2.0
provides.  (I should add that we now have 9 members and that the
Consortium is gaining momentum.  For more information, mail 
sauer@chama.eece.unm.edu).

+ development of k2?  If there are any basic tasks which the user
+ community can help with I think many of us would be glkand to
+ contribute.

John Rasure

+ 
+ Sorry about the length of this: I hope it generates useful discussion
+ and facilitates the progress to k2.
+ 
+ Patrick
+ 
+ - --------------------------------------------------------------------------
+ Patrick Haggard				Email (WORLD): ph@physiol.ox.ac.uk
+ University Laboratory of Physiology	Email (JANET): ph@uk.ac.ox.physiol
+ Parks Road,				Tel. (0865) 272116
+ Oxford, OX1 3PT				Fax. (0865) 272469
+ England
+ - --------------------------------------------------------------------------
End of message from Patrick Haggard