diff --git a/_static/images/gsoc/2024/kaustav/docker_issue_fury.png b/_static/images/gsoc/2024/kaustav/docker_issue_fury.png new file mode 100644 index 00000000..3111cb04 Binary files /dev/null and b/_static/images/gsoc/2024/kaustav/docker_issue_fury.png differ diff --git a/posts/2024/2024_07_29_kaustav_week_9.rst b/posts/2024/2024_07_29_kaustav_week_9.rst new file mode 100644 index 00000000..bdcc9d88 --- /dev/null +++ b/posts/2024/2024_07_29_kaustav_week_9.rst @@ -0,0 +1,65 @@ +My Journey Continues: Week 9 Progress with DIPY +=============================================== + +.. post:: July 29, 2024 + :author: Kaustav + :tags: google + :category: gsoc + +Hello everyone! It’s time for another update on my progress. Week 9 has been a blend of learning, preparation, and a bit of personal work as I continue my journey with the dipy.org project. This week, I focused on diving into Docker, an essential tool for the upcoming tasks in our project. Let me take you through what I accomplished and learned over the past few days. + +Learning Docker +--------------- + +One of the key goals for this week was to get up to speed with Docker, as it will play a significant role in the next phase of our project. I’ve heard a lot about Docker’s versatility and how it simplifies the process of managing development environments, so I was eager to dive in. + +**Getting Started with Docker** + +I started my Docker journey by exploring the official `Docker documentation `_, which provided a solid foundation. The tutorials and examples there were incredibly helpful in understanding the basics of Docker, including concepts like containers, images, Dockerfiles, and volumes. The step-by-step guide walked me through setting up my first container, which was a satisfying experience. + +**Trial and Error** + +While the documentation gave me a good start, much of my learning came through trial and error. I experimented with creating and running containers, exploring how to build custom Docker images, and understanding how to manage multiple containers simultaneously. + +I also explored some video tutorials on YouTube. + +1. `Docker Tutorial for Beginners `_ +2. `Learn Docker in 1 Hour | Full Docker Course for Beginners `_ + +For reference, I was pointed to look at the pyAFQ docker as well. (https://github.com/yeatmanlab/pyAFQ) + +**Docker in the Context of DIPY** + +The reason for learning Docker was for creation of DIPY docker image that can be utilized easily for running DIPY and doing tests. + +PhD Applications +---------------- + +On the personal front, this week also marked the beginning of my PhD application process. Balancing the demands of my work with DIPY and the preparation required for my applications has been challenging, but I’m hanging on. I’ve started drafting my statement of purpose and gathering the necessary documents. + +The process of applying for a PhD is quite intense. I’m excited about this next step in my academic journey, but it does mean I’m a bit busier than usual. Nevertheless, I’m committed to continuing my work with DIPY and ensuring that I stay on track with my GSoC project. + +Difficulties & Challenges +------------------------- + +This week’s challenges were more about balancing my time and managing multiple learning curves. Docker, while immensely powerful, has a steep learning curve, especially when you’re new to containerization. However, I found that breaking down the learning process into smaller, manageable tasks helped me make steady progress. + +The other challenge, of course, was balancing my PhD application work with my commitments to DIPY. It’s a delicate balance, but I’m confident that with careful time management, I’ll be able to handle both effectively. + +Next Week +--------- + +Looking ahead to next week, I plan to: + +1. **Practice with Docker and Create a DIPY Docker Image**: I’ll continue refining my Docker skills and aim to create a Docker image specifically for DIPY. This will involve ensuring all dependencies are correctly configured and the image can be used effectively within our development workflow. + +2. **Fix Tutorials for the Keyword Argument PR**: In addition to working with Docker, I’ll also be fixing the tutorials related to the keyword argument PR that I implemented earlier. This will involve updating the documentation and ensuring the tutorials reflect the latest changes in the codebase. + +Final Thoughts +-------------- + +Week 9 has been a productive blend of learning and preparation, setting the stage for some exciting developments in the coming weeks. I’m particularly looking forward to seeing how Docker can streamline our workflows in DIPY, and I’m equally excited about the progress I’m making on my PhD applications. + +As always, I’m grateful for the support and guidance from my mentor, `Serge Koudoro `__, and the DIPY community. Their feedback and encouragement continue to be invaluable as I navigate both the technical challenges of this project and the personal milestones in my academic journey. + +Stay tuned for more updates as I continue to dive deeper into Docker and tackle the next set of tasks in DIPY! Thank you for reading, and I look forward to sharing more progress next week. diff --git a/posts/2024/2024_08_05_kaustav_week_10.rst b/posts/2024/2024_08_05_kaustav_week_10.rst new file mode 100644 index 00000000..69590b86 --- /dev/null +++ b/posts/2024/2024_08_05_kaustav_week_10.rst @@ -0,0 +1,41 @@ +My Journey Continues: Week 10 Progress with DIPY +================================================ + +.. post:: August 5, 2024 + :author: Kaustav + :tags: google + :category: gsoc + +Hello everyone! Week 10 has been a challenging one, with a lot happening both in my personal life and with the DIPY project. Unfortunately, I wasn’t able to make as much progress as I had hoped, but I still managed to get some important work done. Let me walk you through what I accomplished this week. + +Fixing Tutorials for the Keyword Argument PR +-------------------------------------------- + +This week, my main focus was on fixing the tutorials related to the keyword argument PR that I had worked on earlier. Ensuring that all tutorials are up-to-date and accurately reflect the changes in our codebase is crucial for maintaining the quality and usability of our documentation. + +I spent time reviewing the tutorials, identifying areas where the new keyword arguments were relevant, and updating the examples accordingly. + +Keyword PR: https://github.com/dipy/dipy/pull/3306 + +Busy Week: PhD Applications and Moving Houses +--------------------------------------------- + +On the personal front, this week has been incredibly hectic. I’ve been deep into the process of applying for PhD programs, which has taken up a significant amount of my time and energy. Drafting statements, gathering documents, and try to get the letter of recommendations have all been time-consuming, but I’m making good progress on my applications. + +Additionally, I had to move houses this week, which added another layer of complexity to an already busy schedule. The logistics of packing, moving, and settling into a new place were more exhausting than I anticipated, leaving me with less time and focus for my work on DIPY. + +Next Week +--------- + +Looking ahead to next week, I plan to: + +1. **Resume Docker Practice and Create a DIPY Docker Image**: With the move and PhD applications mostly behind me, I’m aiming to get back on track with Docker. My goal is to continue practicing with Docker and work on creating a Docker image specifically for DIPY, ensuring all dependencies are correctly configured for our development workflow. + +Final Thoughts +-------------- + +Week 10 has been a slower week in terms of progress, but sometimes life throws unexpected challenges our way. Despite the lower productivity, I’m glad I was able to keep moving forward, even if at a slower pace. I’m looking forward to getting back into a more productive rhythm next week as I continue my work on DIPY. + +As always, I appreciate the support and understanding of my mentor, `Serge Koudoro `__, and the DIPY community. Their encouragement is invaluable, especially during weeks like this one. + +Thank you for reading, and I look forward to sharing more updates next week as I pick up the pace again! diff --git a/posts/2024/2024_08_12_kaustav_week_11.rst b/posts/2024/2024_08_12_kaustav_week_11.rst new file mode 100644 index 00000000..f4709b4b --- /dev/null +++ b/posts/2024/2024_08_12_kaustav_week_11.rst @@ -0,0 +1,50 @@ +My Journey Continues: Week 11 Progress with DIPY +================================================ + +.. post:: August 12, 2024 + :author: Kaustav + :tags: google + :category: gsoc + +Hello everyone! Week 11 has been another week of progress, although it came with its own set of challenges. I’ve been working on Docker, making updates to the tutorial fixes, and I also have some exciting news on the personal front. Let me take you through the highlights of this week. + +Creating a Docker Image for DIPY +-------------------------------- + +This week, I focused on creating a Docker image for DIPY. However, I ran into some issues related to the `FURY` and `VTK` packages due to version incompatibilities. These packages are crucial for the visualization components of DIPY, and ensuring they work correctly within the Docker environment has been a bit tricky. + +The version conflicts have caused some build failures, and I’ve been troubleshooting the issue by testing different configurations and dependencies. While I haven’t completely resolved the issue yet, I’m hopeful that I can find a solution soon. I’ll continue to work on this in the coming days, as getting this Docker image ready is important for our continuous integration processes. + +.. image:: /_static/images/gsoc/2024/kaustav/docker_issue_fury.png + :alt: Docker FURY VTK issue + :width: 800 + +Tutorial Fixes PR Update +------------------------ + +In addition to Docker, I’ve been updating the PR for the tutorial fixes related to the keyword argument changes I made earlier. I’m happy to report that I’m about 60% done with the updates. The tutorials are shaping up well, and the changes are making them more robust and easier to follow. + +I plan to complete the remaining 40% by today or tomorrow, ensuring that all tutorials are fully updated. + +PhD Application Submitted +-------------------------- + +On a personal note, I successfully submitted my PhD application this week! This has been a significant milestone for me, and I’m thrilled to have it completed. Applying for a PhD is a rigorous process, and I’ve put a lot of effort into crafting the application. Now that it’s submitted, I’m hopeful for the best outcome. + +If I do get accepted, it would be a dream come true. I’m particularly excited about the prospect of learning from and working with leaders in the field, such as `Dr. Eleftherios Garyfallidis `__, whose work I greatly admire. The opportunity to contribute to and learn from such a program would be invaluable, and I’m eagerly looking forward to the possibility. + +Next Week +--------- + +Looking ahead to next week, my priorities will be: + +1. **Fixing the Docker Image Issues**: I’ll continue troubleshooting the `FURY` and `VTK` package issues within the Docker environment, aiming to get a working Docker image for DIPY. + +2. **Completing the Tutorial Fixes**: I plan to finish the remaining 40% of the tutorial updates, ensuring that the PR is ready for review and merging. + +Final Thoughts +-------------- + +Week 11 has been a productive week, despite some challenges with Docker. I’m pleased with the progress I’ve made on the tutorials and excited about the future, both with DIPY and potentially with my PhD journey. As always, I’m grateful for the support from my mentor, `Serge Koudoro `__, and the DIPY community, who continue to provide invaluable guidance. + +Thank you for reading, and I look forward to sharing more updates next week as I continue working on these tasks!