DOC: Blogpost 9,10,11 #61
Merged
Conversation
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
|
🪓 PR closed, deleted preview at https://github.com/dipy/preview-html/tree/main/dipy.org/pull/61/ |
itellaetxe
requested review from
skoudoro,
itellaetxe,
WassCodeur and
robinroy03
itellaetxe
approved these changes
Aug 13, 2024
WassCodeur
reviewed
Aug 13, 2024
| @@ -0,0 +1,65 @@ | |||
| My Journey Continues: Week 9 Progress with DIPY | |||
There was a problem hiding this comment.
Hi Kaustav!
Great Job and good luck with your PhD applications.
See some comments below
WassCodeur
reviewed
Aug 13, 2024
|
|
||
| I also explored some video tutorials on YouTube. | ||
|
|
||
| 1. https://www.youtube.com/watch?v=pTFZFxd4hOI&t=551s |
There was a problem hiding this comment.
You could use a Sphinx "inline external link" to reference tutorial links like you did at [Ln18].
https://www.youtube.com/watch?v=pTFZFxd4hOI&t=551s -->
`Docker Tutorial for Beginners <https://www.youtube.com/watch?v=pTFZFxd4hOI&t=551s>`_
WassCodeur
reviewed
Aug 13, 2024
| I also explored some video tutorials on YouTube. | ||
|
|
||
| 1. https://www.youtube.com/watch?v=pTFZFxd4hOI&t=551s | ||
| 2. https://www.youtube.com/watch?v=GFgJkfScVNU&t=1432s |
WassCodeur
reviewed
Aug 13, 2024
| 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. |
WassCodeur
reviewed
Aug 13, 2024
| 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 |
WassCodeur
reviewed
Aug 13, 2024
|
|
||
| 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. |
WassCodeur
reviewed
Aug 13, 2024
| @@ -0,0 +1,41 @@ | |||
| My Journey Continues: Week 10 Progress with DIPY | |||
robinroy03
approved these changes
Aug 13, 2024
|
|
||
| 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 |
github-actions bot
added a commit
that referenced
this pull request
Aug 14, 2024
DOC: Blogpost 9,10,11 7daa907
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Blogpost for week 9,10,11