rcurtin_irc changed the topic of #mlpack to: mlpack: a scalable machine learning library (https://www.mlpack.org/) -- channel logs: https://libera.irclog.whitequark.org/mlpack -- NOTE: messages sent here might not be seen by bridged users on matrix, gitter, or slack
aakashi2001 has joined #mlpack
aakashi2001 has quit [Ping timeout: 245 seconds]
_slack_mlpack_37 has quit [Quit: Bridge terminating on SIGTERM]
_slack_mlpack_U7 has quit [Quit: Bridge terminating on SIGTERM]
_slack_mlpack_31 has quit [Quit: Bridge terminating on SIGTERM]
_slack_mlpack_13 has quit [Quit: Bridge terminating on SIGTERM]
_slack_mlpack_U0 has quit [Quit: Bridge terminating on SIGTERM]
_slack_mlpack_27 has quit [Quit: Bridge terminating on SIGTERM]
_slack_mlpack_U4 has quit [Quit: Bridge terminating on SIGTERM]
_slack_mlpack_24 has quit [Quit: Bridge terminating on SIGTERM]
_slack_mlpack_28 has quit [Quit: Bridge terminating on SIGTERM]
_slack_mlpack_22 has quit [Quit: Bridge terminating on SIGTERM]
_slack_mlpack_16 has quit [Quit: Bridge terminating on SIGTERM]
KumarArnav[m] has quit [Quit: Bridge terminating on SIGTERM]
_slack_mlpack_10 has quit [Quit: Bridge terminating on SIGTERM]
_slack_mlpack_19 has quit [Quit: Bridge terminating on SIGTERM]
_slack_mlpack_17 has quit [Quit: Bridge terminating on SIGTERM]
jonpsy[m] has quit [Quit: Bridge terminating on SIGTERM]
_slack_mlpack_14 has quit [Quit: Bridge terminating on SIGTERM]
Prometheus[m] has quit [Quit: Bridge terminating on SIGTERM]
_slack_mlpack_25 has quit [Quit: Bridge terminating on SIGTERM]
ShahAnwaarKhalid has quit [Quit: Bridge terminating on SIGTERM]
MohomedShalik[m] has quit [Quit: Bridge terminating on SIGTERM]
huberspot[m] has quit [Quit: Bridge terminating on SIGTERM]
RishabhGarg108[m has quit [Quit: Bridge terminating on SIGTERM]
ZanHuang[m] has quit [Quit: Bridge terminating on SIGTERM]
jeffin143[m] has quit [Quit: Bridge terminating on SIGTERM]
shrit[m] has quit [Quit: Bridge terminating on SIGTERM]
ABHINAVANAND[m] has quit [Quit: Bridge terminating on SIGTERM]
GauravTirodkar[m has quit [Quit: Bridge terminating on SIGTERM]
KshitijAggarwal[ has quit [Quit: Bridge terminating on SIGTERM]
MatheusAlcntaraS has quit [Quit: Bridge terminating on SIGTERM]
TathagataRaha[m] has quit [Quit: Bridge terminating on SIGTERM]
DavidportlouisDa has quit [Quit: Bridge terminating on SIGTERM]
FranchisNSaikia[ has quit [Quit: Bridge terminating on SIGTERM]
SiddhantJain[m] has quit [Quit: Bridge terminating on SIGTERM]
AmanKashyap[m] has quit [Quit: Bridge terminating on SIGTERM]
DillonKipke[m] has quit [Quit: Bridge terminating on SIGTERM]
Aakash-kaushikAa has quit [Quit: Bridge terminating on SIGTERM]
GaborBakos[m] has quit [Quit: Bridge terminating on SIGTERM]
SaiVamsi[m] has quit [Quit: Bridge terminating on SIGTERM]
ShivamShaurya[m] has quit [Quit: Bridge terminating on SIGTERM]
Kaushalc64[m] has quit [Quit: Bridge terminating on SIGTERM]
SoumyadipSarkar[ has quit [Quit: Bridge terminating on SIGTERM]
mlpack-inviter[m has quit [Quit: Bridge terminating on SIGTERM]
ManishKausikH[m] has quit [Quit: Bridge terminating on SIGTERM]
Gauravkumar[m] has quit [Quit: Bridge terminating on SIGTERM]
NippunSharmaNipp has quit [Quit: Bridge terminating on SIGTERM]
fieryblade[m] has quit [Quit: Bridge terminating on SIGTERM]
LokeshJawale[m] has quit [Quit: Bridge terminating on SIGTERM]
AyushKumarLavani has quit [Quit: Bridge terminating on SIGTERM]
DivyanshKumar[m] has quit [Quit: Bridge terminating on SIGTERM]
AlexNguyen[m] has quit [Quit: Bridge terminating on SIGTERM]
zoq[m]1 has quit [Quit: Bridge terminating on SIGTERM]
ChaithanyaNaik[m has quit [Quit: Bridge terminating on SIGTERM]
sailor[m] has quit [Quit: Bridge terminating on SIGTERM]
HemalMamtora[m] has quit [Quit: Bridge terminating on SIGTERM]
sdev_7211[m] has quit [Quit: Bridge terminating on SIGTERM]
SergioMoralesE[m has quit [Quit: Bridge terminating on SIGTERM]
AyushSingh[m] has quit [Quit: Bridge terminating on SIGTERM]
TrinhNgo[m] has quit [Quit: Bridge terminating on SIGTERM]
swaingotnochill[ has quit [Quit: Bridge terminating on SIGTERM]
ShivamNayak[m] has quit [Quit: Bridge terminating on SIGTERM]
abernauer[m] has quit [Quit: Bridge terminating on SIGTERM]
VedantaJha[m] has quit [Quit: Bridge terminating on SIGTERM]
AbhinavGudipati[ has quit [Quit: Bridge terminating on SIGTERM]
heisenbuugGopiMT has quit [Quit: Bridge terminating on SIGTERM]
Shadow3049[m] has quit [Quit: Bridge terminating on SIGTERM]
VarunGupta[m] has quit [Quit: Bridge terminating on SIGTERM]
ronakypatel[m] has quit [Quit: Bridge terminating on SIGTERM]
RishabhGarg108Ri has quit [Quit: Bridge terminating on SIGTERM]
prasad-dashprasa has quit [Quit: Bridge terminating on SIGTERM]
M074AABGKS has quit [Quit: Bridge terminating on SIGTERM]
Pushker[m] has quit [Quit: Bridge terminating on SIGTERM]
bisakh[m] has quit [Quit: Bridge terminating on SIGTERM]
JatoJoseph[m] has quit [Quit: Bridge terminating on SIGTERM]
KrishnaSashank[m has quit [Quit: Bridge terminating on SIGTERM]
swaingotnochills has quit [Quit: Bridge terminating on SIGTERM]
GopiManoharTatir has quit [Quit: Bridge terminating on SIGTERM]
AbhishekNimje[m] has quit [Quit: Bridge terminating on SIGTERM]
RudraPatil[m] has quit [Quit: Bridge terminating on SIGTERM]
rcurtin_matrixor has quit [Quit: Bridge terminating on SIGTERM]
AbdullahKhilji[m has quit [Quit: Bridge terminating on SIGTERM]
HarshVardhanKuma has quit [Quit: Bridge terminating on SIGTERM]
jjb[m] has quit [Quit: Bridge terminating on SIGTERM]
MayankRaj[m] has quit [Quit: Bridge terminating on SIGTERM]
ryan[m]1 has quit [Quit: Bridge terminating on SIGTERM]
fazamuhammad[m] has quit [Quit: Bridge terminating on SIGTERM]
AbhishekMishra[m has quit [Quit: Bridge terminating on SIGTERM]
Gulshan[m] has quit [Quit: Bridge terminating on SIGTERM]
Cadair has quit [Quit: Bridge terminating on SIGTERM]
zoq[m] has quit [Quit: Bridge terminating on SIGTERM]
NitikJain[m] has quit [Quit: Bridge terminating on SIGTERM]
ABoodhayanaSVish has quit [Quit: Bridge terminating on SIGTERM]
EricTroupeTester has quit [Quit: Bridge terminating on SIGTERM]
HARSHCHAUHAN[m] has quit [Quit: Bridge terminating on SIGTERM]
Gman[m] has quit [Quit: Bridge terminating on SIGTERM]
ArunavShandeelya has quit [Quit: Bridge terminating on SIGTERM]
AyushiJain[m] has quit [Quit: Bridge terminating on SIGTERM]
say4n[m] has quit [Quit: Bridge terminating on SIGTERM]
M068AABMUC has quit [Quit: Bridge terminating on SIGTERM]
RishabhGoel[m] has quit [Quit: Bridge terminating on SIGTERM]
HrithikNambiar[m has quit [Quit: Bridge terminating on SIGTERM]
SlackIntegration has quit [Quit: Bridge terminating on SIGTERM]
halfy has quit [Quit: Bridge terminating on SIGTERM]
rcurtin[m] has quit [Quit: Bridge terminating on SIGTERM]
jonathanplatkiew has quit [Quit: Bridge terminating on SIGTERM]
kartikdutt18kart has quit [Quit: Bridge terminating on SIGTERM]
Amankumar[m] has quit [Quit: Bridge terminating on SIGTERM]
_slack_mlpack_34 has quit [Quit: Bridge terminating on SIGTERM]
PranshuSrivastav has quit [Quit: Bridge terminating on SIGTERM]
AvikantSrivastav has quit [Quit: Bridge terminating on SIGTERM]
Saksham[m] has quit [Quit: Bridge terminating on SIGTERM]
OleksandrNikolsk has quit [Quit: Bridge terminating on SIGTERM]
LolitaNazarov[m] has quit [Quit: Bridge terminating on SIGTERM]
gitter-badgerThe has quit [Quit: Bridge terminating on SIGTERM]
M7Ain7Soph77Ain7 has quit [Quit: Bridge terminating on SIGTERM]
GauravGhati[m] has quit [Quit: Bridge terminating on SIGTERM]
DirkEddelbuettel has quit [Quit: Bridge terminating on SIGTERM]
dkipke[m] has quit [Quit: Bridge terminating on SIGTERM]
say4n[m] has joined #mlpack
Cadair has joined #mlpack
ServerStatsDisco has joined #mlpack
sdev_7211[m] has joined #mlpack
SlackIntegration has joined #mlpack
MatrixTravelerbo has joined #mlpack
psydroid has joined #mlpack
halfy has joined #mlpack
NamanJain[m] has joined #mlpack
DavidportlouisDa has joined #mlpack
rcurtin[m] has joined #mlpack
AbdullahKhilji[m has joined #mlpack
ChaithanyaNaik[m has joined #mlpack
TrinhNgo[m] has joined #mlpack
JatoJoseph[m] has joined #mlpack
KumarArnav[m] has joined #mlpack
NippunSharmaNipp has joined #mlpack
RishabhGarg108Ri has joined #mlpack
gitter-badgerThe has joined #mlpack
GauravTirodkar[m has joined #mlpack
Aakash-kaushikAa has joined #mlpack
HarshVardhanKuma has joined #mlpack
DivyanshKumar[m] has joined #mlpack
ZanHuang[m] has joined #mlpack
M7Ain7Soph77Ain7 has joined #mlpack
shrit[m] has joined #mlpack
kartikdutt18kart has joined #mlpack
AbhishekNimje[m] has joined #mlpack
AbhinavGudipati[ has joined #mlpack
RishabhGarg108[m has joined #mlpack
LolitaNazarov[m] has joined #mlpack
RudraPatil[m] has joined #mlpack
EricTroupeTester has joined #mlpack
DirkEddelbuettel has joined #mlpack
_slack_mlpack_U0 has joined #mlpack
heisenbuugGopiMT has joined #mlpack
jonpsy[m] has joined #mlpack
ShivamShaurya[m] has joined #mlpack
prasad-dashprasa has joined #mlpack
Prometheus[m] has joined #mlpack
zoq[m] has joined #mlpack
RishabhGoel[m] has joined #mlpack
AyushSingh[m] has joined #mlpack
ronakypatel[m] has joined #mlpack
dkipke[m] has joined #mlpack
Gulshan[m] has joined #mlpack
ShahAnwaarKhalid has joined #mlpack
ABHINAVANAND[m] has joined #mlpack
KrishnaSashank[m has joined #mlpack
AyushKumarLavani has joined #mlpack
AmanKashyap[m] has joined #mlpack
AbhishekMishra[m has joined #mlpack
jjb[m] has joined #mlpack
LokeshJawale[m] has joined #mlpack
VedantaJha[m] has joined #mlpack
ABoodhayanaSVish has joined #mlpack
FranchisNSaikia[ has joined #mlpack
HARSHCHAUHAN[m] has joined #mlpack
SaiVamsi[m] has joined #mlpack
AlexNguyen[m] has joined #mlpack
TathagataRaha[m] has joined #mlpack
ManishKausikH[m] has joined #mlpack
HrithikNambiar[m has joined #mlpack
GopiManoharTatir has joined #mlpack
KshitijAggarwal[ has joined #mlpack
DillonKipke[m] has joined #mlpack
AvikantSrivastav has joined #mlpack
Gauravkumar[m] has joined #mlpack
SiddhantJain[m] has joined #mlpack
MohomedShalik[m] has joined #mlpack
_slack_mlpack_U4 has joined #mlpack
SoumyadipSarkar[ has joined #mlpack
NitikJain[m] has joined #mlpack
Kaushalc64[m] has joined #mlpack
MatheusAlcntaraS has joined #mlpack
OleksandrNikolsk has joined #mlpack
jonathanplatkiew has joined #mlpack
swaingotnochill[ has joined #mlpack
SergioMoralesE[m has joined #mlpack
HemalMamtora[m] has joined #mlpack
VarunGupta[m] has joined #mlpack
Amankumar[m] has joined #mlpack
GaborBakos[m] has joined #mlpack
MayankRaj[m] has joined #mlpack
Shadow3049[m] has joined #mlpack
swaingotnochills has joined #mlpack
mlpack-inviter[m has joined #mlpack
GauravGhati[m] has joined #mlpack
zoq[m]1 has joined #mlpack
rcurtin_matrixor has joined #mlpack
fazamuhammad[m] has joined #mlpack
bisakh[m] has joined #mlpack
Pushker[m] has joined #mlpack
sailor[m] has joined #mlpack
abernauer[m] has joined #mlpack
Saksham[m] has joined #mlpack
ShivamNayak[m] has joined #mlpack
ArunavShandeelya has joined #mlpack
jeffin143[m] has joined #mlpack
ryan[m]1 has joined #mlpack
fieryblade[m] has joined #mlpack
Gman[m] has joined #mlpack
PranshuSrivastav has joined #mlpack
AyushiJain[m] has joined #mlpack
huberspot[m] has joined #mlpack
082AAB7FQ has joined #mlpack
078AAEC48 has joined #mlpack
082AAB7FQ has quit [Client Quit]
068AADD97 has joined #mlpack
076AADG9Z has joined #mlpack
068AADD97 has quit [Client Quit]
082AAB7FS has joined #mlpack
078AAEC5B has joined #mlpack
079AADL2L has joined #mlpack
030AABC9W has joined #mlpack
_slack_mlpack_U7 has joined #mlpack
082AAB7FY has joined #mlpack
082AAB7FY has quit [Client Quit]
078AAEC5G has joined #mlpack
030AABC94 has joined #mlpack
079AADL2P has joined #mlpack
082AAB7F0 has joined #mlpack
082AAB7F0 has quit [Client Quit]
078AAEC5I has joined #mlpack
_slack_mlpack_10 has joined #mlpack
078AAEC5J has joined #mlpack
030AABC96 has joined #mlpack
079AADL2R has joined #mlpack
077AADP1Z has joined #mlpack
078AAEC5J has quit [Client Quit]
082AAB7F6 has joined #mlpack
_slack_mlpack_13 has joined #mlpack
078AAEC5Q has joined #mlpack
078AAEC50 has joined #mlpack
078AAEC50 has quit [Client Quit]
030AABDAJ has joined #mlpack
082AAB7GH has joined #mlpack
082AAB7GH has quit [Client Quit]
078AAEC57 has joined #mlpack
068AADEAU has joined #mlpack
076AADHAT has joined #mlpack
068AADEAU has quit [Client Quit]
082AAB7GT has joined #mlpack
079AADL3E has joined #mlpack
078AAEC6D has joined #mlpack
_slack_mlpack_19 has joined #mlpack
030AABDAM has joined #mlpack
_slack_mlpack_16 has joined #mlpack
079AADL3E has quit [Client Quit]
030AABDAM has quit [Client Quit]
_slack_mlpack_22 has joined #mlpack
_slack_mlpack_25 has joined #mlpack
_slack_mlpack_28 has joined #mlpack
082AAB7HW has joined #mlpack
078AAEC7Q has joined #mlpack
078AAEC7Q has quit [Client Quit]
_slack_mlpack_31 has joined #mlpack
082AAB7H6 has joined #mlpack
082AAB7H6 has quit [Client Quit]
078AAEC7V has joined #mlpack
_slack_mlpack_34 has joined #mlpack
_slack_mlpack_37 has joined #mlpack
<NamanJain[m]> Hi! I'm getting a ton of undefined reference errors after compiling covariance computation code. I posted issue on <https://stackoverflow.com/questions/68844764/mlpack-compile-time-issue-linux|stackoverflow>. Kindly help me to fix it.
<shrit[m]> Naman Jain: You need to link with aramdillo and mlpack library.
<shrit[m]> you need to add `-lmlpack -larmadillo -L/path/to/mlpack/lib/ -L/path/to/armadillo/lib` to your compiler command
aakashi2001 has joined #mlpack
aakashi2001 has quit [Remote host closed the connection]
aakashi2001 has joined #mlpack
aakashi2001 has quit [Ping timeout: 252 seconds]
Poozi has joined #mlpack
<jonpsy[m]> rcurtin: I was hoping you'd be able a meet @ 10 PM IST?
<jonpsy[m]> * rcurtin: I was hoping you'd be able to attend a meet @ 10 PM IST?
<rcurtin[m]> that's right over lunch for me... I'm not sure if I'll be available
<rcurtin[m]> some friends are in town so we were going to get lunch, but, I don't know when they are going to be awake ... anyway, I'll try and join... what is the meeting about? 😃
<jonpsy[m]> so i really loved the way you parallelized code using SIMD
<jonpsy[m]> i'm trying to do something similar
<jonpsy[m]> like dividing into 4 blocks, and in each iteration update all four
<rcurtin[m]> yeah, basically that strategy is just a "trick" to try and get the compiler to emit SIMD instructions
<jonpsy[m]> yeah, i wanted to know a little on how i'd apply in my case
<jonpsy[m]> <rcurtin[m]> "some friends are in town so we w" <- thats fyn, we can do it later when you're free?
<rcurtin[m]> are you sure you need to? If you can express things as Armadillo operations, then it's likely that the Armadillo code will handle this type of thing under the hood
<ABHINAVANAND[m]> zoq Is there a way to reduce the number of epoch in group norm gradient test. It will help me in debugging.
<jonpsy[m]> rcurtin[m]: I've thought about it. The orig code used "torch.expand" and lot of redundant stuff.
<jonpsy[m]> but we could save all those if we do it smartly in a loop
<rcurtin[m]> so, my first suggestion would be to determine whether or not this is actually a bottleneck that uses a significant amount of computation time... if not, then it's probably not worthwhile to have the extra code for the SIMD loop
<rcurtin[m]> second, maybe can you use `.transform()` or something like this? if we *can* push SIMD logic down into Armadillo, we should
<rcurtin[m]> third, it really depends on the type of loop. if I am doing this:... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/31a91bd5c44aea54f227a14cb401962fc53ee559)
<rcurtin[m]> the key here is the dependencies of each iteration... in the first loop, every iteration depends on the previous iteration's output and thus it can't be parallelized. in the second loop, every iteration is independent and so the compiler can automatically apply SIMD (and I think it typically will)
<rcurtin[m]> so you only need to do the "crazy" stuff if your loop is like the first one :)
<jonpsy[m]> seeing column wise, we can cut it into 3 chunks. chunkA ```[ [1, 2], [3, 4] ] ``` chunk B ```[[5, 6], [7, 8]]``` so on for chunkC
<jonpsy[m]> are we clear till here?
<rcurtin[m]> okay, I follow
<jonpsy[m]> we already know ```chunkSize```
<jonpsy[m]> now each chunk, would be multipled by a vector ```w```, its dimension is same as dim of each vector in chunk
<jonpsy[m]> so here chunkA has two vecs, ```[1, 2]``` and ```[3, 4]```, so ```w``` would be some ```arma::randn(size(2))```
<jonpsy[m]> * so here chunkA has two vecs each of dim 2, `[1, 2]` and `[3, 4]`, so `w` would be some `arma::randn(size(2))`
<rcurtin[m]> okay, I see
<jonpsy[m]> hm, so `w` multiplies with each vec of chunkA
<jonpsy[m]> giving us, a vec of dim = ```numVecPerChunk```
<jonpsy[m]> ``` w_A * chunkA ```
<zoq[m]> <ABHINAVANAND[m]> "zoq Is there a way to reduce th" <- https://github.com/mlpack/mlpack/blob/master/src/mlpack/tests/ann_test_tools.hpp#L197 you can adjust the for loop.
<rcurtin[m]> sure, I see, and you'll have a bunch of these chunks and a bunch of `w`s and they all need to be multiplied
<jonpsy[m]> rcurtin[m]: yes, for each chunk there is a unique ```w```
<jonpsy[m]> that ```w``` multipled with ```chunk``` gives us a vec, which we will append to ```res```
<rcurtin[m]> can you express this as a matrix multiplication by reshaping the input array and grouping the `w`s into a matrix?
<rcurtin[m]> the reason I suggest this is that while you can go to some lengths to get SIMD instructions and make things fast, the BLAS primitives like matrix-matrix multiplication are blindingly fast
<rcurtin[m]> so if you can structure things such that they can be expressed as a BLAS primitive, that is the most likely route to making things fast
<rcurtin[m]> (and as a bonus, the code remains clean because we can just do this as a couple Armadillo calls)
<jonpsy[m]> > <@jonpsy:matrix.org> ``` w_A * chunkA ```... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/dd8e35dccb5441156b8927dff73fe31f6a60581f)
<rcurtin[m]> yeah, can you do it *all* in batch? so, e.g., reshape `Q` such that each chunk corresponds to a single column, and then multiply directly with the `W` matrix?
<rcurtin[m]> that is maybe not very satisfying because you don't get to play with SIMD instructions, but, if you can do that, the OpenBLAS matrix multiplication code is tuned like crazy and will almost certainly be faster than any other strategy, especially because 1 NxNxN matrix multiplication will tend to be faster than N vector-matrix multiplications of size 1xNxN
<jonpsy[m]> rcurtin[m]: this could work...
<rcurtin[m]> 👍️ yeah, I like optimizing code at a really low level, but most of the time at least with matrix operations, if you can manage to express the problem as a BLAS primitive then OpenBLAS will blow away anything handwritten
halfy_ has joined #mlpack
<halfy_> (testing the bridge quickly)
<NamanJain[m]> <shrit[m]> "you need to add `-lmlpack -larm" <- Thanks, @shrit! It works. I have included only -lmlpack -larmadillo
<jonpsy[m]> say4n: zoq you guys free?
<zoq[m]> Still 5 minutes right?
<jonpsy[m]> yep, jst confirming if anyobody wanted to opt out
<zoq[m]> we are using meet right?
<jonpsy[m]> lets use zoom ?
<zoq[m]> you send a meet link
<zoq[m]> So I would stick to that.
<jonpsy[m]> that was only for reminder xD
<jonpsy[m]> anyway sure
<shrit[m]> zoq: I am happy to open a new pull request and Change the class name to `DiagonalGaussianDist` to `DiagonalGaussianDistType<>`, and then redefine `DiagonalGaussianDist` as using armadillo internaly. It is true that is policy should be easier to review and will not require to modify half of the code base. If you prefer this, I will open a new pull request and close the current one.
aakashi2001 has joined #mlpack
<shrit[m]> * zoq: I am happy to open a new pull request and Change the class name to `DiagonalGaussianDist` to `DiagonalGaussianDistType<>`, and then redefine `DiagonalGaussianDist` as using armadillo internally. It is true that this policy should be easier to review and will not require to modify half of the codebase. If you prefer this, I will open a new pull request and close the current one.
aakashi2001 has quit [Ping timeout: 248 seconds]
<zoq[m]> I just wanted to keep it simple to use (we discussed some of it here https://github.com/mlpack/mlpack/issues/2524) by adding a template parameter I think instead of making it easier to use it is actually more complicated.
<PranshuSrivastav> > You are trying to link statically with armadillo, which is dynamic on your machine
<PranshuSrivastav> Hey I don't really understand this, could you please explain it to me in simpler terms..
<shrit[m]> zoq: Agreed, I did no remember that note when I opened the pull request
<shrit[m]> The library contains a set of functions. When it is created, it is created either statically or dynamically according to your configuration, for more information please have a look here https://stackoverflow.com/questions/1993390/static-linking-vs-dynamic-linking
<shrit[m]> In your case, mlpack is built statically, but armadillo is built dynamically which is not possible to combine both of these together
Poozi has quit [Quit: Client closed]
halfy_ has quit [Remote host closed the connection]