View source for Tracing trajectories of component in machine phase


[[Gemstone metamaterial on-chip factories]] operate in [[machine phase]]. <br>
Operating in machine phase is:
* essentially necessary for [[gemstone metamaterial technology]] to work and is 
* a key factor for the [[high performance of gem-gum technology]] way beyond what [[soft nanosystems]] could ever deliver. 
For a discussion of details see: <br>
See: [[Machine phase]], [[The defining traits of gem-gum-tec]], [[Stiffness]], ...

Machine phase means (among other things) that such a production system is fully deterministic system. <br>
* That is: For any given time there is exactly one uniquely defined system configuration. <br>
* That is: There are no branches in configuration space. 
One maybe can think of the drive system like a slider on a (very complexly shaped) one dimensional rail.

So for any given atom in a [[gemstone metamaterial product]] the complete trajectory can be traced <br>
right from where it was captured into machine phase. <br>
The same holds for [[crystolecule]]s and [[microcomponent]]s. <br
The trajectory of bigger components id fully traceable from the moment "inception" <br>
from the moment of completed assembly.

Side-note: <br>
Of at a high enough level determinism necessarily needs to end given our macroscale reality is not totally deterministic. <br>
E.g. It can't be predicted what kind of product a user is eventually going to produce in the next production run. <br>

== How to represent the date of component trajectories ==

Representing the data for the whole trajectories for the diverse component trajectories in the global frame of reference would be rather impractical. <br>

Instead for some given time combined with some given sub-component of a product one <br>
fist looks up the mechanism that is at that moment of time responsible for keeping this component safely in machine phase. <br>
This gives:
* The pose coordinates of the responsible mechanism and 
* the rigid body pose coordinates (position and rotation) of the component in the local coordinate frame of reference.
* (and a local frames of reference for time)

To decide: <br>
What to call the machanism responsible for keeping the component safely in machine phase? 
* "owner" "onlatcher" "caretaker" "responsible mechanism" "guider" "controller"

=== Avoid imperative modelling ===

In any case a naive imperative approach of modelling is absolutely to avoid. <br>
"Naive imperative way" means storing positions in variables making the <br>
responsible mechanisms into "objects as actors" that look up the old positions and orientations <br>
of components and in place update those values to represent a new time-step. <br>
'''DO NOT DO THAT!!''' <br>

== Related ==

* [[Design of gem-gum on-chip factories]]
* [[Machine phase]]
* ...