Closed
Conversation
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Jakub Sikorski <jakub.sikorski@intel.com>
Fixes the issue of the GLB texture being missing when viewed in 3D UI.
This pull request refactors logging throughout the cluster_analytics codebase to improve log clarity and reduce noise in production logs. The main change is downgrading many log messages from info to debug level, especially those related to routine operations and parameter changes, while retaining info and error for significant events and errors. Additionally, more detailed error information is now logged at the debug level, and some log messages have been clarified or slightly reworded.
Create separate build and demo targets for building and deploying all services. The default targets are reserved for core containers. Additional changes: The mapping container's version is set in docker-compose.yml mapping container health check executes and shows the health status correctly
This PR simplifies cluster analytics configuration by removing JSON-based configuration for tracking parameters and hardcoding them directly in the source code and removing not used tools from Dockerfile.
This PR aligns the generated mesh from mapping service to be in the first quadrant (+x and +y) and the rotation of the mesh is adjusted to have the floor plane flatter on the xy plane. The ortho/top-down view of the generated mesh i.e the thumbnail is properly rendered. The pose of all cameras is accurately reflected in scenescape.
Transform controls of cameras are hidden on load to avoid a cluttered 3D UI when many cameras are in a scene. The colors of reconstructed mesh are muted due to insufficient lighting. Change the ambient light color and directional light intensity.
rawatts10
requested review from
a team,
Irakus,
MikolajKasprzak,
daddo-intel,
dmytroye,
jdanieck,
ltalarcz,
saratpoluri,
sarthakdeva-intel,
sbelhaik and
tdorauintc
as code owners
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
8 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📝 Description
This PR adds comprehensive developer documentation for working with SceneScape's spatial analytics data, focusing on ROIs (Regions of Interest) and Tripwires. The documentation provides complete guidance for building applications that consume spatial analytics events from SceneScape's sensor-agnostic platform.
What was changed:
working-with-spatial-analytics-data.md(872 lines) - complete developer guide for spatial analyticssample_region_tripwire.png- visual example from Intel HQ Santa Clara parking lotWhy it was needed:
How the changes add value:
✨ Type of Change
Select the type of change your PR introduces:
🧪 Testing Scenarios
Describe how the changes were tested and how reviewers can test them too:
discover.py,listen.py) with live MQTT eventsManual Testing Details:
✅ Checklist
Before submitting the PR, ensure the following:
Additional Notes: