The error load.input-hash

user: the script can change it: the error says what happened in the experiment’s names, and what to write instead. environment: something the run needs is missing or different where it runs (a package, a file, a device, the network): the error names what to install, fetch or attach. internal: a check on MIME’s own construction, which no supported script should reach: a MIME defect, to report with the file the error names; or an error MIME raised with no code yet (error.uncoded), keeping its own class, to report so that it gets one.

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/saved/_folder.py:

  • what happened: the document was changed after its lock was written: {…}

  • what to do: build the experiment and save it again, built.save(folder), which writes a new lock; to build the edited document as it is, Experiment.from_document("<folder>/experiment.mime.yaml")

• in mime/saved/_folder.py:

  • what happened: MIME rebuilt its own record of the profile differently from the build that wrote the lock, under the same MIME version: {…}

  • what to do: report it: {…}

• in mime/saved/_folder.py:

  • what happened: the installed entries resolve this document differently from the build that wrote the lock, under the same names and versions: {…}

  • what to do: install the versions the lock names ('pip install <package>==<version>' for each of its entries), or report the entry that changed what it resolves without a new version

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