GSoC 2021 PSF Blogs

Final Check-In

singh.harsh9097@gmail.com (Harsh) — Sun, 29 Aug 2021 19:13:09 +0000

The GSoC journey has come to an end. This summer has been one of the most exciting summers of my life. During this journey, I learned a lot of things from writing clean code to documentation to various soft skills that would help me through my journey/career.

I am extremely grateful to my mentors Terri, John, Anthony, Harmandeep and Saurabh and fellow contributors Sahil, Suhail and Dmitry Volodin for guiding and helping me out through this journey. Thank you Google, Python Software Foundation and Intel for giving me this incredible opportunity! :)

Read my final project report here: Harsh's Final Report

- Harsh (peb) ;)

Post #6: Final blog post

ybrahimmartinez09@gmail.com (ymartinez) — Fri, 27 Aug 2021 20:19:52 +0000

Hi everyone! this is my final blog post in the 2021 GSoC internship. The journey is almost over, it has been 2 months and I can't believe the fast that was.
Although this is the final post required by PSF, I am planning to create a blog post with more detailed information of my overall experience in this internship, but right now I am sick so I hope that will be the next week you can check my personal blog here.

What are you working on?

The last week I was working on document all my code, and also made a report with my activities in the internship, this report I made in the PyZombis wiki.

What have you struggled with?

As I said before, right now I am sick so, it was difficult for me made this report because I was such tired, and with terrible flu, but I needed to do that requirement, and I did it finally!

Final Blog Post: The Finished Product ⭐

debaditya.pal6@gmail.com (DebadityaPal) — Thu, 26 Aug 2021 10:45:08 +0000

Whenever someone tries to learn a new package, usually the first stop is always the documentation. But the documentation is mostly long and boring to read through. Furthermore, since it is auto-generated, it often contains a plethora of arguments, most of which are internal and of no use to the end-user. Data science is an interactive field by nature, thus, packages for data science should also follow suit.

Hub is a data optimization package that enables users to stream unlimited amounts of data from the cloud to any machine without sacrificing performance compared to local storage.

It is an individual package that comes with its own set of APIs. Therefore, if a user wants to incorporate Hub into their project they must first get comfortable with these APIs and understand how to use them.

The primary reason why users would use libraries and packages in their projects is to simplify the coding process and make it much faster. The packages’ main purpose would be to skip the manual implementation of everything in the codebase. Hence, it only makes sense when I say that learning how to use Hub should be faster than having to finish the project without using Hub.

The idea of “Learn” is to provide a much more interesting and faster way of learning how to use Hub. The goal is achieved by serving interactive code-along tutorials, much like DataCamp, that the user can take from the comfort of their local terminals. “Learn” comes with a single command that starts the whole course engine and the rest works based on user feedback.

The way it works is that there exists a course library that contains all of the course content in YAML files. The content is divided into small bits of information we call “Snippets”. The course engine contains a YAML Parser that reads the information from these files and presents the same to the user one snippet at a time. Currently, we have 3 types of snippets to add variety to the way information is presented:

Text Snippet: Purely meant for reading, does not expect user feedback.
MCQ Snippet: Poses a multiple choice question for the user and expects them to enter an answer.
Code Snippet: Provides a prompt and expects the user to code along.

The API has been designed in such a way that more types of Snippets can easily be added.

Writing new courses is also really simple should a user want to add their courses. A full guide can be found at https://learn-hub.readthedocs.io/en/latest/course.html. In short, it just involves writing one Snippet at a time following a particular format. With this package, learning how to use Hub is a much faster process now, we hope to make it as easy as possible for newcomers to start using Hub. Moreover, the package is completely extendable and community-driven, if you feel like writing a course on a topic, feel free to do so!

Final Blog [Aug 23, 2021]

hashimchaudry23@gmail.com (mHash1m) — Wed, 25 Aug 2021 08:26:33 +0000

Hi everyone,

It's a pleasure to let you know that I have completed the project with all the requirements and more! It has been an amazing journey, from learning to getting amazing mentorship from John Andersen, to getting to know a great community. This has really been a wild journey!

If you would like to know more about my project, here is the Final Report.

My Final Post of GSoC 2021

StyloRJ@gmail.com (Juerodriguez) — Tue, 24 Aug 2021 19:27:08 +0000

Hello, in this last week we have done a review of everything we have achieved during the program, the results were reflected in the project wiki which general terms were very satisfactory, personally I have loved participating in the Openlex project since I have been able develop my skills as a programmer as planned. All of this could not have been achieved without the help of my mentors Marian Vignau, Emmanuel Arias and Nicolas Sandoval who accompanied me at all times, so I offer a special thanks to them. I hope to participate again in GSoC as a mentor to help other boys to enter the world of Open Source.

Final Report

robertogrosmaninho@gmail.com (RobertoRosmaninho) — Tue, 24 Aug 2021 18:12:05 +0000

This week I focused in prepare this document and get the last PR approved. Also, I tried to fix the 2 last Issues opened.

GSOC Final Report

After ten weeks of hard work on the project "LLVM Back-end for the Tensor Algebra Compiler" for Google Summer of Code 2021 I was able to develop the following contributions:

Support for branch and loop operations (IfThenElse, While, For)
Support for binary and unary operations (Neg, Sub, Div, Rem, Min, Max, And, Or, BitOr, BitAnd)
Support for comparison operators (LTE, GTE, LT, GT, EQ, NEQ)
Support for other operations (Assign, Cast, Case, Indices property, Comment, BlankLine)
Support for booleans
Added new tests to assess the correctness of new operations

These contributions allow the basic use of TACO with LLVM like arithmetic operations on sparse or dense tensors passed as command-line arguments with llvm flag or using the TACO C++ Library.

The project resulted in 6 Pull Requests and 5 Issues. Five PRs were merged, and one was closed because its content was already been developed by Guilherme, my mentor, on another branch. 3 Issues are still open.

The project can be separated into 3 phases:

First impressions and branch update
Implementation of Basic Operations
Fix old implementation, test writing, and searching for bugs

The first phase was developed in the two first weeks and resulted in the following PRs:

The first phase was to update the llvm-backend branch that I used on the project with the new alterations on the main, and update the readme with instructions to use TACO with LLVM support using a conda environment.

I opened an issue to inform that the LLVM IR generated by TACO lacks information of the target machine when compared with the IR generated by clang:

Currently, the llvm module generated does not contains any Target Information, Function Attributes, or Named Metadata

This issue was not resolved yet because it doesn't impact the program operation and IR generation.

The second and main phase was developed from the third to the eighth week and resulted in the following PRs:

The main implementation was developed during these weeks with the assistance of my mentor Guilherme Leobas. As mentioned before, the first PR wasn't merged because its content was already been implemented on PR #7. The issues that I opened and solved during these weeks were the following:

The last two weeks of development was used to write new tests, find bugs on corner cases and format the code resulting in the following PRs:

Add new tests for llvm-backend

The tests were implemented on a separated folder called "llvm-examples" and on gTest, the framework used by taco to automate tests. The following Issues were opened due to bugs found on these tests:

These issues are the start point for future improvements on the project.

This experience was excellent, I could learn more about TACO, LLVM, compilers, open-source cooperation, and development. I hope to be able to continue contributing to this project soon.

Wrap Up GSoC 2021

cumplileo@gmail.com (LeoCumpli21) — Tue, 24 Aug 2021 18:02:29 +0000

The complete wrap up of my GSoC experience is here: Leo Cumplido GSoC 2021

Hi, I'm Leo Cumplido, an 18 year old data science student at the time I'm writing this. My Google Summer of Code (GSoC) 2021 has nearly come to an end. Here's a wrap up of what I did this summer working with Python Argentina, under the umbrella of the Python Software Foundation (PSF), on a project called PyZombis.

Quickly, PyZombis is an attempt to make an interactive notebook regarding python basics. The overall goal of this project is to make a quality, and free content, kind of MOOC for Spanish speakers. The platform where it is landed is Runestone. The topics covered go from python fundamentals, like basic data structures, flow control, and loops, to web scrapping, accessing APIs, web development, and more.

Milestones

I worked on three milestones:

1 - Fix Lessons 1 to 14, "revisiones" lectures, and add quizzes

Originlly, it consisted of fixing lectures 1 to 14, and quizes 1 to 14 as well. I completed this milestone before the first evaluation period, but then I kept adding issues as they arose. During this period I learned GitHub basics, Playwright for web testing, and pytest for testing python code, correct python formatting following PEP8 rules, and open source best working practices.

2 - Refactor Facebook API Lesson

During my second milestone I worked with APIs principally. Also, I made use of Brython as the python interpreter for some exercises. The thing that took me more time was adding pytest-vcr to mock the requests to APIs in the tests. Here's a gif of the web test for a challenge of the course. It was the most advanced test because to make it I had to mock the API calls, and to handle the dialog boxes that appear. The web test is automated with Playwright.

3 - Add more complex exercises

This third milestone was about implementing new more complex exercises, as if they were challenges, to the course.

Project

Here you can consult all the issues I opened and solved.
GSoC 2021 PyZombis Project

Commits

Here are all the commits I made during GSoC
Commits

Left to do

The course may be ready for a beta, not massive launch. However, there's still work to do. For example:

Pygame lecture can be adapted using Brython. This idea is to be explored. Here's an example of a game made in Brython.

Now that the coding period has ended, I can say I accomplished my goal. Regarding code, I was able to lean and apply new tools quickly, like Playwright and Brtyhon. Regarding the overall open source project, I learned how to work on GitHub, how to apply a good work flow and how to approriately communicate with my working team.

GSoC Weekly Check-In #12 (August 23)

rahulshrestha0101@gmail.com (rahulbshrestha) — Tue, 24 Aug 2021 16:38:51 +0000

GSoC has ended! I've written about my experience here

Week #11: Writing Tests and Finished Submission

xingyuliu@g.harvard.edu (Xingyu-Liu) — Tue, 24 Aug 2021 12:16:38 +0000

What did you do this week?

Finished General implementation of supporting immediate arguments
GSoC submission: blog
Merge some cases WIP: TST: add tests for Pythran somersd

What is coming up next?

ENH: optimize min max and median scipy.stats.binned_statistic by another contributor His performance is even better than our Pythran improvement( ENH: improved binned_statistic_dd via Pythran) He did vectorization improvement and reduced two loops into one. Maybe we can try Pythran again based on his implementation?
Finish WIP: TST: add tests for Pythran somersd

Weekly Check-in #12

aravindmurali711@gmail.com (aravindm711) — Tue, 24 Aug 2021 06:52:04 +0000

Hello everyone! or should I say Good-bye everyone!

1. What did I do this week?

As the coding phase has come to an end, I’ve been making sure that the dedicated GSoC branch that I’ve been working on is in sync with the main development branch, the ‘develop’ branch from the base repository. Also updated the ‘Help’ documentation in the UI, fixed some bugs and covered some things that I had in my ‘To-Do before GSoC ends’ list.

2. What is coming up next?

Now, I wait patiently for the final results. 🤞🏻

Part of the journey is the end | Final Report

gavishpoddar@hotmail.com (gavishpoddar) — Tue, 24 Aug 2021 05:11:25 +0000

Hi, community

Part of the journey is the end. It is time for me to work on my final work report for final evaluation of Google Summer of Code 2021. This week, I will devote my time mainly to write my final report.

Final Work Submission Report

Name: Gavish Poddar
Organisation: Python Software Foundation
Sub-Organisation: Zyte
Project: dateparser Better language detection & reimplementing search_dates
Proposal: dateparser - better language detection

Hello Everyone! My name is Gavish Poddar and I'm excited to tell you about my GSoC journey. For the past couple of months, I have been working on an awesome project dateparser. The dateparser aims to parse datetime from a string.

My GSoC journey would not have been successful without the guidance of my mentors Marc Hernández, Konstantin Lopuhin and Kishan Mehta.

What I Have Learned?

The whole GSoC journey was full of learning thanks to my mentors. I learned how to find good open source dependencies to include in our project. I tried my hands on improving code coverage and writing tests for the code. I learned how to optimize code and the need for extensive research before feature addition.

What I Have Contributed?

As mentioned in my proposal I worked on the implementation of the Optional Language Detection for dateparser and fixing as many issues as possible in the search_dates function of the dateparser.

Optional Language Detection

PR - Optional Language Detection

Implemented optional language detection to improve language detection. This allows to plug in any language detection library with the dateparser. Out of the box, dateparser supports two libraries fasttext and langdetect. The optional language detection works with both parse and search_dates. This PR also introduces a new setting DEFAULT_LANGUAGES which is used if no language is detected by default language detection and the optional language detection.

Reimplimenting `search_dates` (extended goal)

PR - Reimplimenting search_dates

A reimplemented and simplified search_dates improves the results and fixes many issues. The entire search_dates is newly implemented and would be easier to maintain. This PR introduces a new feature search_first_date which returns the first date in the given string. This PR also fixes around 13 issues.

Other `search_dates` improvements

Adding support for date-related objects last decade, next decade, etc in search_date. This PR fixes 1 issue.

PR - Improvements in locale:translate_search fixes

Adding support search_date period separator support. Date string like 23.12.2000 can be parsed. This PR fixes 5 issues.

PR - search_date period separator support

Other Important Details

As part of our GSoC project, Python Software Foundation requires us to post a weekly blog where we usually post about what we have done in the week and what is coming up next. We can also write about any blockages or issues we are facing. I have also written my weekly blogs so if you want to know weekly details of my project you can refer them here.

Weekly Blogs

Future Work and Final Note

The project is very actively maintained the new search_dates and my contributions would improve the library. The main goal of the proposal is achived with the implimentation of the optional language detection and the PR is mergeable. I plan to keep working on the project and contribute as much as I can. Contribute to the search_dates function of the library (dateparser) would be my primary goal.

It was overall a wonderful experience and I learned a lot.

I would like to thank Google, Python Software Foundation and Zyte for providing me with the opportunity and my mentors Marc Hernández, Konstantin Lopuhin and Kishan Mehta.

Thank you for reading!

Weekly Check-In The End

abhiruppalmethodist@gmail.com (abhirup@99) — Tue, 24 Aug 2021 04:57:14 +0000

Time flies and here we are at the end.

I spent the last week cleaning the codebase a bit more, squashing a bug here and there and adding codecov to the repo. The code quality has improved a lot, and the codecov CI would visualize all the test coverage. The UI for the fiigma plugin got an upgrade and now looks pretty neat and clean. I documentated my PRs and the status reports in a separate repo marking the end of these journey :).

I want to thank my mentors for being a massive part in this journey and giving me the opportunity to work on the plugins. This has helped me grow tremendously, and learn React among other things. I would try to keep contributing to EOS after GSOC ends. Till then, peace out :).

Weekly blog post #12

angelasofiaremolinagutierrez@gmail.com (AngelaRemolina) — Tue, 24 Aug 2021 02:48:13 +0000

What are you working on?

This last week of GSOC I worked on documenting all my code. I recorded everything I did this summer in the PyZombis repository’s wiki. I created 4 sections: What was proposed, What was done, What was left to do and a general summary where I put a table with a log of all commits made to the master branch by me.

What have you struggled with?

I did not have any struggles this week.

Weekly Blog - The END!

iifawzie@gmail.com (iifawzi_) — Tue, 24 Aug 2021 01:10:13 +0000

Hi everyone! Time flew so fast.. we've reached the end...

What did you do this week?

I've worked on completing the missing parts, finishing the documentations, and writing the Work Conduct document.. We do really reached the end, couldn't think that I would write this post that fast. Thank you all for being part of this journey. You can find more details about the project @ GSOC-2021-Project-Report

That's it.. I'd love to say that I've passed the best 10 weeks in my life, being able to fix bugs, introduce new features and contribute daily to open source projects under GSoC, was a lifetime experience for me. Thank you all the mentors, python foundation, and program organizers for giving me such an opportunity. Thank you, couldn't be done without you.

Week 10 : Term Finale

vermahrithik812@gmail.com (risehr) — Mon, 23 Aug 2021 20:26:55 +0000

Hey there, guys! Hope you all are doing well.

Finally, the day has come which can be technically termed as the final week of the Google Summer of Code 2021. It was just in a flash when I had written the zeroth blog and this is the eleventh, that I am writing now. So many things have come up, so many things have been handled and so many things are there that I have learnt. But one thing is for sure, that I am going to cherish this time all along my life. GSoC has been like a true experience for me! The people that I interacted with, the amazing mentors that I have and the one-of-its-type journey that I went through, was superb.

What did I do this week?

This week I ran the last mile like the fastest runner, as it seems. There were a lot of things that I did which I never imagined I can do in a week.

The first being that I had written the descriptions in .txt files for each of the tutorial that was made, explaining what is happening in the tutorial and the purpose of the tutorial giving the user a comprehensive idea of what the particular feature that the tutorial denoted was all about. The text files were written in English.

Next, I created the audio module which helped in the automatic generation of audio files from that text. It could be used to translate the text to any major available language (the languages that the translation API supports) from English. Next, the translated text can be converted to speech using text-to-speech APIs. Also, the user has an option of changing an API according to his/her choice and liking.

Finally, I created the tutorials.rst file for filing all the documentations and making an user manual of how to use or develop the tutorial features in MSS.

I fixed the bugs in some files and ameliorated the typos in some files.

Also, I submitted my final evaluation with a link to my work that has been done during the period.

What is coming up next?

Nothing much, I guess. This is the end of the coding period and all the code submissions have been done. Next, there is mentor evaluations and result declaration.

End Note and Acknowledgements

The GSoC period has been almost over and all the submissions already done. I have completed almost all the goals outlined originally in my proposal but some minor things have been left out to do like mixing of the generated audios into the tutorial videos, linking the tutorials in the main UI by uploading to Youtube and by changing the main MSUI UI for the same. Sometimes, there are time constraints for certain things but I am a happy that I had developed the tutorials to a much major extent and that it can be used by people.

There are many valuable learnings and and an uncountable number of assets that got added up to my skill sets due to this accomplished journey. I am very much thankful to my mentors Reimar Bauer, May Bär, Jörn Ungermann, Tanish Grover, and Christian Rolf for their extended support and guidance. I would always love to work with them post GSoC and continue to improve the tutorials features of MSS.

You can find more about my work at this Github Wiki and you can see the automated tutorials that have been generated on a public share, here !

You can also see the documentation right at this place !

Thankyou everyone for staying together, all this while!

GSoC 2021 PSF Blogs

Final Check-In

Post #6: Final blog post

What are you working on?

What have you struggled with?

Final Blog Post: The Finished Product ⭐

Final Blog [Aug 23, 2021]

My Final Post of GSoC 2021

Final Report

GSOC Final Report

Wrap Up GSoC 2021

Milestones

Project

Commits

Left to do

GSoC Weekly Check-In #12 (August 23)

Week #11: Writing Tests and Finished Submission

What did you do this week?

What is coming up next?

Weekly Check-in #12

1. What did I do this week?

2. What is coming up next?

Part of the journey is the end | Final Report

Hi, community

Final Work Submission Report

What I Have Learned?

What I Have Contributed?

Optional Language Detection

Reimplimenting search_dates (extended goal)

Other search_dates improvements

Other Important Details

Future Work and Final Note

It was overall a wonderful experience and I learned a lot.

Weekly Check-In The End

Weekly blog post #12

What are you working on?

What have you struggled with?

Weekly Blog - The END!

What did you do this week?

Week 10 : Term Finale

What did I do this week?

What is coming up next?

End Note and Acknowledgements

Reimplimenting `search_dates` (extended goal)

Other `search_dates` improvements