raidionics / aeropath Goto Github PK

Describe the bug
After a while, it seems like the app runs into a RuntimeError. This seems quite random. This can also be resolved easily by just restarting the space, but this should not be necessary!

Space can be accessed here:
https://huggingface.co/spaces/andreped/AeroPath

Expected behavior
The space should never run into any RuntimeErrors or errors in general of the sort.

Is your feature request related to a problem? Please describe.
The current solution for 2D and 3D rendering, and how the rendering widgets overall are setup was made to be compatible with an older version of gradio in mind. The old version has severe limitations, which can be observed when changing the 2D slider, which takes several seconds to update, as the 3D renderer needs to be updated every single time. This should not be necessary.

The 2D and 3D renderers should ideally be kept as separate processes, handled in separate threads, if possible. There is also no need to update the 3D renderer if the 2D renderer is updated. In the old gradio version this was not possible to change, but maybe it is now.

Describe the solution you'd like
Changing 2D images should not affect the 3D renderer, and should be close to seemless.

Describe the bug
The 2D image orientation does not match what other alternative software such as 3D Slicer and ITK-Snap uses.

Screenshots

Describe the bug
Data reading through Python API fails. This worked fine before the last PR. Seems like the decoding of the files after download is wrong, or not converted to the correct filenames.

I made a separate Discussion about it on the HF datasets page:
https://huggingface.co/datasets/andreped/AeroPath/discussions/6

To Reproduce
I made a gist that reproduces the issue at:
https://colab.research.google.com/gist/andreped/aee5f6ff14db83b23969a04e38ffac84/aeropath-load-dataset-example.ipynb

Desktop (please complete the following information):

• OS: [e.g. Windows] Ubuntu (on Google CoLaboratory)
• Version: [e.g. 10] 22.04
• Python: [e.g. 3.8.10] Python 3.10

Is your feature request related to a problem? Please describe.
Currently, the rendered object in 3D is a plane gray color.

Describe the solution you'd like
It would be better if the color matched the 2D viewer.

Additional context

Describe the bug
I observed the same bug on neukit and I was surprised that I did not see the same. So I tried doing a factory reset on the HF space and it became clear that something has broken.

Error logs
The error message prompted can be observed when the app is launched:

ImportError: cannot import name 'Doc' from 'typing_extensions'

Desktop (please complete the following information):

• OS: [e.g. Windows] Docker
• Python: [e.g. 3.8.10] 3.8

Additional context
This might be a Dockerfile issue, but I am not sure.

Describe the bug
When launching the app, a log file is created which is used to update the logging widget, giving the user valuable feedback on processing progress. However, it has been observed that after accessing the app, the log from previous runs (or other runs) can be seen. This is not ideal.

Expected behavior
The log widget should be clear when first accessing the deployed app. It should be clear for every single user and each time the user accesses the app (also for website resets).

We might need a mechanism to catch a new run or website refresh and force the log file to be reset.

Screenshots

The old log can be seen when first accessing the website: