Hello Marcus, > That is correct, if you like to work on it, please feel free.
Yes sure, I intend to have atleast a basic PSO working before the proposal submission deadline; it will help get down the details better. >> Glad to know that, I'll also look into the idea of using lambdas, and >> see if I can come up with a comparison between the two. > > Sounds good, that might be a good point to include in the application. Thanks, I'll keep that in mind while writing the application. > Google recommends, google docs, which makes it super easy to provide feedback. Yeah, that's easier to handle in most cases. I also tried disabling the python bindings, the build process seems to be much smoother than before. I was thinking of building the mlpack_test cli executable to quickly add and run tests after building; that, however, requires building the cli executables, and it wouldn't hurt bypassing those. I was thinking of manually linking against the generated library and writing tests externally; is there another approach which is more commonly used by everyone? Thanks for all the help, I will keep you updated regarding my progress. Also, should I wait for the existing PR ([1]) to be merged before adding my code to it? Or is it better to just submit code written in a different directory (pso_lbest)? The former might make it easier to integrate the two approaches (gbest and lbest), but it might make adding support for GD a bit tricky. Thanks and regards, Chintan Links used: [1] https://github.com/mlpack/mlpack/pull/1225
_______________________________________________ mlpack mailing list [email protected] http://knife.lugatgt.org/cgi-bin/mailman/listinfo/mlpack
