-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DOC: Blogpost_KD_Week1 #38
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,49 @@ | ||
My Journey Continues: Week 1 Progress with DIPY | ||
=============================================== | ||
|
||
.. post:: June 3 2024 | ||
:author: Kaustav | ||
:tags: google | ||
:category: gsoc | ||
|
||
Hello everyone, | ||
I am back with another update on my Google Summer of Code (GSoC) journey with DIPY. The Community Bonding period has come to an end, and I am now fully immersed in the Coding phase of the project. | ||
|
||
Progress So Far | ||
--------------- | ||
|
||
Last week I updated my PR with required functionality for it to be ready to be integrated. I was having trouble with CI(Continuous Integration) pipeline in Github, I reached out to the whole team in GSOC and received support immediately, | ||
I am really grateful to `Iñigo Tellaetxe <https://github.com/itellaetxe>`__ and my mentor `Serge Koudoro <https://github.com/skoudoro>`__ for providing me necessary insights to fix the issue with CI. | ||
I also put up another very small PR to fix the codespell issues happening in the CI. | ||
|
||
Expanding the Decorator Implementation | ||
-------------------------------------- | ||
|
||
Building upon the foundation laid during the Community Bonding period, I have been looking into the expansion of the decorator implementation across more modules in DIPY. | ||
I have gone through the required functions and tests. I will have to plan which modules are next for change with my mentor. | ||
I will write comprehensive tests in this part as well. Also will be updating the necessary documentation as well. | ||
|
||
Refining Decorator Implementation | ||
--------------------------------- | ||
|
||
I will continue to refine the decorator implementation based on feedback from the community and my mentor. This includes fixing any bugs, improving performance, and enhancing the documentation further. | ||
|
||
Lazy Loading Integration | ||
------------------------ | ||
|
||
In addition to expanding the decorator implementation, I have begun researching for Task 2, which involves integrating lazy loading into DIPY. Lazy loading is a design pattern that can help improve the efficiency and performance of the codebase by delaying the initialization of objects until they are actually needed. | ||
I will begin this task when my mentor will advise me to. | ||
|
||
Community Engagement | ||
-------------------- | ||
|
||
Staying engaged with the DIPY community is crucial. I will try to participate in discussions, seek feedback, and collaborate with other contributors to ensure the success of the project. | ||
|
||
Final Thoughts | ||
-------------- | ||
|
||
The first week of the Coding phase has been incredibly productive, and I am excited about the progress I have made so far. The support and guidance from my mentor and the community have been invaluable, and I am looking forward to the challenges and opportunities that lie ahead. | ||
|
||
Stay tuned for more updates as I continue to work on enhancing DIPY! | ||
|
||
Thank you for reading! |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Week 2 ? week 1 I believe. your filename is week 1, and the previous week was week 0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You are right, Changed.