Difference between revisions of "ARKmatrix"

From ARK
Jump to: navigation, search
(Processing)
(Harris Matrix Software)
 
(7 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
= Harris Matrix Software =
  
Some other notes: http://archaeologic.al/wiki/Harris_Matrix
+
This page summarises L - P : Archaeology's ongoing work on Harris Matrix software.
  
== Strat Units ==
+
* Our ARK Matrix software: https://gitlab.com/arklab/ArkMatrix
 +
* Our survey of the State of the Art in 2015: http://archaeologic.al/wiki/Harris_Matrix
 +
* The Matrix Reloaded - CAA UK 2016 presentation by John Layt of L - P : Archaeology https://www.youtube.com/watch?v=geLD7Fo6crU
 +
 
 +
== ARK Matrix Software ==
 +
 
 +
High-level sketch of docs - a Work-in-Progress!
 +
 
 +
=== Strat Units ===
  
 
Unit Attributes
 
Unit Attributes
* ID
+
* Site Code
 +
* Unit ID
 
* Label
 
* Label
* Class
+
* Class [Context, Subgroup, Group, Landuse]
* Type
+
* Type [Deposit, Fill, Cut, Masonry, Skeleton, Timber]
* Status
+
* Status [Allocated, Assigned, Void]
* Site Code
 
 
* Aggregate Unit
 
* Aggregate Unit
* Period / Phase
+
* Phase
 +
* Period
  
Unit Class:
+
=== Strat Relations ===
* Context
 
* Subgroup
 
* Group
 
* Landuse
 
 
 
Unit Type:
 
* Undefined
 
* Deposit
 
* Fill
 
* Cut
 
* Masonry
 
* Skeleton
 
* Timber
 
 
 
Unit Status:
 
* Allocated
 
* Assigned
 
* Void
 
 
 
== Strat Relations ==
 
  
 
* Above / Below (directed graph)
 
* Above / Below (directed graph)
 
* Same-As (undirected graph)
 
* Same-As (undirected graph)
* Contemporary With (undirected graph)
+
* Contemporary With (undirected graph) [REMOVE?]
  
== Rules / Heuristics ==
+
=== Rules / Heuristics ===
  
 
Any Relations:
 
Any Relations:
 
* Cannot be between same Unit
 
* Cannot be between same Unit
 
* Both Units must be same Class
 
* Both Units must be same Class
 +
 +
Above/Below Relations:
 +
* Adding relation should not create cycles (no intersection between successors and predecessors)
  
 
Same-As Relations:
 
Same-As Relations:
Line 52: Line 45:
 
* Both Units must have the same Period / Phase if set
 
* Both Units must have the same Period / Phase if set
  
 
+
=== Processing ===
== Processing ==
 
  
 
Load
 
Load
Line 71: Line 63:
  
 
Aggregate
 
Aggregate
* For each Context Above/Below relation where the Aggregate Unit is different between the Above and Below Units, add an Above/Below relation to the Subgroup matrix
+
* Validate all Context Units have an Aggregate Unit
 +
* For each Context Above/Below relation where the Aggregate Unit is different between the Above and Below Units, add an Above/Below relation between the Aggregate Units to the Subgroup matrix
 
* Reduce the Subgroup matrix
 
* Reduce the Subgroup matrix
* For each Subgroup Above/Below relation where the Aggregate Unit is different between the Above and Below Units, add an Above/Below relation to the Group matrix
+
* Validate all Subgroup Units have an Aggregate Unit
 +
* For each Subgroup Above/Below relation where the Aggregate Unit is different between the Above and Below Units, add an Above/Below relation between the Aggregate Units to the Group matrix
 
* Reduce the Group matrix
 
* Reduce the Group matrix
 +
 +
== Development Plans ==
 +
 +
* https://github.com/anvaka/graph-drawing-libraries
 +
* https://github.com/ArsMasiuk/qvge

Latest revision as of 09:58, 10 December 2018

Harris Matrix Software

This page summarises L - P : Archaeology's ongoing work on Harris Matrix software.

ARK Matrix Software

High-level sketch of docs - a Work-in-Progress!

Strat Units

Unit Attributes

  • Site Code
  • Unit ID
  • Label
  • Class [Context, Subgroup, Group, Landuse]
  • Type [Deposit, Fill, Cut, Masonry, Skeleton, Timber]
  • Status [Allocated, Assigned, Void]
  • Aggregate Unit
  • Phase
  • Period

Strat Relations

  • Above / Below (directed graph)
  • Same-As (undirected graph)
  • Contemporary With (undirected graph) [REMOVE?]

Rules / Heuristics

Any Relations:

  • Cannot be between same Unit
  • Both Units must be same Class

Above/Below Relations:

  • Adding relation should not create cycles (no intersection between successors and predecessors)

Same-As Relations:

  • Both Units must be Context class
  • Adding relation should not create cycles (no intersection between successors and predecessors)
  • Both Units must have the same Aggregate Unit if set
  • Both Units must have the same Period / Phase if set

Processing

Load

Validate

  • Validate Units
  • Validate Above/Below relations
  • Validate Same-as Units

Resolve

  • For each Same-As relationship add all Above/Below relations to each Unit

Validate

Reduce

  • Remove all redundant Above/Below relations (transitive reduction)

Aggregate

  • Validate all Context Units have an Aggregate Unit
  • For each Context Above/Below relation where the Aggregate Unit is different between the Above and Below Units, add an Above/Below relation between the Aggregate Units to the Subgroup matrix
  • Reduce the Subgroup matrix
  • Validate all Subgroup Units have an Aggregate Unit
  • For each Subgroup Above/Below relation where the Aggregate Unit is different between the Above and Below Units, add an Above/Below relation between the Aggregate Units to the Group matrix
  • Reduce the Group matrix

Development Plans