Hi all,
glad to hear there is somebody else interested in building DNN training 
software with EB.
I will be working on that too so please keep me in the loop and I will be glad 
to help out.

--
Davide Vanzo, PhD
Application Developer
Adjunct Assistant Professor of Chemical and Biomolecular Engineering
Advanced Computing Center for Research and Education (ACCRE)
Vanderbilt University - Hill Center 201
(615)-875-9137
www.accre.vanderbilt.edu

On Oct 18 2016, at 8:16 am, Peretti-Pezzi Guilherme <pere...@cscs.ch> wrote:

Hi

We used EB for all the dependencies (Python, Swig, PCRE, Bazel) when
building a GPU-enabled TF 0.9.0 on our Cray systems.

Building TF itself required a couple of ugly tweaks (see [1]), I was not
convinced that it would work so I didn’t bother to create the .eb for
that.

So far the users didn’t complain much about this build, so I assume it is
working. You can find the .eb files we used for Python, Swig, PCRE and
Bazel on [2].

I hope it helps.

--
Cheers,
G.

[1]
https://github.com/eth-cscs/TensorFlow/wiki/TensorFlow-0.9.0-Daint-GPU-buil
d
[2] https://github.com/eth-cscs/tools/tree/master/easybuild/easyconfigs

-----Original Message-----
From: <easybuild-requ...@lists.ugent.be> on behalf of Erik Smeets
<erik.sme...@asml.com>
Reply-To: "easybuild@lists.ugent.be" <easybuild@lists.ugent.be>
Date: Tuesday 18 October 2016 12:50
To: "easybuild@lists.ugent.be" <easybuild@lists.ugent.be>
Subject: [easybuild] caffe/mxnet/tensorflow easyconfigs

>Hello,
>
>Has anyone got (working) easyconfigs for caffe, mxnet and tensorflow they
>are willing to share? Any work in progress is also appreciated, so we
>could help with these. For Caffe I've already found
>http://www.siliconslick.com/easybuild/ebfiles_repo_cleaned/ada/Caffe/Caffe
>-rc3-intel-2016a-Python-2.7.11.eb and
>https://github.com/hpcugent/easybuild-easyconfigs/pull/3667/files. The
>first is not working (at least for us) and the second is foss toolchain
>based, while we prefer intel toolchain based.
>
>Thanks in advance.
>Kind regards,
>Erik Smeets
>
>-- The information contained in this communication and any attachments is
>confidential and may be privileged, and is for the sole use of the
>intended recipient(s). Any unauthorized review, use, disclosure or
>distribution is prohibited. Unless explicitly stated otherwise in the
>body of this communication or the attachment thereto (if any), the
>information is provided on an AS-IS basis without any express or implied
>warranties or liabilities. To the extent you are relying on this
>information, you are doing so at your own risk. If you are not the
>intended recipient, please notify the sender immediately by replying to
>this message and destroy all copies of this message and any attachments.
>The sender nor the company/group of companies he or she represents shall
>be liable for the proper and complete transmission of the information
>contained in this communication, or for any delay in its receipt.

Reply via email to