Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Features/depth panoramas #412 #496

Open
wants to merge 228 commits into
base: main
Choose a base branch
from
Open

Conversation

LauraFritz14
Copy link
Collaborator

depth panoramas generation:

  • start viewer, load a scene and set sequenced bookmarks
  • start the depth panoramas generation via the "Generate Depth Images" button in the "Depth Panoramas" gui
  • a panoramaInputFormat.json file is generated in the folder specified in the "Output Path"
  • the snapshot.exe starts and generates the panorama depth images for each bookmark in the list

output:
3 images for every direction of each bookmark

  • *.png = color image
  • *.png_depth = scaled depth download (between 0 and 1)
  • *.tiff = real distance (in negative z-direction)

haraldsteinlechner and others added 30 commits January 31, 2024 14:17
continued modelling necessary types
entities can be created and deleted
actually calling spice function and transforming surfaces #379
…PRo3D.SPICE library (for documentation see docs/spice.md). Updated CooTransformation usage accordingly. JR.Wrappers is still there to support InstrumentPlatforms functionality.
haraldsteinlechner and others added 27 commits December 16, 2024 17:06
…peed up build (was unnecessary in the first place), switched icon for kdtree generation
…phic annotation performance (in e.g. shaler) [(String.IsNullOrEmpty text) || (show && visible)] #481
… for large models due to per-value field containing the whole drawing state)
… loading the lowest quality kdtree unfortunately is too expensive, so i teaked the old legacy metric
…iate frames instead of classic scalbars (renamed ScaleBar to ScaleVisualization to reflect his additional visualization behavior), Outline rendering: optional parameter for thickness
reading in new Panorama Snapshot type via sapshot CLI works via
--scn "sceneName.pro3d" --asnap panoramaInput.json --out ".\images"
proper rendering of depth and conversion of individual images
to panorama still needs to be done, code for creating dummy data
needs to be removed after feature is finished
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants