TensorFlow Object Detection API: specifying multiple data_augmentation_options
up vote
0
down vote
favorite
I'm wondering if there's any difference between specifying the data augmentations like this:
data_augmentation_options {
random_horizontal_flip {
}
}
data_augmentation_options {
ssd_random_crop {
}
}
Or like this:
data_augmentation_options {
random_horizontal_flip {
}
ssd_random_crop {
}
}
In the object detection pipeline file?
All the samples in the models repo use the first format, but the second format is accepted as well.
tensorflow object-detection data-augmentation
asked Nov 19 at 21:51
jvlier
52
add a comment |
up vote
0
down vote
favorite
I'm wondering if there's any difference between specifying the data augmentations like this:
data_augmentation_options {
random_horizontal_flip {
}
}
data_augmentation_options {
ssd_random_crop {
}
}
Or like this:
data_augmentation_options {
random_horizontal_flip {
}
ssd_random_crop {
}
}
In the object detection pipeline file?
All the samples in the models repo use the first format, but the second format is accepted as well.
tensorflow object-detection data-augmentation
asked Nov 19 at 21:51
jvlier
52
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm wondering if there's any difference between specifying the data augmentations like this:
data_augmentation_options {
random_horizontal_flip {
}
}
data_augmentation_options {
ssd_random_crop {
}
}
Or like this:
data_augmentation_options {
random_horizontal_flip {
}
ssd_random_crop {
}
}
In the object detection pipeline file?
All the samples in the models repo use the first format, but the second format is accepted as well.
tensorflow object-detection data-augmentation
asked Nov 19 at 21:51
jvlier
52
I'm wondering if there's any difference between specifying the data augmentations like this:
data_augmentation_options {
random_horizontal_flip {
}
}
data_augmentation_options {
ssd_random_crop {
}
}
Or like this:
data_augmentation_options {
random_horizontal_flip {
}
ssd_random_crop {
}
}
In the object detection pipeline file?
All the samples in the models repo use the first format, but the second format is accepted as well.
tensorflow object-detection data-augmentation
tensorflow object-detection data-augmentation
asked Nov 19 at 21:51
jvlier
52
asked Nov 19 at 21:51
jvlier
52
asked Nov 19 at 21:51
jvlier
52
asked Nov 19 at 21:51
jvlier
52
asked Nov 19 at 21:51
jvlier
52
52
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
The only correct format is the first one.
While the second one will not break the pipeline, it will only take the first specified option.
You can verify this yourself by inspecting the created pipeline.config in model_dir.
The reason for that is that data_augmentation_options is of type PreprocessingStep which consists of a oneof preprocessing_step. Note the oneof.
On the other hand, data_augmentation_options is repeated, thus you can specify
data_augmentation_options {
augmentation_option_1 {
}
}
data_augmentation_options {
augmentation_option_2 {
}
}
...
and so on, as many as you like.
answered Nov 20 at 12:02
netanel-sam
2817
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
The only correct format is the first one.
While the second one will not break the pipeline, it will only take the first specified option.
You can verify this yourself by inspecting the created pipeline.config in model_dir.
The reason for that is that data_augmentation_options is of type PreprocessingStep which consists of a oneof preprocessing_step. Note the oneof.
On the other hand, data_augmentation_options is repeated, thus you can specify
data_augmentation_options {
augmentation_option_1 {
}
}
data_augmentation_options {
augmentation_option_2 {
}
}
...
and so on, as many as you like.
answered Nov 20 at 12:02
netanel-sam
2817
add a comment |
up vote
0
down vote
accepted
The only correct format is the first one.
While the second one will not break the pipeline, it will only take the first specified option.
You can verify this yourself by inspecting the created pipeline.config in model_dir.
The reason for that is that data_augmentation_options is of type PreprocessingStep which consists of a oneof preprocessing_step. Note the oneof.
On the other hand, data_augmentation_options is repeated, thus you can specify
data_augmentation_options {
augmentation_option_1 {
}
}
data_augmentation_options {
augmentation_option_2 {
}
}
...
and so on, as many as you like.
answered Nov 20 at 12:02
netanel-sam
2817
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
The only correct format is the first one.
While the second one will not break the pipeline, it will only take the first specified option.
You can verify this yourself by inspecting the created pipeline.config in model_dir.
The reason for that is that data_augmentation_options is of type PreprocessingStep which consists of a oneof preprocessing_step. Note the oneof.
On the other hand, data_augmentation_options is repeated, thus you can specify
data_augmentation_options {
augmentation_option_1 {
}
}
data_augmentation_options {
augmentation_option_2 {
}
}
...
and so on, as many as you like.
answered Nov 20 at 12:02
netanel-sam
2817
The only correct format is the first one.
While the second one will not break the pipeline, it will only take the first specified option.
You can verify this yourself by inspecting the created pipeline.config in model_dir.
The reason for that is that data_augmentation_options is of type PreprocessingStep which consists of a oneof preprocessing_step. Note the oneof.
On the other hand, data_augmentation_options is repeated, thus you can specify
data_augmentation_options {
augmentation_option_1 {
}
}
data_augmentation_options {
augmentation_option_2 {
}
}
...
and so on, as many as you like.
answered Nov 20 at 12:02
netanel-sam
2817
answered Nov 20 at 12:02
netanel-sam
2817
answered Nov 20 at 12:02
netanel-sam
2817
answered Nov 20 at 12:02
netanel-sam
2817
2817
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53383151%2ftensorflow-object-detection-api-specifying-multiple-data-augmentation-options%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
