You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@systemml.apache.org by "Mike Dusenberry (JIRA)" <ji...@apache.org> on 2017/04/12 21:50:41 UTC

[jira] [Resolved] (SYSTEMML-1516) Improve output size calculation in conv2d & max_pool2d

     [ https://issues.apache.org/jira/browse/SYSTEMML-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mike Dusenberry resolved SYSTEMML-1516.
---------------------------------------
       Resolution: Fixed
    Fix Version/s: SystemML 1.0

Merged in [commit 4a941e4 | https://github.com/apache/incubator-systemml/commit/4a941e44e008a9e65e6a5422d727c720980b0a3d].

> Improve output size calculation in conv2d & max_pool2d
> ------------------------------------------------------
>
>                 Key: SYSTEMML-1516
>                 URL: https://issues.apache.org/jira/browse/SYSTEMML-1516
>             Project: SystemML
>          Issue Type: Sub-task
>            Reporter: Mike Dusenberry
>            Assignee: Mike Dusenberry
>            Priority: Minor
>             Fix For: SystemML 1.0
>
>
> The calculation of the output sizes (`Hout`, `Wout`) for conv2d and
> max_pool2d layers rely on a flooring operation to only allow for valid
> operations.  Currently, we simply rely on the `as.integer` call to
> implicitly perform this flooring operation during truncation of the double
> to an integer.  While this gives the correct results, it is less
> readable than it should be, and relies on truncation behavior than explicit mathematical behavior.  We should simply add an explicit `floor`
> operation to each calculation.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)