From: tmoran@acm.org
Subject: Re: Q: Stopping a task running a long simulation
Date: Fri, 12 Mar 2010 00:24:41 +0000 (UTC)
Date: 2010-03-12T00:24:41+00:00 [thread overview]
Message-ID: <hnc1k8$3uq$1@speranza.aioe.org> (raw)
In-Reply-To: f16d58ea-6ff2-44fd-85e1-fd482c2bf3e4@d27g2000yqf.googlegroups.com
> 'Compute' has a generic 'Feedback' procedure for showing progress.
> I could with that way give a Boolean, user_abort, to 'Feedback', and
> 'Compute' would stop when an ad-hoc exception is raised, and return
> normally on its own.
Think of a motor and its control panel. The panel does read-only access
to certain information in the motor, its speed for instance, which the
panel displays. The panel can also write certain information, like Stop,
to a switch that the motor periodically (every rotation?) checks. Compute
is your motor and the GUI is the control panel. Progress information
is regularly written by Compute to a record, which is periodically
read by the GUI, and control information is written as needed by the
GUI and regularly read by Compute.
next prev parent reply other threads:[~2010-03-12 0:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 13:08 Q: Stopping a task running a long simulation Gautier write-only
2010-03-11 18:11 ` Anh Vo
2010-03-12 0:24 ` tmoran [this message]
2010-03-12 1:15 ` Gautier write-only
2010-03-12 1:27 ` Adam Beneschan
2010-03-12 1:50 ` Gautier write-only
2010-03-12 2:03 ` Gautier write-only
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox