Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit 58fdb7a

Browse files
Add note about how class size affects model latency
PiperOrigin-RevId: 410421985
1 parent 90c422f commit 58fdb7a

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

‎retrain_efficientdet_model_maker_tf2.ipynb‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -85,7 +85,9 @@
8585
"id": "PzoNZRp4sVxK"
8686
},
8787
"source": [
88-
"If you want to run the notebook with the salad dataset, you can run the whole thing now by clicking **Runtime \u003e Run all** in the Colab toolbar. But if you want to use your own dataset, then continue down to [Load the training data](#scrollTo=H0XM-oIfhgQ7) and follow the instructions there."
88+
"If you want to run the notebook with the salad dataset, you can run the whole thing now by clicking **Runtime \u003e Run all** in the Colab toolbar. But if you want to use your own dataset, then continue down to [Load the training data](#scrollTo=H0XM-oIfhgQ7) and follow the instructions there.\n",
89+
"\n",
90+
"**Note:** If using a custom dataset, beware that if your dataset includes more than 20 classes, you'll probably have slower inference speeds compared to if you have fewer classes. This is due to an aspect of the EfficientDet architecture in which a certain layer cannot compile for the Edge TPU when it carries more than 20 classes."
8991
]
9092
},
9193
{

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /