From: sleeper75se (sleeper75se_at_yahoo.se)
Date: 2002-01-23 15:35:25
--- In buildcheapeeg_at_yahoogroups.com, "John Morrison" <jmorrison_at_ahc.net.au> wrote:
> > Hi all,
> >
> > just an idea on what threads to use, and where:
> >
> > There should be three threads, I think:
> >
> > 1. Data input, signal processing, protocol management and such
> > 2. User interface (operator)
> > 3. Feedback interface (patient/user)
> >
[...snip...]
> Yep doesn't sound to bad. :-) Good thinking
> Just not sure if we shouldn't data input and processing there own
threads.
> After all the input maybe time sensitive and the processing MAYBE
time
> wasting!
>
> John
Actually, data input already *is* in its own thread. :-) When you
initialize the serial port, you can select how large the buffer
should be and the interrupt service routine takes care of the rest.
Processing can't be time wasting, because then it wouldn't be a real-
time system. If the data is coming in faster than you can process it,
the only way to deal with that is throwing away samples.
Basically, users with slower hardware must settle with less
processing. I don't think the requirements will be that severe
though, the first systems were designed ten years ago (or something
like that) for much slower computers.
/Andreas
This archive was generated by hypermail 2.1.4 : 2002-07-27 12:28:37 BST