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

Handle lag/slow data case on OOI network #41

Open
mcshicks opened this issue Jun 28, 2022 · 0 comments
Open

Handle lag/slow data case on OOI network #41

mcshicks opened this issue Jun 28, 2022 · 0 comments

Comments

@mcshicks
Copy link
Contributor

mcshicks commented Jun 28, 2022

Even though we read the data with a delay sometimes data can come in later. So if data come in later (say within 24 hours) we would still like to have that data put into the delayed livestream so it can be listened to or possibly analyzed. This would mean keeping track of the gaps for one day say and if new data comes in then transcoding it and inserting it into the m3u8 file, or as a minimum just posting the .ts files and maybe logging. Here are some definitions we can use to cover this case.

not delayed: now - file-timestamp < delay
gap: file-timestamp - (prev-file-timestamp + prev-file-duration) > 1 minute
microgap: 1 minute > file-timestamp - (prev-file-timestamp + prev-file-duration) > 0
lag: file with timestamp in range of a gap some time greater than delay. Maybe 24 hours
recovered: file with timestamp after some time greater than 24 hours

use the mseed branch for this

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

No branches or pull requests

1 participant