Spaces:
Running
on
Zero
Running
on
Zero
| # Change Log | |
| ## 2024-10-05 22:00 PST | |
| ### Infinite Image Reloading Issue | |
| - Problem: After recent changes, dragging an image into the interface causes it to flicker and continuously reload. The depth prediction does not run. | |
| - Suspected cause: Recent modifications to the input handling in the Gradio interface, particularly the `input_image.change` event. | |
| - Next steps: Revert the changes to the input handling and investigate a different approach to manage the image path. | |
| ## 2024-10-05 21:20 PST | |
| ### 3D Model Generation File Access Error | |
| - Problem: When attempting to generate the 3D model, an error occurred: "[Errno 2] No such file or directory: '/tmp/tmppgls861k.png'" | |
| - This suggests that the temporary file created during the depth map generation is not accessible or has been deleted before the 3D model generation process. | |
| - Next steps: Investigate the file handling in the `create_3d_model` function and ensure temporary files are properly managed and accessible. | |
| ## 2024-10-05 21:13 PST | |
| ### CUDA Initialization Error Fix | |
| - Problem: CUDA was being initialized in the main process, causing an error in the Spaces Stateless GPU environment. | |
| - Changes made: | |
| 1. Modified `np.savetxt` to ensure depth is converted to a CPU numpy array if it's a torch.Tensor. | |
| 2. Explicitly converted `focallength_px` to a float. | |
| 3. Added more print statements throughout the `predict_depth` function for improved logging and debugging. | |
| 4. Added a print statement just before returning from the `predict_depth` function to log all return values. | |
| - These changes aim to prevent CUDA initialization in the main process and provide more detailed logging for troubleshooting. | |
| ## 2024-10-05 23:00 PST | |
| ### Persistent 3D Model Colorization Issue | |
| - Problem: Despite previous attempts, the 3D model still appears colorless (gray) without the original image overlay. | |
| - Next steps: | |
| 1. Review the texture mapping process in the 3D model generation. | |
| 2. Investigate alternative methods to apply color information to the 3D model. | |
| 3. Ensure color data is being properly passed and applied throughout the pipeline. | |
| ## 2024-10-05 22:30 PST | |
| ### 3D Model Colorization and Thin Threshold Adjustment | |
| - Problem 1: The generated 3D model lacks proper colorization from the original image. | |
| - Problem 2: The range for the 'thin' threshold slider may need adjustment, and its units are unclear. | |
| - Next steps: | |
| 1. Investigate and fix the texture mapping in the 3D model generation process. | |
| 2. Clarify the units for the thin threshold and consider adjusting its range. | |
| ## 2024-10-06 00:30 PST | |
| ### Reverting 3D Model Simplification and Smoothing | |
| - Problem: The 3D model still lacks proper colorization from the original image. | |
| - Action: Reverting simplification and smoothing operations to their default state (no processing) to isolate the colorization issue. | |
| - Changes: | |
| 1. Set default values for simplification_factor, smoothing_iterations, and thin_threshold to 1.0, 0, and 0 respectively. | |
| 2. Adjust the generate_3d_model function to skip simplification and smoothing steps when default values are used. | |
| - Next steps: Re-test the 3D model generation to verify if colorization is restored without these processing steps. | |