- Boost - lists.boost.org

Fwd: Re: [gsoc18][ublas] Proposal to add advanced matrix operations
by Mike Gresens 20 Jan '18

20 Jan '18

Hi Mike, Apart from the operations I was proposing, the idea of solving polynomials via QR reduction seems a great idea to me. I can add this module in the list of operations to be added to Boost.ublas in my proposal. I am looking for someone to mentor me on this project. Regards, Shikhar Srivastava On Sat, Jan 20, 2018 at 10:34 AM, SHIKHAR SRIVASTAVA <shikharsri1996(a)gmail.com <mailto:shikharsri1996@gmail.com>> wrote: Hi Mike, It looks like some of the operations that I suggested were already implemented as a part of GSOC15, though never got merged into the main branch. https://www.google-melange.com/archive/gsoc/2015/orgs/boostcpp/projects/raj… <https://www.google-melange.com/archive/gsoc/2015/orgs/boostcpp/projects/raj…> https://github.com/BoostGSoC15/ublas/ <https://github.com/BoostGSoC15/ublas/> My Idea was to add generalised modules for the operations (Now) - 1. LU and Cholesky 2. QR and QL 3. SVD On Fri, Jan 19, 2018 at 9:14 PM, Mike Gresens <mike.gresens(a)googlemail.com <mailto:mike.gresens@googlemail.com>> wrote: Hi Shikhar, does this include something for solving polynomials (via balanced-QR reduction of the companion matrix)? See https://www.gnu.org/software/gsl/doc/html/poly.html#general-polynomial-equa… <https://www.gnu.org/software/gsl/doc/html/poly.html#general-polynomial-equa…> Thanks! Best regards, Mike... Am 19.01.2018 um 07:37 schrieb SHIKHAR SRIVASTAVA via Boost: Hi everyone, I am a 4th year undergraduate student pursuing a degree in Computer Science and Engineering. I have strong programming experience in C++ through internships, self projects and programming events. I wish to be a part of gsoc18 under boost and am particularly interested in the linear algebra library Boost.ublas. The ublas library can be made more useful for Machine Learning applications like recommendation systems, clustering and classification, pattern recognition by adding some operations required in those. I propose to add advanced matrix operations to ublas including - 1. Triangular Factorisation (LU and Cholesky) 2. Orthogonal Factorisation (QR and QL) 3. Operations to find Singular Value lists 4. Eigenvalue algorithms 5. Singular Value Decomposition (SVD) 6. Jordan Decomposition 7. Schur Decomposition 8. Hessenberg Decomposition This is a very brief description of what I would like to propose. Any suggestions that help in refining the requirements before making a draft proposal would be great. Regards Shikhar Srivastava Github: https://github.com/shikharsrivastava <https://github.com/shikharsrivastava> _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost <http://lists.boost.org/mailman/listinfo.cgi/boost>

1 0

[geometry][gsoc2018] Similarity between geometries
by Xing GUO 20 Jan '18

20 Jan '18

Hello, My name is Guo Xing, I have sent a mail for some ideas on gsoc18 projects. David's uBLAS project on GPU computation is a little bit hard for me. Still thanks for his kind reply :) . These days, I found a project that I could possibly work on. So, I decide to take "Similarity between geometries". Below is my short self-introduction. Name: Guo Xing University: Southeast University Major: Electronic Engineering Email: higuoxing(a)gmail.com Github: https://github.com/higuoxing Homepage: https://higuoxing.com Availability: (Feb-Jun 4 hr/day) (Jun-Aug 6hr/day or more) As for my code competency, I will take the project 1 competency test after my final exam. Thank you! Regards, Guo Xing

1 0

[callable_traits] Incorrect newlines in git
by Andrey Semashev 20 Jan '18

20 Jan '18

Hi, I've created this PR to fix newlines and tabs in Boost.CallableTraits: https://github.com/boostorg/callable_traits/pull/170 Without it, I cannot update my local Boost tree because git treats the files are modified. Could someone, please, merge this PR? It's really annoying that the update process breaks every time. Thanks.

2 1

[gsoc18] Implement HTTP Library
by Xing GUO 19 Jan '18

19 Jan '18

Dear community: I'm Guo Xing, who is currently a student in his third year of college(bachelor's degree). I have interests in web development. I've done some projects with Python and node before. I want to do some work with C++ in GSoC18. So, is there any ideas for me? Or, someone could be my mentor? I love open source, but never contribute to them. I want to do some contribution. Regards, Guo Xing https://github.com/higuoxing

3 2

crypto hash library
by kerukuro 19 Jan '18

19 Jan '18

While boost::hash and the proposed additions and are good for generic hashing, its API is not very suitable for cryptographic hashes and XOFs. Would there be any interest in boostifying this library eg under name 'boost::digest' and putting cryptographic hashes in there? https://github.com/kerukuro/digestpp

1 0

[gsoc18] R-tree serialization
by Kirill Mishchenko 19 Jan '18

19 Jan '18

Hi, My name is Kirill. I’m interested in the contribution to the project “R-tree serialization”. The search through the mailing list archive has shown there was an interest in this project among students in 2017, but as the GSoC 2017 archive site displays there was no student that participated to accomplish this project. Is it possible to work on this project as a GSoC 2018 participant? It seems like last year Adam Wulkiewicz was ready to be a mentor for the project. Briefly about myself. I am a PhD student working on Computational Humor. More precisely I’m working on the problem of finding/generating a humorous response given a textual input. My C++ programming experience includes a summer internship at Yandex Search and my contribution to mlpack (a machine learning library written in C++) as a GSoC 2017 participant (https://summerofcode.withgoogle.com/archive/2017/projects/4812231682293760/ <https://summerofcode.withgoogle.com/archive/2017/projects/4812231682293760/>). For mlpack I designed and implemented cross-validation and hyper-parameter tuning modules with significant usage of C++ metaprogramming. Best regards, Kirill Mishchenko

2 1

mingw and windows.h
by Raffi Enficiaud 18 Jan '18

18 Jan '18

Hi all, I recently pushed something for boost.test on develop that is apparently breaking the builds on mingw: http://www.boost.org/development/tests/develop/developer/output/igaztanaga-… What I do in the code is this: ---------- #ifdef _WIN32 #include <Windows.h> #endif ---------- and then later ---------- #ifdef _WIN32 class setcolor { protected: void set_console_color(std::ostream& os, WORD *attributes = NULL) const { DWORD console_type; /// some additional windows specific code #endif ---------- I thought that this would be enough for having the windows specific code, but apparently mingw disagrees with the error that some windows specific define is not there. Is this an issue with the code, the SDK, the machine? I have no experience with mingw, but if we are able to include windows.h, then we have to have the defines there (the missing macro is there since Windows 2000). Thanks for the help, Raffi

3 4

Google Summer of Code 2018: submit your proposal
by David Bellot 17 Jan '18

17 Jan '18

Hi all, I migrated the GSoC'18 pages to our wiki on Github. Please contribute your proposals here now: https://github.com/boostorg/boost/wiki/Boost-Google-Summer-of-Code-2018 I would love to see plenty of nice proposals before the end of the week so that we are in good conditions to obtain it again this year. If you have problems with permission please contact me directly Best regards, David

1 0

Change Trac wiki permissions
by David Bellot 17 Jan '18

17 Jan '18

Hi, does anyone have access to the boost Trac wiki. I need to change permissions on a page to allow users to edit the page as well, but I can't find any option. There should be an Admin button next to the Search button but it doesn't appear. The page in question is the Google Summer of Code 2018: https://svn.boost.org/trac10/wiki/SoC2018 Thanks David

2 2

Reforming Boost.System and <system_error> round 2
by Niall Douglas 17 Jan '18

17 Jan '18

Many thanks to those who have contributed to the discussion in the other thread regarding making a breaking change to Boost.System in order to provide empirical test data to persuade WG21 to similarly break <system_error> in a future C++ standard for its own good. This fresh email is hopefully to start finishing the discussion. To summarise discussion to date, Peter has made Boost.System's error_code and error_category constexpr except for the virtual functions. A big win for codegen, and the choice of the default constructor of error_code to use system_category now no longer prevents constexpr, so the request for a new special null_category() can also be dropped. There is substantial opposition to making message() return string_view, so let's drop that request. That leaves the request to fix "if(ec) ..." which right now returns true if the value is 0, despite that much code writes "if(ec) ..." to mean "if error then ...". There is also the issue of error coding schemes not being able to have more than one success value, which usually must be 0. That's the remaining discussion point. Myself and Peter feel this is worth fixing despite the increased runtime overhead. Others, including one of its original inventors, feel it is too much overhead. To add some empirical evidence to the discussion, I have coded up a mock up of the improved error_code which can be viewed at https://godbolt.org/g/dDAWih. This demonstrates constexpr error_code and error_category in action as well. To summarise what the mock up demonstrates: 1. error_category() gains a new virtual function called `bool failure(int code)` which is now called by error_code's operator bool. 2. Thanks to the new constexpr construction, the compiler now completely elides from runtime the case where an inlined function returns an error code and the caller acts upon it. As in, **zero code is now generated**. Far better than before. No virtual functions are called, they are optimised out entirely. 3. For unknown error codes from extern sources where the linker is generating an executable, the "final" modifier removes a layer of indirection when calling `failure()` after the linker has run, and indeed clang seems to go ahead and inline the implementation entirely despite us not asking for LTO. Which is kinda cool. 4. Thus only in shared objects, and only for unknown error codes from extern sources, is a virtual function call actually performed. And given the frequency of doing `if(ec) ...`, it'll almost certainly be hot in the branch predictor i.e. no stalls. Question: is this still considered too much overhead? Note that there is no longer ANY proposed breaking change with existing code. This is now 100% enhancement only. Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/

17 57