+
+
+
+
+
+ 15 August 2024
+
+
+
+
+
Hello everyone,
+welcome to the update for Week 11 of my Google Summer of Code (GSoC) 2024 journey. This week, I focused on finalizing the footer issue on the FURY
+
+
+
Read more ...
+
+
+
+
+
+
+
+ 15 August 2024
+
+
+
+
+
Welcome to the week 10 of my Google Summer of Code (GSoC) 2024 journey. This week, I focused on resolving an issue with the FURY
+
+
+
Read more ...
+
+
+
+
+
+
+
+ 13 August 2024
+
+
+
+
+
Hello everyone,
+welcome to my Google Summer of Code (GSoC) 2024 journey! Week 9 was devoted to fixing Sphinx warnings caused by indentation errors in some docstrings of some examples in the auto_examples FURY
+
+
+
Read more ...
+
+
WEEK 8: Refining Lazy Loading Implementation and Simplifying Imports in FURY
diff --git a/v0.10.x/blog/2018.html b/v0.10.x/blog/2018.html
index 887d9be1f..ad7f09806 100644
--- a/v0.10.x/blog/2018.html
+++ b/v0.10.x/blog/2018.html
@@ -7,7 +7,7 @@
Posted in 2018 — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Posted in 2018 — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -43,7 +43,7 @@
https://fury.gl/
Blog - Posted in 2018
- 2024-08-23T18:53:30.765250+00:00
+ 2024-08-23T18:59:47.306892+00:00
ABlog
diff --git a/v0.10.x/blog/2019.html b/v0.10.x/blog/2019.html
index 326ce8ec3..dc94b78c8 100644
--- a/v0.10.x/blog/2019.html
+++ b/v0.10.x/blog/2019.html
@@ -7,7 +7,7 @@
Posted in 2019 — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Posted in 2019 — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -43,7 +43,7 @@
https://fury.gl/
Blog - Posted in 2019
- 2024-08-23T18:53:30.749442+00:00
+ 2024-08-23T18:59:47.291301+00:00
ABlog
diff --git a/v0.10.x/blog/2020.html b/v0.10.x/blog/2020.html
index 5b6a8e8b9..d5cf68002 100644
--- a/v0.10.x/blog/2020.html
+++ b/v0.10.x/blog/2020.html
@@ -7,7 +7,7 @@
Posted in 2020 — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Posted in 2020 — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -43,7 +43,7 @@
https://fury.gl/
Blog - Posted in 2020
- 2024-08-23T18:53:30.701449+00:00
+ 2024-08-23T18:59:47.242765+00:00
ABlog
diff --git a/v0.10.x/blog/2021.html b/v0.10.x/blog/2021.html
index d7886e920..e3babb58d 100644
--- a/v0.10.x/blog/2021.html
+++ b/v0.10.x/blog/2021.html
@@ -7,7 +7,7 @@
Posted in 2021 — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Posted in 2021 — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -43,7 +43,7 @@
https://fury.gl/
Blog - Posted in 2021
- 2024-08-23T18:53:30.637123+00:00
+ 2024-08-23T18:59:46.533481+00:00
ABlog
diff --git a/v0.10.x/blog/2022.html b/v0.10.x/blog/2022.html
index 6887416fc..39c863bc2 100644
--- a/v0.10.x/blog/2022.html
+++ b/v0.10.x/blog/2022.html
@@ -7,7 +7,7 @@
Posted in 2022 — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Posted in 2022 — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -43,7 +43,7 @@
https://fury.gl/
Blog - Posted in 2022
- 2024-08-23T18:53:30.609029+00:00
+ 2024-08-23T18:59:46.506351+00:00
ABlog
diff --git a/v0.10.x/blog/2023.html b/v0.10.x/blog/2023.html
index 856d0ba77..269c16afb 100644
--- a/v0.10.x/blog/2023.html
+++ b/v0.10.x/blog/2023.html
@@ -7,7 +7,7 @@
Posted in 2023 — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Posted in 2023 — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -43,7 +43,7 @@
https://fury.gl/
Blog - Posted in 2023
- 2024-08-23T18:53:30.528434+00:00
+ 2024-08-23T18:59:46.427102+00:00
ABlog
diff --git a/v0.10.x/blog/2024.html b/v0.10.x/blog/2024.html
index f66afa3f7..81820117e 100644
--- a/v0.10.x/blog/2024.html
+++ b/v0.10.x/blog/2024.html
@@ -7,7 +7,7 @@
Posted in 2024 — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Posted in 2024 — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -43,7 +43,7 @@
+
+
+
+
+
+
+ 15 August 2024
+
+
+
+
+
Hello everyone,
+welcome to the update for Week 11 of my Google Summer of Code (GSoC) 2024 journey. This week, I focused on finalizing the footer issue on the FURY
+
+
+
Read more ...
+
+
+
+
+
+
+
+ 15 August 2024
+
+
+
+
+
Welcome to the week 10 of my Google Summer of Code (GSoC) 2024 journey. This week, I focused on resolving an issue with the FURY
+
+
+
Read more ...
+
+
+
+
+
+
+
+ 13 August 2024
+
+
+
+
+
Hello everyone,
+welcome to my Google Summer of Code (GSoC) 2024 journey! Week 9 was devoted to fixing Sphinx warnings caused by indentation errors in some docstrings of some examples in the auto_examples FURY
+
+
+
Read more ...
+
+
WEEK 8: Refining Lazy Loading Implementation and Simplifying Imports in FURY
diff --git a/v0.10.x/blog/2024/atom.xml b/v0.10.x/blog/2024/atom.xml
index 7d81e801f..ebd672717 100644
--- a/v0.10.x/blog/2024/atom.xml
+++ b/v0.10.x/blog/2024/atom.xml
@@ -2,7 +2,7 @@
https://fury.gl/
Blog - Posted in 2024
- 2024-08-23T18:53:30.485619+00:00
+ 2024-08-23T18:59:46.390110+00:00
ABlog
@@ -333,6 +333,155 @@ All good things must come to an end, and it’s with a mixture of satisfaction a
2024-08-15T00:00:00+00:00
+
+ https://fury.gl/posts/2024/2024-08-15-week11-wachiou.html
+ WEEK 11: Resolving the Footer Issue and Addressing Sphinx Warnings
+ 2024-08-15T00:00:00+00:00
+
+ Wachiou BOURAIMA
+
+ <section id="week-11-resolving-the-footer-issue-and-addressing-sphinx-warnings">
+
+<p>Hello everyone,
+welcome to the update for Week 11 of my Google Summer of Code (GSoC) 2024 journey. This week, I focused on finalizing the footer issue on the <code class="docutils literal notranslate"><span class="pre">FURY</span></code> website and tackling some Sphinx warnings related to attribute and property naming conflicts. Here’s a detailed look at what I accomplished and the challenges faced.</p>
+<section id="fixing-the-footer-issue">
+<h2>Fixing the Footer Issue</h2>
+<p>In the previous week, I identified the root cause of the footer deformation. The problem arose when hovering over elements, which caused their size to increase, thereby affecting the padding of their container and subsequently the entire footer layout.
+To illustrate the issue and the resolution, I have included the following videos:</p>
+<p>Before Fixing the Footer Issue:
+Video demonstrating the footer deformation before the fix.</p>
+<iframe src="https://github.com/user-attachments/assets/2f5d4021-b661-4be9-944f-7a2638376f2c" width="640" height="390" frameborder="0" allowfullscreen></iframe><p>After Fixing the Footer Issue:
+Video showing the footer after applying the fix.</p>
+<iframe src="https://github.com/user-attachments/assets/b0ec74df-827b-4280-b3e4-bf968b97a654" width="640" height="390" frameborder="0" allowfullscreen></iframe><p>To address this, I experimented with different approaches. Initially, I tried adjusting the <cite>font-size</cite> of the elements on hover by making them bold instead. This resolved the deformation issue but did not align with the design specifications of the homepage footer.
+After reconsidering, I added some properties to the <code class="docutils literal notranslate"><span class="pre">.class-columns</span></code> in the <code class="docutils literal notranslate"><span class="pre">styles.css</span></code> file to better adapt the footer style and prevent any layout issues. This approach aimed to maintain the design integrity while addressing the layout problem effectively.</p>
+</section>
+<section id="handling-sphinx-warnings">
+<h2>Handling Sphinx Warnings</h2>
+<p>In addition to fixing the footer, I worked on resolving warnings caused by Sphinx due to naming conflicts between attributes and properties. To mitigate these warnings, I initially added <code class="docutils literal notranslate"><span class="pre">:no-index:</span></code> directives in the .rst files for functions and classes to prevent indexing issues.
+However, during our weekly meeting with my mentor <a class="reference external" href="https://github.com/skoudoro">Serge Koudoro</a>, it became clear that this solution might hinder the indexing and referencing of functions, modules, and classes on the <code class="docutils literal notranslate"><span class="pre">FURY</span></code> site and the web. Therefore, I need to re-evaluate the issue and find a more suitable solution that ensures proper indexing while addressing the warnings.</p>
+</section>
+<section id="did-i-get-stuck-anywhere">
+<h2>Did I Get Stuck Anywhere ?</h2>
+<p>While addressing the Sphinx warnings, I encountered some challenges related to the naming conflicts between attributes and properties. The warnings were triggered by the use of the same name for both an attribute and a property in the codebase. This conflict led to Sphinx warnings, which I am currently working to resolve. The complexity of this issue requires a more in-depth analysis to develop an appropriate solution that aligns with the project’s requirements and Sphinx guidelines.</p>
+</section>
+<section id="acknowledgements">
+<h2>Acknowledgements</h2>
+<aside class="system-message">
+<p class="system-message-title">System Message: INFO/1 (<span class="docutils literal">/home/runner/work/fury/fury/docs/source/posts/2024/2024-08-15-week11-wachiou.rst</span>, line 2); <em><a href="#id1">backlink</a></em></p>
+<p>Duplicate explicit target name: “serge koudoro”.</p>
+</aside>
+<p>I am deeply grateful to my peers <a class="reference external" href="https://github.com/itellaetxe">Iñigo Tellaetxe Elorriaga</a>, <a class="reference external" href="https://github.com/robinroy03">Robin Roy</a>, <a class="reference external" href="https://github.com/deka27">Kaustav Deka</a> for their continuous support and insightful suggestions. Special thanks to my mentor, <a class="reference external" href="https://github.com/skoudoro">Serge Koudoro</a> , whose expertise and guidance have been invaluable in navigating these technical challenges.</p>
+</section>
+<section id="whats-next">
+<h2>What’s Next ?</h2>
+<p>For the upcoming week, I plan to:</p>
+<ul class="simple">
+<li><p>Delve deeper into the Sphinx warnings related to attribute and property naming conflicts to develop a more appropriate solution.</p></li>
+<li><p>Continue to refine the footer styling to ensure it meets design specifications while maintaining functionality.</p></li>
+<li><p>Start writing my <cite>GSOC’2024</cite> final report.</p></li>
+</ul>
+<p>Thank you for following my progress. I look forward to sharing further updates and solutions in the coming weeks!</p>
+</section>
+</section>
+
+ Hello everyone,
+welcome to the update for Week 11 of my Google Summer of Code (GSoC) 2024 journey. This week, I focused on finalizing the footer issue on the FURY website and tackling some Sphinx warnings related to attribute and property naming conflicts. Here’s a detailed look at what I accomplished and the challenges faced.
+ 2024-08-15T00:00:00+00:00
+
+
+ https://fury.gl/posts/2024/2024-08-15-week10-wachiou.html
+ WEEK 10: Investigating Footer Deformation and Limited Progress on Warnings
+ 2024-08-15T00:00:00+00:00
+
+ Wachiou BOURAIMA
+
+ <section id="week-10-investigating-footer-deformation-and-limited-progress-on-warnings">
+
+<p>Welcome to the week 10 of my Google Summer of Code (GSoC) 2024 journey. This week, I focused on resolving an issue with the <code class="docutils literal notranslate"><span class="pre">FURY</span></code> website’s footer and made limited progress on fixing documentation warnings. Here’s a detailed overview of my activities and challenges.</p>
+<section id="investigating-footer-deformation-issue-874">
+<h2>Investigating Footer Deformation Issue: <a class="reference external" href="https://github.com/fury-gl/fury/issues/874">#874</a></h2>
+<p>During this week, I identified the root cause of the footer deformation on the FURY website. The problem arose when hovering over an element, which caused the element’s size to increase. This, in turn, increased the padding of its container and subsequently affected the layout of following elements.
+To address this, I initially considered avoiding changes in font size on hover and opted to make elements bold instead. While this approach resolved the deformation issue, it did not align with the design requirements for the homepage footer.
+Due to health constraints, I was unable to continue this work. I plan to explore alternative solutions to align with the design specifications in the upcoming week.</p>
+</section>
+<section id="limited-progress-on-documentation-warnings">
+<h2>Limited Progress on Documentation Warnings</h2>
+<p>I also aimed to make progress on fixing Sphinx warnings related to documentation typos. Unfortunately, I could not advance significantly in this area due to the time constraints imposed by the footer issue and my health.</p>
+</section>
+<section id="what-s-next">
+<h2>What’s Next ?</h2>
+<p>For week 11, I plan to:</p>
+<ul class="simple">
+<li><p>Explore alternative solutions to address the footer deformation issue while aligning with the design requirements.</p></li>
+<li><p>Continue fixing Sphinx warnings in the documentation and address any remaining issues.</p></li>
+</ul>
+</section>
+</section>
+
+ Welcome to the week 10 of my Google Summer of Code (GSoC) 2024 journey. This week, I focused on resolving an issue with the FURY website’s footer and made limited progress on fixing documentation warnings. Here’s a detailed overview of my activities and challenges.
+ 2024-08-15T00:00:00+00:00
+
+
+ https://fury.gl/posts/2024/2024-08-13-week9-wachiou.html
+ WEEK 9: Fixing Sphinx Warnings and Investigating Web Footer Issues
+ 2024-08-13T00:00:00+00:00
+
+ Wachiou BOURAIMA
+
+ <section id="week-9-fixing-sphinx-warnings-and-investigating-web-footer-issues">
+
+<p>Hello everyone,
+welcome to my Google Summer of Code (GSoC) 2024 journey! Week 9 was devoted to fixing Sphinx warnings caused by indentation errors in some docstrings of some examples in the <code class="docutils literal notranslate"><span class="pre">auto_examples</span></code> folder. I also started investigating why the footer of the <code class="docutils literal notranslate"><span class="pre">FURY</span></code> site distorts when you try to move the mouse over an element.</p>
+<section id="continuing-the-fight-against-sphinx-warnings">
+<h2>Continuing the Fight Against Sphinx Warnings</h2>
+<p>My main task this week has been to continue dealing with the Sphinx warnings in our documentation. I focused on the 188 warnings related to the main documentation, as well as 2 warnings in the blog posts.
+I fixed 19 warnings caused by the docstring of <code class="docutils literal notranslate"><span class="pre">viz_**.py</span></code> modules in the <code class="docutils literal notranslate"><span class="pre">source/auto_examples</span></code> folder
+by fixing the indentation errors in the docstrings of the examples.</p>
+<p>Here is an example of indentation error in the docstring of the example <code class="docutils literal notranslate"><span class="pre">auto_examples/04_demos/viz_animated_surfaces.py</span></code>:</p>
+<div class="highlight-python notranslate"><div class="highlight"><pre><span></span><span class="o">...</span> <span class="n">Code</span> <span class="n">block</span> <span class="o">...</span>
+
+<span class="c1">###############################################################################</span>
+<span class="c1"># Variables and their usage:</span>
+<span class="c1"># :time - float: initial value of the time variable i.e. value of the time variable at</span>
+<span class="c1"># the beginning of the program; (default = 0)</span>
+<span class="c1"># dt: float</span>
+<span class="c1"># amount by which ``time`` variable is incremented for every iteration</span>
+<span class="c1"># of timer_callback function (default = 0.1)</span>
+<span class="c1"># lower_xbound: float</span>
+
+<span class="o">...</span> <span class="n">Code</span> <span class="n">block</span> <span class="o">...</span>
+</pre></div>
+</div>
+</section>
+<section id="investigating-web-footer-issues">
+<h2>Investigating Web Footer Issues</h2>
+<p>In parallel, I started investigating an issue with the FURY website’s footer, which deforms when hovering over an element with the mouse. This problem affects the user experience and visual consistency of the site. My work this week has focused on diagnosing the underlying cause of this issue and planning the necessary steps to fix it. This task has been both technically intriguing and a great opportunity to sharpen my web development skills.</p>
+<p>issue number: <a class="reference external" href="https://github.com/fury-gl/fury/issues/874">#874</a></p>
+</section>
+<section id="did-i-get-stuck-anywhere">
+<h2>Did I get stuck anywhere ?</h2>
+<p>I encountered some challenges while fixing the indentation errors in the docstrings of the examples. The errors were caused by inconsistent indentation in the docstrings, which made it difficult to identify the root cause of the warnings. However, I was able to resolve these issues and make progress in addressing the Sphinx warnings.</p>
+</section>
+<section id="what-s-next">
+<h2>What’s next ?</h2>
+<p>For week 10, I plan to:</p>
+<ul class="simple">
+<li><p>Continue fixing the Sphinx warnings in the documentation.</p></li>
+<li><p>Start fixing the issue with the footer of the FURY website.</p></li>
+</ul>
+</section>
+</section>
+
+ Hello everyone,
+welcome to my Google Summer of Code (GSoC) 2024 journey! Week 9 was devoted to fixing Sphinx warnings caused by indentation errors in some docstrings of some examples in the auto_examples folder. I also started investigating why the footer of the FURY site distorts when you try to move the mouse over an element.
+ 2024-08-13T00:00:00+00:00
+
https://fury.gl/posts/2024/2024-08-12-week8-wachiou-bouraima.html
WEEK 8: Refining Lazy Loading Implementation and Simplifying Imports in FURY
@@ -418,221 +567,4 @@ Welcome back to another update on my GSoC 2024 journey. This week, my focus was
2024-08-06T00:00:00+00:00
-
- https://fury.gl/posts/2024/2024-08-06-week6-wachiou-bouraima.html
- WEEK 6: Code reviews, relining and crush challenges
- 2024-08-06T00:00:00+00:00
-
- Wachiou BOURAIMA
-
- <section id="week-6-code-reviews-relining-and-crush-challenges">
-
-<p>Hello everyone,
-As my Google Summer of Code (GSoC) 2024 journey progresses, week6 has brought me a series of technical challenges and accomplishments. My main focus has been on code reviews, rebasing and commits squashing, with a few notable lessons learned along the way.</p>
-<section id="code-reviews-and-merging-pull-requests">
-<h2>Code Reviews and Merging <code class="docutils literal notranslate"><span class="pre">Pull</span> <span class="pre">Requests</span></code></h2>
-<p>One of the main activities this week was receiving and addressing feedback on several of my pull requests. Notably, my mentor <a class="reference external" href="https://github.com/skoudoro/">Serge Koudoro</a>, reviewed and merged the PRs related to the <code class="docutils literal notranslate"><span class="pre">warn_on_args_to_kwargs</span></code> decorator and the application of the <code class="docutils literal notranslate"><span class="pre">warn_on_args_to_kwargs</span></code> decorator across various modules. The merging of these PRs was a critical step in ensuring that our codebase adhered to the project’s evolving standards for clarity and maintainability.</p>
-</section>
-<section id="rebasing-and-squashing-overcoming-challenges">
-<h2>Rebasing and Squashing: Overcoming Challenges</h2>
-<ul class="simple">
-<li><p>I performed rebasing and squashing to integrate the latest changes and consolidate commits. This process was challenging due to several conflicts that arose. Resolving these conflicts required a deep dive into Git’s functionality, including:</p>
-<ul>
-<li><p><strong>Conflict Resolution:</strong> Manually resolving merge conflicts that affected several files.</p></li>
-<li><p><strong>Understanding Git Operations:</strong> Gained hands-on experience with rebasing and squashing, which improved my grasp of version control workflows.</p></li>
-<li><p><strong>Commit Consolidation:</strong> multiple commits into a single commit to streamline the commit history and enhance readability.</p></li>
-</ul>
-</li>
-</ul>
-<p>Here are some of the Git commands I used during the rebasing and squashing process:</p>
-<div class="highlight-bash notranslate"><div class="highlight"><pre><span></span><span class="c1"># Rebase the branch onto the upstream/master branch</span>
-
-git<span class="w"> </span>rebase<span class="w"> </span>upstream/master<span class="w"> </span>-xtheirs
-
-<span class="c1"># Squash the last "n" commits into a single commit</span>
-git<span class="w"> </span>rebase<span class="w"> </span>-i<span class="w"> </span>HEAD~n
-
-<span class="c1"># Continue the rebase process after resolving conflicts</span>
-git<span class="w"> </span>rebase<span class="w"> </span>--continue
-
-git<span class="w"> </span>rebase<span class="w"> </span>--abort
-
-<span class="c1"># Amend the last commit with new changes</span>
-git<span class="w"> </span>commit<span class="w"> </span>--amend
-
-<span class="c1"># Push the changes to the remote repository</span>
-git<span class="w"> </span>push<span class="w"> </span>origin<span class="w"> </span>branch_name<span class="w"> </span>--force
-</pre></div>
-</div>
-<ul class="simple">
-<li><p>Merged PRs:</p>
-<ul>
-<li><p><cite>warn_on_args_to_kwargs</cite>: <a class="github reference external" href="https://github.com/fury-gl/fury/pull/888">fury-gl/fury#888</a></p></li>
-<li><p><cite>actors</cite>: <a class="github reference external" href="https://github.com/fury-gl/fury/pull/898">fury-gl/fury#898</a></p></li>
-<li><p><cite>animation</cite>: <a class="github reference external" href="https://github.com/fury-gl/fury/pull/899">fury-gl/fury#899</a></p></li>
-<li><p><cite>data</cite>: <a class="github reference external" href="https://github.com/fury-gl/fury/pull/900">fury-gl/fury#900</a></p></li>
-<li><p><cite>shares</cite>: <a class="github reference external" href="https://github.com/fury-gl/fury/pull/901">fury-gl/fury#901</a></p></li>
-<li><p><cite>ui</cite>: <a class="github reference external" href="https://github.com/fury-gl/fury/pull/902">fury-gl/fury#902</a></p></li>
-</ul>
-</li>
-</ul>
-</section>
-<section id="technical-insights-and-lessons-learned">
-<h2>Technical Insights and Lessons Learned</h2>
-<ul class="simple">
-<li><p><strong>Version Control Mastery:</strong> Through the rebasing and squashing process, I gained a deeper understanding of Git’s capabilities and the importance of maintaining a clean commit history.</p></li>
-</ul>
-</section>
-<section id="acknowledgements">
-<h2>Acknowledgements</h2>
-<p>I want to extend my thanks to my mentor <a class="reference external" href="https://github.com/skoudoro/">Serge Koudoro</a>, for his detailed feedback and guidance. Your support has been crucial in refining my work. I also appreciate the constructive comments from my peers: <a class="reference external" href="https://github.com/itellaetxe">Iñigo Tellaetxe Elorriaga</a>, <a class="reference external" href="https://github.com/robinroy03">Robin Roy</a>, <a class="reference external" href="https://github.com/deka27">Kaustav Deka</a>, which have been instrumental in improving the quality of my contributions.</p>
-</section>
-<section id="did-i-get-stuck-anywhere">
-<h2>Did I get stuck anywhere?</h2>
-<p>While the rebasing and squashing process presented challenges, I was able to overcome them with the help of my mentor <a class="reference external" href="https://github.com/skoudoro">Serge Koudoro</a> and online resources and documentation.</p>
-<ul class="simple">
-<li><p><a class="reference external" href="https://www.git-tower.com/learn/git/faq/git-squash">How to Squash Commits in Git</a></p></li>
-<li><p><a class="reference external" href="https://dev.to/tariqabughofa/git-theirs-vs-ours-3i7h">Git: Theirs vs Ours</a></p></li>
-<li><p><a class="reference external" href="https://youtu.be/AWayLpQHJeE?si=I-fRM0H3icvm9ua8">How to squash and rebase in git</a></p></li>
-</ul>
-<p>The experience has enhanced my Git proficiency and prepared me for future code management tasks.</p>
-</section>
-<section id="what-s-next">
-<h2>What’s next ?</h2>
-<p>In the week 7, I plan to:</p>
-<ol class="arabic simple">
-<li><p>Review Adjustments: I’ll be reviewing the feedback provided by my mentor <a class="reference external" href="https://github.com/skoudoro/">Serge Koudoro</a>, on the latest changes to ensure that everything meets <code class="docutils literal notranslate"><span class="pre">FURY</span></code>’s coding standards.</p></li>
-<li><p>Finalizing Lazy Loading: Once the reviews are completed and approved, my mentor <a class="reference external" href="https://github.com/skoudoro/">Serge Koudoro</a>, will merge the PR related to the lazy loading implementation. This will mark a significant milestone in optimizing the FURY codebase.</p></li>
-<li><p>Sphinx Warning Fixes: I will start addressing Sphinx warnings related to typos in the blog posts to improve the documentation quality.</p></li>
-</ol>
-</section>
-</section>
-
- Hello everyone,
-As my Google Summer of Code (GSoC) 2024 journey progresses, week6 has brought me a series of technical challenges and accomplishments. My main focus has been on code reviews, rebasing and commits squashing, with a few notable lessons learned along the way.
- 2024-08-06T00:00:00+00:00
-
-
- https://fury.gl/posts/2024/2024-07-31-release-announcement.html
- FURY 0.11.0 Released
- 2024-07-31T00:00:00+00:00
-
- Serge Koudoro
-
- <section id="fury-0-11-0-released">
-
-<p>The FURY project is happy to announce the release of FURY 0.11.0!
-FURY is a free and open source software library for scientific visualization and 3D animations.</p>
-<p>You can show your support by <a class="reference external" href="https://github.com/fury-gl/fury/stargazers">adding a star</a> on FURY github project.</p>
-<p>This Release is mainly a maintenance release. The <strong>major highlights</strong> of this release are:</p>
-<ul class="simple">
-<li><p>New SPEC: Keyword-only adopted.</p></li>
-<li><p>New SPEC: Lazy loading adopted.</p></li>
-<li><p>New standard for coding style.</p></li>
-<li><p>Documentation updated.</p></li>
-<li><p>Website updated.</p></li>
-</ul>
-<div class="admonition note">
-<p class="admonition-title">Note</p>
-<p>The complete release notes are available <a class="reference internal" href="../release_notes/releasev0.11.0.html#releasev0-11-0"><span class="std std-ref">here</span></a></p>
-</div>
-<p><strong>To upgrade or install FURY</strong></p>
-<p>Run the following command in your terminal:</p>
-<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">pip</span> <span class="n">install</span> <span class="o">--</span><span class="n">upgrade</span> <span class="n">fury</span>
-</pre></div>
-</div>
-<p>or:</p>
-<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">conda</span> <span class="n">install</span> <span class="o">-</span><span class="n">c</span> <span class="n">conda</span><span class="o">-</span><span class="n">forge</span> <span class="n">fury</span>
-</pre></div>
-</div>
-<p><strong>Questions or suggestions?</strong></p>
-<p>For any questions go to <a class="reference external" href="http://fury.gl">http://fury.gl</a>, or send an e-mail to <a class="reference external" href="mailto:fury%40python.org">fury<span>@</span>python<span>.</span>org</a>
-We can also join our <a class="reference external" href="https://discord.gg/6btFPPj">discord community</a></p>
-<p>We would like to thanks to <a class="reference internal" href="../community.html#community"><span class="std std-ref">all contributors</span></a> for this release:</p>
-<ul class="simple">
-<li><p>Ishan Kamboj</p></li>
-<li><p>Jon Haitz Legarreta Gorroño</p></li>
-<li><p>Kaustav Deka</p></li>
-<li><p>Robin Roy</p></li>
-<li><p>Serge Koudoro</p></li>
-<li><p>Wachiou BOURAÏMA</p></li>
-<li><p>dependabot[bot]</p></li>
-</ul>
-<p>On behalf of the <a class="reference internal" href="../community.html#community"><span class="std std-ref">FURY developers</span></a>,</p>
-<p>Serge K.</p>
-</section>
-
- The FURY project is happy to announce the release of FURY 0.11.0!
-FURY is a free and open source software library for scientific visualization and 3D animations.
- 2024-07-31T00:00:00+00:00
-
-
- https://fury.gl/posts/2024/2024-07-27-week8-robin.html
- Week 8: Gemini Finetuning
- 2024-07-27T00:00:00+00:00
-
- Robin Roy
-
- <section id="week-8-gemini-finetuning">
-
-<p>Hi, I’m <a class="reference external" href="https://github.com/robinroy03">Robin</a> and this is my blog about week 8.</p>
-<p>This week I worked on finalizing the Discord chat QnA data collection and using it to Fine-Tune the Gemini-1.0-Pro model.</p>
-<section id="things-i-did-in-week-8">
-<h2>Things I did in Week 8</h2>
-<ol class="arabic simple">
-<li><p><strong>Discord Data Collection</strong></p></li>
-</ol>
-<p>I finished collecting data from all the channels in the Discord server, cross-verifying to check whether they still work. I also added some questions which were on the FURY bot testing server. These QnA pairs were later converted to a CSV with input/output pairs and fed to Gemini for finetuning.</p>
-<ol class="arabic simple" start="2">
-<li><p><strong>Gemini Finetuning</strong></p></li>
-</ol>
-<aside class="system-message">
-<p class="system-message-title">System Message: INFO/1 (<span class="docutils literal">/home/runner/work/fury/fury/docs/source/posts/2024/2024-07-27-week8-robin.rst</span>, line 2)</p>
-<p>Enumerated list start value not ordinal-1: “2” (ordinal 2)</p>
-</aside>
-<p>Finetuning is essentially training the model on the input/output. RAG is giving context and asking the model to form an answer using that. Finetuning updates the model weights as per the input/output. Gemini uses <a class="reference external" href="https://huggingface.co/blog/peft">Parameter-Efficient Fine-Tuning</a> in AI Studio as per some reports. It makes sense because the tuning only takes minutes and PEFT is a good strategy to prevent issues like <a class="reference external" href="https://arxiv.org/abs/1312.6211">catastrophic forgetting</a>.</p>
-<p>Finetuning and RAG are complementary to each other. The difference between them can be summarized as follows:</p>
-<p>RAG is like giving an LLM with no prior knowledge about FURY access to some important functions/classes as per the user prompt. It’ll use this given context and its knowledge of graphics libraries (knowledge from pretraining) to form an answer.</p>
-<p>Finetuning is used to make the model follow a certain style or behaviour. It is a form of mimicking the input-output. This will help in increasing the model’s performance. An interesting thing is I had to train the model 1) with RAG and 2) without RAG.</p>
-<p>For finetuning, the input must be in the format the LLM will get the answer from the user. When you ask a question to the FURY bot, the bot does not get your question directly. We are processing it to add additional information. Therefore I had to process all the collected data with RAG.</p>
-<p>This is an interesting direction, and I have a lot of cool things to try out here. I’ll spend the next few weeks trying different ideas.</p>
-</section>
-<section id="what-is-coming-up-next-week">
-<h2>What is coming up next week?</h2>
-<ul class="simple">
-<li><p>Finetuning strategies.</p></li>
-<li><p>Hosting the model on API.</p></li>
-</ul>
-</section>
-<section id="did-you-get-stuck-anywhere">
-<h2>Did you get stuck anywhere?</h2>
-<p>No, I did not get stuck anywhere.</p>
-<p>LINKS:</p>
-<ul>
-<li><aside class="system-message">
-<p class="system-message-title">System Message: INFO/1 (<span class="docutils literal">/home/runner/work/fury/fury/docs/source/posts/2024/2024-07-27-week8-robin.rst</span>, line 2); <em><a href="#id1">backlink</a></em></p>
-<p>Duplicate explicit target name: “parameter-efficient fine-tuning”.</p>
-</aside>
-<p><a class="reference external" href="https://huggingface.co/blog/peft">Parameter-Efficient Fine-Tuning</a></p>
-</li>
-<li><aside class="system-message">
-<p class="system-message-title">System Message: INFO/1 (<span class="docutils literal">/home/runner/work/fury/fury/docs/source/posts/2024/2024-07-27-week8-robin.rst</span>, line 2); <em><a href="#id2">backlink</a></em></p>
-<p>Duplicate explicit target name: “catastrophic forgetting”.</p>
-</aside>
-<p><a class="reference external" href="https://arxiv.org/abs/1312.6211">catastrophic forgetting</a></p>
-</li>
-</ul>
-<p>Thank you for reading!</p>
-</section>
-</section>
-
- Hi, I’m Robin and this is my blog about week 8.
- 2024-07-27T00:00:00+00:00
-
diff --git a/v0.10.x/blog/archive.html b/v0.10.x/blog/archive.html
index a669fa1ae..b6df6a3d7 100644
--- a/v0.10.x/blog/archive.html
+++ b/v0.10.x/blog/archive.html
@@ -7,7 +7,7 @@
All posts — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ All posts — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -43,7 +43,7 @@
+
+
+
+
+
+
diff --git a/v0.10.x/blog/atom.xml b/v0.10.x/blog/atom.xml
index 0afa05280..be80ac23e 100644
--- a/v0.10.x/blog/atom.xml
+++ b/v0.10.x/blog/atom.xml
@@ -2,7 +2,7 @@
https://fury.gl/
Blog
- 2024-08-23T18:53:29.766566+00:00
+ 2024-08-23T18:59:45.684859+00:00
ABlog
@@ -333,6 +333,155 @@ All good things must come to an end, and it’s with a mixture of satisfaction a
2024-08-15T00:00:00+00:00
+
+ https://fury.gl/posts/2024/2024-08-15-week11-wachiou.html
+ WEEK 11: Resolving the Footer Issue and Addressing Sphinx Warnings
+ 2024-08-15T00:00:00+00:00
+
+ Wachiou BOURAIMA
+
+ <section id="week-11-resolving-the-footer-issue-and-addressing-sphinx-warnings">
+
+<p>Hello everyone,
+welcome to the update for Week 11 of my Google Summer of Code (GSoC) 2024 journey. This week, I focused on finalizing the footer issue on the <code class="docutils literal notranslate"><span class="pre">FURY</span></code> website and tackling some Sphinx warnings related to attribute and property naming conflicts. Here’s a detailed look at what I accomplished and the challenges faced.</p>
+<section id="fixing-the-footer-issue">
+<h2>Fixing the Footer Issue</h2>
+<p>In the previous week, I identified the root cause of the footer deformation. The problem arose when hovering over elements, which caused their size to increase, thereby affecting the padding of their container and subsequently the entire footer layout.
+To illustrate the issue and the resolution, I have included the following videos:</p>
+<p>Before Fixing the Footer Issue:
+Video demonstrating the footer deformation before the fix.</p>
+<iframe src="https://github.com/user-attachments/assets/2f5d4021-b661-4be9-944f-7a2638376f2c" width="640" height="390" frameborder="0" allowfullscreen></iframe><p>After Fixing the Footer Issue:
+Video showing the footer after applying the fix.</p>
+<iframe src="https://github.com/user-attachments/assets/b0ec74df-827b-4280-b3e4-bf968b97a654" width="640" height="390" frameborder="0" allowfullscreen></iframe><p>To address this, I experimented with different approaches. Initially, I tried adjusting the <cite>font-size</cite> of the elements on hover by making them bold instead. This resolved the deformation issue but did not align with the design specifications of the homepage footer.
+After reconsidering, I added some properties to the <code class="docutils literal notranslate"><span class="pre">.class-columns</span></code> in the <code class="docutils literal notranslate"><span class="pre">styles.css</span></code> file to better adapt the footer style and prevent any layout issues. This approach aimed to maintain the design integrity while addressing the layout problem effectively.</p>
+</section>
+<section id="handling-sphinx-warnings">
+<h2>Handling Sphinx Warnings</h2>
+<p>In addition to fixing the footer, I worked on resolving warnings caused by Sphinx due to naming conflicts between attributes and properties. To mitigate these warnings, I initially added <code class="docutils literal notranslate"><span class="pre">:no-index:</span></code> directives in the .rst files for functions and classes to prevent indexing issues.
+However, during our weekly meeting with my mentor <a class="reference external" href="https://github.com/skoudoro">Serge Koudoro</a>, it became clear that this solution might hinder the indexing and referencing of functions, modules, and classes on the <code class="docutils literal notranslate"><span class="pre">FURY</span></code> site and the web. Therefore, I need to re-evaluate the issue and find a more suitable solution that ensures proper indexing while addressing the warnings.</p>
+</section>
+<section id="did-i-get-stuck-anywhere">
+<h2>Did I Get Stuck Anywhere ?</h2>
+<p>While addressing the Sphinx warnings, I encountered some challenges related to the naming conflicts between attributes and properties. The warnings were triggered by the use of the same name for both an attribute and a property in the codebase. This conflict led to Sphinx warnings, which I am currently working to resolve. The complexity of this issue requires a more in-depth analysis to develop an appropriate solution that aligns with the project’s requirements and Sphinx guidelines.</p>
+</section>
+<section id="acknowledgements">
+<h2>Acknowledgements</h2>
+<aside class="system-message">
+<p class="system-message-title">System Message: INFO/1 (<span class="docutils literal">/home/runner/work/fury/fury/docs/source/posts/2024/2024-08-15-week11-wachiou.rst</span>, line 2); <em><a href="#id1">backlink</a></em></p>
+<p>Duplicate explicit target name: “serge koudoro”.</p>
+</aside>
+<p>I am deeply grateful to my peers <a class="reference external" href="https://github.com/itellaetxe">Iñigo Tellaetxe Elorriaga</a>, <a class="reference external" href="https://github.com/robinroy03">Robin Roy</a>, <a class="reference external" href="https://github.com/deka27">Kaustav Deka</a> for their continuous support and insightful suggestions. Special thanks to my mentor, <a class="reference external" href="https://github.com/skoudoro">Serge Koudoro</a> , whose expertise and guidance have been invaluable in navigating these technical challenges.</p>
+</section>
+<section id="whats-next">
+<h2>What’s Next ?</h2>
+<p>For the upcoming week, I plan to:</p>
+<ul class="simple">
+<li><p>Delve deeper into the Sphinx warnings related to attribute and property naming conflicts to develop a more appropriate solution.</p></li>
+<li><p>Continue to refine the footer styling to ensure it meets design specifications while maintaining functionality.</p></li>
+<li><p>Start writing my <cite>GSOC’2024</cite> final report.</p></li>
+</ul>
+<p>Thank you for following my progress. I look forward to sharing further updates and solutions in the coming weeks!</p>
+</section>
+</section>
+
+ Hello everyone,
+welcome to the update for Week 11 of my Google Summer of Code (GSoC) 2024 journey. This week, I focused on finalizing the footer issue on the FURY website and tackling some Sphinx warnings related to attribute and property naming conflicts. Here’s a detailed look at what I accomplished and the challenges faced.
+ 2024-08-15T00:00:00+00:00
+
+
+ https://fury.gl/posts/2024/2024-08-15-week10-wachiou.html
+ WEEK 10: Investigating Footer Deformation and Limited Progress on Warnings
+ 2024-08-15T00:00:00+00:00
+
+ Wachiou BOURAIMA
+
+ <section id="week-10-investigating-footer-deformation-and-limited-progress-on-warnings">
+
+<p>Welcome to the week 10 of my Google Summer of Code (GSoC) 2024 journey. This week, I focused on resolving an issue with the <code class="docutils literal notranslate"><span class="pre">FURY</span></code> website’s footer and made limited progress on fixing documentation warnings. Here’s a detailed overview of my activities and challenges.</p>
+<section id="investigating-footer-deformation-issue-874">
+<h2>Investigating Footer Deformation Issue: <a class="reference external" href="https://github.com/fury-gl/fury/issues/874">#874</a></h2>
+<p>During this week, I identified the root cause of the footer deformation on the FURY website. The problem arose when hovering over an element, which caused the element’s size to increase. This, in turn, increased the padding of its container and subsequently affected the layout of following elements.
+To address this, I initially considered avoiding changes in font size on hover and opted to make elements bold instead. While this approach resolved the deformation issue, it did not align with the design requirements for the homepage footer.
+Due to health constraints, I was unable to continue this work. I plan to explore alternative solutions to align with the design specifications in the upcoming week.</p>
+</section>
+<section id="limited-progress-on-documentation-warnings">
+<h2>Limited Progress on Documentation Warnings</h2>
+<p>I also aimed to make progress on fixing Sphinx warnings related to documentation typos. Unfortunately, I could not advance significantly in this area due to the time constraints imposed by the footer issue and my health.</p>
+</section>
+<section id="what-s-next">
+<h2>What’s Next ?</h2>
+<p>For week 11, I plan to:</p>
+<ul class="simple">
+<li><p>Explore alternative solutions to address the footer deformation issue while aligning with the design requirements.</p></li>
+<li><p>Continue fixing Sphinx warnings in the documentation and address any remaining issues.</p></li>
+</ul>
+</section>
+</section>
+
+ Welcome to the week 10 of my Google Summer of Code (GSoC) 2024 journey. This week, I focused on resolving an issue with the FURY website’s footer and made limited progress on fixing documentation warnings. Here’s a detailed overview of my activities and challenges.
+ 2024-08-15T00:00:00+00:00
+
+
+ https://fury.gl/posts/2024/2024-08-13-week9-wachiou.html
+ WEEK 9: Fixing Sphinx Warnings and Investigating Web Footer Issues
+ 2024-08-13T00:00:00+00:00
+
+ Wachiou BOURAIMA
+
+ <section id="week-9-fixing-sphinx-warnings-and-investigating-web-footer-issues">
+
+<p>Hello everyone,
+welcome to my Google Summer of Code (GSoC) 2024 journey! Week 9 was devoted to fixing Sphinx warnings caused by indentation errors in some docstrings of some examples in the <code class="docutils literal notranslate"><span class="pre">auto_examples</span></code> folder. I also started investigating why the footer of the <code class="docutils literal notranslate"><span class="pre">FURY</span></code> site distorts when you try to move the mouse over an element.</p>
+<section id="continuing-the-fight-against-sphinx-warnings">
+<h2>Continuing the Fight Against Sphinx Warnings</h2>
+<p>My main task this week has been to continue dealing with the Sphinx warnings in our documentation. I focused on the 188 warnings related to the main documentation, as well as 2 warnings in the blog posts.
+I fixed 19 warnings caused by the docstring of <code class="docutils literal notranslate"><span class="pre">viz_**.py</span></code> modules in the <code class="docutils literal notranslate"><span class="pre">source/auto_examples</span></code> folder
+by fixing the indentation errors in the docstrings of the examples.</p>
+<p>Here is an example of indentation error in the docstring of the example <code class="docutils literal notranslate"><span class="pre">auto_examples/04_demos/viz_animated_surfaces.py</span></code>:</p>
+<div class="highlight-python notranslate"><div class="highlight"><pre><span></span><span class="o">...</span> <span class="n">Code</span> <span class="n">block</span> <span class="o">...</span>
+
+<span class="c1">###############################################################################</span>
+<span class="c1"># Variables and their usage:</span>
+<span class="c1"># :time - float: initial value of the time variable i.e. value of the time variable at</span>
+<span class="c1"># the beginning of the program; (default = 0)</span>
+<span class="c1"># dt: float</span>
+<span class="c1"># amount by which ``time`` variable is incremented for every iteration</span>
+<span class="c1"># of timer_callback function (default = 0.1)</span>
+<span class="c1"># lower_xbound: float</span>
+
+<span class="o">...</span> <span class="n">Code</span> <span class="n">block</span> <span class="o">...</span>
+</pre></div>
+</div>
+</section>
+<section id="investigating-web-footer-issues">
+<h2>Investigating Web Footer Issues</h2>
+<p>In parallel, I started investigating an issue with the FURY website’s footer, which deforms when hovering over an element with the mouse. This problem affects the user experience and visual consistency of the site. My work this week has focused on diagnosing the underlying cause of this issue and planning the necessary steps to fix it. This task has been both technically intriguing and a great opportunity to sharpen my web development skills.</p>
+<p>issue number: <a class="reference external" href="https://github.com/fury-gl/fury/issues/874">#874</a></p>
+</section>
+<section id="did-i-get-stuck-anywhere">
+<h2>Did I get stuck anywhere ?</h2>
+<p>I encountered some challenges while fixing the indentation errors in the docstrings of the examples. The errors were caused by inconsistent indentation in the docstrings, which made it difficult to identify the root cause of the warnings. However, I was able to resolve these issues and make progress in addressing the Sphinx warnings.</p>
+</section>
+<section id="what-s-next">
+<h2>What’s next ?</h2>
+<p>For week 10, I plan to:</p>
+<ul class="simple">
+<li><p>Continue fixing the Sphinx warnings in the documentation.</p></li>
+<li><p>Start fixing the issue with the footer of the FURY website.</p></li>
+</ul>
+</section>
+</section>
+
+ Hello everyone,
+welcome to my Google Summer of Code (GSoC) 2024 journey! Week 9 was devoted to fixing Sphinx warnings caused by indentation errors in some docstrings of some examples in the auto_examples folder. I also started investigating why the footer of the FURY site distorts when you try to move the mouse over an element.
+ 2024-08-13T00:00:00+00:00
+
https://fury.gl/posts/2024/2024-08-12-week8-wachiou-bouraima.html
WEEK 8: Refining Lazy Loading Implementation and Simplifying Imports in FURY
@@ -418,221 +567,4 @@ Welcome back to another update on my GSoC 2024 journey. This week, my focus was
2024-08-06T00:00:00+00:00
-
- https://fury.gl/posts/2024/2024-08-06-week6-wachiou-bouraima.html
- WEEK 6: Code reviews, relining and crush challenges
- 2024-08-06T00:00:00+00:00
-
- Wachiou BOURAIMA
-
- <section id="week-6-code-reviews-relining-and-crush-challenges">
-
-<p>Hello everyone,
-As my Google Summer of Code (GSoC) 2024 journey progresses, week6 has brought me a series of technical challenges and accomplishments. My main focus has been on code reviews, rebasing and commits squashing, with a few notable lessons learned along the way.</p>
-<section id="code-reviews-and-merging-pull-requests">
-<h2>Code Reviews and Merging <code class="docutils literal notranslate"><span class="pre">Pull</span> <span class="pre">Requests</span></code></h2>
-<p>One of the main activities this week was receiving and addressing feedback on several of my pull requests. Notably, my mentor <a class="reference external" href="https://github.com/skoudoro/">Serge Koudoro</a>, reviewed and merged the PRs related to the <code class="docutils literal notranslate"><span class="pre">warn_on_args_to_kwargs</span></code> decorator and the application of the <code class="docutils literal notranslate"><span class="pre">warn_on_args_to_kwargs</span></code> decorator across various modules. The merging of these PRs was a critical step in ensuring that our codebase adhered to the project’s evolving standards for clarity and maintainability.</p>
-</section>
-<section id="rebasing-and-squashing-overcoming-challenges">
-<h2>Rebasing and Squashing: Overcoming Challenges</h2>
-<ul class="simple">
-<li><p>I performed rebasing and squashing to integrate the latest changes and consolidate commits. This process was challenging due to several conflicts that arose. Resolving these conflicts required a deep dive into Git’s functionality, including:</p>
-<ul>
-<li><p><strong>Conflict Resolution:</strong> Manually resolving merge conflicts that affected several files.</p></li>
-<li><p><strong>Understanding Git Operations:</strong> Gained hands-on experience with rebasing and squashing, which improved my grasp of version control workflows.</p></li>
-<li><p><strong>Commit Consolidation:</strong> multiple commits into a single commit to streamline the commit history and enhance readability.</p></li>
-</ul>
-</li>
-</ul>
-<p>Here are some of the Git commands I used during the rebasing and squashing process:</p>
-<div class="highlight-bash notranslate"><div class="highlight"><pre><span></span><span class="c1"># Rebase the branch onto the upstream/master branch</span>
-
-git<span class="w"> </span>rebase<span class="w"> </span>upstream/master<span class="w"> </span>-xtheirs
-
-<span class="c1"># Squash the last "n" commits into a single commit</span>
-git<span class="w"> </span>rebase<span class="w"> </span>-i<span class="w"> </span>HEAD~n
-
-<span class="c1"># Continue the rebase process after resolving conflicts</span>
-git<span class="w"> </span>rebase<span class="w"> </span>--continue
-
-git<span class="w"> </span>rebase<span class="w"> </span>--abort
-
-<span class="c1"># Amend the last commit with new changes</span>
-git<span class="w"> </span>commit<span class="w"> </span>--amend
-
-<span class="c1"># Push the changes to the remote repository</span>
-git<span class="w"> </span>push<span class="w"> </span>origin<span class="w"> </span>branch_name<span class="w"> </span>--force
-</pre></div>
-</div>
-<ul class="simple">
-<li><p>Merged PRs:</p>
-<ul>
-<li><p><cite>warn_on_args_to_kwargs</cite>: <a class="github reference external" href="https://github.com/fury-gl/fury/pull/888">fury-gl/fury#888</a></p></li>
-<li><p><cite>actors</cite>: <a class="github reference external" href="https://github.com/fury-gl/fury/pull/898">fury-gl/fury#898</a></p></li>
-<li><p><cite>animation</cite>: <a class="github reference external" href="https://github.com/fury-gl/fury/pull/899">fury-gl/fury#899</a></p></li>
-<li><p><cite>data</cite>: <a class="github reference external" href="https://github.com/fury-gl/fury/pull/900">fury-gl/fury#900</a></p></li>
-<li><p><cite>shares</cite>: <a class="github reference external" href="https://github.com/fury-gl/fury/pull/901">fury-gl/fury#901</a></p></li>
-<li><p><cite>ui</cite>: <a class="github reference external" href="https://github.com/fury-gl/fury/pull/902">fury-gl/fury#902</a></p></li>
-</ul>
-</li>
-</ul>
-</section>
-<section id="technical-insights-and-lessons-learned">
-<h2>Technical Insights and Lessons Learned</h2>
-<ul class="simple">
-<li><p><strong>Version Control Mastery:</strong> Through the rebasing and squashing process, I gained a deeper understanding of Git’s capabilities and the importance of maintaining a clean commit history.</p></li>
-</ul>
-</section>
-<section id="acknowledgements">
-<h2>Acknowledgements</h2>
-<p>I want to extend my thanks to my mentor <a class="reference external" href="https://github.com/skoudoro/">Serge Koudoro</a>, for his detailed feedback and guidance. Your support has been crucial in refining my work. I also appreciate the constructive comments from my peers: <a class="reference external" href="https://github.com/itellaetxe">Iñigo Tellaetxe Elorriaga</a>, <a class="reference external" href="https://github.com/robinroy03">Robin Roy</a>, <a class="reference external" href="https://github.com/deka27">Kaustav Deka</a>, which have been instrumental in improving the quality of my contributions.</p>
-</section>
-<section id="did-i-get-stuck-anywhere">
-<h2>Did I get stuck anywhere?</h2>
-<p>While the rebasing and squashing process presented challenges, I was able to overcome them with the help of my mentor <a class="reference external" href="https://github.com/skoudoro">Serge Koudoro</a> and online resources and documentation.</p>
-<ul class="simple">
-<li><p><a class="reference external" href="https://www.git-tower.com/learn/git/faq/git-squash">How to Squash Commits in Git</a></p></li>
-<li><p><a class="reference external" href="https://dev.to/tariqabughofa/git-theirs-vs-ours-3i7h">Git: Theirs vs Ours</a></p></li>
-<li><p><a class="reference external" href="https://youtu.be/AWayLpQHJeE?si=I-fRM0H3icvm9ua8">How to squash and rebase in git</a></p></li>
-</ul>
-<p>The experience has enhanced my Git proficiency and prepared me for future code management tasks.</p>
-</section>
-<section id="what-s-next">
-<h2>What’s next ?</h2>
-<p>In the week 7, I plan to:</p>
-<ol class="arabic simple">
-<li><p>Review Adjustments: I’ll be reviewing the feedback provided by my mentor <a class="reference external" href="https://github.com/skoudoro/">Serge Koudoro</a>, on the latest changes to ensure that everything meets <code class="docutils literal notranslate"><span class="pre">FURY</span></code>’s coding standards.</p></li>
-<li><p>Finalizing Lazy Loading: Once the reviews are completed and approved, my mentor <a class="reference external" href="https://github.com/skoudoro/">Serge Koudoro</a>, will merge the PR related to the lazy loading implementation. This will mark a significant milestone in optimizing the FURY codebase.</p></li>
-<li><p>Sphinx Warning Fixes: I will start addressing Sphinx warnings related to typos in the blog posts to improve the documentation quality.</p></li>
-</ol>
-</section>
-</section>
-
- Hello everyone,
-As my Google Summer of Code (GSoC) 2024 journey progresses, week6 has brought me a series of technical challenges and accomplishments. My main focus has been on code reviews, rebasing and commits squashing, with a few notable lessons learned along the way.
- 2024-08-06T00:00:00+00:00
-
-
- https://fury.gl/posts/2024/2024-07-31-release-announcement.html
- FURY 0.11.0 Released
- 2024-07-31T00:00:00+00:00
-
- Serge Koudoro
-
- <section id="fury-0-11-0-released">
-
-<p>The FURY project is happy to announce the release of FURY 0.11.0!
-FURY is a free and open source software library for scientific visualization and 3D animations.</p>
-<p>You can show your support by <a class="reference external" href="https://github.com/fury-gl/fury/stargazers">adding a star</a> on FURY github project.</p>
-<p>This Release is mainly a maintenance release. The <strong>major highlights</strong> of this release are:</p>
-<ul class="simple">
-<li><p>New SPEC: Keyword-only adopted.</p></li>
-<li><p>New SPEC: Lazy loading adopted.</p></li>
-<li><p>New standard for coding style.</p></li>
-<li><p>Documentation updated.</p></li>
-<li><p>Website updated.</p></li>
-</ul>
-<div class="admonition note">
-<p class="admonition-title">Note</p>
-<p>The complete release notes are available <a class="reference internal" href="release_notes/releasev0.11.0.html#releasev0-11-0"><span class="std std-ref">here</span></a></p>
-</div>
-<p><strong>To upgrade or install FURY</strong></p>
-<p>Run the following command in your terminal:</p>
-<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">pip</span> <span class="n">install</span> <span class="o">--</span><span class="n">upgrade</span> <span class="n">fury</span>
-</pre></div>
-</div>
-<p>or:</p>
-<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">conda</span> <span class="n">install</span> <span class="o">-</span><span class="n">c</span> <span class="n">conda</span><span class="o">-</span><span class="n">forge</span> <span class="n">fury</span>
-</pre></div>
-</div>
-<p><strong>Questions or suggestions?</strong></p>
-<p>For any questions go to <a class="reference external" href="http://fury.gl">http://fury.gl</a>, or send an e-mail to <a class="reference external" href="mailto:fury%40python.org">fury<span>@</span>python<span>.</span>org</a>
-We can also join our <a class="reference external" href="https://discord.gg/6btFPPj">discord community</a></p>
-<p>We would like to thanks to <a class="reference internal" href="community.html#community"><span class="std std-ref">all contributors</span></a> for this release:</p>
-<ul class="simple">
-<li><p>Ishan Kamboj</p></li>
-<li><p>Jon Haitz Legarreta Gorroño</p></li>
-<li><p>Kaustav Deka</p></li>
-<li><p>Robin Roy</p></li>
-<li><p>Serge Koudoro</p></li>
-<li><p>Wachiou BOURAÏMA</p></li>
-<li><p>dependabot[bot]</p></li>
-</ul>
-<p>On behalf of the <a class="reference internal" href="community.html#community"><span class="std std-ref">FURY developers</span></a>,</p>
-<p>Serge K.</p>
-</section>
-
- The FURY project is happy to announce the release of FURY 0.11.0!
-FURY is a free and open source software library for scientific visualization and 3D animations.
- 2024-07-31T00:00:00+00:00
-
-
- https://fury.gl/posts/2024/2024-07-27-week8-robin.html
- Week 8: Gemini Finetuning
- 2024-07-27T00:00:00+00:00
-
- Robin Roy
-
- <section id="week-8-gemini-finetuning">
-
-<p>Hi, I’m <a class="reference external" href="https://github.com/robinroy03">Robin</a> and this is my blog about week 8.</p>
-<p>This week I worked on finalizing the Discord chat QnA data collection and using it to Fine-Tune the Gemini-1.0-Pro model.</p>
-<section id="things-i-did-in-week-8">
-<h2>Things I did in Week 8</h2>
-<ol class="arabic simple">
-<li><p><strong>Discord Data Collection</strong></p></li>
-</ol>
-<p>I finished collecting data from all the channels in the Discord server, cross-verifying to check whether they still work. I also added some questions which were on the FURY bot testing server. These QnA pairs were later converted to a CSV with input/output pairs and fed to Gemini for finetuning.</p>
-<ol class="arabic simple" start="2">
-<li><p><strong>Gemini Finetuning</strong></p></li>
-</ol>
-<aside class="system-message">
-<p class="system-message-title">System Message: INFO/1 (<span class="docutils literal">/home/runner/work/fury/fury/docs/source/posts/2024/2024-07-27-week8-robin.rst</span>, line 2)</p>
-<p>Enumerated list start value not ordinal-1: “2” (ordinal 2)</p>
-</aside>
-<p>Finetuning is essentially training the model on the input/output. RAG is giving context and asking the model to form an answer using that. Finetuning updates the model weights as per the input/output. Gemini uses <a class="reference external" href="https://huggingface.co/blog/peft">Parameter-Efficient Fine-Tuning</a> in AI Studio as per some reports. It makes sense because the tuning only takes minutes and PEFT is a good strategy to prevent issues like <a class="reference external" href="https://arxiv.org/abs/1312.6211">catastrophic forgetting</a>.</p>
-<p>Finetuning and RAG are complementary to each other. The difference between them can be summarized as follows:</p>
-<p>RAG is like giving an LLM with no prior knowledge about FURY access to some important functions/classes as per the user prompt. It’ll use this given context and its knowledge of graphics libraries (knowledge from pretraining) to form an answer.</p>
-<p>Finetuning is used to make the model follow a certain style or behaviour. It is a form of mimicking the input-output. This will help in increasing the model’s performance. An interesting thing is I had to train the model 1) with RAG and 2) without RAG.</p>
-<p>For finetuning, the input must be in the format the LLM will get the answer from the user. When you ask a question to the FURY bot, the bot does not get your question directly. We are processing it to add additional information. Therefore I had to process all the collected data with RAG.</p>
-<p>This is an interesting direction, and I have a lot of cool things to try out here. I’ll spend the next few weeks trying different ideas.</p>
-</section>
-<section id="what-is-coming-up-next-week">
-<h2>What is coming up next week?</h2>
-<ul class="simple">
-<li><p>Finetuning strategies.</p></li>
-<li><p>Hosting the model on API.</p></li>
-</ul>
-</section>
-<section id="did-you-get-stuck-anywhere">
-<h2>Did you get stuck anywhere?</h2>
-<p>No, I did not get stuck anywhere.</p>
-<p>LINKS:</p>
-<ul>
-<li><aside class="system-message">
-<p class="system-message-title">System Message: INFO/1 (<span class="docutils literal">/home/runner/work/fury/fury/docs/source/posts/2024/2024-07-27-week8-robin.rst</span>, line 2); <em><a href="#id1">backlink</a></em></p>
-<p>Duplicate explicit target name: “parameter-efficient fine-tuning”.</p>
-</aside>
-<p><a class="reference external" href="https://huggingface.co/blog/peft">Parameter-Efficient Fine-Tuning</a></p>
-</li>
-<li><aside class="system-message">
-<p class="system-message-title">System Message: INFO/1 (<span class="docutils literal">/home/runner/work/fury/fury/docs/source/posts/2024/2024-07-27-week8-robin.rst</span>, line 2); <em><a href="#id2">backlink</a></em></p>
-<p>Duplicate explicit target name: “catastrophic forgetting”.</p>
-</aside>
-<p><a class="reference external" href="https://arxiv.org/abs/1312.6211">catastrophic forgetting</a></p>
-</li>
-</ul>
-<p>Thank you for reading!</p>
-</section>
-</section>
-
- Hi, I’m Robin and this is my blog about week 8.
- 2024-07-27T00:00:00+00:00
-
diff --git a/v0.10.x/blog/author.html b/v0.10.x/blog/author.html
index 560a24a56..893ac7f11 100644
--- a/v0.10.x/blog/author.html
+++ b/v0.10.x/blog/author.html
@@ -7,7 +7,7 @@
-
Authors — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+
Authors — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -43,7 +43,7 @@
-
+
@@ -2547,6 +2547,42 @@
+
+
+
+
+
+
diff --git a/v0.10.x/blog/author/antriksh-misri.html b/v0.10.x/blog/author/antriksh-misri.html
index e0fd61acf..9bb531266 100644
--- a/v0.10.x/blog/author/antriksh-misri.html
+++ b/v0.10.x/blog/author/antriksh-misri.html
@@ -7,7 +7,7 @@
-
Posts by Antriksh Misri — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+
Posts by Antriksh Misri — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -43,7 +43,7 @@
-
+
diff --git a/v0.10.x/blog/author/antriksh-misri/atom.xml b/v0.10.x/blog/author/antriksh-misri/atom.xml
index 42d7b80a1..5edd9cb1d 100644
--- a/v0.10.x/blog/author/antriksh-misri/atom.xml
+++ b/v0.10.x/blog/author/antriksh-misri/atom.xml
@@ -2,7 +2,7 @@
https://fury.gl/
Blog - Posts by Antriksh Misri
- 2024-08-23T18:53:29.809352+00:00
+ 2024-08-23T18:59:45.723487+00:00
ABlog
diff --git a/v0.10.x/blog/author/bruno-messias.html b/v0.10.x/blog/author/bruno-messias.html
index 76b841504..f6904bfc9 100644
--- a/v0.10.x/blog/author/bruno-messias.html
+++ b/v0.10.x/blog/author/bruno-messias.html
@@ -7,7 +7,7 @@
Posts by Bruno Messias — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Posts by Bruno Messias — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -43,7 +43,7 @@
https://fury.gl/
Blog - Posts by Bruno Messias
- 2024-08-23T18:53:29.846691+00:00
+ 2024-08-23T18:59:45.761276+00:00
ABlog
diff --git a/v0.10.x/blog/author/joao-victor-dell-agli-floriano.html b/v0.10.x/blog/author/joao-victor-dell-agli-floriano.html
index 125b8041e..bea7e48d6 100644
--- a/v0.10.x/blog/author/joao-victor-dell-agli-floriano.html
+++ b/v0.10.x/blog/author/joao-victor-dell-agli-floriano.html
@@ -7,7 +7,7 @@
Posts by João Victor Dell Agli Floriano — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Posts by João Victor Dell Agli Floriano — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -43,7 +43,7 @@
https://fury.gl/
Blog - Posts by João Victor Dell Agli Floriano
- 2024-08-23T18:53:29.904762+00:00
+ 2024-08-23T18:59:45.815263+00:00
ABlog
diff --git a/v0.10.x/blog/author/lenix-lobo.html b/v0.10.x/blog/author/lenix-lobo.html
index c38a4dfc3..f47230dc0 100644
--- a/v0.10.x/blog/author/lenix-lobo.html
+++ b/v0.10.x/blog/author/lenix-lobo.html
@@ -7,7 +7,7 @@
Posts by Lenix Lobo — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Posts by Lenix Lobo — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -43,7 +43,7 @@
https://fury.gl/
Blog - Posts by Lenix Lobo
- 2024-08-23T18:53:29.966136+00:00
+ 2024-08-23T18:59:45.876623+00:00
ABlog
diff --git a/v0.10.x/blog/author/mohamed-abouagour.html b/v0.10.x/blog/author/mohamed-abouagour.html
index 180894594..effac544f 100644
--- a/v0.10.x/blog/author/mohamed-abouagour.html
+++ b/v0.10.x/blog/author/mohamed-abouagour.html
@@ -7,7 +7,7 @@
Posts by Mohamed Abouagour — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Posts by Mohamed Abouagour — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -43,7 +43,7 @@
https://fury.gl/
Blog - Posts by Mohamed Abouagour
- 2024-08-23T18:53:29.994784+00:00
+ 2024-08-23T18:59:45.905343+00:00
ABlog
diff --git a/v0.10.x/blog/author/praneeth-shetty.html b/v0.10.x/blog/author/praneeth-shetty.html
index bcae78df0..6d7c1e558 100644
--- a/v0.10.x/blog/author/praneeth-shetty.html
+++ b/v0.10.x/blog/author/praneeth-shetty.html
@@ -7,7 +7,7 @@
Posts by Praneeth Shetty — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Posts by Praneeth Shetty — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -43,7 +43,7 @@
https://fury.gl/
Blog - Posts by Praneeth Shetty
- 2024-08-23T18:53:30.042085+00:00
+ 2024-08-23T18:59:45.951789+00:00
ABlog
diff --git a/v0.10.x/blog/author/robin-roy.html b/v0.10.x/blog/author/robin-roy.html
index c9cd1d32d..8731ae6ad 100644
--- a/v0.10.x/blog/author/robin-roy.html
+++ b/v0.10.x/blog/author/robin-roy.html
@@ -7,7 +7,7 @@
Posts by Robin Roy — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Posts by Robin Roy — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -43,7 +43,7 @@
https://fury.gl/
Blog - Posts by Robin Roy
- 2024-08-23T18:53:30.085432+00:00
+ 2024-08-23T18:59:45.994126+00:00
ABlog
diff --git a/v0.10.x/blog/author/sajag-swami.html b/v0.10.x/blog/author/sajag-swami.html
index 0c6f6eea7..ab6e6be83 100644
--- a/v0.10.x/blog/author/sajag-swami.html
+++ b/v0.10.x/blog/author/sajag-swami.html
@@ -7,7 +7,7 @@
Posts by Sajag Swami — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Posts by Sajag Swami — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -43,7 +43,7 @@
https://fury.gl/
Blog - Posts by Sajag Swami
- 2024-08-23T18:53:30.130714+00:00
+ 2024-08-23T18:59:46.039269+00:00
ABlog
diff --git a/v0.10.x/blog/author/serge-koudoro.html b/v0.10.x/blog/author/serge-koudoro.html
index 426f304d7..fecc0a8b4 100644
--- a/v0.10.x/blog/author/serge-koudoro.html
+++ b/v0.10.x/blog/author/serge-koudoro.html
@@ -7,7 +7,7 @@
Posts by Serge Koudoro — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Posts by Serge Koudoro — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -43,7 +43,7 @@
https://fury.gl/
Blog - Posts by Serge Koudoro
- 2024-08-23T18:53:30.346812+00:00
+ 2024-08-23T18:59:46.254026+00:00
ABlog
diff --git a/v0.10.x/blog/author/shivam-anand.html b/v0.10.x/blog/author/shivam-anand.html
index 37f2b2fd8..2566f2d66 100644
--- a/v0.10.x/blog/author/shivam-anand.html
+++ b/v0.10.x/blog/author/shivam-anand.html
@@ -7,7 +7,7 @@
Posts by Shivam Anand — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Posts by Shivam Anand — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -43,7 +43,7 @@
https://fury.gl/
Blog - Posts by Shivam Anand
- 2024-08-23T18:53:30.168816+00:00
+ 2024-08-23T18:59:46.077182+00:00
ABlog
diff --git a/v0.10.x/blog/author/shivam-sahu.html b/v0.10.x/blog/author/shivam-sahu.html
index 838720554..5efeaf8b1 100644
--- a/v0.10.x/blog/author/shivam-sahu.html
+++ b/v0.10.x/blog/author/shivam-sahu.html
@@ -7,7 +7,7 @@
Posts by Shivam Sahu — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Posts by Shivam Sahu — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -43,7 +43,7 @@
https://fury.gl/
Blog - Posts by Shivam Sahu
- 2024-08-23T18:53:30.209667+00:00
+ 2024-08-23T18:59:46.117814+00:00
ABlog
diff --git a/v0.10.x/blog/author/soham-biswas.html b/v0.10.x/blog/author/soham-biswas.html
index b267e73cf..15c3a7361 100644
--- a/v0.10.x/blog/author/soham-biswas.html
+++ b/v0.10.x/blog/author/soham-biswas.html
@@ -7,7 +7,7 @@
Posts by Soham Biswas — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Posts by Soham Biswas — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -43,7 +43,7 @@
https://fury.gl/
Blog - Posts by Soham Biswas
- 2024-08-23T18:53:30.213916+00:00
+ 2024-08-23T18:59:46.122004+00:00
ABlog
diff --git a/v0.10.x/blog/author/tania-castillo.html b/v0.10.x/blog/author/tania-castillo.html
index 2dc0615a0..54a084b09 100644
--- a/v0.10.x/blog/author/tania-castillo.html
+++ b/v0.10.x/blog/author/tania-castillo.html
@@ -7,7 +7,7 @@
Posts by Tania Castillo — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Posts by Tania Castillo — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -43,7 +43,7 @@
https://fury.gl/
Blog - Posts by Tania Castillo
- 2024-08-23T18:53:30.260221+00:00
+ 2024-08-23T18:59:46.167783+00:00
ABlog
diff --git a/v0.10.x/blog/author/wachiou-bouraima.html b/v0.10.x/blog/author/wachiou-bouraima.html
index ccc837ee3..9041318b9 100644
--- a/v0.10.x/blog/author/wachiou-bouraima.html
+++ b/v0.10.x/blog/author/wachiou-bouraima.html
@@ -7,7 +7,7 @@
Posts by Wachiou BOURAIMA — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Posts by Wachiou BOURAIMA — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -43,7 +43,7 @@
+
+
+
+
+
+
+ 15 August 2024
+
+
+
+
+
Hello everyone,
+welcome to the update for Week 11 of my Google Summer of Code (GSoC) 2024 journey. This week, I focused on finalizing the footer issue on the FURY
+
+
+
Read more ...
+
+
+
+
+
+
+
+ 15 August 2024
+
+
+
+
+
Welcome to the week 10 of my Google Summer of Code (GSoC) 2024 journey. This week, I focused on resolving an issue with the FURY
+
+
+
Read more ...
+
+
+
+
+
+
+
+ 13 August 2024
+
+
+
+
+
Hello everyone,
+welcome to my Google Summer of Code (GSoC) 2024 journey! Week 9 was devoted to fixing Sphinx warnings caused by indentation errors in some docstrings of some examples in the auto_examples FURY
+
+
+
Read more ...
+
+
WEEK 8: Refining Lazy Loading Implementation and Simplifying Imports in FURY
diff --git a/v0.10.x/blog/author/wachiou-bouraima/atom.xml b/v0.10.x/blog/author/wachiou-bouraima/atom.xml
index a82f0c2be..c40c583d0 100644
--- a/v0.10.x/blog/author/wachiou-bouraima/atom.xml
+++ b/v0.10.x/blog/author/wachiou-bouraima/atom.xml
@@ -2,7 +2,7 @@
https://fury.gl/
Blog - Posts by Wachiou BOURAIMA
- 2024-08-23T18:53:30.297623+00:00
+ 2024-08-23T18:59:46.204567+00:00
ABlog
@@ -98,6 +98,155 @@ All good things must come to an end, and it’s with a mixture of satisfaction a
2024-08-17T00:00:00+00:00
+
+ https://fury.gl/posts/2024/2024-08-15-week11-wachiou.html
+ WEEK 11: Resolving the Footer Issue and Addressing Sphinx Warnings
+ 2024-08-15T00:00:00+00:00
+
+ Wachiou BOURAIMA
+
+ <section id="week-11-resolving-the-footer-issue-and-addressing-sphinx-warnings">
+
+<p>Hello everyone,
+welcome to the update for Week 11 of my Google Summer of Code (GSoC) 2024 journey. This week, I focused on finalizing the footer issue on the <code class="docutils literal notranslate"><span class="pre">FURY</span></code> website and tackling some Sphinx warnings related to attribute and property naming conflicts. Here’s a detailed look at what I accomplished and the challenges faced.</p>
+<section id="fixing-the-footer-issue">
+<h2>Fixing the Footer Issue</h2>
+<p>In the previous week, I identified the root cause of the footer deformation. The problem arose when hovering over elements, which caused their size to increase, thereby affecting the padding of their container and subsequently the entire footer layout.
+To illustrate the issue and the resolution, I have included the following videos:</p>
+<p>Before Fixing the Footer Issue:
+Video demonstrating the footer deformation before the fix.</p>
+<iframe src="https://github.com/user-attachments/assets/2f5d4021-b661-4be9-944f-7a2638376f2c" width="640" height="390" frameborder="0" allowfullscreen></iframe><p>After Fixing the Footer Issue:
+Video showing the footer after applying the fix.</p>
+<iframe src="https://github.com/user-attachments/assets/b0ec74df-827b-4280-b3e4-bf968b97a654" width="640" height="390" frameborder="0" allowfullscreen></iframe><p>To address this, I experimented with different approaches. Initially, I tried adjusting the <cite>font-size</cite> of the elements on hover by making them bold instead. This resolved the deformation issue but did not align with the design specifications of the homepage footer.
+After reconsidering, I added some properties to the <code class="docutils literal notranslate"><span class="pre">.class-columns</span></code> in the <code class="docutils literal notranslate"><span class="pre">styles.css</span></code> file to better adapt the footer style and prevent any layout issues. This approach aimed to maintain the design integrity while addressing the layout problem effectively.</p>
+</section>
+<section id="handling-sphinx-warnings">
+<h2>Handling Sphinx Warnings</h2>
+<p>In addition to fixing the footer, I worked on resolving warnings caused by Sphinx due to naming conflicts between attributes and properties. To mitigate these warnings, I initially added <code class="docutils literal notranslate"><span class="pre">:no-index:</span></code> directives in the .rst files for functions and classes to prevent indexing issues.
+However, during our weekly meeting with my mentor <a class="reference external" href="https://github.com/skoudoro">Serge Koudoro</a>, it became clear that this solution might hinder the indexing and referencing of functions, modules, and classes on the <code class="docutils literal notranslate"><span class="pre">FURY</span></code> site and the web. Therefore, I need to re-evaluate the issue and find a more suitable solution that ensures proper indexing while addressing the warnings.</p>
+</section>
+<section id="did-i-get-stuck-anywhere">
+<h2>Did I Get Stuck Anywhere ?</h2>
+<p>While addressing the Sphinx warnings, I encountered some challenges related to the naming conflicts between attributes and properties. The warnings were triggered by the use of the same name for both an attribute and a property in the codebase. This conflict led to Sphinx warnings, which I am currently working to resolve. The complexity of this issue requires a more in-depth analysis to develop an appropriate solution that aligns with the project’s requirements and Sphinx guidelines.</p>
+</section>
+<section id="acknowledgements">
+<h2>Acknowledgements</h2>
+<aside class="system-message">
+<p class="system-message-title">System Message: INFO/1 (<span class="docutils literal">/home/runner/work/fury/fury/docs/source/posts/2024/2024-08-15-week11-wachiou.rst</span>, line 2); <em><a href="#id1">backlink</a></em></p>
+<p>Duplicate explicit target name: “serge koudoro”.</p>
+</aside>
+<p>I am deeply grateful to my peers <a class="reference external" href="https://github.com/itellaetxe">Iñigo Tellaetxe Elorriaga</a>, <a class="reference external" href="https://github.com/robinroy03">Robin Roy</a>, <a class="reference external" href="https://github.com/deka27">Kaustav Deka</a> for their continuous support and insightful suggestions. Special thanks to my mentor, <a class="reference external" href="https://github.com/skoudoro">Serge Koudoro</a> , whose expertise and guidance have been invaluable in navigating these technical challenges.</p>
+</section>
+<section id="whats-next">
+<h2>What’s Next ?</h2>
+<p>For the upcoming week, I plan to:</p>
+<ul class="simple">
+<li><p>Delve deeper into the Sphinx warnings related to attribute and property naming conflicts to develop a more appropriate solution.</p></li>
+<li><p>Continue to refine the footer styling to ensure it meets design specifications while maintaining functionality.</p></li>
+<li><p>Start writing my <cite>GSOC’2024</cite> final report.</p></li>
+</ul>
+<p>Thank you for following my progress. I look forward to sharing further updates and solutions in the coming weeks!</p>
+</section>
+</section>
+
+ Hello everyone,
+welcome to the update for Week 11 of my Google Summer of Code (GSoC) 2024 journey. This week, I focused on finalizing the footer issue on the FURY website and tackling some Sphinx warnings related to attribute and property naming conflicts. Here’s a detailed look at what I accomplished and the challenges faced.
+ 2024-08-15T00:00:00+00:00
+
+
+ https://fury.gl/posts/2024/2024-08-15-week10-wachiou.html
+ WEEK 10: Investigating Footer Deformation and Limited Progress on Warnings
+ 2024-08-15T00:00:00+00:00
+
+ Wachiou BOURAIMA
+
+ <section id="week-10-investigating-footer-deformation-and-limited-progress-on-warnings">
+
+<p>Welcome to the week 10 of my Google Summer of Code (GSoC) 2024 journey. This week, I focused on resolving an issue with the <code class="docutils literal notranslate"><span class="pre">FURY</span></code> website’s footer and made limited progress on fixing documentation warnings. Here’s a detailed overview of my activities and challenges.</p>
+<section id="investigating-footer-deformation-issue-874">
+<h2>Investigating Footer Deformation Issue: <a class="reference external" href="https://github.com/fury-gl/fury/issues/874">#874</a></h2>
+<p>During this week, I identified the root cause of the footer deformation on the FURY website. The problem arose when hovering over an element, which caused the element’s size to increase. This, in turn, increased the padding of its container and subsequently affected the layout of following elements.
+To address this, I initially considered avoiding changes in font size on hover and opted to make elements bold instead. While this approach resolved the deformation issue, it did not align with the design requirements for the homepage footer.
+Due to health constraints, I was unable to continue this work. I plan to explore alternative solutions to align with the design specifications in the upcoming week.</p>
+</section>
+<section id="limited-progress-on-documentation-warnings">
+<h2>Limited Progress on Documentation Warnings</h2>
+<p>I also aimed to make progress on fixing Sphinx warnings related to documentation typos. Unfortunately, I could not advance significantly in this area due to the time constraints imposed by the footer issue and my health.</p>
+</section>
+<section id="what-s-next">
+<h2>What’s Next ?</h2>
+<p>For week 11, I plan to:</p>
+<ul class="simple">
+<li><p>Explore alternative solutions to address the footer deformation issue while aligning with the design requirements.</p></li>
+<li><p>Continue fixing Sphinx warnings in the documentation and address any remaining issues.</p></li>
+</ul>
+</section>
+</section>
+
+ Welcome to the week 10 of my Google Summer of Code (GSoC) 2024 journey. This week, I focused on resolving an issue with the FURY website’s footer and made limited progress on fixing documentation warnings. Here’s a detailed overview of my activities and challenges.
+ 2024-08-15T00:00:00+00:00
+
+
+ https://fury.gl/posts/2024/2024-08-13-week9-wachiou.html
+ WEEK 9: Fixing Sphinx Warnings and Investigating Web Footer Issues
+ 2024-08-13T00:00:00+00:00
+
+ Wachiou BOURAIMA
+
+ <section id="week-9-fixing-sphinx-warnings-and-investigating-web-footer-issues">
+
+<p>Hello everyone,
+welcome to my Google Summer of Code (GSoC) 2024 journey! Week 9 was devoted to fixing Sphinx warnings caused by indentation errors in some docstrings of some examples in the <code class="docutils literal notranslate"><span class="pre">auto_examples</span></code> folder. I also started investigating why the footer of the <code class="docutils literal notranslate"><span class="pre">FURY</span></code> site distorts when you try to move the mouse over an element.</p>
+<section id="continuing-the-fight-against-sphinx-warnings">
+<h2>Continuing the Fight Against Sphinx Warnings</h2>
+<p>My main task this week has been to continue dealing with the Sphinx warnings in our documentation. I focused on the 188 warnings related to the main documentation, as well as 2 warnings in the blog posts.
+I fixed 19 warnings caused by the docstring of <code class="docutils literal notranslate"><span class="pre">viz_**.py</span></code> modules in the <code class="docutils literal notranslate"><span class="pre">source/auto_examples</span></code> folder
+by fixing the indentation errors in the docstrings of the examples.</p>
+<p>Here is an example of indentation error in the docstring of the example <code class="docutils literal notranslate"><span class="pre">auto_examples/04_demos/viz_animated_surfaces.py</span></code>:</p>
+<div class="highlight-python notranslate"><div class="highlight"><pre><span></span><span class="o">...</span> <span class="n">Code</span> <span class="n">block</span> <span class="o">...</span>
+
+<span class="c1">###############################################################################</span>
+<span class="c1"># Variables and their usage:</span>
+<span class="c1"># :time - float: initial value of the time variable i.e. value of the time variable at</span>
+<span class="c1"># the beginning of the program; (default = 0)</span>
+<span class="c1"># dt: float</span>
+<span class="c1"># amount by which ``time`` variable is incremented for every iteration</span>
+<span class="c1"># of timer_callback function (default = 0.1)</span>
+<span class="c1"># lower_xbound: float</span>
+
+<span class="o">...</span> <span class="n">Code</span> <span class="n">block</span> <span class="o">...</span>
+</pre></div>
+</div>
+</section>
+<section id="investigating-web-footer-issues">
+<h2>Investigating Web Footer Issues</h2>
+<p>In parallel, I started investigating an issue with the FURY website’s footer, which deforms when hovering over an element with the mouse. This problem affects the user experience and visual consistency of the site. My work this week has focused on diagnosing the underlying cause of this issue and planning the necessary steps to fix it. This task has been both technically intriguing and a great opportunity to sharpen my web development skills.</p>
+<p>issue number: <a class="reference external" href="https://github.com/fury-gl/fury/issues/874">#874</a></p>
+</section>
+<section id="did-i-get-stuck-anywhere">
+<h2>Did I get stuck anywhere ?</h2>
+<p>I encountered some challenges while fixing the indentation errors in the docstrings of the examples. The errors were caused by inconsistent indentation in the docstrings, which made it difficult to identify the root cause of the warnings. However, I was able to resolve these issues and make progress in addressing the Sphinx warnings.</p>
+</section>
+<section id="what-s-next">
+<h2>What’s next ?</h2>
+<p>For week 10, I plan to:</p>
+<ul class="simple">
+<li><p>Continue fixing the Sphinx warnings in the documentation.</p></li>
+<li><p>Start fixing the issue with the footer of the FURY website.</p></li>
+</ul>
+</section>
+</section>
+
+ Hello everyone,
+welcome to my Google Summer of Code (GSoC) 2024 journey! Week 9 was devoted to fixing Sphinx warnings caused by indentation errors in some docstrings of some examples in the auto_examples folder. I also started investigating why the footer of the FURY site distorts when you try to move the mouse over an element.
+ 2024-08-13T00:00:00+00:00
+
https://fury.gl/posts/2024/2024-08-12-week8-wachiou-bouraima.html
WEEK 8: Refining Lazy Loading Implementation and Simplifying Imports in FURY
@@ -608,156 +757,4 @@ focusing on the consistent application of the warn_on_args_to_kwargs decorator a
2024-06-26T00:00:00+00:00
-
- https://fury.gl/posts/2024/2024-06-15-week2-wachiou-bouraima.html
- WEEK 2: Refinements and Further Enhancements
- 2024-06-15T00:00:00+00:00
-
- Wachiou BOURAIMA
-
- <section id="week-2-refinements-and-further-enhancements">
-
-<section id="hello-again">
-<h2>Hello again,</h2>
-<p>Welcome back to my Google Summer of Code (GSoC) 2024 journey! This week has been dedicated to refining and improving the work done so far, with a particular focus on the keyword_only decorator.</p>
-</section>
-<section id="renaming-and-updating-the-decorator">
-<h2>Renaming and Updating the Decorator</h2>
-<p>This week, I’ve updated <a class="reference external" href="https://github.com/fury-gl/fury/pull/888">this Pull Request</a> by renaming the <code class="docutils literal notranslate"><span class="pre">keyword_only</span></code> decorator to <code class="docutils literal notranslate"><span class="pre">warn_on_args_to_kwargs</span></code> for greater clarity. The updated decorator now includes version parameters from_version and until_version. This enhancement ensures that the decorator will raise a RuntimeError if the current version of FURY is greater than until_version.</p>
-</section>
-<section id="peer-code-review">
-<h2>Peer Code Review</h2>
-<p>I also spent time reviewing <a class="reference external" href="https://github.com/deka27">Kaustav Deka’s</a> code. This exercise remains rewarding, as it helps me understand different coding styles and approaches. Constructive feedback and suggestions from my classmates were invaluable, not only in helping my teammates but also in improving my own coding and reviewing skills.</p>
-</section>
-<section id="research-into-lazy-loading">
-<h2>Research into lazy loading</h2>
-<p>In parallel, I started researching the lazy loading feature and thinking about how to implement it. This feature will optimize performance by loading resources only when they’re needed, which is crucial to improving the efficiency of FURY’s code base.</p>
-</section>
-<section id="acknowledgements">
-<h2>Acknowledgements</h2>
-<p>I am deeply grateful to my classmates <a class="reference external" href="https://github.com/itellaetxe">Iñigo Tellaetxe Elorriaga</a>, <a class="reference external" href="https://github.com/robinroy03">Robin Roy</a>, and <a class="reference external" href="https://github.com/deka27">Kaustav Deka</a> for their insightful suggestions and comments on my work.
-Special thanks to my mentor, <a class="reference external" href="https://github.com//skoudoro">Serge Koudoro</a>, whose guidance and support enabled me to meet the challenges of this project.
-Their combined efforts have greatly contributed to my progress, and I appreciate their continued help.</p>
-</section>
-<section id="what-happens-next">
-<h2>What happens next?</h2>
-<p>For week 3, I plan to :</p>
-<ul class="simple">
-<li><p>Ensure that the <code class="docutils literal notranslate"><span class="pre">warn_on_args_to_kwargs</span></code> decorator is applied consistently in all necessary functions.</p></li>
-<li><p>Continue to update the calling of these functions in the code to maintain consistency and avoid warnings.</p></li>
-<li><p>Refine decorator as necessary based on feedback and testing.</p></li>
-<li><p>Start implementing lazy loading functionality based on my research to optimize performance.</p></li>
-</ul>
-<p>🥰 Thank you for taking the time to follow my progress. Your feedback is always welcome and I look forward to sharing more updates with you next week.</p>
-</section>
-</section>
-
- Welcome back to my Google Summer of Code (GSoC) 2024 journey! This week has been dedicated to refining and improving the work done so far, with a particular focus on the keyword_only decorator.
- 2024-06-15T00:00:00+00:00
-
-
- https://fury.gl/posts/2024/2024-06-06-week1-wachiou-bouraima.html
- WEEK 1: Progress and challenges at Google Summer of Code (GSoC) 2024
- 2024-06-06T00:00:00+00:00
-
- Wachiou BOURAIMA
-
- <section id="week-1-progress-and-challenges-at-google-summer-of-code-gsoc-2024">
-
-<p>Hello👋🏾,</p>
-<p>Welcome back to my Google Summer of Code (GSoC) 2024 journey!
-This week has been filled with progress and challenges as I continue to work on modernizing the FURY code base.</p>
-<section id="applying-the-keyword-only-decorator">
-<h2>Applying the keyword_only decorator</h2>
-<p>My main task this week was to apply the keyword_only decorator to several functions.
-The decorator ensures that all arguments except the first are keyword-only,
-which helps to make the code clearer and parameter passing more explicit.
-Some warnings appeared after applying this decorator, and to resolve them,
-I updated all the code where these functions were called with the necessary format. This was a very important step in maintaining the integrity and functionality of the code base.</p>
-</section>
-<section id="managing-the-challenges-of-git-rebasing">
-<h2>Managing the challenges of Git rebasing</h2>
-<p>Rebasing the branch I was working on was the other major activity of my week.
-It was a real challenge because of the conflicts that arose and had to be resolved.
-It involved a lot of research and problem-solving on how to resolve these conflicts,
-which greatly enhanced my understanding of Git. It was a challenging but satisfying experience of version control management and complex mergers.</p>
-</section>
-<section id="peer-code-review">
-<h2>Peer code review</h2>
-<p>In addition to my duties, I was also tasked with reviewing the code of my peers.
-This exercise was very rewarding, as it enabled me to understand different coding styles and approaches.
-The constructive comments and suggestions were beneficial not only for teammates,
-but also for improving my own coding and reviewing skills.</p>
-</section>
-<section id="acknowledgements">
-<h2>Acknowledgements</h2>
-<p>I would like to thank all my classmates: <a class="reference external" href="https://github.com/itellaetxe">Iñigo Tellaetxe Elorriaga</a>, <a class="reference external" href="https://github.com/robinroy03">Robin Roy</a>, <a class="reference external" href="https://github.com/deka27">Kaustav Deka</a> and my guide: <a class="reference external" href="https://github.com//skoudoro">Serge Koudoro</a> for their constructive suggestions on my work.
-Their ideas and suggestions were of great help to me and I am grateful for their support and advice.</p>
-</section>
-<section id="what-happens-next">
-<h2>What happens next?</h2>
-<p>Here’s a summary of what I plan to do in week two:</p>
-<ul class="simple">
-<li><p>Apply the keyword_only decorator to all other necessary functions.</p></li>
-<li><p>Update the calling of these functions in the code to ensure consistency and avoid raising warnings.</p></li>
-<li><p>Rename the decorator with a more descriptive name.</p></li>
-<li><p>Add two parameters to the decorator, specifying from which version of FURY it will work.</p></li>
-</ul>
-<p>🥰Thanks for reading! Your comments are most welcome, and I look forward to giving you a sneak preview of my work next week.</p>
-</section>
-</section>
-
- Hello👋🏾,
- 2024-06-06T00:00:00+00:00
-
-
- https://fury.gl/posts/2024/2024-05-28-first-post-wachiou-bouraima.html
- WEEK 0: The beginning of my journey in Google Summer of Code (GSoC) 2024
- 2024-05-28T00:00:00+00:00
-
- Wachiou BOURAIMA
-
- <section id="week-0-the-beginning-of-my-journey-in-google-summer-of-code-gsoc-2024">
-
-<section id="here-we-go">
-<h2>Here we go…..</h2>
-<div class="line-block">
-<div class="line">Hello and welcome to my GSoC 24 journey, I’m Wachiou Bouraima pronounced (Wasiu Ibrahima).</div>
-<div class="line"><br /></div>
-<div class="line">First of all, I’d like to express my deep gratitude for this immense opportunity.</div>
-<div class="line">In this first article, yes you read “first article” correctly, as it won’t be the only one, I’m going to share with you my first adventures in GSoC’24. Happy read</div>
-</div>
-</section>
-<section id="welcome-and-integration-into-the-community">
-<h2>Welcome and integration into the community.</h2>
-<p>Like any good start, this week I have the incredible opportunity to be welcomed into the community by the Core Team and my Mentor himself, during this session the Mentors welcomed us warmly and also congratulated us. They shared with us the rules respected during and after the GSoC program. This session made me feel comfortable and confident.</p>
-<p>I also have to admit that the mentors are experienced and willing to share their knowledge, which I really appreciate. I also got to know the DIPY and FURY community members.</p>
-<p>Not only that, but I also attended the GSoC’24 summit organised by Google. This session was very informative and aimed to ease our way into GSoC’24, and help us avoid certain mistakes during and after the program.
-I was able to meet the other GSoC students, and I must say that they are all very talented and motivated. I am very happy to be part of this community.</p>
-</section>
-<section id="project-details">
-<h2>Project details</h2>
-<p>I will work on the project: <strong>Modernization of the FURY code base to improve readability, maintainability and performance</strong></p>
-<p>This project aims to modernize the FURY code base by implementing keyword-only arguments to improve code clarity and explicit parameter passing. In addition, the integration of lazy loading functionality will optimize performance by loading resources only when they are needed. Finally, active participation in code refactoring efforts will improve the structure and maintainability of the FURY code base. The project will result in a modernized code base, comprehensive unit testing, updated Sphinx documentation and public presentations illustrating the improvements and benefits. Ultimately, the aim is to significantly improve the FURY code base for future developers and users.</p>
-</section>
-<section id="weekly-tasks">
-<h2>Weekly tasks</h2>
-<p>I had to work on my first mission of the adventure, which was to create a decorator named <strong>keyword_only</strong> to ensure that all arguments after the first are keyword arguments only. It also checks that all keyword arguments are expected by the function. You can check what I had to do in this Pull Request : <a class="github reference external" href="https://github.com/fury-gl/fury/pull/888">fury-gl/fury#888</a>. I’ve learned a lot from implementing the <strong>keyword_only</strong> decorator</p>
-</section>
-<section id="what-s-next">
-<h2>What’s next?</h2>
-<p>For my next task, I’ll first apply the advice and comments from my first task, adding the <strong>keyword_only</strong> decorator after all the necessary reviews and member approval, on all the functions concerned next, then I’ll start and finish, integrating the lazy loading feature.</p>
-<p>🥰 Thank you for reading. Your comments are most welcome, and I learn from them.</p>
-</section>
-</section>
-
- Like any good start, this week I have the incredible opportunity to be welcomed into the community by the Core Team and my Mentor himself, during this session the Mentors welcomed us warmly and also congratulated us. They shared with us the rules respected during and after the GSoC program. This session made me feel comfortable and confident.
- 2024-05-28T00:00:00+00:00
-
diff --git a/v0.10.x/blog/category.html b/v0.10.x/blog/category.html
index c116b270a..b5949193c 100644
--- a/v0.10.x/blog/category.html
+++ b/v0.10.x/blog/category.html
@@ -7,7 +7,7 @@
Categories — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Categories — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -43,7 +43,7 @@
+
+
+
+
+
+
diff --git a/v0.10.x/blog/category/gsoc.html b/v0.10.x/blog/category/gsoc.html
index 95c073252..17cd00455 100644
--- a/v0.10.x/blog/category/gsoc.html
+++ b/v0.10.x/blog/category/gsoc.html
@@ -7,7 +7,7 @@
-
Posts in gsoc — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+
Posts in gsoc — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -43,7 +43,7 @@
-
+
@@ -748,6 +748,227 @@
+
+
+
+
+
+
+ 15 August 2024
+
+
+
+
+
Hello everyone,
+welcome to the update for Week 11 of my Google Summer of Code (GSoC) 2024 journey. This week, I focused on finalizing the footer issue on the FURY
+
+
+
Read more ...
+
+
+
+
+
+
+
+ 15 August 2024
+
+
+
+
+
Welcome to the week 10 of my Google Summer of Code (GSoC) 2024 journey. This week, I focused on resolving an issue with the FURY
+
+
+
Read more ...
+
+
+
+
+
+
+
+ 13 August 2024
+
+
+
+
+
Hello everyone,
+welcome to my Google Summer of Code (GSoC) 2024 journey! Week 9 was devoted to fixing Sphinx warnings caused by indentation errors in some docstrings of some examples in the auto_examples FURY
+
+
+
Read more ...
+
+
WEEK 8: Refining Lazy Loading Implementation and Simplifying Imports in FURY
diff --git a/v0.10.x/blog/category/gsoc/atom.xml b/v0.10.x/blog/category/gsoc/atom.xml
index 6ab47a598..491f5a43a 100644
--- a/v0.10.x/blog/category/gsoc/atom.xml
+++ b/v0.10.x/blog/category/gsoc/atom.xml
@@ -2,7 +2,7 @@
https://fury.gl/
Blog - Posts in gsoc
- 2024-08-23T18:53:30.390866+00:00
+ 2024-08-23T18:59:46.298306+00:00
ABlog
@@ -333,6 +333,155 @@ All good things must come to an end, and it’s with a mixture of satisfaction a
2024-08-15T00:00:00+00:00
+
+ https://fury.gl/posts/2024/2024-08-15-week11-wachiou.html
+ WEEK 11: Resolving the Footer Issue and Addressing Sphinx Warnings
+ 2024-08-15T00:00:00+00:00
+
+ Wachiou BOURAIMA
+
+ <section id="week-11-resolving-the-footer-issue-and-addressing-sphinx-warnings">
+
+<p>Hello everyone,
+welcome to the update for Week 11 of my Google Summer of Code (GSoC) 2024 journey. This week, I focused on finalizing the footer issue on the <code class="docutils literal notranslate"><span class="pre">FURY</span></code> website and tackling some Sphinx warnings related to attribute and property naming conflicts. Here’s a detailed look at what I accomplished and the challenges faced.</p>
+<section id="fixing-the-footer-issue">
+<h2>Fixing the Footer Issue</h2>
+<p>In the previous week, I identified the root cause of the footer deformation. The problem arose when hovering over elements, which caused their size to increase, thereby affecting the padding of their container and subsequently the entire footer layout.
+To illustrate the issue and the resolution, I have included the following videos:</p>
+<p>Before Fixing the Footer Issue:
+Video demonstrating the footer deformation before the fix.</p>
+<iframe src="https://github.com/user-attachments/assets/2f5d4021-b661-4be9-944f-7a2638376f2c" width="640" height="390" frameborder="0" allowfullscreen></iframe><p>After Fixing the Footer Issue:
+Video showing the footer after applying the fix.</p>
+<iframe src="https://github.com/user-attachments/assets/b0ec74df-827b-4280-b3e4-bf968b97a654" width="640" height="390" frameborder="0" allowfullscreen></iframe><p>To address this, I experimented with different approaches. Initially, I tried adjusting the <cite>font-size</cite> of the elements on hover by making them bold instead. This resolved the deformation issue but did not align with the design specifications of the homepage footer.
+After reconsidering, I added some properties to the <code class="docutils literal notranslate"><span class="pre">.class-columns</span></code> in the <code class="docutils literal notranslate"><span class="pre">styles.css</span></code> file to better adapt the footer style and prevent any layout issues. This approach aimed to maintain the design integrity while addressing the layout problem effectively.</p>
+</section>
+<section id="handling-sphinx-warnings">
+<h2>Handling Sphinx Warnings</h2>
+<p>In addition to fixing the footer, I worked on resolving warnings caused by Sphinx due to naming conflicts between attributes and properties. To mitigate these warnings, I initially added <code class="docutils literal notranslate"><span class="pre">:no-index:</span></code> directives in the .rst files for functions and classes to prevent indexing issues.
+However, during our weekly meeting with my mentor <a class="reference external" href="https://github.com/skoudoro">Serge Koudoro</a>, it became clear that this solution might hinder the indexing and referencing of functions, modules, and classes on the <code class="docutils literal notranslate"><span class="pre">FURY</span></code> site and the web. Therefore, I need to re-evaluate the issue and find a more suitable solution that ensures proper indexing while addressing the warnings.</p>
+</section>
+<section id="did-i-get-stuck-anywhere">
+<h2>Did I Get Stuck Anywhere ?</h2>
+<p>While addressing the Sphinx warnings, I encountered some challenges related to the naming conflicts between attributes and properties. The warnings were triggered by the use of the same name for both an attribute and a property in the codebase. This conflict led to Sphinx warnings, which I am currently working to resolve. The complexity of this issue requires a more in-depth analysis to develop an appropriate solution that aligns with the project’s requirements and Sphinx guidelines.</p>
+</section>
+<section id="acknowledgements">
+<h2>Acknowledgements</h2>
+<aside class="system-message">
+<p class="system-message-title">System Message: INFO/1 (<span class="docutils literal">/home/runner/work/fury/fury/docs/source/posts/2024/2024-08-15-week11-wachiou.rst</span>, line 2); <em><a href="#id1">backlink</a></em></p>
+<p>Duplicate explicit target name: “serge koudoro”.</p>
+</aside>
+<p>I am deeply grateful to my peers <a class="reference external" href="https://github.com/itellaetxe">Iñigo Tellaetxe Elorriaga</a>, <a class="reference external" href="https://github.com/robinroy03">Robin Roy</a>, <a class="reference external" href="https://github.com/deka27">Kaustav Deka</a> for their continuous support and insightful suggestions. Special thanks to my mentor, <a class="reference external" href="https://github.com/skoudoro">Serge Koudoro</a> , whose expertise and guidance have been invaluable in navigating these technical challenges.</p>
+</section>
+<section id="whats-next">
+<h2>What’s Next ?</h2>
+<p>For the upcoming week, I plan to:</p>
+<ul class="simple">
+<li><p>Delve deeper into the Sphinx warnings related to attribute and property naming conflicts to develop a more appropriate solution.</p></li>
+<li><p>Continue to refine the footer styling to ensure it meets design specifications while maintaining functionality.</p></li>
+<li><p>Start writing my <cite>GSOC’2024</cite> final report.</p></li>
+</ul>
+<p>Thank you for following my progress. I look forward to sharing further updates and solutions in the coming weeks!</p>
+</section>
+</section>
+
+ Hello everyone,
+welcome to the update for Week 11 of my Google Summer of Code (GSoC) 2024 journey. This week, I focused on finalizing the footer issue on the FURY website and tackling some Sphinx warnings related to attribute and property naming conflicts. Here’s a detailed look at what I accomplished and the challenges faced.
+ 2024-08-15T00:00:00+00:00
+
+
+ https://fury.gl/posts/2024/2024-08-15-week10-wachiou.html
+ WEEK 10: Investigating Footer Deformation and Limited Progress on Warnings
+ 2024-08-15T00:00:00+00:00
+
+ Wachiou BOURAIMA
+
+ <section id="week-10-investigating-footer-deformation-and-limited-progress-on-warnings">
+
+<p>Welcome to the week 10 of my Google Summer of Code (GSoC) 2024 journey. This week, I focused on resolving an issue with the <code class="docutils literal notranslate"><span class="pre">FURY</span></code> website’s footer and made limited progress on fixing documentation warnings. Here’s a detailed overview of my activities and challenges.</p>
+<section id="investigating-footer-deformation-issue-874">
+<h2>Investigating Footer Deformation Issue: <a class="reference external" href="https://github.com/fury-gl/fury/issues/874">#874</a></h2>
+<p>During this week, I identified the root cause of the footer deformation on the FURY website. The problem arose when hovering over an element, which caused the element’s size to increase. This, in turn, increased the padding of its container and subsequently affected the layout of following elements.
+To address this, I initially considered avoiding changes in font size on hover and opted to make elements bold instead. While this approach resolved the deformation issue, it did not align with the design requirements for the homepage footer.
+Due to health constraints, I was unable to continue this work. I plan to explore alternative solutions to align with the design specifications in the upcoming week.</p>
+</section>
+<section id="limited-progress-on-documentation-warnings">
+<h2>Limited Progress on Documentation Warnings</h2>
+<p>I also aimed to make progress on fixing Sphinx warnings related to documentation typos. Unfortunately, I could not advance significantly in this area due to the time constraints imposed by the footer issue and my health.</p>
+</section>
+<section id="what-s-next">
+<h2>What’s Next ?</h2>
+<p>For week 11, I plan to:</p>
+<ul class="simple">
+<li><p>Explore alternative solutions to address the footer deformation issue while aligning with the design requirements.</p></li>
+<li><p>Continue fixing Sphinx warnings in the documentation and address any remaining issues.</p></li>
+</ul>
+</section>
+</section>
+
+ Welcome to the week 10 of my Google Summer of Code (GSoC) 2024 journey. This week, I focused on resolving an issue with the FURY website’s footer and made limited progress on fixing documentation warnings. Here’s a detailed overview of my activities and challenges.
+ 2024-08-15T00:00:00+00:00
+
+
+ https://fury.gl/posts/2024/2024-08-13-week9-wachiou.html
+ WEEK 9: Fixing Sphinx Warnings and Investigating Web Footer Issues
+ 2024-08-13T00:00:00+00:00
+
+ Wachiou BOURAIMA
+
+ <section id="week-9-fixing-sphinx-warnings-and-investigating-web-footer-issues">
+
+<p>Hello everyone,
+welcome to my Google Summer of Code (GSoC) 2024 journey! Week 9 was devoted to fixing Sphinx warnings caused by indentation errors in some docstrings of some examples in the <code class="docutils literal notranslate"><span class="pre">auto_examples</span></code> folder. I also started investigating why the footer of the <code class="docutils literal notranslate"><span class="pre">FURY</span></code> site distorts when you try to move the mouse over an element.</p>
+<section id="continuing-the-fight-against-sphinx-warnings">
+<h2>Continuing the Fight Against Sphinx Warnings</h2>
+<p>My main task this week has been to continue dealing with the Sphinx warnings in our documentation. I focused on the 188 warnings related to the main documentation, as well as 2 warnings in the blog posts.
+I fixed 19 warnings caused by the docstring of <code class="docutils literal notranslate"><span class="pre">viz_**.py</span></code> modules in the <code class="docutils literal notranslate"><span class="pre">source/auto_examples</span></code> folder
+by fixing the indentation errors in the docstrings of the examples.</p>
+<p>Here is an example of indentation error in the docstring of the example <code class="docutils literal notranslate"><span class="pre">auto_examples/04_demos/viz_animated_surfaces.py</span></code>:</p>
+<div class="highlight-python notranslate"><div class="highlight"><pre><span></span><span class="o">...</span> <span class="n">Code</span> <span class="n">block</span> <span class="o">...</span>
+
+<span class="c1">###############################################################################</span>
+<span class="c1"># Variables and their usage:</span>
+<span class="c1"># :time - float: initial value of the time variable i.e. value of the time variable at</span>
+<span class="c1"># the beginning of the program; (default = 0)</span>
+<span class="c1"># dt: float</span>
+<span class="c1"># amount by which ``time`` variable is incremented for every iteration</span>
+<span class="c1"># of timer_callback function (default = 0.1)</span>
+<span class="c1"># lower_xbound: float</span>
+
+<span class="o">...</span> <span class="n">Code</span> <span class="n">block</span> <span class="o">...</span>
+</pre></div>
+</div>
+</section>
+<section id="investigating-web-footer-issues">
+<h2>Investigating Web Footer Issues</h2>
+<p>In parallel, I started investigating an issue with the FURY website’s footer, which deforms when hovering over an element with the mouse. This problem affects the user experience and visual consistency of the site. My work this week has focused on diagnosing the underlying cause of this issue and planning the necessary steps to fix it. This task has been both technically intriguing and a great opportunity to sharpen my web development skills.</p>
+<p>issue number: <a class="reference external" href="https://github.com/fury-gl/fury/issues/874">#874</a></p>
+</section>
+<section id="did-i-get-stuck-anywhere">
+<h2>Did I get stuck anywhere ?</h2>
+<p>I encountered some challenges while fixing the indentation errors in the docstrings of the examples. The errors were caused by inconsistent indentation in the docstrings, which made it difficult to identify the root cause of the warnings. However, I was able to resolve these issues and make progress in addressing the Sphinx warnings.</p>
+</section>
+<section id="what-s-next">
+<h2>What’s next ?</h2>
+<p>For week 10, I plan to:</p>
+<ul class="simple">
+<li><p>Continue fixing the Sphinx warnings in the documentation.</p></li>
+<li><p>Start fixing the issue with the footer of the FURY website.</p></li>
+</ul>
+</section>
+</section>
+
+ Hello everyone,
+welcome to my Google Summer of Code (GSoC) 2024 journey! Week 9 was devoted to fixing Sphinx warnings caused by indentation errors in some docstrings of some examples in the auto_examples folder. I also started investigating why the footer of the FURY site distorts when you try to move the mouse over an element.
+ 2024-08-13T00:00:00+00:00
+
https://fury.gl/posts/2024/2024-08-12-week8-wachiou-bouraima.html
WEEK 8: Refining Lazy Loading Implementation and Simplifying Imports in FURY
@@ -418,197 +567,4 @@ Welcome back to another update on my GSoC 2024 journey. This week, my focus was
2024-08-06T00:00:00+00:00
-
- https://fury.gl/posts/2024/2024-08-06-week6-wachiou-bouraima.html
- WEEK 6: Code reviews, relining and crush challenges
- 2024-08-06T00:00:00+00:00
-
- Wachiou BOURAIMA
-
- <section id="week-6-code-reviews-relining-and-crush-challenges">
-
-<p>Hello everyone,
-As my Google Summer of Code (GSoC) 2024 journey progresses, week6 has brought me a series of technical challenges and accomplishments. My main focus has been on code reviews, rebasing and commits squashing, with a few notable lessons learned along the way.</p>
-<section id="code-reviews-and-merging-pull-requests">
-<h2>Code Reviews and Merging <code class="docutils literal notranslate"><span class="pre">Pull</span> <span class="pre">Requests</span></code></h2>
-<p>One of the main activities this week was receiving and addressing feedback on several of my pull requests. Notably, my mentor <a class="reference external" href="https://github.com/skoudoro/">Serge Koudoro</a>, reviewed and merged the PRs related to the <code class="docutils literal notranslate"><span class="pre">warn_on_args_to_kwargs</span></code> decorator and the application of the <code class="docutils literal notranslate"><span class="pre">warn_on_args_to_kwargs</span></code> decorator across various modules. The merging of these PRs was a critical step in ensuring that our codebase adhered to the project’s evolving standards for clarity and maintainability.</p>
-</section>
-<section id="rebasing-and-squashing-overcoming-challenges">
-<h2>Rebasing and Squashing: Overcoming Challenges</h2>
-<ul class="simple">
-<li><p>I performed rebasing and squashing to integrate the latest changes and consolidate commits. This process was challenging due to several conflicts that arose. Resolving these conflicts required a deep dive into Git’s functionality, including:</p>
-<ul>
-<li><p><strong>Conflict Resolution:</strong> Manually resolving merge conflicts that affected several files.</p></li>
-<li><p><strong>Understanding Git Operations:</strong> Gained hands-on experience with rebasing and squashing, which improved my grasp of version control workflows.</p></li>
-<li><p><strong>Commit Consolidation:</strong> multiple commits into a single commit to streamline the commit history and enhance readability.</p></li>
-</ul>
-</li>
-</ul>
-<p>Here are some of the Git commands I used during the rebasing and squashing process:</p>
-<div class="highlight-bash notranslate"><div class="highlight"><pre><span></span><span class="c1"># Rebase the branch onto the upstream/master branch</span>
-
-git<span class="w"> </span>rebase<span class="w"> </span>upstream/master<span class="w"> </span>-xtheirs
-
-<span class="c1"># Squash the last "n" commits into a single commit</span>
-git<span class="w"> </span>rebase<span class="w"> </span>-i<span class="w"> </span>HEAD~n
-
-<span class="c1"># Continue the rebase process after resolving conflicts</span>
-git<span class="w"> </span>rebase<span class="w"> </span>--continue
-
-git<span class="w"> </span>rebase<span class="w"> </span>--abort
-
-<span class="c1"># Amend the last commit with new changes</span>
-git<span class="w"> </span>commit<span class="w"> </span>--amend
-
-<span class="c1"># Push the changes to the remote repository</span>
-git<span class="w"> </span>push<span class="w"> </span>origin<span class="w"> </span>branch_name<span class="w"> </span>--force
-</pre></div>
-</div>
-<ul class="simple">
-<li><p>Merged PRs:</p>
-<ul>
-<li><p><cite>warn_on_args_to_kwargs</cite>: <a class="github reference external" href="https://github.com/fury-gl/fury/pull/888">fury-gl/fury#888</a></p></li>
-<li><p><cite>actors</cite>: <a class="github reference external" href="https://github.com/fury-gl/fury/pull/898">fury-gl/fury#898</a></p></li>
-<li><p><cite>animation</cite>: <a class="github reference external" href="https://github.com/fury-gl/fury/pull/899">fury-gl/fury#899</a></p></li>
-<li><p><cite>data</cite>: <a class="github reference external" href="https://github.com/fury-gl/fury/pull/900">fury-gl/fury#900</a></p></li>
-<li><p><cite>shares</cite>: <a class="github reference external" href="https://github.com/fury-gl/fury/pull/901">fury-gl/fury#901</a></p></li>
-<li><p><cite>ui</cite>: <a class="github reference external" href="https://github.com/fury-gl/fury/pull/902">fury-gl/fury#902</a></p></li>
-</ul>
-</li>
-</ul>
-</section>
-<section id="technical-insights-and-lessons-learned">
-<h2>Technical Insights and Lessons Learned</h2>
-<ul class="simple">
-<li><p><strong>Version Control Mastery:</strong> Through the rebasing and squashing process, I gained a deeper understanding of Git’s capabilities and the importance of maintaining a clean commit history.</p></li>
-</ul>
-</section>
-<section id="acknowledgements">
-<h2>Acknowledgements</h2>
-<p>I want to extend my thanks to my mentor <a class="reference external" href="https://github.com/skoudoro/">Serge Koudoro</a>, for his detailed feedback and guidance. Your support has been crucial in refining my work. I also appreciate the constructive comments from my peers: <a class="reference external" href="https://github.com/itellaetxe">Iñigo Tellaetxe Elorriaga</a>, <a class="reference external" href="https://github.com/robinroy03">Robin Roy</a>, <a class="reference external" href="https://github.com/deka27">Kaustav Deka</a>, which have been instrumental in improving the quality of my contributions.</p>
-</section>
-<section id="did-i-get-stuck-anywhere">
-<h2>Did I get stuck anywhere?</h2>
-<p>While the rebasing and squashing process presented challenges, I was able to overcome them with the help of my mentor <a class="reference external" href="https://github.com/skoudoro">Serge Koudoro</a> and online resources and documentation.</p>
-<ul class="simple">
-<li><p><a class="reference external" href="https://www.git-tower.com/learn/git/faq/git-squash">How to Squash Commits in Git</a></p></li>
-<li><p><a class="reference external" href="https://dev.to/tariqabughofa/git-theirs-vs-ours-3i7h">Git: Theirs vs Ours</a></p></li>
-<li><p><a class="reference external" href="https://youtu.be/AWayLpQHJeE?si=I-fRM0H3icvm9ua8">How to squash and rebase in git</a></p></li>
-</ul>
-<p>The experience has enhanced my Git proficiency and prepared me for future code management tasks.</p>
-</section>
-<section id="what-s-next">
-<h2>What’s next ?</h2>
-<p>In the week 7, I plan to:</p>
-<ol class="arabic simple">
-<li><p>Review Adjustments: I’ll be reviewing the feedback provided by my mentor <a class="reference external" href="https://github.com/skoudoro/">Serge Koudoro</a>, on the latest changes to ensure that everything meets <code class="docutils literal notranslate"><span class="pre">FURY</span></code>’s coding standards.</p></li>
-<li><p>Finalizing Lazy Loading: Once the reviews are completed and approved, my mentor <a class="reference external" href="https://github.com/skoudoro/">Serge Koudoro</a>, will merge the PR related to the lazy loading implementation. This will mark a significant milestone in optimizing the FURY codebase.</p></li>
-<li><p>Sphinx Warning Fixes: I will start addressing Sphinx warnings related to typos in the blog posts to improve the documentation quality.</p></li>
-</ol>
-</section>
-</section>
-
- Hello everyone,
-As my Google Summer of Code (GSoC) 2024 journey progresses, week6 has brought me a series of technical challenges and accomplishments. My main focus has been on code reviews, rebasing and commits squashing, with a few notable lessons learned along the way.
- 2024-08-06T00:00:00+00:00
-
-
- https://fury.gl/posts/2024/2024-07-27-week8-robin.html
- Week 8: Gemini Finetuning
- 2024-07-27T00:00:00+00:00
-
- Robin Roy
-
- <section id="week-8-gemini-finetuning">
-
-<p>Hi, I’m <a class="reference external" href="https://github.com/robinroy03">Robin</a> and this is my blog about week 8.</p>
-<p>This week I worked on finalizing the Discord chat QnA data collection and using it to Fine-Tune the Gemini-1.0-Pro model.</p>
-<section id="things-i-did-in-week-8">
-<h2>Things I did in Week 8</h2>
-<ol class="arabic simple">
-<li><p><strong>Discord Data Collection</strong></p></li>
-</ol>
-<p>I finished collecting data from all the channels in the Discord server, cross-verifying to check whether they still work. I also added some questions which were on the FURY bot testing server. These QnA pairs were later converted to a CSV with input/output pairs and fed to Gemini for finetuning.</p>
-<ol class="arabic simple" start="2">
-<li><p><strong>Gemini Finetuning</strong></p></li>
-</ol>
-<aside class="system-message">
-<p class="system-message-title">System Message: INFO/1 (<span class="docutils literal">/home/runner/work/fury/fury/docs/source/posts/2024/2024-07-27-week8-robin.rst</span>, line 2)</p>
-<p>Enumerated list start value not ordinal-1: “2” (ordinal 2)</p>
-</aside>
-<p>Finetuning is essentially training the model on the input/output. RAG is giving context and asking the model to form an answer using that. Finetuning updates the model weights as per the input/output. Gemini uses <a class="reference external" href="https://huggingface.co/blog/peft">Parameter-Efficient Fine-Tuning</a> in AI Studio as per some reports. It makes sense because the tuning only takes minutes and PEFT is a good strategy to prevent issues like <a class="reference external" href="https://arxiv.org/abs/1312.6211">catastrophic forgetting</a>.</p>
-<p>Finetuning and RAG are complementary to each other. The difference between them can be summarized as follows:</p>
-<p>RAG is like giving an LLM with no prior knowledge about FURY access to some important functions/classes as per the user prompt. It’ll use this given context and its knowledge of graphics libraries (knowledge from pretraining) to form an answer.</p>
-<p>Finetuning is used to make the model follow a certain style or behaviour. It is a form of mimicking the input-output. This will help in increasing the model’s performance. An interesting thing is I had to train the model 1) with RAG and 2) without RAG.</p>
-<p>For finetuning, the input must be in the format the LLM will get the answer from the user. When you ask a question to the FURY bot, the bot does not get your question directly. We are processing it to add additional information. Therefore I had to process all the collected data with RAG.</p>
-<p>This is an interesting direction, and I have a lot of cool things to try out here. I’ll spend the next few weeks trying different ideas.</p>
-</section>
-<section id="what-is-coming-up-next-week">
-<h2>What is coming up next week?</h2>
-<ul class="simple">
-<li><p>Finetuning strategies.</p></li>
-<li><p>Hosting the model on API.</p></li>
-</ul>
-</section>
-<section id="did-you-get-stuck-anywhere">
-<h2>Did you get stuck anywhere?</h2>
-<p>No, I did not get stuck anywhere.</p>
-<p>LINKS:</p>
-<ul>
-<li><aside class="system-message">
-<p class="system-message-title">System Message: INFO/1 (<span class="docutils literal">/home/runner/work/fury/fury/docs/source/posts/2024/2024-07-27-week8-robin.rst</span>, line 2); <em><a href="#id1">backlink</a></em></p>
-<p>Duplicate explicit target name: “parameter-efficient fine-tuning”.</p>
-</aside>
-<p><a class="reference external" href="https://huggingface.co/blog/peft">Parameter-Efficient Fine-Tuning</a></p>
-</li>
-<li><aside class="system-message">
-<p class="system-message-title">System Message: INFO/1 (<span class="docutils literal">/home/runner/work/fury/fury/docs/source/posts/2024/2024-07-27-week8-robin.rst</span>, line 2); <em><a href="#id2">backlink</a></em></p>
-<p>Duplicate explicit target name: “catastrophic forgetting”.</p>
-</aside>
-<p><a class="reference external" href="https://arxiv.org/abs/1312.6211">catastrophic forgetting</a></p>
-</li>
-</ul>
-<p>Thank you for reading!</p>
-</section>
-</section>
-
- Hi, I’m Robin and this is my blog about week 8.
- 2024-07-27T00:00:00+00:00
-
-
- https://fury.gl/posts/2024/2024-07-27-week7-robin.html
- Week 7: Surviving final examinations
- 2024-07-27T00:00:00+00:00
-
- Robin Roy
-
- <section id="week-7-surviving-final-examinations">
-
-<p>Hi, I’m <a class="reference external" href="https://github.com/robinroy03">Robin</a> and this is my blog about week 7.</p>
-<p>I majorly took this week off due to my semester final examinations :) They were fun. Major topics were x86, ARM and 8051. I had not written a lot of assembly apart from school work. I took the week to experiment with some assembly. The course was more into hardware architecture than programming. I’ve now enough knowledge to read a given piece of ASM code with a wiki to look up mnemonics (and Gemini/Claude to help). I’m not fast in writing ASM (yet), one day I’ll find a project to dive into, or maybe some reverse engineering and CTFs. GPU instruction sets are also something interesting.</p>
-<p><strong>Discord data collection</strong></p>
-<p>I collected some Q&A questions from the FURY discord server. I did it manually because the volume wasn’t high, and I wanted it to be correct. Had to cross-check with GitHub also to check whether the answer/code mentioned still stands. The format I used was [User question, Answer]. If the answer/question is spread across multiple conversations, I’ll adjust it to this format.</p>
-<section id="what-is-coming-up-next-week">
-<h2>What is coming up next week?</h2>
-<ul class="simple">
-<li><p>Gemini Finetuning</p></li>
-<li><p>Collect more Discord data.</p></li>
-</ul>
-</section>
-<section id="did-you-get-stuck-anywhere">
-<h2>Did you get stuck anywhere?</h2>
-<p>Not really apart from some silly ASM bugs.</p>
-<p>Thank you for reading!</p>
-</section>
-</section>
-
- Hi, I’m Robin and this is my blog about week 7.
- 2024-07-27T00:00:00+00:00
-
diff --git a/v0.10.x/blog/category/news.html b/v0.10.x/blog/category/news.html
index 431367431..46696cb35 100644
--- a/v0.10.x/blog/category/news.html
+++ b/v0.10.x/blog/category/news.html
@@ -7,7 +7,7 @@
Posts in news — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Posts in news — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -43,7 +43,7 @@
https://fury.gl/
Blog - Posts in news
- 2024-08-23T18:53:30.431050+00:00
+ 2024-08-23T18:59:46.335606+00:00
ABlog
diff --git a/v0.10.x/blog/category/release.html b/v0.10.x/blog/category/release.html
index 03b0b160f..e360e3253 100644
--- a/v0.10.x/blog/category/release.html
+++ b/v0.10.x/blog/category/release.html
@@ -7,7 +7,7 @@
Posts in release — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Posts in release — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -43,7 +43,7 @@
https://fury.gl/
Blog - Posts in release
- 2024-08-23T18:53:30.433014+00:00
+ 2024-08-23T18:59:46.337652+00:00
ABlog
diff --git a/v0.10.x/blog/drafts.html b/v0.10.x/blog/drafts.html
index c2df11382..34517cfd2 100644
--- a/v0.10.x/blog/drafts.html
+++ b/v0.10.x/blog/drafts.html
@@ -7,7 +7,7 @@
Drafts — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Drafts — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -43,7 +43,7 @@
Tags — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Tags — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -43,7 +43,7 @@
+
+
+
+
+
+
diff --git a/v0.10.x/blog/tag/fury.html b/v0.10.x/blog/tag/fury.html
index 8d2e9a8dc..e7418f557 100644
--- a/v0.10.x/blog/tag/fury.html
+++ b/v0.10.x/blog/tag/fury.html
@@ -7,7 +7,7 @@
-
Posts tagged fury — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+
Posts tagged fury — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -43,7 +43,7 @@
-
+
diff --git a/v0.10.x/blog/tag/fury/atom.xml b/v0.10.x/blog/tag/fury/atom.xml
index 32426d2fd..b86adc806 100644
--- a/v0.10.x/blog/tag/fury/atom.xml
+++ b/v0.10.x/blog/tag/fury/atom.xml
@@ -2,7 +2,7 @@
https://fury.gl/
Blog - Posts tagged fury
- 2024-08-23T18:53:30.779206+00:00
+ 2024-08-23T18:59:47.319600+00:00
ABlog
diff --git a/v0.10.x/blog/tag/google.html b/v0.10.x/blog/tag/google.html
index bf427ac1e..70f67c27b 100644
--- a/v0.10.x/blog/tag/google.html
+++ b/v0.10.x/blog/tag/google.html
@@ -7,7 +7,7 @@
Posts tagged google — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Posts tagged google — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -43,7 +43,7 @@
+
+
+
+
+
+
+ 15 August 2024
+
+
+
+
+
Hello everyone,
+welcome to the update for Week 11 of my Google Summer of Code (GSoC) 2024 journey. This week, I focused on finalizing the footer issue on the FURY
+
+
+
Read more ...
+
+
+
+
+
+
+
+ 15 August 2024
+
+
+
+
+
Welcome to the week 10 of my Google Summer of Code (GSoC) 2024 journey. This week, I focused on resolving an issue with the FURY
+
+
+
Read more ...
+
+
+
+
+
+
+
+ 13 August 2024
+
+
+
+
+
Hello everyone,
+welcome to my Google Summer of Code (GSoC) 2024 journey! Week 9 was devoted to fixing Sphinx warnings caused by indentation errors in some docstrings of some examples in the auto_examples FURY
+
+
+
Read more ...
+
+
WEEK 8: Refining Lazy Loading Implementation and Simplifying Imports in FURY
diff --git a/v0.10.x/blog/tag/google/atom.xml b/v0.10.x/blog/tag/google/atom.xml
index f858437a4..c896f19f2 100644
--- a/v0.10.x/blog/tag/google/atom.xml
+++ b/v0.10.x/blog/tag/google/atom.xml
@@ -2,7 +2,7 @@
https://fury.gl/
Blog - Posts tagged google
- 2024-08-23T18:53:30.831969+00:00
+ 2024-08-23T18:59:47.374034+00:00
ABlog
@@ -333,6 +333,155 @@ All good things must come to an end, and it’s with a mixture of satisfaction a
2024-08-15T00:00:00+00:00
+
+ https://fury.gl/posts/2024/2024-08-15-week11-wachiou.html
+ WEEK 11: Resolving the Footer Issue and Addressing Sphinx Warnings
+ 2024-08-15T00:00:00+00:00
+
+ Wachiou BOURAIMA
+
+ <section id="week-11-resolving-the-footer-issue-and-addressing-sphinx-warnings">
+
+<p>Hello everyone,
+welcome to the update for Week 11 of my Google Summer of Code (GSoC) 2024 journey. This week, I focused on finalizing the footer issue on the <code class="docutils literal notranslate"><span class="pre">FURY</span></code> website and tackling some Sphinx warnings related to attribute and property naming conflicts. Here’s a detailed look at what I accomplished and the challenges faced.</p>
+<section id="fixing-the-footer-issue">
+<h2>Fixing the Footer Issue</h2>
+<p>In the previous week, I identified the root cause of the footer deformation. The problem arose when hovering over elements, which caused their size to increase, thereby affecting the padding of their container and subsequently the entire footer layout.
+To illustrate the issue and the resolution, I have included the following videos:</p>
+<p>Before Fixing the Footer Issue:
+Video demonstrating the footer deformation before the fix.</p>
+<iframe src="https://github.com/user-attachments/assets/2f5d4021-b661-4be9-944f-7a2638376f2c" width="640" height="390" frameborder="0" allowfullscreen></iframe><p>After Fixing the Footer Issue:
+Video showing the footer after applying the fix.</p>
+<iframe src="https://github.com/user-attachments/assets/b0ec74df-827b-4280-b3e4-bf968b97a654" width="640" height="390" frameborder="0" allowfullscreen></iframe><p>To address this, I experimented with different approaches. Initially, I tried adjusting the <cite>font-size</cite> of the elements on hover by making them bold instead. This resolved the deformation issue but did not align with the design specifications of the homepage footer.
+After reconsidering, I added some properties to the <code class="docutils literal notranslate"><span class="pre">.class-columns</span></code> in the <code class="docutils literal notranslate"><span class="pre">styles.css</span></code> file to better adapt the footer style and prevent any layout issues. This approach aimed to maintain the design integrity while addressing the layout problem effectively.</p>
+</section>
+<section id="handling-sphinx-warnings">
+<h2>Handling Sphinx Warnings</h2>
+<p>In addition to fixing the footer, I worked on resolving warnings caused by Sphinx due to naming conflicts between attributes and properties. To mitigate these warnings, I initially added <code class="docutils literal notranslate"><span class="pre">:no-index:</span></code> directives in the .rst files for functions and classes to prevent indexing issues.
+However, during our weekly meeting with my mentor <a class="reference external" href="https://github.com/skoudoro">Serge Koudoro</a>, it became clear that this solution might hinder the indexing and referencing of functions, modules, and classes on the <code class="docutils literal notranslate"><span class="pre">FURY</span></code> site and the web. Therefore, I need to re-evaluate the issue and find a more suitable solution that ensures proper indexing while addressing the warnings.</p>
+</section>
+<section id="did-i-get-stuck-anywhere">
+<h2>Did I Get Stuck Anywhere ?</h2>
+<p>While addressing the Sphinx warnings, I encountered some challenges related to the naming conflicts between attributes and properties. The warnings were triggered by the use of the same name for both an attribute and a property in the codebase. This conflict led to Sphinx warnings, which I am currently working to resolve. The complexity of this issue requires a more in-depth analysis to develop an appropriate solution that aligns with the project’s requirements and Sphinx guidelines.</p>
+</section>
+<section id="acknowledgements">
+<h2>Acknowledgements</h2>
+<aside class="system-message">
+<p class="system-message-title">System Message: INFO/1 (<span class="docutils literal">/home/runner/work/fury/fury/docs/source/posts/2024/2024-08-15-week11-wachiou.rst</span>, line 2); <em><a href="#id1">backlink</a></em></p>
+<p>Duplicate explicit target name: “serge koudoro”.</p>
+</aside>
+<p>I am deeply grateful to my peers <a class="reference external" href="https://github.com/itellaetxe">Iñigo Tellaetxe Elorriaga</a>, <a class="reference external" href="https://github.com/robinroy03">Robin Roy</a>, <a class="reference external" href="https://github.com/deka27">Kaustav Deka</a> for their continuous support and insightful suggestions. Special thanks to my mentor, <a class="reference external" href="https://github.com/skoudoro">Serge Koudoro</a> , whose expertise and guidance have been invaluable in navigating these technical challenges.</p>
+</section>
+<section id="whats-next">
+<h2>What’s Next ?</h2>
+<p>For the upcoming week, I plan to:</p>
+<ul class="simple">
+<li><p>Delve deeper into the Sphinx warnings related to attribute and property naming conflicts to develop a more appropriate solution.</p></li>
+<li><p>Continue to refine the footer styling to ensure it meets design specifications while maintaining functionality.</p></li>
+<li><p>Start writing my <cite>GSOC’2024</cite> final report.</p></li>
+</ul>
+<p>Thank you for following my progress. I look forward to sharing further updates and solutions in the coming weeks!</p>
+</section>
+</section>
+
+ Hello everyone,
+welcome to the update for Week 11 of my Google Summer of Code (GSoC) 2024 journey. This week, I focused on finalizing the footer issue on the FURY website and tackling some Sphinx warnings related to attribute and property naming conflicts. Here’s a detailed look at what I accomplished and the challenges faced.
+ 2024-08-15T00:00:00+00:00
+
+
+ https://fury.gl/posts/2024/2024-08-15-week10-wachiou.html
+ WEEK 10: Investigating Footer Deformation and Limited Progress on Warnings
+ 2024-08-15T00:00:00+00:00
+
+ Wachiou BOURAIMA
+
+ <section id="week-10-investigating-footer-deformation-and-limited-progress-on-warnings">
+
+<p>Welcome to the week 10 of my Google Summer of Code (GSoC) 2024 journey. This week, I focused on resolving an issue with the <code class="docutils literal notranslate"><span class="pre">FURY</span></code> website’s footer and made limited progress on fixing documentation warnings. Here’s a detailed overview of my activities and challenges.</p>
+<section id="investigating-footer-deformation-issue-874">
+<h2>Investigating Footer Deformation Issue: <a class="reference external" href="https://github.com/fury-gl/fury/issues/874">#874</a></h2>
+<p>During this week, I identified the root cause of the footer deformation on the FURY website. The problem arose when hovering over an element, which caused the element’s size to increase. This, in turn, increased the padding of its container and subsequently affected the layout of following elements.
+To address this, I initially considered avoiding changes in font size on hover and opted to make elements bold instead. While this approach resolved the deformation issue, it did not align with the design requirements for the homepage footer.
+Due to health constraints, I was unable to continue this work. I plan to explore alternative solutions to align with the design specifications in the upcoming week.</p>
+</section>
+<section id="limited-progress-on-documentation-warnings">
+<h2>Limited Progress on Documentation Warnings</h2>
+<p>I also aimed to make progress on fixing Sphinx warnings related to documentation typos. Unfortunately, I could not advance significantly in this area due to the time constraints imposed by the footer issue and my health.</p>
+</section>
+<section id="what-s-next">
+<h2>What’s Next ?</h2>
+<p>For week 11, I plan to:</p>
+<ul class="simple">
+<li><p>Explore alternative solutions to address the footer deformation issue while aligning with the design requirements.</p></li>
+<li><p>Continue fixing Sphinx warnings in the documentation and address any remaining issues.</p></li>
+</ul>
+</section>
+</section>
+
+ Welcome to the week 10 of my Google Summer of Code (GSoC) 2024 journey. This week, I focused on resolving an issue with the FURY website’s footer and made limited progress on fixing documentation warnings. Here’s a detailed overview of my activities and challenges.
+ 2024-08-15T00:00:00+00:00
+
+
+ https://fury.gl/posts/2024/2024-08-13-week9-wachiou.html
+ WEEK 9: Fixing Sphinx Warnings and Investigating Web Footer Issues
+ 2024-08-13T00:00:00+00:00
+
+ Wachiou BOURAIMA
+
+ <section id="week-9-fixing-sphinx-warnings-and-investigating-web-footer-issues">
+
+<p>Hello everyone,
+welcome to my Google Summer of Code (GSoC) 2024 journey! Week 9 was devoted to fixing Sphinx warnings caused by indentation errors in some docstrings of some examples in the <code class="docutils literal notranslate"><span class="pre">auto_examples</span></code> folder. I also started investigating why the footer of the <code class="docutils literal notranslate"><span class="pre">FURY</span></code> site distorts when you try to move the mouse over an element.</p>
+<section id="continuing-the-fight-against-sphinx-warnings">
+<h2>Continuing the Fight Against Sphinx Warnings</h2>
+<p>My main task this week has been to continue dealing with the Sphinx warnings in our documentation. I focused on the 188 warnings related to the main documentation, as well as 2 warnings in the blog posts.
+I fixed 19 warnings caused by the docstring of <code class="docutils literal notranslate"><span class="pre">viz_**.py</span></code> modules in the <code class="docutils literal notranslate"><span class="pre">source/auto_examples</span></code> folder
+by fixing the indentation errors in the docstrings of the examples.</p>
+<p>Here is an example of indentation error in the docstring of the example <code class="docutils literal notranslate"><span class="pre">auto_examples/04_demos/viz_animated_surfaces.py</span></code>:</p>
+<div class="highlight-python notranslate"><div class="highlight"><pre><span></span><span class="o">...</span> <span class="n">Code</span> <span class="n">block</span> <span class="o">...</span>
+
+<span class="c1">###############################################################################</span>
+<span class="c1"># Variables and their usage:</span>
+<span class="c1"># :time - float: initial value of the time variable i.e. value of the time variable at</span>
+<span class="c1"># the beginning of the program; (default = 0)</span>
+<span class="c1"># dt: float</span>
+<span class="c1"># amount by which ``time`` variable is incremented for every iteration</span>
+<span class="c1"># of timer_callback function (default = 0.1)</span>
+<span class="c1"># lower_xbound: float</span>
+
+<span class="o">...</span> <span class="n">Code</span> <span class="n">block</span> <span class="o">...</span>
+</pre></div>
+</div>
+</section>
+<section id="investigating-web-footer-issues">
+<h2>Investigating Web Footer Issues</h2>
+<p>In parallel, I started investigating an issue with the FURY website’s footer, which deforms when hovering over an element with the mouse. This problem affects the user experience and visual consistency of the site. My work this week has focused on diagnosing the underlying cause of this issue and planning the necessary steps to fix it. This task has been both technically intriguing and a great opportunity to sharpen my web development skills.</p>
+<p>issue number: <a class="reference external" href="https://github.com/fury-gl/fury/issues/874">#874</a></p>
+</section>
+<section id="did-i-get-stuck-anywhere">
+<h2>Did I get stuck anywhere ?</h2>
+<p>I encountered some challenges while fixing the indentation errors in the docstrings of the examples. The errors were caused by inconsistent indentation in the docstrings, which made it difficult to identify the root cause of the warnings. However, I was able to resolve these issues and make progress in addressing the Sphinx warnings.</p>
+</section>
+<section id="what-s-next">
+<h2>What’s next ?</h2>
+<p>For week 10, I plan to:</p>
+<ul class="simple">
+<li><p>Continue fixing the Sphinx warnings in the documentation.</p></li>
+<li><p>Start fixing the issue with the footer of the FURY website.</p></li>
+</ul>
+</section>
+</section>
+
+ Hello everyone,
+welcome to my Google Summer of Code (GSoC) 2024 journey! Week 9 was devoted to fixing Sphinx warnings caused by indentation errors in some docstrings of some examples in the auto_examples folder. I also started investigating why the footer of the FURY site distorts when you try to move the mouse over an element.
+ 2024-08-13T00:00:00+00:00
+
https://fury.gl/posts/2024/2024-08-12-week8-wachiou-bouraima.html
WEEK 8: Refining Lazy Loading Implementation and Simplifying Imports in FURY
@@ -418,197 +567,4 @@ Welcome back to another update on my GSoC 2024 journey. This week, my focus was
2024-08-06T00:00:00+00:00
-
- https://fury.gl/posts/2024/2024-08-06-week6-wachiou-bouraima.html
- WEEK 6: Code reviews, relining and crush challenges
- 2024-08-06T00:00:00+00:00
-
- Wachiou BOURAIMA
-
- <section id="week-6-code-reviews-relining-and-crush-challenges">
-
-<p>Hello everyone,
-As my Google Summer of Code (GSoC) 2024 journey progresses, week6 has brought me a series of technical challenges and accomplishments. My main focus has been on code reviews, rebasing and commits squashing, with a few notable lessons learned along the way.</p>
-<section id="code-reviews-and-merging-pull-requests">
-<h2>Code Reviews and Merging <code class="docutils literal notranslate"><span class="pre">Pull</span> <span class="pre">Requests</span></code></h2>
-<p>One of the main activities this week was receiving and addressing feedback on several of my pull requests. Notably, my mentor <a class="reference external" href="https://github.com/skoudoro/">Serge Koudoro</a>, reviewed and merged the PRs related to the <code class="docutils literal notranslate"><span class="pre">warn_on_args_to_kwargs</span></code> decorator and the application of the <code class="docutils literal notranslate"><span class="pre">warn_on_args_to_kwargs</span></code> decorator across various modules. The merging of these PRs was a critical step in ensuring that our codebase adhered to the project’s evolving standards for clarity and maintainability.</p>
-</section>
-<section id="rebasing-and-squashing-overcoming-challenges">
-<h2>Rebasing and Squashing: Overcoming Challenges</h2>
-<ul class="simple">
-<li><p>I performed rebasing and squashing to integrate the latest changes and consolidate commits. This process was challenging due to several conflicts that arose. Resolving these conflicts required a deep dive into Git’s functionality, including:</p>
-<ul>
-<li><p><strong>Conflict Resolution:</strong> Manually resolving merge conflicts that affected several files.</p></li>
-<li><p><strong>Understanding Git Operations:</strong> Gained hands-on experience with rebasing and squashing, which improved my grasp of version control workflows.</p></li>
-<li><p><strong>Commit Consolidation:</strong> multiple commits into a single commit to streamline the commit history and enhance readability.</p></li>
-</ul>
-</li>
-</ul>
-<p>Here are some of the Git commands I used during the rebasing and squashing process:</p>
-<div class="highlight-bash notranslate"><div class="highlight"><pre><span></span><span class="c1"># Rebase the branch onto the upstream/master branch</span>
-
-git<span class="w"> </span>rebase<span class="w"> </span>upstream/master<span class="w"> </span>-xtheirs
-
-<span class="c1"># Squash the last "n" commits into a single commit</span>
-git<span class="w"> </span>rebase<span class="w"> </span>-i<span class="w"> </span>HEAD~n
-
-<span class="c1"># Continue the rebase process after resolving conflicts</span>
-git<span class="w"> </span>rebase<span class="w"> </span>--continue
-
-git<span class="w"> </span>rebase<span class="w"> </span>--abort
-
-<span class="c1"># Amend the last commit with new changes</span>
-git<span class="w"> </span>commit<span class="w"> </span>--amend
-
-<span class="c1"># Push the changes to the remote repository</span>
-git<span class="w"> </span>push<span class="w"> </span>origin<span class="w"> </span>branch_name<span class="w"> </span>--force
-</pre></div>
-</div>
-<ul class="simple">
-<li><p>Merged PRs:</p>
-<ul>
-<li><p><cite>warn_on_args_to_kwargs</cite>: <a class="github reference external" href="https://github.com/fury-gl/fury/pull/888">fury-gl/fury#888</a></p></li>
-<li><p><cite>actors</cite>: <a class="github reference external" href="https://github.com/fury-gl/fury/pull/898">fury-gl/fury#898</a></p></li>
-<li><p><cite>animation</cite>: <a class="github reference external" href="https://github.com/fury-gl/fury/pull/899">fury-gl/fury#899</a></p></li>
-<li><p><cite>data</cite>: <a class="github reference external" href="https://github.com/fury-gl/fury/pull/900">fury-gl/fury#900</a></p></li>
-<li><p><cite>shares</cite>: <a class="github reference external" href="https://github.com/fury-gl/fury/pull/901">fury-gl/fury#901</a></p></li>
-<li><p><cite>ui</cite>: <a class="github reference external" href="https://github.com/fury-gl/fury/pull/902">fury-gl/fury#902</a></p></li>
-</ul>
-</li>
-</ul>
-</section>
-<section id="technical-insights-and-lessons-learned">
-<h2>Technical Insights and Lessons Learned</h2>
-<ul class="simple">
-<li><p><strong>Version Control Mastery:</strong> Through the rebasing and squashing process, I gained a deeper understanding of Git’s capabilities and the importance of maintaining a clean commit history.</p></li>
-</ul>
-</section>
-<section id="acknowledgements">
-<h2>Acknowledgements</h2>
-<p>I want to extend my thanks to my mentor <a class="reference external" href="https://github.com/skoudoro/">Serge Koudoro</a>, for his detailed feedback and guidance. Your support has been crucial in refining my work. I also appreciate the constructive comments from my peers: <a class="reference external" href="https://github.com/itellaetxe">Iñigo Tellaetxe Elorriaga</a>, <a class="reference external" href="https://github.com/robinroy03">Robin Roy</a>, <a class="reference external" href="https://github.com/deka27">Kaustav Deka</a>, which have been instrumental in improving the quality of my contributions.</p>
-</section>
-<section id="did-i-get-stuck-anywhere">
-<h2>Did I get stuck anywhere?</h2>
-<p>While the rebasing and squashing process presented challenges, I was able to overcome them with the help of my mentor <a class="reference external" href="https://github.com/skoudoro">Serge Koudoro</a> and online resources and documentation.</p>
-<ul class="simple">
-<li><p><a class="reference external" href="https://www.git-tower.com/learn/git/faq/git-squash">How to Squash Commits in Git</a></p></li>
-<li><p><a class="reference external" href="https://dev.to/tariqabughofa/git-theirs-vs-ours-3i7h">Git: Theirs vs Ours</a></p></li>
-<li><p><a class="reference external" href="https://youtu.be/AWayLpQHJeE?si=I-fRM0H3icvm9ua8">How to squash and rebase in git</a></p></li>
-</ul>
-<p>The experience has enhanced my Git proficiency and prepared me for future code management tasks.</p>
-</section>
-<section id="what-s-next">
-<h2>What’s next ?</h2>
-<p>In the week 7, I plan to:</p>
-<ol class="arabic simple">
-<li><p>Review Adjustments: I’ll be reviewing the feedback provided by my mentor <a class="reference external" href="https://github.com/skoudoro/">Serge Koudoro</a>, on the latest changes to ensure that everything meets <code class="docutils literal notranslate"><span class="pre">FURY</span></code>’s coding standards.</p></li>
-<li><p>Finalizing Lazy Loading: Once the reviews are completed and approved, my mentor <a class="reference external" href="https://github.com/skoudoro/">Serge Koudoro</a>, will merge the PR related to the lazy loading implementation. This will mark a significant milestone in optimizing the FURY codebase.</p></li>
-<li><p>Sphinx Warning Fixes: I will start addressing Sphinx warnings related to typos in the blog posts to improve the documentation quality.</p></li>
-</ol>
-</section>
-</section>
-
- Hello everyone,
-As my Google Summer of Code (GSoC) 2024 journey progresses, week6 has brought me a series of technical challenges and accomplishments. My main focus has been on code reviews, rebasing and commits squashing, with a few notable lessons learned along the way.
- 2024-08-06T00:00:00+00:00
-
-
- https://fury.gl/posts/2024/2024-07-27-week8-robin.html
- Week 8: Gemini Finetuning
- 2024-07-27T00:00:00+00:00
-
- Robin Roy
-
- <section id="week-8-gemini-finetuning">
-
-<p>Hi, I’m <a class="reference external" href="https://github.com/robinroy03">Robin</a> and this is my blog about week 8.</p>
-<p>This week I worked on finalizing the Discord chat QnA data collection and using it to Fine-Tune the Gemini-1.0-Pro model.</p>
-<section id="things-i-did-in-week-8">
-<h2>Things I did in Week 8</h2>
-<ol class="arabic simple">
-<li><p><strong>Discord Data Collection</strong></p></li>
-</ol>
-<p>I finished collecting data from all the channels in the Discord server, cross-verifying to check whether they still work. I also added some questions which were on the FURY bot testing server. These QnA pairs were later converted to a CSV with input/output pairs and fed to Gemini for finetuning.</p>
-<ol class="arabic simple" start="2">
-<li><p><strong>Gemini Finetuning</strong></p></li>
-</ol>
-<aside class="system-message">
-<p class="system-message-title">System Message: INFO/1 (<span class="docutils literal">/home/runner/work/fury/fury/docs/source/posts/2024/2024-07-27-week8-robin.rst</span>, line 2)</p>
-<p>Enumerated list start value not ordinal-1: “2” (ordinal 2)</p>
-</aside>
-<p>Finetuning is essentially training the model on the input/output. RAG is giving context and asking the model to form an answer using that. Finetuning updates the model weights as per the input/output. Gemini uses <a class="reference external" href="https://huggingface.co/blog/peft">Parameter-Efficient Fine-Tuning</a> in AI Studio as per some reports. It makes sense because the tuning only takes minutes and PEFT is a good strategy to prevent issues like <a class="reference external" href="https://arxiv.org/abs/1312.6211">catastrophic forgetting</a>.</p>
-<p>Finetuning and RAG are complementary to each other. The difference between them can be summarized as follows:</p>
-<p>RAG is like giving an LLM with no prior knowledge about FURY access to some important functions/classes as per the user prompt. It’ll use this given context and its knowledge of graphics libraries (knowledge from pretraining) to form an answer.</p>
-<p>Finetuning is used to make the model follow a certain style or behaviour. It is a form of mimicking the input-output. This will help in increasing the model’s performance. An interesting thing is I had to train the model 1) with RAG and 2) without RAG.</p>
-<p>For finetuning, the input must be in the format the LLM will get the answer from the user. When you ask a question to the FURY bot, the bot does not get your question directly. We are processing it to add additional information. Therefore I had to process all the collected data with RAG.</p>
-<p>This is an interesting direction, and I have a lot of cool things to try out here. I’ll spend the next few weeks trying different ideas.</p>
-</section>
-<section id="what-is-coming-up-next-week">
-<h2>What is coming up next week?</h2>
-<ul class="simple">
-<li><p>Finetuning strategies.</p></li>
-<li><p>Hosting the model on API.</p></li>
-</ul>
-</section>
-<section id="did-you-get-stuck-anywhere">
-<h2>Did you get stuck anywhere?</h2>
-<p>No, I did not get stuck anywhere.</p>
-<p>LINKS:</p>
-<ul>
-<li><aside class="system-message">
-<p class="system-message-title">System Message: INFO/1 (<span class="docutils literal">/home/runner/work/fury/fury/docs/source/posts/2024/2024-07-27-week8-robin.rst</span>, line 2); <em><a href="#id1">backlink</a></em></p>
-<p>Duplicate explicit target name: “parameter-efficient fine-tuning”.</p>
-</aside>
-<p><a class="reference external" href="https://huggingface.co/blog/peft">Parameter-Efficient Fine-Tuning</a></p>
-</li>
-<li><aside class="system-message">
-<p class="system-message-title">System Message: INFO/1 (<span class="docutils literal">/home/runner/work/fury/fury/docs/source/posts/2024/2024-07-27-week8-robin.rst</span>, line 2); <em><a href="#id2">backlink</a></em></p>
-<p>Duplicate explicit target name: “catastrophic forgetting”.</p>
-</aside>
-<p><a class="reference external" href="https://arxiv.org/abs/1312.6211">catastrophic forgetting</a></p>
-</li>
-</ul>
-<p>Thank you for reading!</p>
-</section>
-</section>
-
- Hi, I’m Robin and this is my blog about week 8.
- 2024-07-27T00:00:00+00:00
-
-
- https://fury.gl/posts/2024/2024-07-27-week7-robin.html
- Week 7: Surviving final examinations
- 2024-07-27T00:00:00+00:00
-
- Robin Roy
-
- <section id="week-7-surviving-final-examinations">
-
-<p>Hi, I’m <a class="reference external" href="https://github.com/robinroy03">Robin</a> and this is my blog about week 7.</p>
-<p>I majorly took this week off due to my semester final examinations :) They were fun. Major topics were x86, ARM and 8051. I had not written a lot of assembly apart from school work. I took the week to experiment with some assembly. The course was more into hardware architecture than programming. I’ve now enough knowledge to read a given piece of ASM code with a wiki to look up mnemonics (and Gemini/Claude to help). I’m not fast in writing ASM (yet), one day I’ll find a project to dive into, or maybe some reverse engineering and CTFs. GPU instruction sets are also something interesting.</p>
-<p><strong>Discord data collection</strong></p>
-<p>I collected some Q&A questions from the FURY discord server. I did it manually because the volume wasn’t high, and I wanted it to be correct. Had to cross-check with GitHub also to check whether the answer/code mentioned still stands. The format I used was [User question, Answer]. If the answer/question is spread across multiple conversations, I’ll adjust it to this format.</p>
-<section id="what-is-coming-up-next-week">
-<h2>What is coming up next week?</h2>
-<ul class="simple">
-<li><p>Gemini Finetuning</p></li>
-<li><p>Collect more Discord data.</p></li>
-</ul>
-</section>
-<section id="did-you-get-stuck-anywhere">
-<h2>Did you get stuck anywhere?</h2>
-<p>Not really apart from some silly ASM bugs.</p>
-<p>Thank you for reading!</p>
-</section>
-</section>
-
- Hi, I’m Robin and this is my blog about week 7.
- 2024-07-27T00:00:00+00:00
-
diff --git a/v0.10.x/blog/tag/shader.html b/v0.10.x/blog/tag/shader.html
index f6f435235..1ceaf9c24 100644
--- a/v0.10.x/blog/tag/shader.html
+++ b/v0.10.x/blog/tag/shader.html
@@ -7,7 +7,7 @@
Posts tagged shader — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Posts tagged shader — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -43,7 +43,7 @@
https://fury.gl/
Blog - Posts tagged shader
- 2024-08-23T18:53:30.872934+00:00
+ 2024-08-23T18:59:47.410997+00:00
ABlog
diff --git a/v0.10.x/community.html b/v0.10.x/community.html
index ceddecf7a..c782e9e37 100644
--- a/v0.10.x/community.html
+++ b/v0.10.x/community.html
@@ -8,7 +8,7 @@
Community — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Community — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
FURY - pyBullet Integration Guide — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ FURY - pyBullet Integration Guide — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Index — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Index — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -43,7 +43,7 @@
Getting Started — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Getting Started — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Installation — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Installation — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
About — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ About — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
FURY 0.1.0 Released — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ FURY 0.1.0 Released — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
FURY 0.1.3 Released — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ FURY 0.1.3 Released — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
FURY 0.1.4 Released — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ FURY 0.1.4 Released — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
FURY 0.2.0 Released — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ FURY 0.2.0 Released — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Success on Brain Art Competition using FURY — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Success on Brain Art Competition using FURY — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
FURY 0.3.0 Released — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ FURY 0.3.0 Released — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
FURY 0.4.0 Released — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ FURY 0.4.0 Released — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Google Summer of Code — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Google Summer of Code — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
FURY 0.5.1 Released — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ FURY 0.5.1 Released — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Weekly Check-in #1 — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Weekly Check-in #1 — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Welcome to my GSoC Blog!!! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Welcome to my GSoC Blog!!! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
First week of coding!! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ First week of coding!! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
First week of coding!! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ First week of coding!! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Raymarching!! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Raymarching!! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
ComboBox2D Progress!! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ ComboBox2D Progress!! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Raymarching continued — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Raymarching continued — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
TextBlock2D Progress!! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ TextBlock2D Progress!! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Spherical harmonics — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Spherical harmonics — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
May the Force be with you!! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ May the Force be with you!! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Spherical harmonics, Continued. — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Spherical harmonics, Continued. — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Translation, Reposition, Rotation. — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Translation, Reposition, Rotation. — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Orientation, Sizing, Tab UI. — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Orientation, Sizing, Tab UI. — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Multiple SDF primitives. — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Multiple SDF primitives. — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
ComboBox2D, TextBlock2D, Clipping Overflow. — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ ComboBox2D, TextBlock2D, Clipping Overflow. — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
FURY 0.6.0 Released — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ FURY 0.6.0 Released — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Improvements in SDF primitives. — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Improvements in SDF primitives. — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Tab UI, TabPanel2D, Tab UI Tutorial. — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Tab UI, TabPanel2D, Tab UI Tutorial. — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Merging SDF primitives. — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Merging SDF primitives. — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
More Shaders!! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ More Shaders!! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Single Actor, Physics, Scrollbars. — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Single Actor, Physics, Scrollbars. — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
More Shaders!! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ More Shaders!! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Chain Simulation, Scrollbar Refactor, Tutorial Update. — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Chain Simulation, Scrollbar Refactor, Tutorial Update. — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Wrecking Ball Simulation, Scrollbars Update, Physics Tutorials. — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Wrecking Ball Simulation, Scrollbars Update, Physics Tutorials. — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Outline Picker — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Outline Picker — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
FURY 0.6.1 Released — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ FURY 0.6.1 Released — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Part of the Journey is the end unless its Open Source! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Part of the Journey is the end unless its Open Source! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Google Summer of Code 2020 Final Work Product — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Google Summer of Code 2020 Final Work Product — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Google Summer of Code Final Work Product — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Google Summer of Code Final Work Product — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Shader Showcase — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Shader Showcase — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Google Summer of Code — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Google Summer of Code — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
FURY 0.7.0 Released — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ FURY 0.7.0 Released — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Weekly Check-In #1 — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Weekly Check-In #1 — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week #1: Welcome to my weekly Blogs! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week #1: Welcome to my weekly Blogs! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Welcome to my GSoC Blog! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Welcome to my GSoC Blog! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
A Stadia-like system for data visualization — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ A Stadia-like system for data visualization — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week #2: Feature additions in UI and IO modules — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week #2: Feature additions in UI and IO modules — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
First week of coding! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ First week of coding! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Weekly Check-In #3 — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Weekly Check-In #3 — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week #3: Adapting GridLayout to work with UI — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week #3: Adapting GridLayout to work with UI — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Second week of coding! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Second week of coding! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
SOLID, monkey patching a python issue and network visualization through WebRTC — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ SOLID, monkey patching a python issue and network visualization through WebRTC — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week #4: Adding Tree UI to the UI module — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week #4: Adding Tree UI to the UI module — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Third week of coding! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Third week of coding! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Weekly Check-In #5 — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Weekly Check-In #5 — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week #5: Rebasing all PRs w.r.t the UI restructuring, Tree2D, Bug Fixes — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week #5: Rebasing all PRs w.r.t the UI restructuring, Tree2D, Bug Fixes — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Fourth week of coding! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Fourth week of coding! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Network layout algorithms using IPC — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Network layout algorithms using IPC — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week #6: Bug fixes, Working on Tree2D UI — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week #6: Bug fixes, Working on Tree2D UI — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Fifth week of coding! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Fifth week of coding! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Weekly Check-In #7 — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Weekly Check-In #7 — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week #7: Finalizing the stalling PRs, finishing up Tree2D UI. — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week #7: Finalizing the stalling PRs, finishing up Tree2D UI. — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Sixth week of coding! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Sixth week of coding! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Weekly Check-In #8 — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Weekly Check-In #8 — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week #8: Code Cleanup, Finishing up open PRs, Continuing work on Tree2D — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week #8: Code Cleanup, Finishing up open PRs, Continuing work on Tree2D — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Seventh week of coding! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Seventh week of coding! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week #09: Sphinx custom summary — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week #09: Sphinx custom summary — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week #9: More Layouts! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week #9: More Layouts! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Eighth coding week! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Eighth coding week! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
FURY 0.7.0 Released — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ FURY 0.7.0 Released — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week#10: Accordion UI, Support for sprite sheet animations — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week#10: Accordion UI, Support for sprite sheet animations — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Ninth coding week! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Ninth coding week! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week #11: Finalizing open Pull Requests — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week #11: Finalizing open Pull Requests — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Tenth coding week! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Tenth coding week! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Google Summer of Code Final Work Product — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Google Summer of Code Final Work Product — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Google Summer of Code Final Work Product — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Google Summer of Code Final Work Product — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Google Summer of Code 2021 - Final Report - Bruno Messias — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Google Summer of Code 2021 - Final Report - Bruno Messias — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week #10: SDF Fonts — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week #10: SDF Fonts — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 11: Removing the flickering effect — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 11: Removing the flickering effect — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
FURY 0.8.0 Released — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ FURY 0.8.0 Released — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Contribute to FURY via Google Summer of Code 2022 — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Contribute to FURY via Google Summer of Code 2022 — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
My journey till getting accepted into GSoC22 — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ My journey till getting accepted into GSoC22 — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
My Journey to GSoC 2022 — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ My Journey to GSoC 2022 — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Pre-GSoC Journey — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Pre-GSoC Journey — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 1: Implementing a basic Keyframe animation API — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 1: Implementing a basic Keyframe animation API — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 1 - Laying the Foundation of DrawPanel UI — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 1 - Laying the Foundation of DrawPanel UI — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 2 - Improving DrawPanel UI — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 2 - Improving DrawPanel UI — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 1 - A Basic glTF Importer — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 1 - A Basic glTF Importer — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 3 - Dealing with Problems — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 3 - Dealing with Problems — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 2: Implementing non-linear and color interpolators — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 2: Implementing non-linear and color interpolators — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 4 - Fixing the Clamping Issue — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 4 - Fixing the Clamping Issue — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 2 - Improving Fetcher and Exporting glTF — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 2 - Improving Fetcher and Exporting glTF — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 3: Redesigning the API, Implementing cubic Bezier Interpolator, and making progress on the GPU side! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 3: Redesigning the API, Implementing cubic Bezier Interpolator, and making progress on the GPU side! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 3 - Fixing fetcher, adding tests and docs — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 3 - Fixing fetcher, adding tests and docs — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 5 - Working on new features — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 5 - Working on new features — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 4: Camera animation, interpolation in GLSL, and a single Timeline! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 4: Camera animation, interpolation in GLSL, and a single Timeline! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 4 - Finalizing glTF loader — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 4 - Finalizing glTF loader — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 6 - Supporting Rotation of the Shapes from the Center — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 6 - Supporting Rotation of the Shapes from the Center — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 5: Slerp implementation, documenting the Timeline, and adding unit tests — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 5: Slerp implementation, documenting the Timeline, and adding unit tests — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 5 - Creating PR for glTF exporter and fixing the loader — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 5 - Creating PR for glTF exporter and fixing the loader — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 7 - Working on Rotation PR and Trying Freehand Drawing — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 7 - Working on Rotation PR and Trying Freehand Drawing — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 6: Fixing the Timeline issues and equipping it with more features — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 6: Fixing the Timeline issues and equipping it with more features — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 6 - Extracting the animation data — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 6 - Extracting the animation data — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 8 - Working on the polyline feature — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 8 - Working on the polyline feature — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 7: Billboard spheres and implementing interpolators using closures — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 7: Billboard spheres and implementing interpolators using closures — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 7 - Fixing bugs in animations — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 7 - Fixing bugs in animations — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 9 - Grouping and Transforming Shapes — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 9 - Grouping and Transforming Shapes — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 8 - Fixing animation bugs — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 8 - Fixing animation bugs — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 8: Back to the shader-based version of the Timeline — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 8: Back to the shader-based version of the Timeline — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 10 - Understanding Codes and Playing with Animation — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 10 - Understanding Codes and Playing with Animation — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 9: Animating primitives of the same actor — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 9: Animating primitives of the same actor — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 9 - First working skeletal animation prototype — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 9 - First working skeletal animation prototype — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 11 - Creating a base for Freehand Drawing — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 11 - Creating a base for Freehand Drawing — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 10: Supporting hierarchical animating — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 10: Supporting hierarchical animating — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 12 - Fixing translating issues and updating tests — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 12 - Fixing translating issues and updating tests — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 10 - Multi-node skinning support — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 10 - Multi-node skinning support — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 11: Improving tutorials a little — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 11: Improving tutorials a little — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 11 - Multiple transformations support and adding tests — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 11 - Multiple transformations support and adding tests — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 13 - Separating tests and fixing bugs — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 13 - Separating tests and fixing bugs — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 14 - Updating DrawPanel architecture — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 14 - Updating DrawPanel architecture — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 12 - Adding skeleton as actors and fix global transformation — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 12 - Adding skeleton as actors and fix global transformation — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 15 - Highlighting DrawShapes — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 15 - Highlighting DrawShapes — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 13 - Multi-bone skeletal animation support — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 13 - Multi-bone skeletal animation support — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 13: Keyframes animation is now a bit easier in FURY — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 13: Keyframes animation is now a bit easier in FURY — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 16 - Working with Rotations! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 16 - Working with Rotations! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 14: Keyframes animation is now a bit easier in FURY — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 14: Keyframes animation is now a bit easier in FURY — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 14 - Morphing is here! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 14 - Morphing is here! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 12: Adding new tutorials — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 12: Adding new tutorials — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Google Summer of Code Final Work Product — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Google Summer of Code Final Work Product — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Google Summer of Code Final Work Product — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Google Summer of Code Final Work Product — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Google Summer of Code Final Work Product — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Google Summer of Code Final Work Product — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Contribute to FURY via Google Summer of Code 2023 — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Contribute to FURY via Google Summer of Code 2023 — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
FURY 0.9.0 Released — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ FURY 0.9.0 Released — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
The Beginning of Everything - Week 0 — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ The Beginning of Everything - Week 0 — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 0: Community Bounding Period — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 0: Community Bounding Period — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 0: Community Bounding Period — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 0: Community Bounding Period — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 1: Working with SpinBox and TextBox Enhancements — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 1: Working with SpinBox and TextBox Enhancements — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
The FBO Saga - Week 1 — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ The FBO Saga - Week 1 — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 1: Ellipsoid actor implemented with SDF — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 1: Ellipsoid actor implemented with SDF — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 2: Tackling Text Justification and Icon Flaw Issues — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 2: Tackling Text Justification and Icon Flaw Issues — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 2: The Importance of (good) Documentation — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 2: The Importance of (good) Documentation — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 2: Making adjustments to the Ellipsoid Actor — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 2: Making adjustments to the Ellipsoid Actor — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 3: Resolving Combobox Icon Flaw and TextBox Justification — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 3: Resolving Combobox Icon Flaw and TextBox Justification — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 3: Watch Your Expectations — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 3: Watch Your Expectations — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 3: Working on uncertainty and details of the first PR — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 3: Working on uncertainty and details of the first PR — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 4: Exam Preparations and Reviewing — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 4: Exam Preparations and Reviewing — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 4: Nothing is Ever Lost — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 4: Nothing is Ever Lost — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 4: First draft of the DTI uncertainty visualization — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 4: First draft of the DTI uncertainty visualization — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 5: Trying out PRs and Planning Ahead — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 5: Trying out PRs and Planning Ahead — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 5: All Roads Lead to Rome — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 5: All Roads Lead to Rome — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 5: Preparing the data for the Ellipsoid tutorial — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 5: Preparing the data for the Ellipsoid tutorial — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 6: BoundingBox for TextBlock2D! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 6: BoundingBox for TextBlock2D! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 6: Things are Starting to Build Up — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 6: Things are Starting to Build Up — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 6: First draft of the Ellipsoid tutorial — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 6: First draft of the Ellipsoid tutorial — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 7: Sowing the seeds for TreeUI — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 7: Sowing the seeds for TreeUI — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 7: Experimentation Done — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 7: Experimentation Done — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 7: Adjustments on the Uncertainty Cones visualization — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 7: Adjustments on the Uncertainty Cones visualization — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 8: Another week with TextBlockUI — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 8: Another week with TextBlockUI — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 8: The Birth of a Versatile API — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 8: The Birth of a Versatile API — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 8: Working on Ellipsoid Tutorial and exploring SH — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 8: Working on Ellipsoid Tutorial and exploring SH — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 9: TextBlock2D is Finally Merged! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 9: TextBlock2D is Finally Merged! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 9: It is Polishing Time! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 9: It is Polishing Time! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 9: Tutorial done and polishing DTI uncertainty — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 9: Tutorial done and polishing DTI uncertainty — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 10: Its time for a Spin-Box! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 10: Its time for a Spin-Box! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 10: Ready for Review! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 10: Ready for Review! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 10 : Start of SH implementation experiments — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 10 : Start of SH implementation experiments — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 11: Bye Bye SpinBox — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 11: Bye Bye SpinBox — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 11: A Refactor is Sometimes Needed — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 11: A Refactor is Sometimes Needed — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 11 : Adjusting ODF implementation and looking for solutions on issues found — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 11 : Adjusting ODF implementation and looking for solutions on issues found — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 12: FileDialog Quest Begins! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 12: FileDialog Quest Begins! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Google Summer of Code Final Work Product — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Google Summer of Code Final Work Product — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 12: Now That is (almost) a Wrap! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 12: Now That is (almost) a Wrap! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Google Summer of Code Final Work Product — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Google Summer of Code Final Work Product — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 12 : Experimenting with ODFs implementation — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 12 : Experimenting with ODFs implementation — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Google Summer of Code Final Work Product — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Google Summer of Code Final Work Product — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
WEEK 0: The beginning of my journey in Google Summer of Code (GSoC) 2024 — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ WEEK 0: The beginning of my journey in Google Summer of Code (GSoC) 2024 — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 0: Community Bonding! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 0: Community Bonding! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 1: It officially begins… — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 1: It officially begins… — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
WEEK 1: Progress and challenges at Google Summer of Code (GSoC) 2024 — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ WEEK 1: Progress and challenges at Google Summer of Code (GSoC) 2024 — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
WEEK 2: Refinements and Further Enhancements — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ WEEK 2: Refinements and Further Enhancements — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 2: The first iteration! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 2: The first iteration! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 3: Data Data Data! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 3: Data Data Data! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
WEEK 3: Refinements and Further Enhancements — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ WEEK 3: Refinements and Further Enhancements — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
WEEK 4: Updating Decorator, Exploring Lazy Loading, and Code Reviews — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ WEEK 4: Updating Decorator, Exploring Lazy Loading, and Code Reviews — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 4: Pipeline Improvements and Taking The Bot Public! — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 4: Pipeline Improvements and Taking The Bot Public! — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 5: LLM Benchmarking & Architecture Modifications — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 5: LLM Benchmarking & Architecture Modifications — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
WEEK 5: Implementing Lazy Loading in FURY with lazy_loader — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ WEEK 5: Implementing Lazy Loading in FURY with lazy_loader — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 6: UI Improvements and RAG performance evaluation — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 6: UI Improvements and RAG performance evaluation — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 7: Surviving final examinations — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 7: Surviving final examinations — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 8: Gemini Finetuning — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 8: Gemini Finetuning — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
FURY 0.11.0 Released — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ FURY 0.11.0 Released — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
WEEK 6: Code reviews, relining and crush challenges — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ WEEK 6: Code reviews, relining and crush challenges — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
WEEK 7: Fixing Sphinx Warnings in Blog Posts — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ WEEK 7: Fixing Sphinx Warnings in Blog Posts — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
WEEK 8: Refining Lazy Loading Implementation and Simplifying Imports in FURY — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ WEEK 8: Refining Lazy Loading Implementation and Simplifying Imports in FURY — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
What’s Next?
- Week 9: Hosting FineTuned Models
+
+ WEEK 9: Fixing Sphinx Warnings and Investigating Web Footer Issues
WEEK 9: Fixing Sphinx Warnings and Investigating Web Footer Issues — FURY 0.12.0.dev21+gc483d2c9 documentation
+
+
+
+
+
+
+ Skip to main content
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ WEEK 9:...
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
WEEK 10: Investigating Footer Deformation and Limited Progress on Warnings — FURY 0.12.0.dev21+gc483d2c9 documentation
+
+
+
+
+
+
+ Skip to main content
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ WEEK 10:...
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
WEEK 11: Resolving the Footer Issue and Addressing Sphinx Warnings — FURY 0.12.0.dev21+gc483d2c9 documentation
+
+
+
+
+
+
+ Skip to main content
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ WEEK 11:...
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
Week 9: Hosting FineTuned Models — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 9: Hosting FineTuned Models — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Did you get stuck anywhere?
+
WEEK 8: Refining Lazy Loading Implementation and Simplifying Imports in FURY
+ WEEK 11: Resolving the Footer Issue and Addressing Sphinx Warnings
diff --git a/v0.10.x/posts/2024/2024-08-16_week10.html b/v0.10.x/posts/2024/2024-08-16_week10.html
index 658bb0f9e..92f71c4bc 100644
--- a/v0.10.x/posts/2024/2024-08-16_week10.html
+++ b/v0.10.x/posts/2024/2024-08-16_week10.html
@@ -8,7 +8,7 @@
Week 10: Learning GraphQL — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 10: Learning GraphQL — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
WEEK 12: The final straight — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ WEEK 12: The final straight — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 11: Getting the App Live — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 11: Getting the App Live — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Week 12: Wrapping things up — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Week 12: Wrapping things up — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Python Module Index — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Python Module Index — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -43,7 +43,7 @@
Release History — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Release History — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Release notes v0.1.0 (2018-09-21) — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Release notes v0.1.0 (2018-09-21) — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Release notes v0.1.1 (2018-10-29) — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Release notes v0.1.1 (2018-10-29) — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Release notes v0.1.2 and v0.1.3 (2018-10-31) — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Release notes v0.1.2 and v0.1.3 (2018-10-31) — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Release notes v0.1.4 (2018-11-26) — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Release notes v0.1.4 (2018-11-26) — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Release notes v0.10.0 (2024/02/28) — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Release notes v0.10.0 (2024/02/28) — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Release notes v0.11.0 — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Release notes v0.11.0 — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Release notes v0.2.0 (2019-03-08) — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Release notes v0.2.0 (2019-03-08) — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Release notes v0.3.0 (2019-08-02) — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Release notes v0.3.0 (2019-08-02) — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Release notes v0.4.0 (2019-10-29) — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Release notes v0.4.0 (2019-10-29) — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Release notes v0.5.1 (2020-04-01) — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Release notes v0.5.1 (2020-04-01) — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Release notes v0.6.0 (2020-07-20) — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Release notes v0.6.0 (2020-07-20) — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Release notes v0.6.1 (2020-08-20) — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Release notes v0.6.1 (2020-08-20) — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Release notes v0.7.0 (2021/03/13) — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Release notes v0.7.0 (2021/03/13) — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Release notes v0.7.1 (2021/08/03) — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Release notes v0.7.1 (2021/08/03) — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Release notes v0.8.0 (2022/01/31) — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Release notes v0.8.0 (2022/01/31) — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Release notes v0.9.0 (2023/04/15) — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Release notes v0.9.0 (2023/04/15) — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Search - FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Search - FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -42,7 +42,7 @@
Timeline Timeline Timeline ", "Week 10 - Understanding Codes and Playing with Animation", "Week 9: Animating primitives of the same actor", "Week 9 - First working skeletal animation prototype", "Week 11 - Creating a base for Freehand Drawing", "Week 10: Supporting hierarchical animating", "Week 12 - Fixing translating issues and updating tests", "Week 10 - Multi-node skinning support", "Week 11: Improving tutorials a little", "Week 11 - Multiple transformations support and adding tests", "Week 13 - Separating tests and fixing bugs", "Week 14 - Updating DrawPanel architecture", "Week 12 - Adding skeleton as actors and fix global transformation", "Week 15 - Highlighting DrawShapes", "Week 13 - Multi-bone skeletal animation support", "Week 13: Keyframes animation is now a bit easier in FURY", "Week 16 - Working with Rotations!", "Week 14: Keyframes animation is now a bit easier in FURY", "Week 14 - Morphing is here!", "Week 12: Adding new tutorials", "Google Summer of Code Final Work Product", "Google Summer of Code Final Work Product", "Google Summer of Code Final Work Product", "Contribute to FURY via Google Summer of Code 2023", "FURY 0.9.0 Released", "The Beginning of Everything - Week 0", "Week 0: Community Bounding Period", "Week 0: Community Bounding Period", "Week 1: Working with SpinBox and TextBox Enhancements", "The FBO Saga - Week 1", "Week 1: Ellipsoid actor implemented with SDF", "Week 2: Tackling Text Justification and Icon Flaw Issues", "Week 2: The Importance of (good) Documentation", "Week 2: Making adjustments to the Ellipsoid Actor", "Week 3: Resolving Combobox Icon Flaw and TextBox Justification", "Week 3: Watch Your Expectations", "Week 3: Working on uncertainty and details of the first PR", "Week 4: Exam Preparations and Reviewing", "Week 4: Nothing is Ever Lost", "Week 4: First draft of the DTI uncertainty visualization", "Week 5: Trying out PRs and Planning Ahead", "Week 5: All Roads Lead to Rome", "Week 5: Preparing the data for the Ellipsoid tutorial", "Week 6: BoundingBox for TextBlock2D!", "Week 6: Things are Starting to Build Up", "Week 6: First draft of the Ellipsoid tutorial", "Week 7: Sowing the seeds for TreeUI", "Week 7: Experimentation Done", "Week 7: Adjustments on the Uncertainty Cones visualization", "Week 8: Another week with TextBlockUI", "Week 8: The Birth of a Versatile API", "Week 8: Working on Ellipsoid Tutorial and exploring SH", "Week 9: TextBlock2D is Finally Merged!", "Week 9: It is Polishing Time!", "Week 9: Tutorial done and polishing DTI uncertainty", "Week 10: Its time for a Spin-Box!", "Week 10: Ready for Review!", "Week 10 : Start of SH implementation experiments", "Week 11: Bye Bye SpinBox", "Week 11: A Refactor is Sometimes Needed", "Week 11 : Adjusting ODF implementation and looking for solutions on issues found", "Week 12: FileDialog Quest Begins!", "Google Summer of Code Final Work Product", "Week 12: Now That is (almost) a Wrap!", "Google Summer of Code Final Work Product", "Week 12 : Experimenting with ODFs implementation", "Google Summer of Code Final Work Product", "WEEK 0: The beginning of my journey in Google Summer of Code (GSoC) 2024", "Week 0: Community Bonding!", "Week 1: It officially begins\u2026", "WEEK 1: Progress and challenges at Google Summer of Code (GSoC) 2024", "WEEK 2: Refinements and Further Enhancements", "Week 2: The first iteration!", "Week 3: Data Data Data!", "WEEK 3: Refinements and Further Enhancements", "WEEK 4: Updating Decorator, Exploring Lazy Loading, and Code Reviews", "Week 4: Pipeline Improvements and Taking The Bot Public!", "Week 5: LLM Benchmarking & Architecture Modifications", "WEEK 5: Implementing Lazy Loading in FURY with lazy_loader fury actor actors animation colormap convert data decorators deprecator gltf io layout lib material molecular pick pkg_info primitive shaders stream transform ui utils window Timeline Timeline Timeline ", "Week 10 - Understanding Codes and Playing with Animation", "Week 9: Animating primitives of the same actor", "Week 9 - First working skeletal animation prototype", "Week 11 - Creating a base for Freehand Drawing", "Week 10: Supporting hierarchical animating", "Week 12 - Fixing translating issues and updating tests", "Week 10 - Multi-node skinning support", "Week 11: Improving tutorials a little", "Week 11 - Multiple transformations support and adding tests", "Week 13 - Separating tests and fixing bugs", "Week 14 - Updating DrawPanel architecture", "Week 12 - Adding skeleton as actors and fix global transformation", "Week 15 - Highlighting DrawShapes", "Week 13 - Multi-bone skeletal animation support", "Week 13: Keyframes animation is now a bit easier in FURY", "Week 16 - Working with Rotations!", "Week 14: Keyframes animation is now a bit easier in FURY", "Week 14 - Morphing is here!", "Week 12: Adding new tutorials", "Google Summer of Code Final Work Product", "Google Summer of Code Final Work Product", "Google Summer of Code Final Work Product", "Contribute to FURY via Google Summer of Code 2023", "FURY 0.9.0 Released", "The Beginning of Everything - Week 0", "Week 0: Community Bounding Period", "Week 0: Community Bounding Period", "Week 1: Working with SpinBox and TextBox Enhancements", "The FBO Saga - Week 1", "Week 1: Ellipsoid actor implemented with SDF", "Week 2: Tackling Text Justification and Icon Flaw Issues", "Week 2: The Importance of (good) Documentation", "Week 2: Making adjustments to the Ellipsoid Actor", "Week 3: Resolving Combobox Icon Flaw and TextBox Justification", "Week 3: Watch Your Expectations", "Week 3: Working on uncertainty and details of the first PR", "Week 4: Exam Preparations and Reviewing", "Week 4: Nothing is Ever Lost", "Week 4: First draft of the DTI uncertainty visualization", "Week 5: Trying out PRs and Planning Ahead", "Week 5: All Roads Lead to Rome", "Week 5: Preparing the data for the Ellipsoid tutorial", "Week 6: BoundingBox for TextBlock2D!", "Week 6: Things are Starting to Build Up", "Week 6: First draft of the Ellipsoid tutorial", "Week 7: Sowing the seeds for TreeUI", "Week 7: Experimentation Done", "Week 7: Adjustments on the Uncertainty Cones visualization", "Week 8: Another week with TextBlockUI", "Week 8: The Birth of a Versatile API", "Week 8: Working on Ellipsoid Tutorial and exploring SH", "Week 9: TextBlock2D is Finally Merged!", "Week 9: It is Polishing Time!", "Week 9: Tutorial done and polishing DTI uncertainty", "Week 10: Its time for a Spin-Box!", "Week 10: Ready for Review!", "Week 10 : Start of SH implementation experiments", "Week 11: Bye Bye SpinBox", "Week 11: A Refactor is Sometimes Needed", "Week 11 : Adjusting ODF implementation and looking for solutions on issues found", "Week 12: FileDialog Quest Begins!", "Google Summer of Code Final Work Product", "Week 12: Now That is (almost) a Wrap!", "Google Summer of Code Final Work Product", "Week 12 : Experimenting with ODFs implementation", "Google Summer of Code Final Work Product", "WEEK 0: The beginning of my journey in Google Summer of Code (GSoC) 2024", "Week 0: Community Bonding!", "Week 1: It officially begins\u2026", "WEEK 1: Progress and challenges at Google Summer of Code (GSoC) 2024", "WEEK 2: Refinements and Further Enhancements", "Week 2: The first iteration!", "Week 3: Data Data Data!", "WEEK 3: Refinements and Further Enhancements", "WEEK 4: Updating Decorator, Exploring Lazy Loading, and Code Reviews", "Week 4: Pipeline Improvements and Taking The Bot Public!", "Week 5: LLM Benchmarking & Architecture Modifications", "WEEK 5: Implementing Lazy Loading in FURY with lazy_loader fury actor actors animation colormap convert data decorators deprecator gltf io layout lib material molecular pick pkg_info primitive shaders stream transform ui utils window Computation times — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Computation times — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
Contributing — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ Contributing — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
License — FURY 0.12.0.dev19+gf7d8d5b5 documentation
+ License — FURY 0.12.0.dev21+gc483d2c9 documentation
@@ -44,7 +44,7 @@
+
+