Hey Cem.

I went through the draft proposal and had some questions.

Which direction do you think I should pursue? I am more inclined towards refactoring the enitre data_frame because if I believe correctly uBlas is moving towards C++20. Should I stick with ETs or can I use Ranges and Concepts?

I was thinking to stick to standard C++20 Ranges only instead of Eric Neibler's One Ranges v3 library considering std to be more relevant.

On Wed, 18 Mar 2020, 23:49 Aniket Chowdhury, <8.aniket.chowdhury@gmail.com> wrote:

Hey Cem.
Thanks for replying. Will do the needful and get back to you.
I understand that the proposal could do with a few more code examples.
Thanks.

On Wed, Mar 18, 2020 at 8:15 PM Cem Bassoy via ublas <ublas@lists.boost.org> wrote:
Hi Aniket,

thanks for considering Boost/uBLAS. Your potential mentor is David. If he does not respond, just follow the instructions on the GSoC page and upload your proposal.

Please note that we appreciate concrete (with code samples), realistic (regarding time) and referring (to previous or pull requests) proposals. Concrete examples inside the proposal will help us to understand intention and it will demonstrate your experience and expertise.

I am pretty cobfident with the timeline that I have provided with. Again, regarding code examples should I add them for both C++20 and/or ET?

Additionally, I advise to read
previous gsoc discussions on this or on the general boost mailing list
former gsoc student projects and proposals
to have a good feeling of the requirements.

Best,
Cem

Am Mo., 16. März 2020 um 23:15 Uhr schrieb Aniket Chowdhury via ublas <ublas@lists.boost.org>:
Hi,
My name is Aniket Chowdhury and I am second-year undergraduate student.

I wish to implement the DataFrame library for Boost. I have made the project proposal and am attaching the same.
As, this project is an expansion of the previous project there are a few directions that I would like to work in whichever adds more to the project.

1. We could be to keep the existing code base as it is and implement new features on top of it.
2. We could try to restructure the code into Modules(C++20 feature) and then implement the features.
3. Or, we could restructure the code without ET but rather using C++20 One Ranges. This makes more sense to me as I believe that uBlas is being ported to C++20.

The DataFrame would include the following features:
1. All the features already present(union, combine, join).
2. Read/write from DataFrame using JSON(boost::property_tree to DataFrame)
3. Operator support for addition, subtraction, multiplication, division, modulo and power, etc as well as support for comparison operators.
4. Functions to perform apply, apply_element_wise, aggregate, transform and expand on a given DataFrame.
5. Data analysis tools for standard deviation, variance, mean, etc.
6. Re-indexing methods like replace, duplicate, filter, etc.
7. Reshaping methods for sorting, append, pivot, etc.

Also, could you tell me if I am on the right track regarding the free form functions that Boost is looking for?

Full Details of the same can be found in the Project Proposal.

I have been in contact with David Bellot for the past week regarding GSoC. I have completed the first draft of the competency check and sent the same to him. I would love to work I am requesting him to be assigned as a mentor for the same.
PFA: The Project Proposal(linked in case the attachment fails)

Here was the old proposal.

This is an official application for the GSoC' 20. I am open to any and all suggestions.

Aniket Chowdhury
_______________________________________________
ublas mailing list
ublas@lists.boost.org
https://lists.boost.org/mailman/listinfo.cgi/ublas
Sent to: cem.bassoy@gmail.com

_______________________________________________
ublas mailing list
ublas@lists.boost.org
https://lists.boost.org/mailman/listinfo.cgi/ublas
Sent to: 8.aniket.chowdhury@gmail.com