fixed warning in test_utils.py.

warning was: #317

fury/tests/test_utils.py::test_trilinear_interp
fury/tests/test_utils.py::test_trilinear_interp
  D:\fury-master\fury\tests\test_utils.py:133: DeprecationWarning: Converting `np.integer` or `np.signedinteger` to a dtype is deprecated. The current result is `np.dtype(np.int_)` which is not strictly correct. Note that the result depends on the system. To ensure stable results use may want to use `np.int64` or `np.int32`.
    x0 = x_indices.astype(np.integer)

fury/tests/test_utils.py::test_trilinear_interp
fury/tests/test_utils.py::test_trilinear_interp
  D:\fury-master\fury\tests\test_utils.py:134: DeprecationWarning: Converting `np.integer` or `np.signedinteger` to a dtype is deprecated. The current result is `np.dtype(np.int_)` which is not strictly correct. Note that the result depends on the system. To ensure stable results use may want to use `np.int64` or `np.int32`.
    y0 = y_indices.astype(np.integer)

fury/tests/test_utils.py::test_trilinear_interp
fury/tests/test_utils.py::test_trilinear_interp
  D:\fury-master\fury\tests\test_utils.py:135: DeprecationWarning: Converting `np.integer` or `np.signedinteger` to a dtype is deprecated. The current result is `np.dtype(np.int_)` which is not strictly correct. Note that the result depends on the system. To ensure stable results use may want to use `np.int64` or `np.int32`.
    z0 = z_indices.astype(np.integer)

It is not much but I noticed it so I just changed it.

The equation looks like this in tutorial of solar system visualization,

link - https://en.wikipedia.org/wiki/Orbital_period

This PR update some FURY functions due to some changes in VTK 9. The main change is better management of vtkCellArray.

Wheels available on Pypi only for Windows and macOS. Concerning Linux, you have to download the wheel on VTK website. (https://discourse.vtk.org/t/vtk-9-wheels-on-pypi/3340/4)

VTK Releases Announcement : https://blog.kitware.com/vtk-9-0-0-available-for-download/ VTK API changes from 8.2 to 9.0: https://vtk.org/Wiki/VTK/API_Changes_8_2_0_to_9_0_0 VTK 9 build process : https://vtk.org/doc/nightly/html/md__home_kitware_dashboards_buildbot_vtk_nightly-master-ike-linux-shared-release_doc_nightly_osm749dd663df9981384f2598c108aac3b0.html

Render a video on an actor.

This PR Consists of 2 parts:

• Function to change the texture of a vtkActor
• A demo file to visualize, rendering of a Video.

Function to change the texture of a vtkActor

Changes in fury.actor

Fury actors didn't have a function to change the texture of an already textured vtkActor. There was a requirement for this function while rendering a video on an Actor. The function accepts an actor object and an image. The image gets mapped in the same mapper as configured while creating the actor.

Tests

To test the function an actor is created with a black texture which is changed and tested with the new texture.

A demo file to visualize, rendering of a Video

The goal of this demo is to show how to visualize a video on a Plane, which can be extended to potentially all shapes

The Video Class

This class wraps OpenCV VideoCapture with the required functionalities

The Animation Class

This class creates an object of the video class and initializes the scene with an Actor.

The run() function adds a timer callback to the show_manager that changes the frame of the video on every call after a specific interval.

How it Looks

When you run FURY tests, a bunch of warnings is popping up. The goal of this task is to track and fix them. Some of them are expected, others not. We will need many PR for this issue and more precisely, 1PR per module

TODO:

• [x] fury/actor.py (pytest -svv fury/test_actor.py)
• [x] fury/colormap.py (pytest -svv fury/test_colormap.py)
• [x] fury/convert.py (pytest -svv fury/test_convert.py)
• [x] fury/decorators.py (pytest -svv fury/test_decorators.py)
• [x] fury/interactor.py (pytest -svv fury/test_interactor.py)
• [x] fury/io.py (pytest -svv fury/test_io.py)
• [ ] fury/layout.py (pytest -svv fury/test_layout.py)
• [x] fury/ui.py (pytest -svv fury/test_ui.py)
• [x] fury/pick.py (pytest -svv fury/test_pick.py)
• [x] fury/primitive.py (pytest -svv fury/test_primitive.py)
• [x] fury/transform.py (pytest -svv fury/test_transform.py)
• [x] fury/window.py (pytest -svv fury/test_window.py)
• [x] fury/utils.py (pytest -svv fury/test_utils.py)

#297 Moved all the Physics tutorials under examples section with a heading 'Integrate physics using pybullet'

Fixed the buggy wrecking ball behavior, the problem was radii was the links or rope's radius instead of the wrecking ball. Changing it to 1 was making a cylindrical collider of radius 1 greater than wrecking ball's radius hence the bug. Ball's radius was hardcoded to 0.2, assigned it to the variable ball_radius so now you can mess with wrecking ball by changing the radius. Fixed some typos that I found along with it.

PS : There was some weird behavior after 100 simulation steps. The ball went crazy and there were some weird stretched lines instead of ropes, I think the code to make the rope has to be redone.

Fixes #324

An example to illustrate how one can render a time-varying 2D function using FURY. I have added quite a few comments to make the code easy to interpret.

Preview-

ComboBox2D UI element

• [X] Skeleton
• [X] Callbacks
• [X] Methods
• [X] Properties
• [X] Tests
• [X] Moving the whole panel with the mouse.
• [X] Make Draggable optional.
• [X] resizing TextBlock2D.
• [X] Recording tests.

Things to be covered:

• a bit of design
• Scrollbar bug when items are added using on_change method.

A simple actor that permits you to draw the shader that you want on one or many Canvas. it uses the billboard technique for always facing the camera. This offers us a powerful tool to draw whatever we want really fast. Below an example of 5 Million funky spheres.

This is close to being done, Maybe today.

Description

UI tests are failing because of a "segmentation error" in Ubuntu only. @xtanion confirmed it on his machine. The error message is: tests/test_elements_callback.py Fatal Python error: Segmentation fault I tried to trace back the cause of this error and it's not caused by the test in which this error occurred. Running only test_elements_callback.py gives a success.

Way to reproduce

Running the UI tests in Ubuntu OS.

This PR will allow us to load gltf files and get actors or polydata from it.

It currently supports:

• [x] multiple Nodes
• [x] multiple Meshes
• [x] Normals
• [x] Cameras
• [x] Textures (baseColor)

Demo:

WIP: glTF exporter, tests

Reference Issues/PRs Closes #309

What does this implement/fix? Explain your changes. I have implemented code that shows how to use pybullet to render physics simulations in fury. More specifically, In this PR, I render a series of Dominoes that are under the Domino Effect.

• This PR changes the logo and logo sizes and fonts according to the new design.
• This PR uses the home-page-mobile-friendly as the base PR, thus will require that PR to be merged to master first.

• What kind of change does this PR introduce?

• It is a bugfix PR. It fixes all the issues related to the home page's mobile-friendliness.

• What is the new behavior (if this is a feature change)?

• Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

• No

• List of fixes:

• Main logo and description alignment issues.

• Hamburger menu alignment fixed.

• Horizontal scrolling due to overflowing elements fixed.

• Install text and command showing properly.

• Tab sections got a new mobile-friendly layout.

• Footer properly aligned and readable.

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

• This PR introduces the feature that on hovering the scientific domain, the popup with the animated gif will appear in the home page of the fury website

• What is the current behavior? (You can also link to an open issue here)

• No effect on hover.

• What is the new behavior (if this is a feature change)?

• It will open up a popup.
• The popup can be closed in two ways
  1. By hovering out of the popup
  2. By clicking outside of the popup

• Other information:

• The animations in the popup are modified a little bit from the original tutorials.
• The animation for the data-science field is created from a newly created example(which will be pushed in upcoming PRs).

This PR needs a lot of cleaning and still in progress. As of now this PR adds ORM, Normal & Emissive materials. Most of the glTF models has been modified to use the ORM material, however few of them still use MetallicRoughness and AmbientOcclusion materials separately (for e.g. DamagedHelmet & Avocado). Few model may have RoughnessMetallic instead of MetallicRoughness which changes switches the channels (For e.g. the Avocado model), as mentioned in this comment. This PR currently does not support the RoughnessMetallic.

Preview with the DamagedHelmet (has all three of materials) model:

Sample of the Avocado model (without switching the channels in RoughnessMetallic to MetallicRoughness) ( Left) After switching channels (Right):

Description

The example fury/docs/tutorials/01_introductory/viz_earth_coordinates.py is not working properly.

The world is upside down and the coordinates does not match the real locations. (Can't figure out what changed to make this happen, it works fine in older versions.

Way to reproduce

Just run python fury/docs/tutorials/01_introductory/viz_earth_coordinates.py

Version information

{
  'fury_version': '0.8.0',
  'pkg_path': '/Users/filsilva/miniforge3/envs/furyearth/lib/python3.9/site-packages/fury',
   'commit_hash': 'b937ff3418e7c64b0fa89921a54c083ff78dc055',
  'sys_version': '3.9.15 | packaged by conda-forge | (main, Nov 22 2022, 08:48:25) \n[Clang 14.0.6 ]',
  'sys_executable': '/Users/filsilva/miniforge3/envs/furyearth/bin/python',
  'sys_platform': 'darwin',
  'numpy_version': '1.23.5',
  'scipy_version': '1.9.3',
  'vtk_version': '9.2.2',
  'matplotlib_version': '3.6.2'
}

• [x] Code example
• [x] Relevant images (if any)
• [x] Operating system and versions (run python -c "from fury import get_info; print(get_info())")

Description

[The docs generation fails with pyData theme v0.11.0 and fixes the aliases]

Way to reproduce

1. Start with a clean code installation via the Source method.
2. try to build the project make -C . clean && make -C . html-no-examples.
3. The build will fail due to version incompatibility.

System Specs

{'fury_version': '0.8.0.post1304+gb37669f8', 'pkg_path': '/Users/maharshigor/Desktop/GRG/fury/fury', 'commit_hash': 'b37669f8767d460b97e17584106ad8a6b5d26491', 'sys_version': '3.10.6 | packaged by conda-forge | (main, Aug 22 2022, 20:41:54) [Clang 13.0.1 ]', 'sys_executable': '/Users/maharshigor/opt/anaconda3/envs/Py310/bin/python', 'sys_platform': 'darwin', 'numpy_version': '1.23.4', 'scipy_version': '1.9.3', 'vtk_version': '9.1.0', 'matplotlib_version': '3.6.2', 'dipy_version': '1.5.0'}