Closed halkszavu closed 1 year ago
childID timestamp coordinates parentID ! child starts following parent
above the existing timestamp entryhttps://github.com/halkszavu/Project-Artifexia/pull/27 The required visuals are done.
- Get the parent and the child plate. The parent will move onward and the child plate will follow the parent. (It is enough to have the two plate IDs as the parent will be with the smaller ID)
It will be convenient if there is a window form with two ID inputs.
- Get the parent and the child plate. The parent will move onward and the child plate will follow the parent. (It is enough to have the two plate IDs as the parent will be with the smaller ID)
- Get the timestamp for the collision (or any other type of joining event)
- In GPlates: Specify Anchored Plate ID (Ctrl+D): set the parent ID
- In GPlates: Total Reconstruction Poles (Ctrl+P): Equivalent Rotations relative to Anchored Plate, fetch the child's coordinates
- Input the coordinates to the form (New windows needed #6 ).
- Create new entry:
childID timestamp coordinates parentID ! child starts following parent
above the existing timestamp entry- Copy the coordinates and the conjugate plateID into the drift correction
- Also update the conjugate plateID in the 0.0 entry
The 7th point won't be done, the user should explicitly create a new drift correction, if it is desired.
Need to be reimplemented
First unit
- Get the parent and the child plate. The parent will move onward and the child plate will follow the parent. (It is enough to have the two plate IDs as the parent will be with the smaller ID)
- Get the timestamp for the collision (or any other type of joining event)
- In GPlates: Specify Anchored Plate ID (Ctrl+D): set the parent ID
- In GPlates: Total Reconstruction Poles (Ctrl+P): Equivalent Rotations relative to Anchored Plate, fetch the child's coordinates
- Input the coordinates to the form (New windows needed #6 ).
- Create new entry:
childID timestamp coordinates parentID ! child starts following parent
above the existing timestamp entry- Copy the coordinates and the conjugate plateID into the drift correction
- Also update the conjugate plateID in the 0.0 entry
One unit is enough. Every data can be frontloaded, and later used.
Data needed: Parent and child ID Coordinates (3. and 4.)
Create the required features to join independently moving plates