1. Prepare a clean export version
Start in the Export workspace. The notebook uses the exact version you save.
What to do
- 1Open Export and choose a version.
- 2Check format, size, and split settings.
- 3Save before downloading the notebook.
Prepare a dataset version, download the generated notebook, run the training cells, and export the finished model artifact.
What BBoxML configures for you
The notebook already includes your chosen dataset source, training model, output destination, and export artifact.
Follow these steps in order the first time. After that, the same loop becomes much faster.
Start in the Export workspace. The notebook uses the exact version you save.
What to do
Choose how the notebook should behave before you download it.
What to do
Choose the simplest storage path for your workflow. Google Drive is safer if you want to avoid losing the final export.
What to do
Use the first notebook cells to confirm the saved settings.
What to do
The notebook always trains with a YOLO checkpoint.
What to do
The last cell exports the artifact you chose in BBoxML.
What to do
These are the easiest ways to avoid friction on early training runs.
For the first run, use Upload ZIP, a smaller checkpoint, and `best.pt`.
For repeat runs, switch both source and output to Google Drive.
Some startup delay is normal while Colab spins up the runtime.
No. They are dataset formats. The notebook converts them to YOLO training layout first.
Use Upload ZIP for quick starts. Use Google Drive ZIP for larger or repeat runs.
No. The notebook trains from a `.pt` checkpoint first, then exports the result to `.tflite`.
Prepare a dataset version in BBoxML, then use the Colab Notebook button to generate a notebook that already matches your workflow.