From dev-return-2223-archive-asf-public=cust-asf.ponee.io@mxnet.incubator.apache.org Fri Feb 23 19:01:52 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id A4DBE180652 for ; Fri, 23 Feb 2018 19:01:51 +0100 (CET) Received: (qmail 19786 invoked by uid 500); 23 Feb 2018 18:01:50 -0000 Mailing-List: contact dev-help@mxnet.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@mxnet.incubator.apache.org Delivered-To: mailing list dev@mxnet.incubator.apache.org Received: (qmail 19769 invoked by uid 99); 23 Feb 2018 18:01:50 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Feb 2018 18:01:50 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 854C4C0090 for ; Fri, 23 Feb 2018 18:01:49 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.879 X-Spam-Level: * X-Spam-Status: No, score=1.879 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=googlemail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 8qENpVue7ZaM for ; Fri, 23 Feb 2018 18:01:47 +0000 (UTC) Received: from mail-lf0-f46.google.com (mail-lf0-f46.google.com [209.85.215.46]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 7BE085F369 for ; Fri, 23 Feb 2018 18:01:46 +0000 (UTC) Received: by mail-lf0-f46.google.com with SMTP id x196so13522337lfd.12 for ; Fri, 23 Feb 2018 10:01:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=FQaJZFP/3nTIbjtDm6Vfp/0OUuO9sCCjgNnAyXpW05I=; b=N7HT2cMn3mx1K/+DlsVf2c3uk/47yNFwREtkMfSFKyp6HWJ2+Ehxq9BK5Kh6qwX7Dn kZipVmfvu9uBIN+LLK80u1Pmv/ZyFvp/MkdxTdPLEHLZz/jd9QY92droEb0nTNBr9AJD atvk6y2r0AJpVZmva6T+sUB0aybt6vCc9dm9FYRSkQi7oN0+6m8TxhZ+BhSbzvdAs5nG 08gGRbvkZPRdiVGkYF/+r4nNKvXY1bYsnZhFonlt39Aa5Mm55mRKWmKRW6BUN30rIvJF 82rI4Xc2k5smIBfdlzRsdsrLVlqnlCqrve1aE43E74Ozu3xr/tZ8jn/jxISZYPOkBWS3 HYCw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=FQaJZFP/3nTIbjtDm6Vfp/0OUuO9sCCjgNnAyXpW05I=; b=s0QdJPX+96Hu3SCrXdN7d64FZ1r0fOBcrL0lEZxCiabYXdaWcsSOvYtgjxt8/6WHZg GVDJwNDOkn4jbvaYy12oGMJlTN5gpxDBrS67Ip5WbiSvyOfQTEMbvXYf0ysRfeGVlHav xrJ2jv6K17AnROLlXNm3z276Ue+5VFacg9dcHkiUCBD+64caBwpHqfgX0DDT3NvqBYlm U4GLz3xxjiglrjYOm7tkJ4QIvzZynv8NNk1tKUskBgECMYcoSBcVpzqa30RAfJwkAC4J QpvmLPywlXHIzs9xTJ6OH48NU+ksxgpAEwDg9ocWwdbB985GWRisPg6fojfb8/VDzLik Ta/A== X-Gm-Message-State: APf1xPCh/pkbvScsW69sZZ0aK7FYqOH3e9XjWN/tB/3FnkVNAsrB3eTS YbFNo8G8NKfSSEgjOsxrtPH2Zm3tWi6HfkyFJ2M= X-Google-Smtp-Source: AG47ELuud6VoU+5Aeo3By2iMK43RetHWU0WndRWM9Evs0pIUsCGAov4iojX3XzpaEZ31eW+IMHrZt9jac3bc/4sinRI= X-Received: by 10.25.113.14 with SMTP id m14mr1936012lfc.71.1519408898554; Fri, 23 Feb 2018 10:01:38 -0800 (PST) MIME-Version: 1.0 Received: by 10.25.235.88 with HTTP; Fri, 23 Feb 2018 10:01:37 -0800 (PST) Received: by 10.25.235.88 with HTTP; Fri, 23 Feb 2018 10:01:37 -0800 (PST) In-Reply-To: References: <6A91AA90-480E-4A55-94AA-6381BE0D1F8C@amazon.com> From: Marco de Abreu Date: Fri, 23 Feb 2018 19:01:37 +0100 Message-ID: Subject: Re: Request for comments: Proposal for import/export model formats module into MXNet To: dev@mxnet.incubator.apache.org Content-Type: multipart/alternative; boundary="089e082f4370aac34f0565e4f31f" --089e082f4370aac34f0565e4f31f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Good point, Mu! I think this discussion could be taken one step further into re-thinking how we version the components of MXNet. At the moment everything is covered by one version, but this could bring the constraints you mentioned. Another example is the Scala namespace change. We have to hold on doing that change until we do a major version change - something nobody here would like to do just because of a namespace change. Maybe we could modularize these third party components and language bindings and then version each of them separately to the core of MXNet. Best regards, Marco Am 23.02.2018 6:54 nachm. schrieb "Li, Mu" : A general concern is that if we want to include a package under active developing into MXNet. I saw ONNX made a lot of progress these days, such as control flow, while none of us participant into it. It worries me that mxnet=E2=80=99s release may need to be correlated to oonx version. How do o= ther frameworks handle it? Caffe2 and PyTorch should be the two that support onnx most well. > On Feb 22, 2018, at 5:23 PM, Roshani Nagmote wrote: > > Hi Marco, > > Good question. ONNX models come with a version number in the model protobuf > file. We can make use of that field when importing into MXNet. > > You can see the discussion and design of versioning policies in ONNX here= : > https://github.com/onnx/onnx/issues/119 > > - Roshani > > > On Thu, Feb 22, 2018 at 5:21 PM, Naveen Swamy wrote: > >> If you train with a newer version of MXNet and try running on a older >> version of MXNet, it might not already work today, I am not sure if we >> want to support such use-cases. This is tangential to this piece of work >> >> If ONNX were to update their version, I think the right place to keep >> future versions of ONNX compatible should be in ONNX by providing a tool to >> move from ONNX.v0 to ONNX.v1. so that various framework converters alway= s >> move with the latest version of ONNX. >> >> ONNX models I believe already contains the ONNX version with which it wa= s >> built. >> >> >> On Thu, Feb 22, 2018 at 4:38 PM, Marco de Abreu < >> marco.g.abreu@googlemail.com> wrote: >> >>> Hello Roshani, >>> >>> interesting document and a good step towards allowing customers and >>> developers to adopt MXNet faster. >>> >>> Just one quick question: How would your proposed design handle >>> compatibility between old and new versions of MXNet as well as other >>> frameworks? Since serde (import/export) is part of the MXNet source, we >>> won't be able to update it independently. One example I'm thinking abou= t >> is >>> training on the latest version of MXNet and running inference on an older >>> version. Could this cause issues since the ONNX model could be of a >> higher >>> version than the import on the old MXNet version is able to load? Would >> it >>> be necessary to have some kind of compatibility mode during the export >>> process in which you define the target ONNX model version? There might >> also >>> be different operator versions etc. >>> >>> Best regards, >>> Marco >>> >>> >>> >>> On Fri, Feb 23, 2018 at 1:15 AM, Roshani Nagmote < >>> roshaninagmote2@gmail.com> >>> wrote: >>> >>>> Hi all, >>>> >>>> I wanted to follow up on the proposal I sent before. >>>> https://cwiki.apache.org/confluence/display/MXNET/ >>>> Proposal%3A+ImportExport+ >>>> module >>>> >>>> It will be great if you can provide your feedback or suggestions. >>>> >>>> Thanks, >>>> Roshani >>>> >>>> On Thu, Jan 18, 2018 at 4:47 PM, Roshani Nagmote < >>>> roshaninagmote2@gmail.com> >>>> wrote: >>>> >>>>> Hello all, >>>>> >>>>> I have written an initial design proposal for a `serde`(temporary >> name) >>>>> module for importing and exporting different model formats like onnx, >>>>> coreml to and from MXNet. >>>>> >>>>> Please take a look and feel free to provide suggestions in the >> comment >>>>> section. >>>>> >>>>> https://cwiki.apache.org/confluence/display/MXNET/ >>>>> Proposal%3A+ImportExport+module >>>>> >>>>> Note: I will be traveling next week with limited access to emails. >> So, >>>>> responses might be delayed. >>>>> >>>>> Thanks, >>>>> Roshani >>>>> >>>> >>> >> --089e082f4370aac34f0565e4f31f--