Interactively probing data
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python
- Domain
- computer-graphics, data-visualization
Research direction
Start with the VISOR rendering window and review the linked Figma prototype and feature documentation to understand the proposed interaction. Verify how a loaded model and its currently colored variable are exposed before implementing the probe behavior. Done means the acceptance criteria pass for scalar, vector, and constant-color parts, including X,Y,Z display and vector magnitude handling.
Written by the indexing model from the issue text.
Description
User Story Description
As a user, I want to probe interactively the model so I can see the values of variables at specific points.
The probe will display the X,Y,Z position and the value of the variable the part is currently colored by. We will display the nearest data available (no need to interpolate the nearest nodes).
When probing a vector variable, the probe will return the magnitude of the variable.
Here links to UI proposals:
Documentation/Slides: https://www.figma.com/slides/K31bZ6YPOhV4JG7jIk6Bzc/Theia-Interactive-Probe-Feature-Doc?node-id=1-42&t=IW44F1Snbz363qJX-0
Acceptance Criteria
Start a session of VISOR. Load a model. Color a part by a variable.
Probe the part. On the rendering window, the X,Y,Z values and variable values will appear.
Repeat with a vector variable. The probe returns the magnitude of the vector.
Now, make the part with a constant color - no color by variable. Probe a point again. The probe returns X,Y,Z but no variable value.
Additional Links
No response
Requires new or update to third party ? If "yes" add the name(s) and the version(s) of the Third Party Software.
No
Name and Version for Third Parties
No response
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 47
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ansys/Visual-Interactive-Simulation-Object-Renderer
-
Difficulty 3/5 1-2 days Newbie friendliness 50/100
-
Library updates Opentechnical
ansys/Visual-Interactive-Simulation-Object-Renderer#136 · 1 assignee ·
-
maintenance
ansys/Visual-Interactive-Simulation-Object-Renderer#131 · 1 assignee ·
-
Release 1.0.2 Openmaintenance
ansys/Visual-Interactive-Simulation-Object-Renderer#130 · 1 assignee ·
-
enhancement
ansys/Visual-Interactive-Simulation-Object-Renderer#126 · 1 assignee ·
All issues in ansys/Visual-Interactive-Simulation-Object-Renderer
Similar issues
-
agent-ready documentation needs-triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 91/100
-
workflow-status page template still says reusable workflows are "triggered only by workflow_call:" Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
instance instance add
Difficulty 1/5 Under an hour Newbie friendliness 72/100
searxng/searx-instances#939 · 1 comment ·
-
area-deployment area-integrations triage:bot-seen
Difficulty 2/5 Half a day Newbie friendliness 86/100