Week #11: Removing the flickering effect

What did I do this week?

FURY

• PR fury-gl/fury#489:

This PR give to FURY three pre-built texture maps using different fonts. However, is quite easy to create new fonts to be used in a visualization.

It’s was quite hard to develop the shader code and find the correct positions of the texture maps to be used in the shader. Because we used the freetype-py to generate the texture and packing the glyps. However, the lib has some examples with bugs. But fortunelly, now everything is woking on FURY. I’ve also created two different examples to show how this PR works.

The first example, viz_huge_amount_of_labels.py, shows that the user can draw hundreds of thousands of characters.

The second example, viz_billboad_labels.py, shows the different behaviors of the label actor. In addition, presents to the user how to create a new texture atlas font to be used across different visualizations.

• PR fury-gl/fury#437:

  • Fix: avoid multiple OpenGl context on windows using asyncio

    The streaming system must be generic, but opengl and vtk behaves in uniques ways in each Operating System. Thus, can be tricky to have the same behavior acrros different OS. One hard stuff that we founded is that was not possible to use my TimeIntervals objects (implemented with threading module) with vtk. The reason for this impossibility is because we can’t use vtk in windows in different threads. But fortunely, moving from the threading (multithreading) to the asyncio approcach (concurrency) have fixed this issue and now the streaming system is ready to be used anywhere.

  • Flickering:

    Finally, I could found the cause of the flickering effect on the streaming system. This flickering was appearing only when the streaming was created using the Widget object. The cause seems to be a bug or a strange behavior from vtk. Calling iren.MouseWheelForwardEvent() or iren.MouseWheelBackwardEvent() inside of a thread without invoking the Start method from a vtk instance produces a memory corruption. Fortunately, I could fix this behavior and now the streaming system is working without this glitch effect.

FURY/Helios

• PR fury-gl/helios#24 :

This uses the PRfury-gl/fury#489: to give the network label feature to helios. Is possible to draw node labels, update the colors, change the positions at runtime. In addition, when a network layout algorithm is running this will automatically update the node labels positions to follow the nodes across the screen.

• PR fury-gl/helios#23: Merged.

This PR granted compatibility between IPC Layouts and Windows. Besides that , now is quite easier to create new network layouts using inter process communication

Did I get stuck anywhere?

I did not get stuck this week.

Week #11: Finalizing open Pull Requests   Google Summer of Code 2021 - Final Report - Bruno Messias