Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
S
seminar-breakout
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Shashank Suhas
seminar-breakout
Commits
191d4691
Commit
191d4691
authored
Nov 14, 2017
by
Yuxin Wu
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
[FasterRCNN] update notes
parent
3040586d
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
19 additions
and
9 deletions
+19
-9
examples/FasterRCNN/NOTES.md
examples/FasterRCNN/NOTES.md
+19
-9
No files found.
examples/FasterRCNN/NOTES.md
View file @
191d4691
...
@@ -13,22 +13,32 @@ This is a minimal implementation that simply contains these files:
...
@@ -13,22 +13,32 @@ This is a minimal implementation that simply contains these files:
### Implementation Notes
### Implementation Notes
1.
You can easily add more augmentations such as rotation, but be careful how a box should be
Data:
1.
It's easy to train on your own data. Just replace
`COCODetection.load_many`
in
`data.py`
by your own loader.
2.
You can easily add more augmentations such as rotation, but be careful how a box should be
augmented. The code now will always use the minimal axis-aligned bounding box of the 4 corners,
augmented. The code now will always use the minimal axis-aligned bounding box of the 4 corners,
which is probably not the optimal way.
which is probably not the optimal way.
A TODO is to generate bounding box from segmentation, so more augmentations can be naturally supported.
2.
Floating-point boxes are defined like this
:
Model
:
<p
align=
"center"
>
<img
src=
"https://user-images.githubusercontent.com/1381301/31527740-2f1b38ce-af84-11e7-8de1-628e90089826.png"
>
</p>
1.
Floating-point boxes are defined like this:
3.
We use ROIAlign, and because of (3),
`tf.image.crop_and_resize`
is NOT ROIAlign.
<p
align=
"center"
>
<img
src=
"https://user-images.githubusercontent.com/1381301/31527740-2f1b38ce-af84-11e7-8de1-628e90089826.png"
>
</p>
4.
Inference is not quite fast, because either you disable convolution autotune and end up with
2.
We use ROIAlign, and because of (1),
`tf.image.crop_and_resize`
is __NOT__ ROIAlign.
a slow convolution algorithm, or you spend more time on autotune.
This is a general problem of TensorFlow when running against variable-sized input.
5
.
We only support single image per GPU for now.
3
.
We only support single image per GPU for now.
6.
Because of (4
), BatchNorm statistics are not supposed to be updated during fine-tuning.
4.
Because of (3
), BatchNorm statistics are not supposed to be updated during fine-tuning.
This specific kind of BatchNorm will need
[
my kernel
](
https://github.com/tensorflow/tensorflow/pull/12580
)
This specific kind of BatchNorm will need
[
my kernel
](
https://github.com/tensorflow/tensorflow/pull/12580
)
which is included since TF 1.4. If using an earlier version of TF, it will be either slow or wrong.
which is included since TF 1.4. If using an earlier version of TF, it will be either slow or wrong.
Speed:
1.
Inference is not quite fast, because either you disable convolution autotune and end up with
a slow convolution algorithm, or you spend more time on autotune.
This is a general problem of TensorFlow when running against variable-sized input.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment