Handling gaps in mseed data #40
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
* Initial version for mseed and multiple architectures on single branch * fixed ffmpeg command * made files safe names * Hardcod URL for now, made env vars to int * removed from project * Fixed debug message * make data directory if it doesn't exist * initial combo version * initial version * run actual commands, add logspout * fix typos, use shutil.move instead of os.rename for docker * Fixed m3u8 path * fixed to encode in realtime, wait for file * change to ts files * use a bunch of ts files * force new dummy.ts on start * Fix Dockerfile case sensitive name * Added logging * make streaming privleged to use nice * fix audio sampling rate at 64000 * check before deleting/moving files, fixed audio rate, speed up start * change to mono * updates * Split docker-compose.yml into rpi and x86 version * Fix file permsissions * chagne segment to minutes, debug statements * make node run for 24 hours * Fixed rpi baseline build * added support for virtual streaming mode * moved to node folder * made different compose files for build and pull * Added info about logical soundcard names * checking .env adding hls loopback * add image tag for rpi * Removed empty build section To be updated * Fix typo in readme sentence. * Fix minor typos in README paragraph 1 Co-authored-by: steve <steve@mcshicks@gmail.com> Co-authored-by: Scott Veirs <sveirs@gmail.com>
* arm64: install ffmpeg instaed of building * No logspout for arm64 There is no logspout for arm64 so comment this out. * Create docker-compose.arm64-pull.yml New version to support arm64 dockerhub image Co-authored-by: JoyceLiao <joyliao07@gmail.com>
karan2704
changed the title
mcshicks
reviewed
Jun 18, 2022
mcshicks
reviewed
Jun 27, 2022
karan2704
changed the title
|
Yes, that would be great. Can you please create a new issue with the specific requirements mentioned? |
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.
This pull request is intended to close #30
What this PR will achieve?
This particular commit handles fetching and uploading of mseed data in .wav format (for now) to "dev-streaming-orcasound-net" bucket which can be checked out here in the karan_test node
Upload handled using the same upload_s3.py script
How the gaps will be handled?
In the ooipy_pull.py I have used dates 27 Apr 2021 - 30 Apr 2021 (these are randomly chosen dates where data seems to be consistent i.e. without gaps). These highlighted texts should explain how the gaps will be handled.
For large gaps, the download will be skipped and latest.txt will be made to point to the most recently downloaded audio segment. Possibly, we can work on improving ooipy library to handle gaps more efficiently.
What's left to do?
Convert .wav to .ts before uploading. I will use pydub for the same.
Add logic for writing and updating latest.txt currently it just uploads an empty txt file.