-
Notifications
You must be signed in to change notification settings - Fork 9
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
SF: Adapt SFH_EvaluateRange for multi dataset input #1987
Merged
Merged
Conversation
This file contains 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
acd7dd0
to
5c3642d
Compare
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
|
d28b4e0
to
ae4b8e8
Compare
@MichaelHuth Please have a look. I've also changed your commits to better fit the new story. |
This comment was marked as outdated.
This comment was marked as outdated.
3eddef3
to
7a4e7ee
Compare
MichaelHuth
commented
Feb 9, 2024
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.
See comments
Make the wave sizes and contents assymetric so that wrong row/column major order issues would be found.
- SFH_EvaluateRange did not accept multi dataset input, which prevented formulas like "epochs(ST) + [1, -2]" to work. This functionality is added. - Changed SFH_GetSweepsForFormula to accept dataset input only. - Adapted calling sites. - added tests as part of tests for data operation - also added test for (n, 2) numerical ranges
…ision And fix call sites which don't fullfill that requirement.
This is nicer for the data as we then have sweep numbers in the annotation and correct trace colors.
Since we added support for inputting multiple numeric ranges into data the case of sel=select(channels(AD9),[31,32,35,37,39],all) data(epochs(["E0", "TP"] , $sel), $sel) did not work correctly. This was because epochs returns 10 waves for this case but we only have 5 sweeps. The information that we have two ranges per sweep was lost. The epochs operation now outputs $numSweeps datasets were all ranges are contained in a 2D wave.
We already have the epoch shortnames, with fallback to the tag if empty, so we can just use these.
We only want to match classical for loops with for(<>; <>; <>) and not range-based for loops with for(<> : <>).
7a4e7ee
to
c826f60
Compare
timjarsky
approved these changes
Feb 13, 2024
MichaelHuth
commented
Feb 15, 2024
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.
Looks good to me.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
close #1819
epochs
in SFH_GetSweepsForFormula graciously