[NLPL Task Force (A)] early feedback

[Stephan Oepen]

hi asad,

thanks for your feedback!  i am glad you like the Abel cluster, even
though it cannot currently run what you would like to do :-).

it seems it did not take very long for an NLPL user to question our
assumption that folks should be able to make do with just Python 3.x
these days.  challenge accepted!

i cannot yet promise this will play out in the long run, nor do i want
to promise we will commit to supporting it.  but it appears i may have
managed to apply the ‘glibc gymnastics’ to a TensorFlow installation
that supports both Python 2.7 and 3.5.

i would encourage you to try the following:

module purge
module use -a /projects/nlpl/software/modulefiles
module load nlpl-play/1.11/2.7

does the above work for you?  oe

On Thu, Oct 4, 2018 at 12:56 AM Asad Sayeed <asayeed at mbl.ca> wrote:
>
> Hi,
>
> I've started trying to use the cluster.  It's great but my current task
> seems to be impossible there, so I am running it for longer on local
> machines.  The most recent issue is that I wanted to run a neural
> semantic role labeller that requires a recent tensorflow that runs on
> python2.7.  I was only able to find a tensorflow that runs on python3,
> and my attempts to use a singularity container failed on abel even when
> I tried to package the container on my local system with the same
> singularity version that is on abel.  Also virtualenv and user-level
> package install did not work for me because of an incompatible glibc
> library. Would there be any chance of getting a tensorflow for python2.7
> working on abel, along with tensorflow_hub?
>
> The purpose is to perform SRL on about 10 million sentences, which
> should take a day if I can run 400 processes with 10GB memory each (to
> hold glove vectors).  I may in the future have even larger SRL-related
> tasks.
>
> Yours,
> --Asad.
>