Re: [mlpack] Introduction and Help

On Mon, Mar 16, 2020 at 02:25:58PM +0530, ajay wayase wrote: > I am Ajay Wayase , final year student of Computer Engineering at Pune > Institute Of Computer Technology and incoming data analyst at Rakuten > Mobile,Tokyo. I would like to work with mlpack for the GSoc20. Can you > please provide me

Re: [mlpack] Introduction

Hi Durgesh, Welcome to the mlpack community! I would say the first step would be to try and build mlpack from source on your machine. This will be required if you want to make additions to the library. I found this guide helpful: https://github.com/mlpack/mlpack#4-building-mlpack-from-source.

Re: [mlpack] Introduction GSoc 2018

Yeah, it finally did. It seemed i didn't add the path variable right. Thank you for the help. Regards Rahul ‌ On Mon, Dec 11, 2017 at 1:29 AM, Evgeny Freyman wrote: > Seems that it still can't find the libmlpack.so. Try calling this before > building (check that there

Re: [mlpack] Introduction GSoc 2018

Seems that it still can't find the libmlpack.so. Try calling this before building (check that there is a mlpack library at specified path) export LD_LIBRARY_PATH="/usr/local/lib/:$LD_LIBRARY_PATH" Another option is to specify location of library thorough -L parameter (g++ -L/usr/local/lib/,

Re: [mlpack] Introduction GSoc 2018

Hi Rahul, Just getting started with MLPack myself and had the similar problem. The solution is: 1. As far as I know gcc is for C and g++ is for C++ language, so you need to use g++ 2. You didn't specify dependencies, thats why you got lots of unresolved references. The proper way to compile your

Re: [mlpack] Introduction of ExecutionPolicy

On Tue, May 16, 2017 at 09:30:52PM +0530, Ankit Aggarwal wrote: > Hi Shikhar > > Just a tip > > Please avoid using *"auto t0 = std::chrono::high_resolution_clock::now();*" > and rather use* gettimeofday* for any kind of benchmarking as if you > measure the performance of these two function you

Re: [mlpack] Introduction of ExecutionPolicy

Hi Shikhar Just a tip Please avoid using *"auto t0 = std::chrono::high_resolution_clock::now();*" and rather use* gettimeofday* for any kind of benchmarking as if you measure the performance of these two function you will find out that high_resolution_clock to be atleast 2-3x slower than

Re: [mlpack] Introduction for GSoC 2017

On Tue, Mar 14, 2017 at 11:09:42PM +0530, Saumya Sachdev wrote: > Hello to everyone at mlpack! > > My name is Saumya Sachdev and I am a Computer Science Engineering student > at PES Institute of Technology, Bangalore, India. I am currently in my > second year of the degree course. I want to