similar to: GSoC 2016 - Introducing Myself

Hello Matthias Reisinger, It is simple html page that shows simple abstract ( which I have already added for all projects as per GSoC page) , link to your read-only proposal, blog URL (if you maintain any) , and status reporting interval (if you want to follow) and any other relevant information. You can check out (SVN) related code here http://llvm.org/svn/llvm-project/www/trunk/SummerOfCode/

Hello all, GSOC is around the corner, and the LLVM projects plans to participate again this year. For those who don’t know about GSOC, students are proposing a project that they will work on for 3 months. Amongst other, one goal for LLVM is to mentor students to become good developers and also contributors to the LLVM project (or user/advocate of LLVM for building other cool projects). A key

Thank you Vivek, I posted an according patch on phabricator. I also took the liberty to change the design a little bit (based on the open projects page http://llvm.org/OpenProjects.html). But take it with a grain of salt, I'm no html expert :) Best regards, Matthias Am Dienstag, 10. Mai 2016 19:48:21 UTC+2 schrieb vivek pandya: > > > > *Vivek Pandya* > > > On Tue, May

> Do you happen to have any plans on reporting your progress publicly? > I will try to make my progress transparent by writing about it on my blog as often as possible and definitely give updates at the mailing lists ( julia-dev <https://groups.google.com/group/julia-dev>, polly-dev and llvm-dev). Also, please submit a patch to llvm.org/SummerOfCode/2016.html to add > some

Dear libguestfs developers and users, it is my pleasure to welcome Hiroyuki Katsura as Google Summer of Code 2019 student for libguestfs! He will work on adding Rust bindings, to allow using libguestfs in Rust applications. You can read the project submission here: https://summerofcode.withgoogle.com/projects/#6730007286644736 I'm the main mentor of this project, with Rich Jones, and Martin

Hi! I'm currently a final year student of Informatics Institute of Technology Sri Lanka affiliated with the University of Westminster, a successful GSOC 2017 participant <https://summerofcode.withgoogle.com/projects/#6522320890888192>. Witnessing the usage of machine learning and information retrieval I'm keen to contribute to The Xapian project thus, enhancing my skills in machine

Hello, I am Mohammed Nafees, a Computer Science student at the University of Waterloo, Canada and I am going to apply for Google Summer of Code 2018. I am interested in working on the project "Reimplement LLDB's command-line commands using the public SB API. ". How can I start, and how can I contact the mentors? I have completed Google Summer of Code 2017 with KDE (project

You mean, to take review on proposal I need to create an application? and if it is the case then please tell me how to create application? On Tue, Mar 22, 2016 at 6:24 PM, James Aylett <james-xapian at tartarus.org> wrote: > On Tue, Mar 22, 2016 at 12:49:58PM +0530, MURTUZA BOHRA wrote: > > > I have prepared a draft proposal for clustering problem. If you have > >

Agreed. I think it's worth thinking about what GSoC is actually about, which according to the website: "Google Summer of Code is a global program focused on introducing students to open source software development." Strongly favouring students with prior experience in community involvement with LLVM is somewhat missing the point, and I think we should be mindful of the differences

On Wed, Feb 1, 2017 at 9:19 AM, Michael Kruse <llvmdev at meinersbur.de> wrote: > 2017-02-01 18:07 GMT+01:00 Kostya Serebryany <kcc at google.com>: > > Yes, I used to run clang-fuzzer and clang-format-fuzzer on this bot, but > not > > any more. > > The reason is simple -- the bot was always red (well, orange) and the > bugs > > were never fixed. >

Hello everyone, I have been working on adding support for BM25+ weighting function from the last couple of weeks. Initially, I considered modifying bm25weight.cc to add support for BM25+ function without disturbing functionalities of BM25. But that didn't work out very well. A day or two was spent trying to refactor and debug the same code. Later, I took another approach following the

On Mon, Apr 10, 2017 at 11:47:36PM +0530, Vivek Pal wrote: > > No, use Xapian::Registry to find the weighting scheme from the name > > like how Weight::unserialise() does (otherwise every caller would need > > code similar to that above). > > Okay, I looked into Xapian::Registry and it seems you are referring to using > the get_weighting_scheme method? (which expects a

> `ptr` is, if I inferred correctly, a `const char *`. (I'm not sure, > because I don't know why you're incrementing it. Please push your code > to github if you need further help so people can see the entire > context of your changes.) I've pushed all the changes I made so far https://github.com/xapian/xapian/compare/master...ivmarkp:piv+?diff=split&name=piv%2B

Hi, In my explorations of Omega codebase, I have found that Omega is currently missing support for newer weighting schemes added in 1.4.1 (BM25+, PL2+, Dir+). I'd submit a PR addressing that but as I think I might be missing something so just wanted to check if there's a particular reason for that? P.S. Finally back after a long week. Been eagerly waiting for a weekend since the

> Each scheme already has a human-readable name, and Xapian::Registry > can map that to an "examplar" object of the right type, so we > could take a string like "bm25 1 0.8", see the first word is "bm25" > and get a BM25Weight object, then call parse_params("1 0.8") on it to > create the correct Weight object (broadly similar to how

Dear All, I am glad to be part of GSoC 2016 with LLVM organization. I am a first year PhD student at IIT Hyderabad, India and my research area is compiler optimizations using polyhedral model. My GSoC 2016 project is to implement Polly as an Analysis pass in LLVM [1]. We have a discussion on Polly-dev mailing list [2] on taking a better approach to implement this project. Based upon this

Hi, I have added support for Piv normalization in Tf-Idf weighting scheme as a intermediate step to implementing the support for Piv+ normalization. All tests pass. But I'm running into some issues with Piv+ normalization. In the Piv+ formula , there are two parameters (s and delta) that control the weight assigned. I think the way I'm serialising and unserialising these parameters has

> You could do that by identifying the search session instead of the user, > which makes it closer to what we need than to something that might trip you > into privacy concerns. Okay, that would be much better. :) > Third records some information about what sort of query it is — add, > morelike or a plain query. Last provides the estimated match size and then > the HTTP

> It may be worth splitting that part of the $set documentation out into its > own section somehow, because it's getting a bit long - Undoubtedly; $set command has the longest section on the documentation page :) But it would be hard splitting that up because the documentation is organised in a way that each command is really contained in its own specific section. > and the details

> Two of those are compile errors, suggesting you aren't pulling in the > right header file (it's in common/serialise-double.h I believe). Thanks, fixed those errors. > I can't tell for sure without seeing the diff. You may mean just > `ptr++`? But it could be something else, depending on what you're > trying to do. I'm trying to unserialise normalization