so-rose
/
oscillode
1
0
Fork 0
Code Issues 50 Pull Requests Packages Projects Releases Wiki Activity

Line/Plane/Volume based spatial size and spatial subdivisions in monitors #7

New Issue
Closed
opened 2024-05-04 16:11:35 +02:00 by so-rose · 1 comment
so-rose commented 2024-05-04 16:11:35 +02:00
Owner

Having to manually zero-out a particular axis size is an anti-pattern, as is the specification of some arbitrary spatial subdivision with absolutely no feedback.

Best to have an enum_many choice of axes to zero-out, causing the monitor to either take the form of a line, plane, or volume. The shape of the ExprSocketDef, specifically Size and Spatial Subdivs, should also adapt.

Having to manually zero-out a particular axis size is an anti-pattern, as is the specification of some arbitrary spatial subdivision with absolutely no feedback. Best to have an `enum_many` choice of axes to zero-out, causing the monitor to either take the form of a line, plane, or volume. The shape of the `ExprSocketDef`, specifically `Size` and `Spatial Subdivs`, should also adapt.
so-rose added the
enhancement
 label 2024-05-04 16:12:53 +02:00
so-rose added this to the Robust Simulation milestone 2024-05-07 10:06:41 +02:00
so-rose commented 2024-05-16 13:07:40 +02:00
Poster
Owner

We don't have line/point for FieldMonitor, but the interface is honestly quite nice now.

We don't have line/point for `FieldMonitor`, but the interface is honestly quite nice now.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
uv-refactor
main
Labels
Clear labels   
abstractions

Related to the functionality of the abstractions used to make node/socket design tolerable.   
architecture

Related to the internal approach / structuring of functionality.   
bug

Something that isn't working.   
distribution

Related to processes that gets the software into the hands of users.   
docs

Related to the documentation, both reference and user-facing.   
duplicate

An issue that already exists.   
enhancement

Something to improve existing functionality.   
feature

A feature to implement ex. node, socket, etc. .   
physical

Related to the physical correctness or modelling of the tool.   
proposal

A proposal for a large/radical feature or change, to explain the why/how/status.   
question

A question for a more qualified person.   
simulation

A particular simulation-based test, benchmark, or project of real-world significance.   
tooling

Related to the developer tooling that keeps the developer's mind sane and happy.   
tracker

Aggregating tracker for other Issues.   
unconfirmed

Don't know exactly what's going on yet - ideal for ex. user reports.   
ux

Related to the user experience, visual communication, etc. .   
wontfix

Something that doesn't work that won't be fixed, on purpose.
No Label
abstractions
architecture
bug
distribution
docs
duplicate
enhancement
feature
physical
proposal
question
simulation
tooling
tracker
unconfirmed
ux
wontfix
Milestone
Clear milestone
No items
No Milestone
Robust Simulation
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: so-rose/oscillode#7
There is no content yet.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?