KSLCore/ksl.modeling.guidedpath.spec/IntersectionData/IntersectionData

IntersectionData

constructor(name: String, length: Double = 0.0, velocityFactor: Double = 1.0, x: Double = Double.NaN, y: Double = Double.NaN, z: Double = 0.0)(source)

Parameters

name

unique within the network, and the name process code uses to address the junction

length

the distance to cross the junction, zero or more

velocityFactor

multiplies transporter velocity while crossing, strictly positive

layout abscissa, or not-a-number when no layout was supplied

layout ordinate, or not-a-number when no layout was supplied

layout height, defaulting to zero rather than to not-a-number. A guide path with no layout at all is a flat one at ground level, which is a meaningful position; a height of not-a-number would be a third way of saying "unspecified" that every reader would have to handle, and would poison any renderer that added it to a camera. The two planar coordinates keep not-a-number because there it distinguishes "no layout" from "the origin", and a reader testing x.isNaN() for that still gets the right answer.