Papers › Learning Data Augmentation Strategies for Object Detection

Learning Data Augmentation Strategies for Object Detection

26 Jun 2019ECCV 2020 8arXiv:1906.11172archive 2025-07-28

Barret Zoph, Ekin D. Cubuk, Golnaz Ghiasi, Tsung-Yi Lin, Jonathon Shlens, Quoc V. Le

Data augmentation is a critical component of training deep learning models. Although data augmentation has been shown to significantly improve image classification, its potential has not been thoroughly investigated for object detection. Given the additional cost for annotating images for object detection, data augmentation may be of even greater importance for this computer vision task. In this work, we study the impact of data augmentation on object detection. We first demonstrate that data augmentation operations borrowed from image classification may be helpful for training detection models, but the improvement is limited. Thus, we investigate how learned, specialized data augmentation policies improve generalization performance for detection models. Importantly, these augmentation policies only affect training and leave a trained model unchanged during evaluation. Experiments on the COCO dataset indicate that an optimized data augmentation policy improves detection accuracy by more than +2.3 mAP, and allow a single inference model to achieve a state-of-the-art accuracy of 50.7 mAP. Importantly, the best policy found on COCO may be transferred unchanged to other detection datasets and models to improve predictive accuracy. For example, the best augmentation policy identified with COCO improves a strong baseline on PASCAL-VOC by +2.7 mAP. Our results also reveal that a learned augmentation policy is superior to state-of-the-art architecture regularization methods for object detection, even when considering strong baselines. Code for training with the learned policy is available online at https://github.com/tensorflow/tpu/tree/master/models/official/detection

PaperPDFConference PDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

No sample from the archive's official repository (tensorflow/tpu) is linked to this paper; the 3 samples below come from 1 community repository. Syntology harvested code from tensorflow/tpu for another paper.

tensorflow/tpu: Syntology's graph links these samples to Towards Understanding Why Label Smoothing Degrades Selective Classification and How to Fix It (arXiv:2403.14715; that paper's own run record: 9 ran (of which 2 constructed an object rather than computing a result; 6 with no instrument failure: 1 honoured, 0 violated, 5 with no contract checked; 3 where Syntology's instrument failed) · 1 unverified); nothing checks that they implement this paper's method.

Syntology 3 code samples harvested from 1 repository linked to this paper: 3 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 1 violated, 0 with no contract checked; 2 where Syntology's instrument failed) · 0 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; 1 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: community (archive-listed): 3 samples from 1 repository, 3 ran (1 with no instrument failure; 2 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

No sample is linked to this paper from 1 of its repositories that Syntology harvested for other papers:

Levels written on 2026-09-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

tensorflow/tpu officialmentioned in papertfApache-2.0Syntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Towards Understanding Why Label Smoothing Degrades Selective Classification and How to Fix It (arXiv:2403.14715; that paper's own run record: 9 ran (of which 2 constructed an object rather than computing a result; 6 with no instrument failure: 1 honoured, 0 violated, 5 with no contract checked; 3 where Syntology's instrument failed) · 1 unverified); nothing checks that they implement this paper's method. report
Jasonlee1995/AutoAugment_Detection mentioned on GitHubpytorchSyntology: not harvested report
chenyouxin113/sota-status-investigation mentioned on GitHubtfSyntology: not harvested report
cy0616/data_augment mentioned on GitHubtfSyntology: 3 samples, 3 ran (2 instrument-failed) · 0 unverified report
zzl-pointcloud/Data_Augmentation_Zoo_for_Object_Detection mentioned on GitHubpytorchSyntology: not harvested report
tensorflow/tpu tfSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Towards Understanding Why Label Smoothing Degrades Selective Classification and How to Fix It (arXiv:2403.14715; that paper's own run record: 9 ran (of which 2 constructed an object rather than computing a result; 6 with no instrument failure: 1 honoured, 0 violated, 5 with no contract checked; 3 where Syntology's instrument failed) · 1 unverified); nothing checks that they implement this paper's method. report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

3 samples harvested: 3 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 1 violated, 0 with no contract checked; 2 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · violated contract
1ran · our draft was wrong
1ran; the contract check could not run

Licence: 3 of the 3 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from cy0616/data_augment. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

cy0616/data_augment community (archive-listed) 3 samples, 3 ran (2 instrument-failed) · 0 unverified
change_center synthetic-occlusion.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant GPL-3.0 (copyleft) · pointer only · 4ef4e8e84c07e6e7 · report fixture: signature center:ndarray/1/float, width_height:ndarray/1/float, annotation:list/1/list · returned ndarray · level recorded 2026-09-22
cutout in 17 papers autoaugment_utils.py.py ran · our draft was wrong GPL-3.0 (copyleft) · pointer only · d845de56fb50b753 · report fixture: signature image:ndarray/3/float, pad_size:int/0/int, replace:int/0/int · returned ndarray · level recorded 2026-09-22
random_negate autoaugment_utils.py.py ran · violated contract fingerprinted GPL-3.0 (copyleft) · pointer only · 80ba651549ee2038 · report fixture: signature degree:float/0/float · returned float · level recorded 2026-09-22

Tasks

Data AugmentationImage AugmentationImage ClassificationObjectObject DetectionRobust Object Detectionimage-classificationobject-detection

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Object Detection COCO test-dev NAS-FPN (AmoebaNet-D, learned aug) APL 64.5 #87 of 225 Archive leaderboard report
Object Detection COCO test-dev NAS-FPN (AmoebaNet-D, learned aug) APM 55.5 #87 of 225 Archive leaderboard report
Object Detection COCO test-dev NAS-FPN (AmoebaNet-D, learned aug) APS 34.2 #87 of 225 Archive leaderboard report
Object Detection COCO test-dev NAS-FPN (AmoebaNet-D, learned aug) box mAP 50.7 #87 of 225 Archive leaderboard report
Robust Object Detection Cityscapes AutoAug-det mPC [AP] 15.8 #11 of 13 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

Methods

1x1 ConvolutionAmoebaNetAverage PoolingBatch NormalizationBottleneck Residual BlockConvolutionEntropy RegularizationFPNFaster R-CNNFocal LossGlobal Average PoolingImage Scale AugmentationKaiming InitializationLSTMMax PoolingNAS-FPNPPORPNRandom Horizontal FlipReLUResidual BlockResidual ConnectionRetinaNetRoIPoolSGDSigmoid ActivationSoftmaxSpatially Separable ConvolutionStep DecayTanh Activation

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections