IRC logs of #shogun for Sunday, 2013-07-28

--- Log opened Sun Jul 28 00:00:50 2013
shogun-buildbotbuild #1412 of deb3 - modular_interfaces is complete: Failure [failed test python_modular]  Build details are at http://www.shogun-toolbox.org/buildbot/builders/deb3%20-%20modular_interfaces/builds/1412  blamelist: Soeren Sonnenburg <sonne@debian.org>00:05
-!- travis-ci [~travis-ci@ec2-54-234-43-199.compute-1.amazonaws.com] has joined #shogun00:07
travis-ci[travis-ci] it's Soeren Sonnenburg's turn to pay the next round of drinks for the massacre he caused in shogun-toolbox/shogun: http://travis-ci.org/shogun-toolbox/shogun/builds/956166700:07
-!- travis-ci [~travis-ci@ec2-54-234-43-199.compute-1.amazonaws.com] has left #shogun []00:07
shogun-buildbotbuild #1287 of deb2 - static_interfaces is complete: Failure [failed compile r_static]  Build details are at http://www.shogun-toolbox.org/buildbot/builders/deb2%20-%20static_interfaces/builds/1287  blamelist: Soeren Sonnenburg <sonne@debian.org>00:08
shogun-buildbotbuild #1413 of deb3 - modular_interfaces is complete: Failure [failed compile r_modular]  Build details are at http://www.shogun-toolbox.org/buildbot/builders/deb3%20-%20modular_interfaces/builds/1413  blamelist: Soeren Sonnenburg <sonne@debian.org>00:28
shogun-buildbotbuild #1096 of cyg1 - libshogun is complete: Failure [failed compile]  Build details are at http://www.shogun-toolbox.org/buildbot/builders/cyg1%20-%20libshogun/builds/1096  blamelist: Evgeniy Andreev <gsomix@gmail.com>, Soeren Sonnenburg <sonne@debian.org>00:36
@iglesiasggood night!01:07
-!- iglesiasg [~Fernando@s83-179-44-135.cust.tele2.se] has quit [Quit: Leaving]01:08
shogun-buildbotbuild #1414 of deb3 - modular_interfaces is complete: Failure [failed test python_modular]  Build details are at http://www.shogun-toolbox.org/buildbot/builders/deb3%20-%20modular_interfaces/builds/1414  blamelist: Evgeniy Andreev <gsomix@gmail.com>, Soeren Sonnenburg <sonne@debian.org>01:15
shogun-buildbotbuild #1288 of deb2 - static_interfaces is complete: Success [build successful]  Build details are at http://www.shogun-toolbox.org/buildbot/builders/deb2%20-%20static_interfaces/builds/128801:16
-!- shogun-notifier- [~irker@7nn.de] has quit [Quit: transmission timeout]02:20
shogun-buildbotbuild #414 of nightly_none is complete: Failure [failed compile]  Build details are at http://www.shogun-toolbox.org/buildbot/builders/nightly_none/builds/41403:11
shogun-buildbotbuild #471 of nightly_default is complete: Failure [failed test]  Build details are at http://www.shogun-toolbox.org/buildbot/builders/nightly_default/builds/47104:52
-!- abinash [~abinash@1.38.21.237] has joined #shogun05:07
-!- abinash [~abinash@1.38.21.237] has quit [Quit: Leaving]05:18
-!- pickle27 [~Kevin@d67-193-243-174.home3.cgocable.net] has joined #shogun05:53
-!- nube [~rho@49.244.123.113] has quit [Ping timeout: 246 seconds]06:45
gsomixgood morning06:52
-!- nube [~rho@49.244.127.129] has joined #shogun07:00
pickle27gsomix: hey!07:16
-!- hushell [~hushell@c-24-21-169-136.hsd1.or.comcast.net] has joined #shogun07:19
-!- pickle27 [~Kevin@d67-193-243-174.home3.cgocable.net] has quit [Quit: Leaving]07:31
-!- foulwall` [~user@222.36.81.211] has joined #shogun07:40
-!- nube [~rho@49.244.127.129] has left #shogun []07:42
-!- foulwall` [~user@222.36.81.211] has quit [Ping timeout: 240 seconds]08:36
-!- gsomix [~gsomix@95.67.178.31] has quit [Ping timeout: 240 seconds]08:49
-!- gsomix [~gsomix@85.26.234.67] has joined #shogun09:07
-!- foulwall` [~user@222.36.81.211] has joined #shogun09:11
-!- gsomix [~gsomix@85.26.234.67] has quit [Ping timeout: 264 seconds]09:14
-!- nube [~rho@49.244.127.129] has joined #shogun09:33
-!- gsomix [~gsomix@95.67.178.31] has joined #shogun09:40
-!- lambday [67157f37@gateway/web/freenode/ip.103.21.127.55] has joined #shogun10:20
lambdaysonney2k: moin moin :)10:20
lambdaysonney2k: lisitsyn: how does our lapack support work?10:21
lambdayI mean, is every routine in lapack available or just the ones that are defined in lapack.h?10:23
lisitsynlambday: every but for some of them we have some wrappers10:31
lisitsynlambday: I wanted to talk out that thing you have with your tridiagonalization10:31
lisitsynI am afraid I don't get the exact problem10:31
-!- lambday_ [67157d37@gateway/web/freenode/ip.103.21.125.55] has joined #shogun10:32
lambday_lisitsyn: sorry I got disconnected :(10:32
lambday_lisitsyn: please tell me what you think10:33
lambday_we need a tridiagonal eigen solver for implementing Lanczos10:33
lambday_and as of now, I don't know if I can use that using eigen310:34
-!- lambday [67157f37@gateway/web/freenode/ip.103.21.127.55] has quit [Ping timeout: 250 seconds]10:34
lambday_lisitsyn: we can use readymade Lanczos implementation from external libs (like, the one you showed me the other day)10:36
lisitsynlambday_: the matrix you work on is sparse right?10:36
lambday_lisitsyn: yes... I need that for Lanczos T-matrix10:36
lambday_lisitsyn: so, this matrix will get huge if the iteration goes on for quite long10:37
lambday_and using dense matrix won't be an efficient soln for that...10:38
lisitsynokay I see10:38
lambday_lisitsyn: so in krylstat, they used a tridiagonal eigen solver from alglib for that10:39
lambday_while I was checking that, turns out that alglib has taken it from lapack10:39
lambday_and since we have lapack support, I guess I can use that routine directly?10:40
lisitsynlambday_: yes sure10:40
lisitsynlambday_: are you talking about the step that works with tridiagonalized matrix?10:40
lisitsynor tridiagonalization itself?10:40
lisitsynthere is a nice method implemented in lapack10:41
lisitsynMRRR10:41
lisitsynor MR310:41
lambday_the step that works with a tridiagonal matrix (the diagonal and subdiagonals are formed from CG iteration)... its already tridiagonalized10:41
lambday_what does this method do?10:41
lisitsynlambday_: T -> eigenpairs10:42
lambday_lisitsyn: then this is probably exactly what I need :D10:42
lambday_lisitsyn: but I never worked with lapack :-/10:42
lisitsynah nevermind I'll guide you here10:42
lambday_lisitsyn: thanks man! :D10:43
lambday_I'm checking the documentation for MR3 then10:43
lisitsynlambday_: do you need all eigenpairs?10:43
lisitsynor?10:43
lambday_lisitsyn: we need only max/min eig values10:43
lisitsynlambday_: just one maximal10:44
lisitsynand just one minimal?10:44
lambday_lisitsyn: yes10:44
lisitsynhttp://www.netlib.org/clapack/CLAPACK-3.1.1/SRC/dstemr.c10:44
lisitsynlambday_: you need DSTEMR10:44
lisitsynlambday_: well or SSTEMR if you work with float10:45
lisitsynlambday_: you'd need to call it twice then I think10:45
lambday_lisitsyn: ah.. thanks..10:45
lambday_lisitsyn: twice?10:45
lisitsynlambday_: well for max and min10:45
lambday_lisitsyn: okay10:45
lisitsynlambday_: in the first case you call it with10:45
lisitsyn[0,1)10:45
lisitsynlike compute 0th eigenpair10:46
lisitsynand in the second you know10:46
lisitsynother side10:46
lambday_lisitsyn: alright...10:46
lisitsynlambday_: will you call it more than once in your code?10:46
lambday_lisitsyn: just once10:47
lisitsynoh then lets not write a wrapper10:47
lisitsynlambday_: http://www.netlib.org/clapack/CLAPACK-3.1.1/SRC/dstemr.c lets just go through all parameters10:47
lisitsynI guess you need10:47
lisitsynJOBZ = 'N'10:48
lisitsyn?10:48
lambday_yes10:48
lisitsynRANGE = 'I'10:48
lambday_yes10:48
lisitsynN = size of your matrix10:48
lambday_N will be equal to Lanczos iteration10:48
lambday_yep10:48
lisitsynD = that's diagonal of your T thing10:48
lisitsynE = subdiagonal10:48
lisitsynjust pointers10:48
lambday_alright10:49
lisitsynVL = 0.010:49
lisitsynVU = 0.010:49
lisitsynIL = 110:49
lisitsynIU = 210:49
lambday_why VL and VU=0.0?10:49
lisitsynlambday_: they are not used here10:49
lisitsynlambday_: you may set bounds of eigenvalues you need10:49
lambday_lisitsyn: okay10:49
lisitsynthat's a different mode10:50
lambday_alright10:50
lisitsynM - just create some integer before call and pass it by reference10:50
lisitsynint M;10:50
lisitsynf(&m)10:50
lisitsynlike that10:50
lambday_alright10:50
lisitsynZ = null10:51
lisitsynLDZ = 110:51
lambday_there is a W10:51
lisitsynoops10:51
lambday_which is of length one (since we'll call it once for max and once for min)10:51
lambday_right?10:51
foulwall`ls10:52
lisitsynlambday_: for W you'd have to allocate an array10:52
lisitsynlambday_: no unfortunately it has to be of size N10:52
lambday_lisitsyn: okay10:52
lisitsynlambday_: but it shouldn't be a big deal10:52
lisitsynlambday_: just allocate it once10:52
lisitsynand use twice10:52
lisitsynthen delete10:52
lisitsynokay10:52
lambday_okay... alright10:52
lisitsynNZC should not be referenced I think10:53
lisitsynjust set it to 110:53
lisitsynISUPPZ = null10:53
lambday_okay10:53
lisitsynTRYRAC - you could play with it10:53
lisitsyntry both false and true10:54
lambday_lisitsyn: alright.. for accuracy stuffs10:54
lambday_okay10:54
lisitsynlambday_: argh I guess you'd still need to call it once to estimate worksizes10:54
lambday_lisitsyn: once more? you mean thrice??10:55
lisitsynlambday_: yeah they use such interface10:55
lisitsynwhen you call it once to estimate work sizes10:55
lisitsynand then work with it10:55
lambday_lisitsyn: alright10:55
lisitsynlambday_: but you may try without yet10:55
lisitsynokay lets pass through all the rest parameters10:56
lambday_WORK10:56
lisitsynlambday_: for WORK allocate some thing of size 12*N10:56
lambday_why 12?10:56
lisitsynLWORK >= max(1,12*N) if JOBZ = 'N'10:57
lisitsynlambday_: magic :)10:57
lambday_:D10:57
lisitsynlambday_: they want it to be >= 12*N10:57
lisitsynso WORK = some array of 12*N or 2*12*N10:57
lisitsynLWORK = size of that array10:57
lambday_okay10:57
lisitsynIWORK = some INTEGER array of size 8*N or 8*2*N10:58
lisitsynand LIWORK = size of that array10:58
lambday_LIWORK size of that array10:58
lambday_alright10:58
lisitsynINFO = some integer variable passed by reference10:58
lambday_info - reference?10:58
lambday_yes10:58
lambday_phew!!!10:58
lambday_man!!! :(10:58
lisitsynlambday_: that's okay DSYEVR has even more parameters10:59
lambday_why so complicated :'(10:59
lambday_lisitsyn: now I get why Heiko hates it :'(10:59
lisitsynwell there is a reason why they made it that way I think10:59
lambday_must be11:00
lisitsynlambday_: now the worst part of our adventure11:00
* lambday_ holds his breath11:00
lisitsynlambday_: well I'd skip it for now11:00
lisitsynlambday_: if user doesn't have ATLAS11:00
lisitsynwe'd have to write a simple C++ wrapper11:00
lisitsynthat just calls this function11:00
lisitsynlambday_: but for now lets just #ifdef HAVE_ATLAS your part of code11:01
lambday_lisitsyn: umm... okay, alright11:01
lambday_lisitsyn: I am trying this thing out... in a small example code..11:01
lisitsynlambday_: with atlas11:02
lisitsynyour call would be11:02
lisitsynclapack_dormtr(...)11:02
lisitsynlambday_: with all these parameters11:02
lambday_trying11:03
lambday_lisitsyn: okay11:03
lisitsynlambday_: ahh one more thing11:03
lisitsynlambday_: put an assertion that info = 0 after the call11:03
lambday_lisitsyn: okay.. success check11:04
lisitsynand better output its value11:04
lisitsynbecause if it failed it would be hard to understand anyway11:04
lisitsynbut without error value impossible at all :)11:04
lisitsynlambday_: you're quite lucky you don't have to compute eigenvectors11:09
lambday_lisitsyn: that would have been a nightmare I am guessing :-s11:10
lisitsynlambday_: you'd need to call it once with all LWORK, LIWORK set to -111:10
lisitsynon output they will say you how much memory you need11:11
lisitsynhowever they are not going to be changed11:11
lisitsynthat thing will be stored in WORK and IWORK11:11
lisitsynas integer11:11
lisitsynWORK[0] to be precise11:11
lisitsynand then you'd allocate your memory11:11
lisitsynand then finally call it11:11
-!- iglesiasg [~Fernando@s83-179-44-135.cust.tele2.se] has joined #shogun11:13
-!- mode/#shogun [+o iglesiasg] by ChanServ11:13
lambday_lisitsyn: allocate my memory for?11:13
lisitsynlambday_: WORK, IWORK11:13
lambday_lisitsyn: oh so its not 12*N or 8*N fixed... they will give me how much I need... and I'd do that... alright11:14
lisitsynlambday_: yes that's implementation dependent I guess11:14
lisitsynlambday_: 12N and 8N are minimal sizes11:14
lambday_lisitsyn: alright11:14
lisitsynlambday_: I'd try 12*N*2 too11:14
lisitsynjust to check performance11:14
lambday_okay.. I'll check11:15
lisitsynlambday_: that thing is scary indeed but when you think how much effort would be to write all these algorithms11:19
lisitsynto test it and to check its accuracy11:19
lisitsynefficiency whatever11:19
lambday_lisitsyn: yeah..11:20
lambday_lisitsyn: in standard operations, which performs better? lapack or eigen3?11:20
lisitsynlambday_: lapack is just an interface11:21
lisitsynlambday_: but it is implemented in MKL11:21
lambday_to blas?11:21
lisitsynno11:21
lisitsynblas is basic linear algebra11:21
lisitsynlapack is something advanced11:21
lisitsynlike decompositions and solver11:21
lisitsyns11:21
lisitsynlambday_: MKL has the best performance on intel cpus11:22
lambday_okay11:22
lisitsynbut that's predictable11:22
lisitsynI mean MKL is made by intel11:22
lisitsynthey know how to work with intel processors :D11:22
lambday_haha :D11:22
lisitsynlambday_: good thing about eigen3 is that you can use MKL in it11:22
lisitsynlambday_: anyway eigen3 is ok with multiplications and etc11:23
lambday_that's awesome11:23
lisitsynbut it is pretty bad with SVD11:23
lambday_lisitsyn: what about other decompositions?11:23
lambday_QR etc11:23
lisitsynlambday_: QR is ok iirc11:23
lambday_alright11:23
lisitsynlambday_: they don't have that fancy MRRR too11:24
lambday_lisitsyn: yeah :( they should :(11:24
lisitsynmultiple relative robust representation11:24
lisitsynlambday_: their development slowed down a bit it seems11:24
lambday_err.. what it is for? (I was thinking about this tridiagonal solver)11:24
lisitsynwell that's what happens to mature software11:24
lisitsynlambday_: yes it is that tridiag solver11:25
lambday_eigen3 is used by many many projects right?11:25
lambday_I saw somewhere that Google uses it too11:25
lisitsynlambday_: yes in their nonlinear least squares solver11:25
lisitsynforgot its name11:26
lisitsynwhich is used for google maps and etc11:26
lisitsynceres11:26
lambday_wow!11:26
lambday_lisitsyn: one offbit question.. does modern gcc (say, 4.6) produces vectorized instructions already automatically/11:27
-!- foulwall` [~user@222.36.81.211] has quit [Remote host closed the connection]11:32
lambday_lisitsyn: did you mean clapack_dormtr or clapack_dstemr ?11:38
lambday_lisitsyn: I checked with both and it says method doesn't exist.. I have clapach.h in /usr/include... compiling with "g++ lapack.cpp -lshogun -llapack".. am I missing something?11:43
-!- gsomix_ [~gsomix@109.169.249.121] has joined #shogun11:50
lisitsynlambday_: dstemr indeed11:52
-!- gsomix [~gsomix@95.67.178.31] has quit [Ping timeout: 240 seconds]11:52
lambday_lisitsyn: tried with " g++ lapack.cpp -lshogun -L/usr/lib64/atlas/liblapack.so" too11:52
lisitsynlambday_: yes gcc uses SSE and stuff already11:52
lisitsynlambday_: is there clapack_dstemr11:53
lisitsynin clapack.h?11:53
lambday_lisitsyn: nope :|11:53
lisitsynuhh11:53
lisitsynthat's worse11:53
lambday_what does this mean?11:54
lambday_atlas didn't create code for this routine for this arch?11:54
-!- dekun [7ae07e1e@gateway/web/freenode/ip.122.224.126.30] has joined #shogun11:58
lisitsynlambday_: okay I am back12:31
lisitsynlets think about it12:31
lambday_lisitsyn: wb :) I am manually installing a different version of clapack12:31
lisitsynlambday_: oops! does it have that method?12:32
lambday_lisitsyn: yep... its 3.1.112:32
lambday_but not installed yet12:32
lambday_make is tricky for this12:32
lambday_argh! :( its horrible :(12:55
lambday_lisitsyn: finally able to compile BUT13:13
lambday_lisitsyn: this version uses liblapacke.a13:14
lambday_lisitsyn: the method is LAPACKE_dstemr(..)13:14
lambday_its 3.413:14
lisitsynlambday_: well just make it work locally13:14
lisitsynlater we will check13:14
lambday_lisitsyn: alright13:14
lambday_I can't use shogun's lapack with it as of now13:14
-!- votjakovr [~votjakovr@host-46-241-3-209.bbcustomer.zsttk.net] has joined #shogun13:15
lambday_lisitsyn: I'll be back soon.. pretty hungry :(13:15
lisitsynalright13:15
@sonney2kgsomix_, so on a coding spre now?13:16
@sonney2kiglesiasg, did you figure out anything about the build failure?13:16
gsomix_sonney2k, yep. recently started.13:18
@iglesiasgsonney2k: do you mean the python example?13:18
@iglesiasgsonney2k: AFAIK the build works fine13:18
gsomix_sonney2k, how is weather? heat?13:18
@sonney2kiglesiasg, nope http://shogun-toolbox.org/buildbot/builders/deb3%20-%20modular_interfaces/builds/1414/steps/test%20python_modular/logs/stdio13:19
@iglesiasgsonney2k: all right, we are talking about the same. I worked on it yesterday night a while, but didn't manage to solve it yet13:20
@iglesiasgsonney2k: But now I am working on LMNN, I have to make some progress with it. I will work again on that ASAP13:21
-!- shogun-notifier- [~irker@7nn.de] has joined #shogun13:22
shogun-notifier-shogun: Soeren Sonnenburg :develop * 3c5a95b / src/shogun/structure/FactorGraph.cpp: https://github.com/shogun-toolbox/shogun/commit/3c5a95b1da818cef0a47bc456e69bb255e26345f13:22
shogun-notifier-shogun: move ifdef to appropriate place13:22
@sonney2kgsomix_, yes hot but water is 12 C13:22
@sonney2kwind is just changing so I guess it will be 20 C in the evening13:23
shogun-notifier-shogun-data: foulwall :master * 9f3e8b7 / ocr/ocr.svm.gz: https://github.com/shogun-toolbox/shogun-data/commit/9f3e8b7217e46711e12aa9d72e0bf67807bd2afd13:23
shogun-notifier-shogun-data: add the ocr.svm.gz to data/ocr13:23
shogun-notifier-shogun-data: Soeren Sonnenburg :master * 0d0c9d6 / ocr/ocr.svm.gz: https://github.com/shogun-toolbox/shogun-data/commit/0d0c9d67195a18ad2bb9424e5dc49b16fb9c3a3913:23
shogun-notifier-shogun-data: Merge pull request #9 from ZhengyangL/master13:23
shogun-notifier-shogun-data:13:23
shogun-notifier-shogun-data: add the ocr.svm.gz to data/ocr13:23
shogun-notifier-shogun-demo: foulwall :master * 20cd8b9 / / (12 files): https://github.com/shogun-toolbox/shogun-demo/commit/20cd8b9a0940b2a68dbfb5375c0906b74a8d013613:24
shogun-notifier-shogun-demo: perfect ocr13:24
shogun-notifier-shogun-demo: foulwall :master * 58b475a / / (9 files): https://github.com/shogun-toolbox/shogun-demo/commit/58b475a87a575a70c2ac1c806fda012be96865a613:24
shogun-notifier-shogun-demo: 1. fixed the preview redrawing bug. 2. fixed the circle turn-white bug. 3. add shogun-data submodule back. 4. put ocr.svm.gz into local/13:24
shogun-notifier-shogun-demo: Soeren Sonnenburg :master * 08afcfc / / (16 files): https://github.com/shogun-toolbox/shogun-demo/commit/08afcfc810f9c2bdec6f1e8c32a7155fafee8b7c13:24
shogun-notifier-shogun-demo: Merge pull request #16 from ZhengyangL/ocr13:24
shogun-notifier-shogun-demo:13:24
shogun-notifier-shogun-demo: perfect ocr13:24
@sonney2kgsomix_, please also shorten the constructor13:25
gsomix_sonney2k, yes, I remember.13:25
@sonney2kshogun-buildbot, force build nightly_none13:27
shogun-buildbotbuild forced [ETA 23m31s]13:27
shogun-buildbotI'll give a shout when the build finishes13:27
shogun-notifier-shogun-data: Soeren Sonnenburg :master * 77d078c / ocr/ocr.svm.gz,ocr/train_data_x.asc.gz,ocr/train_data_y.asc.gz: https://github.com/shogun-toolbox/shogun-data/commit/77d078cf617f3e3fb128c4b7e27761de104954d313:34
shogun-notifier-shogun-data: put all ocr data into the ocr dir13:34
shogun-notifier-shogun: Soeren Sonnenburg :develop * ce0aca3 / data/ (5 files): https://github.com/shogun-toolbox/shogun/commit/ce0aca3de8042c8582648b1f9931d03ee1678eaf13:37
shogun-notifier-shogun: move all ocr data into data/ocr13:37
@sonney2kgsomix_, I would like to convert the examples we have to use your csvfile so it would be good to have the stable api13:41
lambday_lisitsyn: back13:41
lambday_lisitsyn: apparently it computes perfectly13:41
lisitsynlambday_: so everything is correctly computed?13:42
lisitsynyou mean eigenvalues?13:42
lambday_lisitsyn: just checked with a diagonal matrix.. it gives perfect result13:42
@sonney2kgsomix_, so basically I want to get rid of tools/load.py in the python_modular examples13:42
lambday_lisitsyn: now checking with a true tridiag one13:42
@sonney2ksome way to go still13:43
lambday_lisitsyn: cross checked with octave - perfect!13:45
gsomix_sonney2k, aha, got it.13:45
lisitsynlambday_: gut13:45
lambday_lisitsyn: Germen for good? :D13:45
lisitsynlambday_: ja13:45
lambday_ya for spanish :D13:45
gsomix_sonney2k, now I'm working on quoting and set/get_string_list methods13:46
lambday_lisitsyn: so, I am working with #include <lapacke.h> (from lapack-3.4.2/lapacke/include), with static lib lapacke.a)13:47
shogun-buildbotbuild #1097 of cyg1 - libshogun is complete: Failure [failed compile]  Build details are at http://www.shogun-toolbox.org/buildbot/builders/cyg1%20-%20libshogun/builds/1097  blamelist: Soeren Sonnenburg <sonne@debian.org>13:47
lambday_lisitsyn: now how can I make it work with shogun's lapack wrapper?13:48
lambday_lisitsyn: apparently including this lapacke.h and shogun/mathematics/lapack.h in a single file gives error (they made quite a few changes, params shuffled/dropped etc)13:48
lisitsynlambday_: check shogun/mathematics/lapack.cpp13:49
lambday_lisitsyn: for example, this new one don't have WORK thing13:49
lisitsynlambday_: first add these defines13:49
lambday_lisitsyn: checking'13:49
-!- travis-ci [~travis-ci@ec2-54-234-72-29.compute-1.amazonaws.com] has joined #shogun13:49
travis-ci[travis-ci] it's Soeren Sonnenburg's turn to pay the next round of drinks for the massacre he caused in shogun-toolbox/shogun: http://travis-ci.org/shogun-toolbox/shogun/builds/957331613:49
-!- travis-ci [~travis-ci@ec2-54-234-72-29.compute-1.amazonaws.com] has left #shogun []13:49
lisitsynlambday_: next13:49
lisitsynlambday_: in .h13:49
lisitsynadd clapack_dstemr13:50
lisitsynor how is it called?13:50
lambday_lisitsyn: but the problem is, in mathematics/lapack.h it includes lapack.h, I need lapacke.h, can't include these two together13:51
lisitsynlambday_: nahh nevermind for now13:51
lambday_lisitsyn: so, new ifdef required?13:51
lisitsynno13:51
lisitsynlambday_: hmmmm I think we can do it simpler13:52
lambday_lisitsyn: how?13:52
lisitsynlambday_: shogun/mathematics/lapack.h:10113:52
lisitsynlambday_: just add dstemr_(...) here13:53
lambday_lisitsyn: alright13:53
lambday_lisitsyn: and then what will I do in the cpp?13:53
lisitsynlambday_: well you may call dstemr_ directly13:54
lambday_lisitsyn: but that's defined in my clapack.h13:54
lisitsynlambday_: ohh then try to call it13:55
lambday_lisitsyn: okay I'm trying..13:55
lisitsynI would avoid writing a wrapper here13:56
-!- travis-ci [~travis-ci@ec2-54-234-72-29.compute-1.amazonaws.com] has joined #shogun14:08
travis-ci[travis-ci] it's Soeren Sonnenburg's turn to pay the next round of drinks for the massacre he caused in shogun-toolbox/shogun: http://travis-ci.org/shogun-toolbox/shogun/builds/957349214:08
-!- travis-ci [~travis-ci@ec2-54-234-72-29.compute-1.amazonaws.com] has left #shogun []14:08
lambday_lisitsyn: I get a few undefined ref from libshogun, like "/usr/local/lib/libshogun.so: undefined reference to `clapack_dgetrf'", clapack_dgetri, etc..14:17
lambday_lisitsyn: when I just add the function declaration in mathematics/lapack.h14:18
lisitsynlambday_: looks strange for me14:20
lisitsynis it with atlas or?14:20
lambday_lisitsyn: there are in lapack.h already!14:20
lisitsynwell but that's undefined reference14:20
lisitsynso no implementation14:20
shogun-buildbotbuild #1415 of deb3 - modular_interfaces is complete: Failure [failed test python_modular]  Build details are at http://www.shogun-toolbox.org/buildbot/builders/deb3%20-%20modular_interfaces/builds/1415  blamelist: Soeren Sonnenburg <sonne@debian.org>14:24
lambday_lisitsyn: weird! they are there in clapack.h (for atlas is present).. and implemented in lapack.cpp too14:26
lambday_oh I see14:27
lambday_lisitsyn: yippie!14:27
lambday_:D14:27
lisitsynlambday_: solved?14:27
lambday_lisitsyn: yep14:27
lambday_I was using -llapack so it was using /usr/lib64/lapack.so, not /usr/lib64/atlas/lapack.so14:28
lambday_phew!14:28
lisitsynahh I see14:28
lambday_so, I am adding this14:28
lambday_but creating every variable and passing a pointer is surely a pain'14:29
lambday_:(14:29
lisitsynlambday_: what do you mean?14:30
lambday_lisitsyn: all 21 vars should be passed as pointers14:30
lambday_params I mean14:30
lisitsynohhh14:30
lisitsynhaha I see14:30
lisitsynlambday_: what do you think about adding a wrapper then?14:30
lambday_lisitsyn: might be better idea14:31
lisitsynlambday_: like wrap_dsyevr14:31
lambday_lisitsyn: although I will be using it at one place only but may be it comes handy later?14:31
lisitsynlambday_: well it would simplify your code anyway14:31
lambday_lisitsyn: yep14:31
lambday_I wanna get rid of these working vectors14:31
lambday_allocate 12*2 and 8*2 by default :D14:32
shogun-buildbotbuild #1098 of cyg1 - libshogun is complete: Failure [failed compile]  Build details are at http://www.shogun-toolbox.org/buildbot/builders/cyg1%20-%20libshogun/builds/1098  blamelist: Soeren Sonnenburg <sonne@debian.org>14:34
shogun-buildbotbuild #415 of nightly_none is complete: Failure [failed compile]  Build details are at http://www.shogun-toolbox.org/buildbot/builders/nightly_none/builds/41514:35
lambday_lisitsyn: why would you wanted to avoid writing a wrapper?14:36
lisitsynlambday_: just to simplify things14:36
lisitsyn but it doesn't simplify things you see14:36
lambday_lisitsyn: alright... so I am adding a wrapper :)14:37
wiking_yo :)14:45
-!- wiking_ is now known as wiking14:45
-!- wiking [~wiking@info2k1.hu] has quit [Changing host]14:46
-!- wiking [~wiking@huwico/staff/wiking] has joined #shogun14:46
-!- mode/#shogun [+o wiking] by ChanServ14:46
shogun-buildbotbuild #1416 of deb3 - modular_interfaces is complete: Failure [failed test python_modular]  Build details are at http://www.shogun-toolbox.org/buildbot/builders/deb3%20-%20modular_interfaces/builds/1416  blamelist: Soeren Sonnenburg <sonne@debian.org>15:05
gsomix_wiking, hey ho15:12
-!- gsomix_ is now known as gsomix15:12
@sonney2kgsomix, what does hey ho mean?15:12
@iglesiasgsee you later people15:17
@iglesiasglunch time!15:17
gsomixsonney2k, hm... I think just inspiring exclamation15:17
-!- iglesiasg [~Fernando@s83-179-44-135.cust.tele2.se] has quit [Quit: Leaving]15:17
@sonney2kshogun-buildbot, force build nightly_none --branch=develop15:20
shogun-buildbotbuild forced [ETA 23m31s]15:20
shogun-buildbotI'll give a shout when the build finishes15:20
gsomixsonney2k, something wrong wit "hey ho"? :)15:24
gsomix*with15:24
@sonney2kgsomix, I am just wondering if that is a good sign :)15:25
@sonney2klisitsyn, apparently strdup is not part of the standard and we have a compile error with cyg15:29
lisitsynsonney2k: strdup is not std?15:30
lisitsynthat's weird15:30
lisitsyn:D15:30
@sonney2klisitsyn, http://stackoverflow.com/questions/5573775/strdup-error-on-g-with-c0x15:31
@sonney2kit is now happening with our std=c++1115:31
lisitsynsonney2k: what to use instead? memcpy?15:31
@sonney2klisitsyn, I don't understand why it doesn't work it says in the bottom of the manpage15:32
@sonney2khttp://linux.die.net/man/3/strdup15:32
@sonney2kstrdup() conforms to SVr4, 4.3BSD, POSIX.1-200115:32
@sonney2kso wtf?15:32
shogun-buildbotbuild #416 of nightly_none is complete: Success [build successful]  Build details are at http://www.shogun-toolbox.org/buildbot/builders/nightly_none/builds/41615:40
@sonney2klisitsyn, I mean OK it is not ansi C but cygwin == posix so including string should give it to us or is this std=c+11 overriding this?15:40
lisitsynsonney2k: I haven't heard about it so no clue15:40
@sonney2kI guess that is the only explanation15:41
@sonney2klisitsyn, so what do we do? add some sg_strdup somewhere (where??)15:41
gsomixsonney2k, just replace by strcpy?15:47
gsomixsonney2k, btw now we use SGVector<char> as strings. but there is no null-terminate chars at end. it can cause errors in parse functions like atoi/strtol, isn't it?15:57
-!- dekun [7ae07e1e@gateway/web/freenode/ip.122.224.126.30] has quit [Quit: Page closed]16:00
lambday_lisitsyn: could you please have a look at the PR16:13
lambday_lisitsyn: few doxygen things fixed (did it earlier)16:14
lambday_lisitsyn: and added a unit-test that checks this lapack routine's accuracy with eigen3 (considering the matrix as a dense one)16:14
lisitsynlambday_: looks cool16:25
lambday_lisitsyn: thanks to you :)16:25
-!- shogun-notifier- [~irker@7nn.de] has quit [Quit: transmission timeout]16:37
-!- pickle27 [~Kevin@d67-193-243-174.home3.cgocable.net] has joined #shogun16:40
lambday_lisitsyn: gotta go16:42
lambday_ciao guys16:42
-!- lambday_ [67157d37@gateway/web/freenode/ip.103.21.125.55] has quit []16:42
pickle27sonney2k: lisitsyn around?16:43
-!- iglesiasg [~Fernando@s83-179-44-135.cust.tele2.se] has joined #shogun17:10
-!- mode/#shogun [+o iglesiasg] by ChanServ17:10
pickle27sonney2k: I'll be back on later but I wanted to update on my progress with r_modular17:21
pickle27sonney2k: it now builds but I had some issues with the install script17:22
pickle27I had to change lin 152 in .r-install.sh to remove the file ext from f before writing it17:23
pickle27otherwise it would look for shogun.so.so as it isn't expecting the ext17:23
pickle27I also think the the last arg is missing in the makefile as saverds is passed when calling the scipt for the staic interface but not for the modular one17:23
pickle27anyways after all these changes i get the following message when running library(shogun) in R17:24
pickle27Welcome! This is SHOGUN version 2.2.017:24
pickle27Error in namespaceExport(ns, exports) : undefined exports: shogun17:24
pickle27Error: package/namespace load failed for ‘shogun’17:24
@wikinglet's fix cmake  ;)18:00
-!- hushell [~hushell@c-24-21-169-136.hsd1.or.comcast.net] has quit [Read error: Connection reset by peer]18:54
-!- hushell [~hushell@c-24-21-169-136.hsd1.or.comcast.net] has joined #shogun19:08
lisitsynwiking: ooh so you are back19:13
lisitsyn?19:13
-!- shogun-notifier- [~irker@7nn.de] has joined #shogun19:18
shogun-notifier-shogun: Fernando Iglesias :develop * ce25859 / / (4 files): https://github.com/shogun-toolbox/shogun/commit/ce258590b70a01eac28553d410a4df26188bb1db19:18
shogun-notifier-shogun: Faster computation of LMNN objective19:18
shogun-notifier-shogun: Update LMNN solution in unit tests19:18
shogun-notifier-shogun: Fernando Iglesias :develop * cb21763 / / (4 files): https://github.com/shogun-toolbox/shogun/commit/cb21763fd15d0ebd992c3821b1fd60819a8a251d19:18
shogun-notifier-shogun: Merge pull request #1322 from iglesias/feature/lmnn19:18
shogun-notifier-shogun:19:18
shogun-notifier-shogun: Faster computation of LMNN objective19:18
shogun-buildbotbuild #1099 of cyg1 - libshogun is complete: Failure [failed compile]  Build details are at http://www.shogun-toolbox.org/buildbot/builders/cyg1%20-%20libshogun/builds/1099  blamelist: Fernando Iglesias <fernando.iglesiasg@gmail.com>19:31
@wikinglisitsyn: yeah19:31
votjakovrgsomix: hi! i seems like CSVFile_unittest.cc has memory leaks (when i've run valgrind on unit tests, it reported that to me)19:43
gsomixvotjakovr, yeah, really, thanks.19:49
votjakovrgsomix: You are welcome ;)19:51
gsomixnot memory leak - just invalid read. I think it because of I don't have zero-terminate char at end of strings :(19:51
gsomixok, I'll fix it19:53
votjakovrgsomix: good :)19:56
shogun-buildbotbuild #1417 of deb3 - modular_interfaces is complete: Failure [failed test python_modular]  Build details are at http://www.shogun-toolbox.org/buildbot/builders/deb3%20-%20modular_interfaces/builds/1417  blamelist: Fernando Iglesias <fernando.iglesiasg@gmail.com>20:02
-!- nube [~rho@49.244.127.129] has quit [Quit: Leaving.]20:10
shogun-buildbotbuild #1100 of cyg1 - libshogun is complete: Failure [failed compile]  Build details are at http://www.shogun-toolbox.org/buildbot/builders/cyg1%20-%20libshogun/builds/1100  blamelist: Fernando Iglesias <fernando.iglesiasg@gmail.com>20:13
-!- iglesiasg [~Fernando@s83-179-44-135.cust.tele2.se] has quit [Quit: Leaving]20:41
@sonney2kgsomix, what I did with strings is add a '\0' to the end of the string21:18
gsomixsonney2k, already fixed21:19
gsomixsonney2k, just added read_cstring method for reading zero-terminated strings21:20
shogun-notifier-shogun: lambday :develop * 7456300 / src/shogun/ (8 files): https://github.com/shogun-toolbox/shogun/commit/74563008f0aab20f98cefc4158da3e0b320415ee21:20
shogun-notifier-shogun: few doxygen warning fixed in log-det21:20
shogun-notifier-shogun: lambday :develop * 914b611 / / (3 files): https://github.com/shogun-toolbox/shogun/commit/914b611bb5773020a0d9c9c7613b6987817400be21:20
shogun-notifier-shogun: tridiagonal eigensolver lapack routine wrapper added21:20
shogun-notifier-shogun: Soeren Sonnenburg :develop * 6076c05 / / (11 files): https://github.com/shogun-toolbox/shogun/commit/6076c05d0e59bce65597cebc1f95fa78d1bdd85821:20
shogun-notifier-shogun: Merge pull request #1321 from lambday/feature/log_determinant21:20
shogun-notifier-shogun:21:20
shogun-notifier-shogun: lapack wrapper for tridiagonal eigensolver added21:20
gsomixsonney2k, need check unit-tests by valgrind - then send PR for fixing than "invalid read" error.21:20
shogun-buildbotbuild #1101 of cyg1 - libshogun is complete: Failure [failed configure]  Build details are at http://www.shogun-toolbox.org/buildbot/builders/cyg1%20-%20libshogun/builds/1101  blamelist: lambday <heavensdevil6909@gmail.com>21:24
shogun-buildbotbuild #1102 of cyg1 - libshogun is complete: Failure [failed compile]  Build details are at http://www.shogun-toolbox.org/buildbot/builders/cyg1%20-%20libshogun/builds/1102  blamelist: lambday <heavensdevil6909@gmail.com>, Soeren Sonnenburg <sonne@debian.org>21:36
@sonney2kpickle27, pong!21:40
pickle27sonney2k: hey!21:40
-!- travis-ci [~travis-ci@ec2-54-234-72-29.compute-1.amazonaws.com] has joined #shogun21:41
travis-ci[travis-ci] it's Fernando Iglesias's turn to pay the next round of drinks for the massacre he caused in shogun-toolbox/shogun: http://travis-ci.org/shogun-toolbox/shogun/builds/957981521:41
-!- travis-ci [~travis-ci@ec2-54-234-72-29.compute-1.amazonaws.com] has left #shogun []21:41
@sonney2kpickle27, we have 2 things here the r-static interface and the modular one21:42
@sonney2kpickle27, what did you have to change to get any of these working21:43
@sonney2kpickle27, IIRC r-static is working just fine - at least the tests on the buildbot do21:43
pickle27sonney2k: yes I didn't change anything for r_static21:43
pickle27I simply looked at how it was because it was working and then tried to replicate for r_modular21:44
@sonney2kpickle27, ok so what are the issues you found for r-modular again?21:45
* sonney2k compiles for r-moduar21:45
pickle27sonney2k: okay first issue was for r_modular the makefile passes less args to the install script compared to r_static21:46
pickle27the last arg $SAVERDS is not passed for r_modular21:46
@sonney2kpickle27, ok I fixed that21:46
@sonney2kpickle27, the other?21:46
pickle27I don't know fully what this affects21:46
@sonney2kpickle27, it is for creating the compiled Rdata file21:47
pickle27second is that for the library.dynam.load line21:47
pickle27we need to pass ${f%%.*} to stip the file ext rather than simply $f21:47
pickle27otherwise it looks for modshogun.so.so and can't find it21:47
pickle27sonney2k: however after that I had an import error from R so21:48
pickle27something is still wrong21:48
@sonney2kpickle27, but library(sg) works?21:50
pickle27sonney2k: yes21:50
@sonney2kpickle27, which R version do you have btw?21:52
pickle27sonney2k: 2.1521:52
@sonney2k> library(shogun)21:52
@sonney2kError in if (!res) stop(gettextf("This is R %s, package %s needs %s %s",  :21:52
@sonney2k  missing value where TRUE/FALSE needed21:52
@sonney2kthis is how it fails here btw21:52
pickle27sonney2k: hmm I've never had that one on my machine21:53
@sonney2kpickle27, 2.15.121:54
pickle27sonney2k: yeah I just opened mine I'm 2.15.221:54
-!- travis-ci [~travis-ci@ec2-54-234-72-29.compute-1.amazonaws.com] has joined #shogun22:09
travis-ci[travis-ci] it's Soeren Sonnenburg's turn to pay the next round of drinks for the massacre he caused in shogun-toolbox/shogun: http://travis-ci.org/shogun-toolbox/shogun/builds/958206222:09
-!- travis-ci [~travis-ci@ec2-54-234-72-29.compute-1.amazonaws.com] has left #shogun []22:09
shogun-buildbotbuild #1419 of deb3 - modular_interfaces is complete: Failure [failed test python_modular]  Build details are at http://www.shogun-toolbox.org/buildbot/builders/deb3%20-%20modular_interfaces/builds/1419  blamelist: lambday <heavensdevil6909@gmail.com>, Soeren Sonnenburg <sonne@debian.org>22:17
pickle27sonney2k: first it seems to me that the makefile in each interface folder is the same, is this so?22:25
pickle27and why is it so?22:25
lisitsynpickle27: yeah that's true22:26
pickle27lisitsyn: why isn't it just the makefile for that modular lib22:27
lisitsyncan't explain22:27
lisitsyn:D22:27
pickle27so if one of them needs to be changed then they all do?22:27
lisitsynpickle27: they are built from Makefile.template22:27
pickle27oh so they get built22:28
pickle27okay thats different then22:28
lisitsynno I mean Makefiles are distributed to each folder22:28
pickle27okay built wasn't a good word on my part22:28
pickle27they get generated is that correct?22:28
lisitsynon my part as well22:28
lisitsyn:D22:28
lisitsynpickle27: yes better word22:28
pickle27okay cool22:29
pickle27lisitsyn: I'm looking into changing our ruby modular to use nmatrix rather than narray22:29
lisitsynpickle27: no clue about that22:30
lisitsynwhat's pro/cons?22:30
pickle27lisitsyn: nmatrix is bascially just the new narray22:31
pickle27lisitsyn: its like a fork but doesn't look like anyone is working on narray anymore22:31
lisitsynI see22:31
pickle27and there is the whole sciruby group behind nmatrix22:31
gsomixpickle27, sciruby? good idea I think22:40
pickle27gsomix: yes22:40
pickle27gsomix: I'm actually working on it right now - seems not too bad because nmatrix is based on narray so the api is bascially the same22:41
gsomixpickle27, I can help a little if it's needed.22:41
-!- iglesiasg [~Fernando@s83-179-44-135.cust.tele2.se] has joined #shogun22:41
-!- mode/#shogun [+o iglesiasg] by ChanServ22:41
pickle27gsomix: okay awesome I'll see how far I get here22:41
gsomixsonney2k, iglesiasg hey guys I sent small PR, review is needed. https://github.com/shogun-toolbox/shogun/pull/132322:47
gsomixvotjakovr, done with invalid read22:47
votjakovrgsomix: thanks :)22:48
@iglesiasgsonney2k: let's see if sonney2k can have a look soon since he is the one revising your stuff22:51
@iglesiasggsomix: ^ that was for you, sorry :)22:51
@iglesiasgotherwise I will have a look soon22:51
gsomixiglesiasg, ok, thanks22:51
@sonney2kgsomix, only comment I have is maybe use an enum for the order FORTRAN_ORDER  / C_ORDER23:05
gsomixsonney2k, ok!23:07
gsomixsonney2k, I'll do it tomorrow, ok?23:08
@sonney2kgsomix, sure23:08
gsomixneed to sleep a little23:08
gsomixgood night guys23:08
@sonney2kgsomix, so you would have a setter23:08
@sonney2klike set_matrix_order(enum ...)23:08
@sonney2kwith fortran as default23:08
gsomixsonney2k, aha, got it23:08
@sonney2klisitsyn, do you remember why we named the modular interfaces for shogun modshogun?23:09
@sonney2kand not shogun?23:10
lisitsynsonney2k: some name clash23:10
@sonney2klisitsyn, then we should do it consistently across r/java/...23:11
lisitsynsonney2k: what is the name in java?23:11
@sonney2kpickle27, then just add support for that in interfaces/ruby/swig_typemaps.i23:12
pickle27sonney2k: yeah Im looking around at that right now23:12
pickle27although I actually can23:12
pickle27oops23:12
pickle27can't seem to get nmatrix (the new ruby linalg) to even install at the moment23:13
@sonney2klisitsyn, shogun.jar ...23:13
pickle27so might be a bit premature but in a few months I think it will deffs be the right call23:13
pickle27I'll see what I can do now though23:13
pickle27sonney2k: also are we going to c++11? saw some talk about it but wasn;t paying attention23:16
pickle27can I start using c11 stuff in shogun now?23:17
@sonney2kpickle27, only optionally and we would need to add a configure test for each function you use23:18
pickle27sonney2k: okay i will avoid for now then23:18
@iglesiasgpickle27: I am with you in the go idea :)23:21
@iglesiasgsonney2k: is it crazy to even consider a new interface?23:21
@iglesiasgbrb23:22
@sonney2kiglesiasg, which language?23:27
pickle27sonney2k: we were think of Go23:27
@sonney2kpickle27, one more interfaces doesn't make a big difference23:29
@sonney2kpickle27, if swig is supporting it well all that is needed are typemaps23:29
pickle27sonney2k: swig does support it23:29
@sonney2kpickle27, 'well'?23:29
@sonney2kor like R?23:29
pickle27sonney2k: haha unsure..23:29
@sonney2kif well it is IMHO very easy to add a new language23:30
pickle27sonney2k: my gut tells me better than R because Go is a "cleaner" language than R23:30
@sonney2kjust a few days work if one is not familiar with GO's C interfacing23:30
@sonney2kpickle27, there is no language that is messier than R IMHO23:30
pickle27sonney2k: yeah I'm not a big fan of what I've seen so far23:31
pickle27the only neat thing is how easy it is to call c from R23:31
pickle27otherwise not a fan23:31
pickle27NumPy is king of high level numerical programming in my mind23:32
pickle27and I've actually grown quite fond of eigen323:32
lisitsynyou want one more interface?23:32
lisitsyn:D23:32
pickle27bit of full disclosure the company Im working for next year is ruby and Go so I'm trying to learn the langquages a bit and I want shogun at my disposal lol23:33
lisitsynpickle27: I am curious how do they use Go23:34
pickle27lisitsyn: don't know much about how they use it really23:34
pickle27lisitsyn: for web severs etc I think23:34
pickle27maybe some of their db stuff23:34
lisitsynpickle27: I guess something with lightweight threads23:34
lisitsynwell there are now23:35
lisitsynerlang23:35
lisitsynjava with akka23:35
lisitsynand go23:35
lisitsynI don't know anything else with mature concurrency stuff23:35
pickle27I haven't done a ton of threading stuff but I've kind of gathered that the way go does concurency is why a lot of people are moving to it23:36
lisitsynI do some concurrency at my job23:37
lisitsynbasically a lot of trees with message passing23:37
lisitsynin our tasks everything is interdependent and it is basically brute force :D23:38
lisitsynbut with message passing so it scales23:38
@sonney2kpickle27, btw when you do libray(shogun) in R - and you get that failure you should still be able to use all of shoguns stuff23:39
@sonney2kpickle27, just try x=GaussianKernel()23:39
pickle27really - sweet!23:39
shogun-buildbotbuild #1418 of deb3 - modular_interfaces is complete: Failure [failed test python_modular]  Build details are at http://www.shogun-toolbox.org/buildbot/builders/deb3%20-%20modular_interfaces/builds/1418  blamelist: Fernando Iglesias <fernando.iglesiasg@gmail.com>23:41
pickle27sonney2k: hmm it isn't working for me23:41
@sonney2kpickle27, what are you getting?23:42
pickle27well I can run x=GaussianKernel()23:42
pickle27but I can't run my example23:42
pickle27says Error in RealFeatures(X) : could not find function "f"23:43
pickle27sonney2k: although just entering RealFeatures gives me something23:43
pickle27this might be a my example thing23:43
@sonney2kpickle27, try to run some example from the examples folder23:44
pickle27hmm same thing on classifier_lda_modular example23:45
@sonney2kpickle27, try the simplest possible thing e.g. gaussiankernel23:45
pickle27sonney2k: same error each time we try and create a RealFeatures23:47
@sonney2kpickle27, some stuff works however:23:50
@sonney2kx=GaussianKernel()23:50
@sonney2k> x$get_width()23:50
@sonney2k[1] 123:50
pickle27sonney2k: yeah some stuff is working, just something is off with the RealFeatures23:50
pickle27which almost all the examples use23:50
@sonney2k> x=matrix(c(1,2,3,4,5,6),2,3)23:51
@sonney2k> x23:51
@sonney2k     [,1] [,2] [,3]23:51
@sonney2k[1,]    1    3    523:51
@sonney2k[2,]    2    4    623:51
@sonney2k> y=RealFeatures(x)23:51
@sonney2kError in RealFeatures(x) : could not find function "f"23:51
@sonney2kyeah seems like23:51
@sonney2kpickle27, might be a general typemap thing23:52
@sonney2kz<-BinaryLabels(c(-1,1))23:52
@sonney2kError in BinaryLabels(c(-1, 1)) : could not find function "f"23:52
@sonney2ksame error23:52
pickle27yeah23:52
@sonney2kpickle27, we changed sooo damn much since stuff worked the last time for R modular23:54
@sonney2kmight as well be that typemaps don't even use SGVector23:54
* sonney2k checks23:54
shogun-notifier-shogun: Soeren Sonnenburg :develop * 5812e0d / src/.r-install.sh,src/Makefile.template: https://github.com/shogun-toolbox/shogun/commit/5812e0d9af7931b3152977aae3226c291066d99e23:55
shogun-notifier-shogun: rename shogun -> modshogun for R and add some fixes23:55
pickle27yeah23:55
pickle27main reason I'm working on an R example is because it seems a lot of groups who work on this stuff use R23:56
pickle27and I want them to be able to find and use us after this23:56
pickle27because we'll have essentially the best unified collection of ICA techniques based off AJD of anyone23:56
@sonney2kpickle27, what shall I say23:57
@sonney2kpickle27, it works for all languages except R23:57
pickle27yeah - also23:57
pickle27I didn't realize how rough R was for wrapping until these past few days23:58
@sonney2kpickle27, typemaps exist but look buggy (will lead to crashes)23:59
@sonney2kpickle27, but biggest issue is to figure out why this happens23:59
--- Log closed Mon Jul 29 00:00:12 2013

Generated by irclog2html.py 2.10.0 by Marius Gedminas - find it at mg.pov.lt!