DynaML/Lobby

Scala REPL for Machine Learning

Israel Herraiz

@iht

dependencies.dot.js

yes :)

download those three files, you can explore the graph with a web browser

Spire is coming from tensorflow, on one side

version 0.14.1

with organization org.typelevel

on the other hand, breeze is importing spire 0.13.0

with organization org.spire-math

Mandar Chandorkar

@mandar2812

ahhh

:fire:

i see

i have been trying to include tensorflow support

so generally sbt just evicts the spire of breeze

and uses the spire loaded by tensorflow

im wondering why that is not happening in your case

Israel Herraiz

@iht

let me try to exclude spire when importing breeze, and see what happens

Mandar Chandorkar

@mandar2812

yes that is a workaround

Israel Herraiz

@iht

Ah, another thing, i changed build.properties to use sbt 0.13.16

that’s why the plugin did not work

Mandar Chandorkar

@mandar2812

ahh

ill also try it then!

Israel Herraiz

@iht

spire is not evicted because it is using different org names

Mandar Chandorkar

@mandar2812

i made a change to Dependencies.scala

"org.scalanlp" % "breeze_2.11" % "0.13.1" % "compile" exclude("org.spire-math", "spire")

and now i am building to see if it works

Israel Herraiz

@iht

yes, i have tried that

it did not work in my case

breeze is also imported by spark

So I removed the import of breeze, and excluding org.spire-math in the spark dependencies

Mandar Chandorkar

@mandar2812

after excluding spire from breeze, the project compiles but running legacy code is having a runtime error

Mandar Chandorkar

@mandar2812

okay I realise that including tensorflow_scala is causing all sorts of problems with respect to spire dependency resolution

i am going to spend some time to find out how we can resolve them

Israel Herraiz

@iht

thank you for that :)

Mandar Chandorkar

@mandar2812

because tensorflow support is going to be an important feature in DynaML

so i dont want to sacrifice it!

Israel Herraiz

@iht

the main problem is because tensorflow is redefining the organization of spire (and others)

and spire is imported without using the organization name

the package names in spire should include the organization

and tensorflow should not rename the organizations

that way, it would be easy to let sbt handle the conflicts

Mandar Chandorkar

@mandar2812

From what I know about the spire project i know there are two orgs which deliver it

https://mvnrepository.com/artifact/org.spire-math/spire_2.11

and

https://mvnrepository.com/artifact/org.typelevel/spire_2.11

typelevel

Israel Herraiz

@iht

yes

Mandar Chandorkar

@mandar2812

breeze imports spire from the first one

while TF imports from second

Where communities thrive

People

Repo info

Activity