LSST Applications
22.0.1,22.0.1+01bcf6a671,22.0.1+046ee49490,22.0.1+05c7de27da,22.0.1+0c6914dbf6,22.0.1+1220d50b50,22.0.1+12fd109e95,22.0.1+1a1dd69893,22.0.1+1c910dc348,22.0.1+1ef34551f5,22.0.1+30170c3d08,22.0.1+39153823fd,22.0.1+611137eacc,22.0.1+771eb1e3e8,22.0.1+94e66cc9ed,22.0.1+9a075d06e2,22.0.1+a5ff6e246e,22.0.1+a7db719c1a,22.0.1+ba0d97e778,22.0.1+bfe1ee9056,22.0.1+c4e1e0358a,22.0.1+cc34b8281e,22.0.1+d640e2c0fa,22.0.1+d72a2e677a,22.0.1+d9a6b571bd,22.0.1+e485e9761b,22.0.1+ebe8d3385e
LSST Data Management Base Package
|
This represents an unique identifier of a node within an individual construction of a `QuantumGraph`. This identifier will stay constant through a pickle, and any `QuantumGraph` methods that return a new `QuantumGraph`. A `NodeId` will not be the same if a new graph is built containing the same information in a `QuantumNode`, or even built from exactly the same inputs. `NodeId`s do not play any role in deciding the equality or identity (hash) of a `QuantumNode`, and are mainly useful in debugging or working with various subsets of the same graph. This interface is a convenance only, and no guarantees on long term stability are made. New implementations might change the `NodeId`, or provide more or less guarantees.
Definition at line 39 of file quantumNode.py.