Add transect update monitoring flow - #174
Merged
LOCEANlloydizard merged 4 commits intoAug 14, 2026
Merged
Conversation
Member
|
Oh sorry @LOCEANlloydizard I turned on the auto RTD build, but until #170 is merged that would continue to fail. 😅 |
Contributor
Author
|
oh cheers! yes i saw the fails and then saw the #170.. it all make sense now! 😅 |
LOCEANlloydizard
force-pushed
the
monitor-transect-updates
branch
from
August 14, 2026 16:05
8f9dcbf to
d15aa6f
Compare
Contributor
Author
|
@leewujung i updated this PR to also include the generic raw-directory monitoring discussed in #159, together with the transect monitoring from #163! I think its good for review, cheers! |
2 tasks
This file contains hidden or 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
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.
EDIT
following the workflow discussed in #163, this PR adds event-based monitoring of transect start/end updates, and builds toward the event-driven processing described in #159.
we add:
watchdog.rawfiles arrive/updatetransect_updateflow triggered by this event, including:The Sv lookup currently uses
Sv_files.csvfrom the existingraw2Svworkflow. This can later be replaced by the database-backed lookup as that functionality is integrated (#141)A small companion example showing how to configure and launch the watchers is included in the corresponding
echodataflow-recipesPR: echostack-org/echodataflow-recipes#5Refs: #163, #159