From: Jim Peters (jim_at_uazu.net)
Date: 2002-01-23 23:12:57
Doug Sutherland wrote:
> > If other people want to go and create some fancy app
> > by designing screens and copying other people's apps
>
> You are going to the other extreme here, the idea is
> not to copy, it's to look at what works and what does
> not work. Reinventing wheels is not always a good
> thing, and perhaps we can evolve to a better wheel.
Okay, you're right. Perhaps it is a good thing, though, that we have
both extremes of the spectrum covered in this group.
> 1) What is the best way to represent the data? This
> will depend on the reason for measuring, but if
> it's for biofeedback then certainly raw wave forms
> are NOT the best way.
I'm guessing you're talking about how to display it on the screen, and
how to put it into a form that is good for basing biofeedback on. For
saving to disk, the raw waveform is definitely the best way so that no
data is lost.
> So the point of looking at other apps is to see what has been
> done, look at each feature/component and decide if it is just
> fluff, focus on the ones that look good.
Good, yes.
> 2) What is the best way to interact with the user,
> and what things should be configurable for sessions?
> How do we manage the saving of configurations? How
> do other EEG systems do this (see 1)
>
> 3) What are good training protocols, and how do we
> best support those in the software? How do other
> EEGs do this (see 1)
>
> 4) What is the best way to layer/abstract the software
> for maximum flexibility?
>
> By all means, keep on coding, but can you answer #3
> above, and how will your software support that?
If I build up all the tools I might need first, then as soon as I can
get some hardware to play with, I'll be ready to start experimenting.
Then I'll try things, discard what doesn't seem to work, keep things
that work. For me personally, it's at this point that I'd be
interested in how other people have approached it to get new ideas.
But that info is useless until you have some hardware to try it on.
Maybe people like Rob do indeed have hardware already, but I don't
feel happy basing huge design decisions on things like that until I've
seen it working and tried some alternatives. For me, the program
design grows outwards from what it actually does. An outside-in
approach doesn't work for me at all.
For that reason, I'll keep going along my `alternative' track, even if
everyone else gets down and starts coding up a big application based
on research into other EEG software.
I don't think this will be a problem -- any code I write will be
available to incorporate into the big app if people think it's useful.
Jim
-- Jim Peters (_)/=\~/_(_) Uazú (_) /=\ ~/_ (_) jim@ (_) /=\ ~/_ (_) www. uazu.net (_) ____ /=\ ____ ~/_ ____ (_) uazu.net
This archive was generated by hypermail 2.1.4 : 2002-07-27 12:28:37 BST