Title: No title found

Abstract: indented 1/2 inch (3 picas) on both left and righthand margins. Use 10 point type, with a vertical spacing of 11 points.

:

If your paper is ultimately accepted, the statement \iclrfinalcopy should be inserted to adjust the format to the camera ready requirements.

The format for the submissions is a variant of the NIPS format. Please read carefully the instructions below, and follow them faithfully.

1.1. STYLE:

Papers to be submitted to ICLR 2019 must be prepared according to the instructions presented here.

Authors are required to use the ICLR L A T E X style files obtainable at the ICLR website. Please make sure you use the current files and not previous versions. Tweaking the style files may be grounds for rejection.

1.2. RETRIEVAL OF STYLE FILES:

The style files for ICLR and other conference information are available on the World Wide Web at http://www.iclr.cc/ The file iclr2019_conference.pdf contains these instructions and illustrates the various formatting requirements your ICLR paper must satisfy. Submissions must be made using L A T E X and the style files iclr2019_conference.sty and iclr2019_conference.bst (to be used with L A T E X2e). The file iclr2019_conference.tex may be used as a "shell" for writing your paper. All you have to do is replace the author, title, abstract, and text of the paper with your own. The formatting instructions contained in these style files are summarized in sections 2, 3, and 4 below.

2. GENERAL FORMATTING INSTRUCTIONS:

The text must be confined within a rectangle 5.5 inches (33 picas) wide and 9 inches (54 picas) long. The left margin is 1.5 inch (9 picas). Use 10 point type with a vertical spacing of 11 points. Times New Roman is the preferred typeface throughout. Paragraphs are separated by 1/2 line space, with no indentation. Authors' names are set in boldface, and each name is placed above its corresponding address. The lead author's name is to be listed first, and the co-authors' names are set to follow. Authors sharing the same address can be on the same line.

Please pay special attention to the instructions in section 4 regarding figures, tables, acknowledgments, and references.

3 HEADINGS: FIRST LEVEL First level headings are in small caps, flush left and in point size 12. One line space before the first level heading and 1/2 line space after the first level heading.

3.1. HEADINGS: SECOND LEVEL:

Second level headings are in small caps, flush left and in point size 10. One line space before the second level heading and 1/2 line space after the second level heading.

3.1.1. HEADINGS: THIRD LEVEL:

Third level headings are in small caps, flush left and in point size 10. One line space before the third level heading and 1/2 line space after the third level heading.

4. CITATIONS, FIGURES, TABLES, REFERENCES:

These instructions apply to everyone, regardless of the formatter being used.

4.1. CITATIONS WITHIN THE TEXT:

Citations within the text should be based on the natbib package and include the authors' last names and year (with the "et al." construct for more than two authors). When the authors or the publication are included in the sentence, the citation should not be in parenthesis (as in "See Hinton et al. (2006) for more information."). Otherwise, the citation should be in parenthesis (as in "Deep learning shows promise to make progress towards AI (Bengio & LeCun, 2007) .").

The corresponding references are to be listed in alphabetical order of authors, in the REFERENCES section. As to the format of the references themselves, any style is acceptable as long as it is used consistently.

4.2. FOOTNOTES:

Indicate footnotes with a number1 in the text. Place the footnotes at the bottom of the page on which they appear. Precede the footnote with a horizontal rule of 2 inches (12 picas). You may use color figures. However, it is best for the figure captions and the paper body to make sense if the paper is printed either in black/white or in color. 

∂f ∂x Jacobian matrix J ∈ R m×n of f : R n → R m ∇ 2 x f (x) or H(f )(x)

The Hessian matrix of f at input point x 

f (x)dx Definite integral

Paper title is 17 point, in small caps and left-aligned. All pages should start at 1 inch (6 picas) from the top of the page.

Sample of the first footnote

Sample of the second footnote

Figures and Tables:

2

All artwork must be neat, clean, and legible. Lines should be dark enough for purposes of reproduction; art work should not be hand-drawn. The figure number and caption always appear after the figure. Place one line space before the figure caption, and one line space after the figure. The figure caption is lower case (except for first word and proper nouns); figures are numbered consecutively. Make sure the figure caption does not get separated from the figure. Leave sufficient space to avoid splitting the figure and figure caption.

Figure 1: Sample figure caption.

Sample table title

Table content: <table><tr><td/><td>PART</td><td>DESCRIPTION</td></tr><tr><td/><td colspan="2">Dendrite Input terminal</td></tr><tr><td/><td>Axon</td><td>Output terminal</td></tr><tr><td/><td>Soma</td><td>Cell body (contains cell nucleus)</td></tr><tr><td>4.4 TABLES</td><td/></tr><tr><td/><td/><td>Numbers and Arrays</td></tr><tr><td>a</td><td colspan="2">A scalar (integer or real)</td></tr><tr><td>a</td><td>A vector</td></tr><tr><td>A</td><td>A matrix</td></tr><tr><td>A</td><td>A tensor</td></tr><tr><td>I n</td><td colspan="2">Identity matrix with n rows and n columns</td></tr><tr><td>I</td><td colspan="2">Identity matrix with dimensionality implied by context</td></tr><tr><td>e (i)</td><td colspan="2">Standard basis vector [0, . . . , 0, 1, 0, . . . , 0] with a 1 at po-</td></tr><tr><td/><td>sition i</td></tr><tr><td>diag(a)</td><td colspan="2">A square, diagonal matrix with diagonal entries given by a</td></tr><tr><td>a</td><td colspan="2">A scalar random variable</td></tr><tr><td>a</td><td colspan="2">A vector-valued random variable</td></tr><tr><td>A</td><td colspan="2">A matrix-valued random variable</td></tr></table>

over the entire domain of x Do not change any aspects of the formatting parameters in the style files. In particular, do not modify the width or length of the rectangle the text should fit into, and do not change font sizes (except perhaps in the REFERENCES section; see below). Please note that pages should be numbered.Most of the margin problems come from figures positioned by hand using \special or other commands. We suggest using the command \includegraphics from the graphicx package.Always specify the figure width as a multiple of the line width as in the example below using .eps graphics \usepackage[dvips]{graphicx} ... \includegraphics[width=0.8\linewidth]{myfile.eps} or \usepackage[pdftex]{graphicx} ... \includegraphics[width=0.8\linewidth]{myfile.pdf} for .pdf graphics. See section 4.4 in the graphics bundle documentation (http://www.ctan. org/tex-archive/macros/latex/required/graphics/grfguide.ps) A number of width problems arise when LaTeX cannot properly hyphenate a line. Please give LaTeX hyphenation hints using the \-command.

Table content: <table><tr><td>P (a)</td><td colspan="2">A probability distribution over a discrete variable</td></tr><tr><td>p(a)</td><td colspan="2">A probability distribution over a continuous variable, or</td></tr><tr><td/><td colspan="2">over a variable whose type has not been specified</td></tr><tr><td>a ∼ P</td><td colspan="2">Random variable a has distribution P</td></tr><tr><td colspan="3">E x∼P [f (x)] or Ef (x) Expectation of f (x) with respect to P (x)</td></tr><tr><td>Var(f (x))</td><td colspan="2">Variance of f (x) under P (x)</td></tr><tr><td>Cov(f (x), g(x))</td><td colspan="2">Covariance of f (x) and g(x) under P (x)</td></tr><tr><td>H(x)</td><td colspan="2">Shannon entropy of the random variable x</td></tr><tr><td>D KL (P Q)</td><td colspan="2">Kullback-Leibler divergence of P and Q</td></tr><tr><td>N (x; µ, Σ)</td><td colspan="2">Gaussian distribution over x with mean µ and covariance</td></tr><tr><td/><td>Σ</td><td/></tr><tr><td/><td colspan="2">Functions</td></tr><tr><td>f : A → B</td><td colspan="2">The function f with domain A and range B</td></tr><tr><td>f • g</td><td colspan="2">Composition of the functions f and g</td></tr><tr><td>f (x; θ)</td><td colspan="2">A function of x parametrized by θ. (Sometimes we write</td></tr><tr><td/><td colspan="2">f (x) and omit the argument θ to lighten notation)</td></tr><tr><td>log x</td><td colspan="2">Natural logarithm of x</td></tr><tr><td>σ(x)</td><td>Logistic sigmoid,</td><td>1 1 + exp(-x)</td></tr><tr><td>ζ(x)</td><td colspan="2">Softplus, log(1 + exp(x))</td></tr><tr><td>||x|| p</td><td>L p norm of x</td><td/></tr><tr><td>||x||</td><td>L 2 norm of x</td><td/></tr><tr><td>x +</td><td colspan="2">Positive part of x, i.e., max(0, x)</td></tr><tr><td>1 condition</td><td colspan="2">is 1 if the condition is true, 0 otherwise</td></tr><tr><td colspan="2">6 FINAL INSTRUCTIONS</td><td/></tr><tr><td colspan="3">7 PREPARING POSTSCRIPT OR PDF FILES</td></tr><tr><td colspan="3">Please prepare PostScript or PDF files with paper size "US Letter", and not, for example, "A4". The</td></tr><tr><td colspan="3">-t letter option on dvips will produce US Letter files.</td></tr><tr><td colspan="3">f (x)dx Consider directly generating PDF files using pdflatex (especially if you are a MiKTeX user). Definite integral with respect to x over the set S S Probability and Information Theory PDF figures must be substituted for EPS figures, however.</td></tr><tr><td colspan="3">Otherwise, please generate your PostScript and PDF files with the following commands:</td></tr><tr><td colspan="3">dvips mypaper.dvi -t letter -Ppdf -G0 -o mypaper.ps</td></tr><tr><td colspan="2">ps2pdf mypaper.ps mypaper.pdf</td><td/></tr><tr><td colspan="2">7.1 MARGINS IN LATEX</td><td/></tr></table>

Peer review (iclr2019):
 The authors propose a variant to convLSTMs with convolutional peephole units (as opposed to the original Hadamard product) and tied gates. The description of the model is confusing, the authors don*t offer a strong justification for the proposed approach, some of the technical choices seem flawed. It is also obviously false that removing an LSTM gate does not incur in a reduction of trainable parameters: "There were other attempts to design smaller recurrent gated models [...] based on either removing one of the gates or the activation functions [...] these models had no significant reduction in trainable parameters". The model description is difficult to follow, but from what I can gather the model depiction is flawed. In particular, the proposed model bases on the idea to use tied gates to reduce the number of parameters. f^{(t)}, i.e., the value that governs the input, forger and output gates, is derived via a sigmoid. When the sigmoid is zero, the network will hence set all the gates to zero, ignoring the input, forgetting the memory and suppressing the output, which is hardly a behaviour one could ever want. Unfortunately, almost half of the sigmoid spectrum will lead to such behavior. This seems to be a poor modeling decision. The nodes in Figure 1 seem to suggest that two consecutive non-linearities are applied in a row, if W_fc is clamped to zero, as reported by the authors, there is no reason to specify it, the corresponding part of the equation can be removed and the narrative simplified. In sec3, the meaning of “net input image” and “network gate image value” is unclear. Also the description of the equation is hard to follow, e.g., the square bracket notation is eventually explained only after 8 lines of text. At the beginning of Sec4 err_1 and err_2 are defined as the difference between the predicted frame and the target frame, and vice versa. This error is then fed to the “rgcLSTM input arranger unit and to the next higher layer”. By my understanding the error of one layer is fed in the next as an input. I wonder if such error is provided also at inference time, giving a clear guidance to the network to produce the correct output exploiting privileged information. This could also explain why the training process was completed in only one epoch. - Typos: *Intro: More important → more importantly * page5: ReL -> ReLu