realtime design
Dennis Lee Bieber
wlfraed at ix.netcom.com
Wed Oct 16 21:47:48 EDT 2002
Tim Daneliuk fed this fish to the penguins on Wednesday 16 October 2002
04:10 pm:
>
> One last thing: The scenarios and problems outlined above can be
> avoided if the simulation in fact simulates *time* itself (I think Mr.
> Ewing was hinting at this as I reread his post). In this case, a clock
> "tick" is merely a software counter which moves things forward one
> system quantum. In such simulations, actual "real" time is not
> preserved but determinism and sequencing are. This can be very useful
> in examining the behavior of a proposed or existing real world system.
>
> In this case Python absolutely could and would serve nicely as an
> implementation vehicle. Some very interesting OO design issues emerged
> as I thought about this. What should the central set of objects
> include, for example? Clearly hardware events like interrupts need to
> be represented, but so does time itself - or at least the behavior of
> hardware clocks. 'Mighty interesting project indeed...
>
Would the announced SimPy be a starting place? Of course, you'd likely
have to build a model of the Python interpreter in order to simulate
the threading with emulated time <G>
--
--
> ============================================================== <
> wlfraed at ix.netcom.com | Wulfraed Dennis Lee Bieber KD6MOG <
> wulfraed at dm.net | Bestiaria Support Staff <
> ============================================================== <
> Bestiaria Home Page: http://www.beastie.dm.net/ <
> Home Page: http://www.dm.net/~wulfraed/ <
More information about the Python-list
mailing list