Input validation wire information lacking

[brettviren]

There are a number of conventions and assumptions that WCT code relies on and which various inputs must honor. For example in the realm of describing "wires":

• wire ident being globally unique, non-negative

  • WCT otherwise treats it as an opaque number (no patterns)

• wire-in-plane (WIP) number/index proper ordering

  • WIP index counts starting at 0
  • per-plane wire order has ascending Z of wire centers,
  • if wire plane is degenerate in Z then ascending Y of wire centers.
  • WIP index only unique to the context of one wire plane.

• wire segment numbering convention

  • counts number of segments between current segment and channel input
  • ie, segment 0 is directly connected to channel

• channel id being globally unique

  • WCT otherwise treats it as an opaque number (no patterns)

• wire face convention

  • face 0 or "front" has the larger X value, face 1 or "back" has the smaller X value
  • single-face anodes may be "back" faced if they, uh, face, toward smaller X values

• [ ] centrally catalog all the assumptions in a document held in the repo in iface/docs/

• [ ] add validation functions to aux taking each in the hierarchy of IWire, IWirePlane, IAnodeFace and IAnodePlane.

• [ ] apply these validation functions in the existing producers of these interface objects.

[brettviren]

The cluster files are producing wire arrays with duplicate wire ident but unique channel id for at least pdsp. This may be due to duplication in the "wires file".

[brettviren]

microboone-celltree-wires-v2.1 follows the Z ordering convention

protodune-wires-larsoft-v4 follows it only up to per-plane variability in the sign