-
Notifications
You must be signed in to change notification settings - Fork 373
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
Introduce Scalar, SeriesLine, and SeriesPoint archetypes with their own visualizers #4875
Conversation
5b5146f
to
7293db7
Compare
7293db7
to
eb4bac8
Compare
eb4bac8
to
20446a4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is just moving all the aggregation pieces out of visualizer_system.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looking good overall. Heuristic needs patching and duplication of amount of aggregation is problematic
Was fairly trusting on the moved code, hard to follow all of the details how which thing moved
crates/re_types/definitions/rerun/blueprint/archetypes/series_line.fbs
Outdated
Show resolved
Hide resolved
#[derive(Default, Debug)] | ||
pub struct TimeSeriesSystem { | ||
pub struct LegacyTimeSeriesSystem { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
rename the file as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I originally did but it made the git diff much more annoying because it failed to track the move
31e7e05
to
caadc94
Compare
caadc94
to
ff87c9e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚢
for indicated in [ | ||
LegacyTimeSeriesSystem::identifier(), | ||
SeriesLineSystem::identifier(), | ||
SeriesPointSystem::identifier(), | ||
] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm if one would only log the new scalar archetype, then this wouldn't spawn a space view. But then again we also don't know what visualizer to activate right now, so I figure this is correct? All a bit confusing with the Legacy one around right now
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This actually works because the SeriesLineSystem and SeriesPointSystem both accept Scalar as an indicator.
"scalar": ["cpp", "py", "rust"], # TODO(jleibs) | ||
"series_line": ["cpp", "py", "rust"], # TODO(jleibs) | ||
"series_point": ["cpp", "py", "rust"], # TODO(jleibs) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we really need roundtrip tests for these? worth bringing up as a post-standup topic how many of these we want/need in the future
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, TODO there until I've at least made sure they are covered somehow. With it's implicit via code-examples or explicit via RTT.
What
Checklist
main
build: app.rerun.ionightly
build: app.rerun.io