Skip to content

Update BrainScript-epochSize-and-Python-epoch_size-in-CNTK.md #156

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: live
Choose a base branch
from
Open

Update BrainScript-epochSize-and-Python-epoch_size-in-CNTK.md #156

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion articles/BrainScript-epochSize-and-Python-epoch_size-in-CNTK.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ Note that the definition of the number of label samples is similar to the number

So, importantly, for sequential data, a sample is an individual item of a sequence.
Hence, CNTK's `epochSize` does *not* refer to a number of *sequences*,
but the of sequence *items* across the sequence **labels** that constitute the minibatch.
but the number of sequence *items* across the sequence **labels** that constitute the minibatch.

Equally important, it is **label** samples, not input samples, and the number of labels per sequence is not necessarily the number of input samples. It is possible, for example, to have one label per sequence and for each sequence to have many samples (in which case `epochSize` acts like number of sequences), and it is possible to have one label per sample in a sequence, in which case `epochSize` acts exactly like `minibatchSize` in that every sample (not sequence) is counted.

Expand Down