Skip to content

fix: use correct column names when plotting the lickspout positions in qc#44

Open
arjunsridhar12345 wants to merge 5 commits into
devfrom
43-use-correct-column-names-when-plotting-the-lickspout-positions-in-qc
Open

fix: use correct column names when plotting the lickspout positions in qc#44
arjunsridhar12345 wants to merge 5 commits into
devfrom
43-use-correct-column-names-when-plotting-the-lickspout-positions-in-qc

Conversation

@arjunsridhar12345

Copy link
Copy Markdown
Collaborator

Attempts to close #43. Note that this gets the lickspout positions to show up in the QC plot. It's currently using the positions from the static manipulator software event which is not correct. This does NOT fix issue #22 which still needs to be looked at for getting the correct values.

Sample output, now showing lickspout position in the plot. Not sure if we want to merge this or wait for #22 to be fixed first:

image

@arjunsridhar12345
arjunsridhar12345 marked this pull request as ready for review July 17, 2026 23:51
@alexpiet

Copy link
Copy Markdown

Can you make all the plots be aligned in time? The xlimit starts at different points for the different plots

@arjunsridhar12345

Copy link
Copy Markdown
Collaborator Author

tried to align in this commit: 5ad3b1e

Sample output is below:

image

@alexpiet

Copy link
Copy Markdown

Whats the blocker on getting #22 fixed?

@arjunsridhar12345

Copy link
Copy Markdown
Collaborator Author

@micahwoodard I think were you going to talk to Jessy about the lickspout positions?

@micahwoodard

Copy link
Copy Markdown

@arjunsridhar12345 replied on the issue :)

@micahwoodard

Copy link
Copy Markdown

tried to align in this commit: 5ad3b1e

Sample output is below:

image

@arjunsridhar12345 what are you looking at for stage positions? These graphs imply to me that the bias correction isn't working as intended and wanted to try and debugg

@alexpiet

Copy link
Copy Markdown

@arjunsridhar12345 You can test to make sure the QC plot shows mid-session lickspout movements on this session: 864253_2026-07-17_19-28-27

@alexpiet alexpiet left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fix #22 first

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants