The error chain.mount-rates

user: the script can change it: the error says what happened in the experiment’s names, and what to write instead.

Where MIME gives it, with what its message says happened and what its action says to do ({…} is filled in from the experiment):

• in mime/build/_masses.py:

  • what happened: {…} carries its rotor's absolute spin, which needs the angular velocity of the frame it is mounted on, and {…} publishes none (apparatus.frame_angular_velocities), or does not know its own mount's

  • what to do: publish apparatus.frame_angular_velocities from {…}'s segment (in its capabilities()), or use the kinematic rung of {…}, Motor.Kinematic(...)

• in mime/build/_plan.py:

  • what happened: {…}'s read {…} names {…}, and {…} does not know its frames' angular velocities: the frame it is mounted on publishes none ({…})

  • what to do: publish {…} from the segment {…} is mounted on (in its capabilities()), or read its frame poses instead, {…}, in place of {…} in the read {…}

Reading an error and reaching its full traceback: reading an error. Every code: the index.