The method avoids complexity and performance uncertainty by assigning priorities and timeslicing parameters using only the order of magnitude of the required response time to input stimuli.
“Ooh, I like that. By making the levels in order of magnitude, prioritizations nest neatly into one another, logically.
Target Functionalities | |||
Item | Response time | ||
Event1 | 1 | us | |
Event2 | 1 | us | |
System clock | 1 | us | |
Serial byte | 5 | us | |
Sound generator | 1 | ms | |
Mouse | 1 | ms | |
Motor1 | 2 | ms | |
Motor2 | 10 | ms | |
Click response | 100 | ms | |
Window response | 100 | ms | |
Math output | 1 | s | |
Search1 output | 2 | s | |
Search2 output | 2 | s=== |
j000
Priority Response Times | |||
Minimum | |||
Priority | response | Timeslice | Process response |
0 | 1 us | — | 100 ns |
1 | 1 ms | 100 us | 100 us |
2 | 100 ms | 10 ms | 10 ms |
3 | 1 s | 100 ms | 100 ms |
In this case, the fraction described above is 1/10.
—
man he’s nailing it. This is how things are normally done – what he calls ‘deep’ model [hidden – where lag comes from etc]
—-
his ‘wide’ model exposes the systems allowing for better control of time flow, instead of pretending time doesn’t exist, which is what current programming methodologies tend to do.
—-
Ah ha! Here we go. He has a site:
http://lazm.org/
—
more related concepts you never hear about:
https://en.wikipedia.org/wiki/Process-oriented_programming
==
Ah ha! Full circle, from Hoare logic (hidden logic behind programming – if you’ve done programming, you’ve used this logic and didn’t know it) – to his later development https://en.wikipedia.org/wiki/Communicating_sequential_processes which has been and is used on critical fault tolerant real time systems.
—-
Currently learning more about CSP or “Communicating Sequential Processing” which is about describing patterns of interaction in concurrent computing systems.
Reading prior version of : http://www.cs.ox.ac.uk/ucs/ which is freely available called “Theory and Practice of Concurrency” by the same author.
====
process algebras
—‘
I made an object using Processing (I think it was OpenProcessing) – to illustrate a concept I had/have called the “leaky triangle”. Basically, there’s no closed systems. Information always ‘leaks’ somehow. Since the triangle (or pyramid?) is the smallest shape that’s supposedly closed, the only way we get information about the inside is if it ‘leaks information’ out somehow.
But if a system is entirely closed, we’ll never know what’s inside.
Anyway, I modeled a rotating partial pyramid in Processing designed to “leak” and not work properly. On my current version of Waterfox, it spills over my whole screen and had other effects on other browsers.
and yes – I think I like Z-Brush’s way of thinking better.
wait – i said it wrong – if a system is entirely closed, we won’t see the system at all]
—-