Papers › Multi-Sample Dropout for Accelerated Training and Better Generalization

Multi-Sample Dropout for Accelerated Training and Better Generalization

23 May 2019arXiv:1905.09788archive 2025-07-28

Hiroshi Inoue

Dropout is a simple but efficient regularization technique for achieving better generalization of deep neural networks (DNNs); hence it is widely used in tasks based on DNNs. During training, dropout randomly discards a portion of the neurons to avoid overfitting. This paper presents an enhanced dropout technique, which we call multi-sample dropout, for both accelerating training and improving generalization over the original dropout. The original dropout creates a randomly selected subset (called a dropout sample) from the input in each training iteration while the multi-sample dropout creates multiple dropout samples. The loss is calculated for each sample, and then the sample losses are averaged to obtain the final loss. This technique can be easily implemented by duplicating a part of the network after the dropout layer while sharing the weights among the duplicated fully connected layers. Experimental results using image classification tasks including ImageNet, CIFAR-10, and CIFAR-100 showed that multi-sample dropout accelerates training. Moreover, the networks trained using multi-sample dropout achieved lower error rates compared to networks trained with the original dropout. The additional computation cost due to the duplicated operations is not significant for deep convolutional networks because most of the computation time is consumed in the convolution layers before the dropout layer, which are not duplicated.

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

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

By repository: community (archive-listed): 7 samples from 2 repositories, 7 ran (6 with no instrument failure; 1 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.

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

StephKua/Kaggle-Twitter-Sentiment-Extraction mentioned on GitHubtfSyntology: not harvested report
alyaxey/bert_for_intent_recognition mentioned on GitHubSyntology: not harvested report
apalle1/Sentiment-Span-Extraction-Using-Transformer-Models mentioned on GitHubpytorchSyntology: not harvested report
lonePatient/multi-sample_dropout_pytorch mentioned on GitHubpytorchSyntology: 1 sample, 1 ran (1 instrument-failed) · 0 unverified report
lsqdecodebox/Transformer_Classifier_FrameWork mentioned on GitHubpytorchSyntology: not harvested report
ywu94/Code-Notes mentioned on GitHubpytorchMITSyntology: 6 samples, 6 ran (0 instrument-failed) · 0 unverified 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.

Code Syntology ran Syntology

7 samples harvested: 7 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 1 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 · our draft was wrong
6ran

Licence: 1 of the 7 samples is 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 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “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. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

lonePatient/multi-sample_dropout_pytorch community (archive-listed) 1 sample, 1 ran (1 instrument-failed) · 0 unverified
MiniResNet nn.py ran · our draft was wrong no licence file found · pointer only · ebdc10a64c9c2f8a · report fixture: signature num_classes:int/0/int, dropout_num:int/0/int, dropout_p:float/0/float · returned ResNet · level recorded 2026-09-22
ywu94/Code-Notes community (archive-listed) 6 samples, 6 ran (0 instrument-failed) · 0 unverified
get_GTSRB_dataloader PytorchLightning-GTSRB/dataset.py ran MIT (permissive) · bd236068d0231084 · report fixture: signature target:str/0/str, batch_size:int/0/int, num_workers:int/0/int, pin_memory:bool/0/bool · returned DataLoader · level recorded 2026-09-24
get_bert_tokenizer HuggingFace-TSE/dataset.py ran MIT (permissive) · 66185ba843fd431d · report fixture: signature vocab_path:str/0/str · returned tuple · level recorded 2026-09-24
initiate_logger HuggingFace-TSE/utils.py ran MIT (permissive) · 5b37f5d880c825bf · report fixture: signature log_path:str/0/str · returned Logger · level recorded 2026-09-24
jaccard_iterable HuggingFace-TSE/dataset.py ran fingerprinted MIT (permissive) · 3d5744556206e92a · report fixture: signature a:list/1/int, b:list/1/int · returned float · level recorded 2026-09-24
preprocess in 284 papers
census: 11 implementations from 13 papers, 10 distinct outputs across 5 buckets, one shared input per bucket
HuggingFace-TSE/prepare.py ran fingerprinted MIT (permissive) · 4ed843c936fff706 · report fixture: signature orig_text:str/0/str, orig_selected:str/0/str, sentiment:str/0/str · returned str · level recorded 2026-09-24
process_bert_data HuggingFace-TSE/dataset.py ran MIT (permissive) · 70086749b8492c95 · report fixture: signature text:str/0/str, sentiment:str/0/str, tokenizer:MockTokenizer/0/?, spc_token:dict/0/?, selected_text:str/0/str, max_len:int/0/int, alpha:float/0/float · returned dict · level recorded 2026-09-24

Tasks

Image Classificationimage-classification

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

ConvolutionDropout

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