Skip to main content

​
Get help

Email [email protected]. Say what you ran, what you expected and what happened instead. A support bundle shows us what your machine sees. Attach one to your email:
  1. Check your secure environment:
    It checks the connection to tracebloc and whether your secure environment is ready to train. For each problem it finds, it says what to do.
  2. If that doesn’t fix it, write a support bundle:
    It writes the file tracebloc-doctor-<timestamp>.txt in the folder you run it from. Credentials are removed from it. Read it before you send it.
If the installer stopped before it installed the tracebloc CLI, the installer writes a support bundle of its own: see Troubleshooting.

​
Delete tracebloc from your machine

It lists what it deletes and what it keeps, then asks you to type the name of your secure environment. Sign in first: its first step disconnects this machine from tracebloc.
  • Deleted from this machine: your secure environment and everything tracebloc installed to run it, your data on this machine, the folder ~/.tracebloc (%USERPROFILE%\.tracebloc on Windows) and the tracebloc CLI.
  • Kept on tracebloc: your use cases and trained models, and your dataset records, marked unavailable.
  • Kept on this machine: tools other programs may use, such as Helm, and NVIDIA drivers. Remove them yourself if nothing else uses them.
This can’t be undone. To keep your local data, run tracebloc delete --keep-data. What it keeps on each system is in Operations.
A training runs. tracebloc delete refuses while a training runs or waits to run on your secure environment, and names the experiment. Wait for it to finish, or pass --force to stop it. It can’t delete everything. It says what is left and how to finish by hand. Its last lines name a file, after Details:. Email that file to [email protected]. You signed out. See With no secure environment linked.