ChanServ changed the topic of #mlpack to: "mlpack: a fast, flexible machine learning library :: We don't always respond instantly, but we will respond; please be patient :: Logs at http://www.mlpack.org/irc/
MattGomes has quit [Remote host closed the connection]
Beeblebrox-BSD has quit [Remote host closed the connection]
< AlexNguyen[m]>
<iamarchit123Gitt "Hey folks small query here how "> I think if you are testing, you have to change the `ignoreInput` flag to False in the main test file. I.e, `Log::Info::IgnoreInput = False`
onur has joined #mlpack
onur has quit [Client Quit]
MattGomes has joined #mlpack
MattGomes has quit [Remote host closed the connection]
tobelegitGitter[ has joined #mlpack
< tobelegitGitter[>
Hey everyone. I was looking forward to contributing to mlpack, however, I am unable to get started. Any help?
< rcurtin>
I'm not sure if you also got a license for pioneer and polar
< zoq>
rcurtin: I think I saw the same issue on the other nodes as well, I take a closer look into the issue.
< rcurtin>
maybe they changed their licensing or something like that
MattGomes has joined #mlpack
< zoq>
rcurtin: yep, let use the offical repo, instead of my fork.
< rcurtin>
ok, if you can let me know what you run on polar and pioneer to fix it, I will do the same on knife, pretzel, and bigglesworth :)
< rcurtin>
I am still negotiating with Georgia Tech to get dealgood back online, by the way
< rcurtin>
all I need them to let me do is come to the datacenter and then work on the system, but because of COVID restrictions the IT team barely comes to campus anymore, so it's hard to figure out a time
< zoq>
I just updated the jenkins job config, to use the viva64 repo.
< rcurtin>
oh, nice, I thought we had installed packages on the system through apt
< rcurtin>
I guess I forgot how it was set up
< zoq>
Maybe they like it and never go back?
< zoq>
I guess you can do a lot from home, if there is no hardware failure.
< rcurtin>
:)
< rcurtin>
yeah, you can avoid atlanta traffic when working from home, which is nice
< rcurtin>
but in this case dealgood actually does have a hardware failure so it needs an in-person visit :)
< MattGomes>
rcurtin Managed to get the build working on Visual Studio. I had some really bad time trying to compile OpenBLAS/Lapack with mingw. The only solution that worked was to build both with `clang-cl` and `flang`, with a few other dependencies pulled with Conda. Aside from that, there were a few tweaks to the root CMake to link some libraries needed by
< MattGomes>
the `OpenBLAS` lib (mainly fortran ones). After all that, Visual Studio could fully use the CMake integration to build the full project!
< rcurtin>
MattGomes: awesome! if you have any ideas of how we can improve our documentation to make the process easier for others in the future, please feel free to open a PR
< rcurtin>
very few of us are Windows experts (I am definitely not very knowledgeable about Windows builds), so I think our Windows documentation can be pretty imperfect at times
< zoq>
rcurtin: And what is proposed fix, to remove the Xserver?
< MattGomes>
I could write a visual studio guide, might create a PR this week when I have some time from work.
< rcurtin>
zoq: yeah, I'll just remove it; there's no need for the Xserve storage when all dealgood is is a Jenkins slave
< rcurtin>
MattGomes: sounds good, thank you!
< MattGomes>
rcurtin I was only able to build with VS as the CMake is quite well written and simple. Most open source projects don't really write CMake that is compatible with Windows, unfortunately. Kudos to you guys.
< rcurtin>
thanks! one good thing we have going is that we do test our builds on Windows systems via Azure and AppVeyor
< rcurtin>
without those tools it would be so much harder
< rcurtin>
so we were able to get things at least working on the setup that our build nodes have :)
< MattGomes>
rcurtin indeed, having a multi platform pipeline helps with portability :)
< MattGomes>
rcurtin the issue is that it seems that Mingw64 is not shipping `libgfortran-3.dll` which was needed for the OpenBLAS project (at least when building the shared lib version)
< MattGomes>
maybe you guys have a different version of mingw to mine, I'll definitely try this again at some point to see if I can figure it out
< rcurtin>
MattGomes: hmm, I'm not sure that we are building with MinGW64 at all, I think our full build in our test pipeline is on MSVC, and we download precompiled OpenBLAS
< rcurtin>
but, I could be wrong
< zoq>
The build instructions I referenced above use mingw, so at some point it worked :)
< MattGomes>
Yeah I think you guys have the precompiled `openblas.dll.a` with the corresponding DLL from one of the `OpenBLAS` contributors. I tried that too but it still required `libfortran-3.dll` on my build :(
< rcurtin>
hmm, strange... I don't fully understand linking on Windows so I'm not sure why it would be needed in your situation but not on Azure
< MattGomes>
It's crazy how badly supported BLAS libraries are on windows, I thought we would have done better by now.
< rcurtin>
yes, especially because everything in scientific computing is built on BLAS!
< rcurtin>
I know that the Julia and Python folks get around this by basically hiding everything in their package managers
< MattGomes>
yes, I had no issues with BLAS/LAPACK on linux before. But it's extra painful getting these on Windows haha
< rcurtin>
so for instance, if you install numpy on Windows, it comes in a "wheel" which contains a carefully compiled OpenBLAS dll
< MattGomes>
It does, I kind of did that with Anaconda to compile OpenBLAS
< MattGomes>
I guess I could have pulled OpenBLAS from Anaconda as well
< MattGomes>
but I was on a mission to compile it myself :D
< rcurtin>
:)
< MattGomes>
Anyway, I need to get some sleep now as I am working tomorrow. Will get that VS guide PR this week when I get some time. See ya
< rcurtin>
sounds good, see you later!
ImQ009 has quit [Quit: Leaving]
MattGomes has quit [Remote host closed the connection]