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/
ib07 has quit [Quit: No Ping reply in 180 seconds.]
ib07 has joined #mlpack
< zoq>
GauravGhati[m]: Build mlpack with -DCMAKE_EXPORT_COMPILE_COMMANDS=ON that will generate a compiler_commands.json file that we can use to tell pvs how to build certain files.
< zoq>
from within the build folder run - pvs-studio-analyzer analyze -o project.log
< zoq>
that will use the compiler_commands.json file generate before.
< zoq>
the last step is to convert the output into something readable
< zoq>
plog-converter -a GA:1,2 -t tasklist -o build/project.tasks build/project.log
< zoq>
open-source projects can get a free license
< zoq>
so on your local system you can eit her test out the trail version
< zoq>
Happy holiday season everyone.
< AakashkaushikGit>
Merry Christmas !
< AakashkaushikGit>
Hey @zoq btw why have we removed delta and outputParameter objects and also adding the word "Type" after the layer names is that so when you `typedef` them they are different ?
< zoq[m]>
The delta and output parameter is part of the base class, so I figured we can remove them from the actual layer implementation to make it easier.
< zoq[m]>
Also you are right about the typedef.
< GauravGhati[m]>
Thanks a lot zoq.
< GauravGhati[m]>
And Merry Christmas you all!
< AakashkaushikGit>
Hey @zoq, thanks for the quick reply, I just have one more doubt we are going to be adding all the changed layer tests in the `ann_layer_test.hpp` so should we include each separate `.hpp` file or create something similar to layer_types.hpp which simply imports all the layers and then we can just import that file instead of importing each layer for testing
< zoq[m]>
A consolidated header file sounds like a good idea.
< AakashkaushikGit>
Awesome, will do that in the `layer_types.hpp` file itself. I think that's ok ?