Handle partial STB data selections in averaging UIs - #37
Draft
ronangiss wants to merge 2 commits into
Draft
Conversation
using measured freq for time phasing rather than the desired freq
Co-authored-by: ronangiss <ronangiss@users.noreply.github.com>
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
2 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.
Summary
phaseAvg_UIandtimeAvg_UIderive available Calimero distance/type options from files present on disk.turbineto appear as selectable type labels instead of requiring all legacy downstream Calimero types.Testing
git diff --check HEAD~1 HEADpython3static selection-mapping validation for turbine-only, single-Calimero, and mixed datasetsNote: MATLAB/Octave is not installed in the container, so constructor/UI runtime validation could not be executed here.