Skip to content
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

Add threshold-specific pellet delivery timestamps as dj table #382

Open
jkbhagatio opened this issue Jul 16, 2024 · 1 comment
Open

Add threshold-specific pellet delivery timestamps as dj table #382

jkbhagatio opened this issue Jul 16, 2024 · 1 comment
Assignees
Labels
feature New planned feature

Comments

@jkbhagatio
Copy link
Member

jkbhagatio commented Jul 16, 2024

This should have the timestamp a pellet was delivered (from beambreak ideally) and the corresponding threshold value

@jkbhagatio jkbhagatio added the feature New planned feature label Jul 16, 2024
@ttngu207
Copy link
Contributor

Add here the latest logic discussed and finalized for this procedure

  1. Get all patch state update timestamps: let's call these events "A"
  2. Remove all "A" events near manual pellet delivery events (so we don't include manual pellet delivery events in downstream analysis)
  3. For the remaining "A" events, find the nearest delivery event within 1s: for this delivery event, check if there are any repeat delivery events within 0.5 seconds - take the last of these as the pellet delivery timestamp (discard all "A" events that don't have such a corresponding delivery event)
  4. Now for these 'clean' "A" events, go back in time to the SECOND preceding pellet threshold value: this is the threshold value for this pellet delivery (as seen in this image we discussed before)
    MicrosoftTeams-image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New planned feature
Projects
None yet
Development

No branches or pull requests

2 participants