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.

Sign up for GitHub

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

Jump to bottom

Distance and duration handling #122

Closed
ivnsch opened this issue Jul 10, 2020 · 0 comments · Fixed by #123
Closed

Distance and duration handling #122

ivnsch opened this issue Jul 10, 2020 · 0 comments · Fixed by #123
Assignees
@ivnsch

Comments

@ivnsch
Copy link
Collaborator

ivnsch commented Jul 10, 2020 •
edited
Loading

  • Modify DB TCN records to { TCN, start_timestamp, min_distance, avg_distance, end_timestamp }
  • Aggregate TCNs during matching, considering contiguity.
  • Add duration and distance fields to alerts.

To be determined:

  • To pass TCNs to core, apps can either pass individual TCNs (with distance) or batches. Individual TCNs would be ideal, as there would be no duplicated logic in the apps, but we've to confirm FFI/JNI performance.
  • Confirm whether we need min / avg distance or only min.

More context
@ivnsch ivnsch self-assigned this Jul 10, 2020
@ivnsch ivnsch linked a pull request Jul 23, 2020 that will close this issue
Contact duration and distance #123
Merged
@ivnsch ivnsch closed this as completed Jul 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ivnsch ivnsch

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Contact duration and distance Co-Epi/app-backend-rust
1 participant
@ivnsch