Skip to content

Add flow to monitor transect start/end info updates #163

Description

@leewujung

On the Lasker now Kevin Stierhoff has set up a mechanism to update transect_start_end_time.csv that contains the start and end time of individual transect segment. This file will be overwritten each day at 0700, and then usually manually after a new transect or transect segment is processed in Echoview. Therefore, we need to watch the filesystem for update of this file. The watchdog library mentioned in #159 seems also a good candidate for doing this.

What we need for this flow would be:

  • A utility function that watches update for updates of transect_start_end_time.csv
  • Hooking this watchdog event to an event emission in Prefect to trigger a flow run -- this flow will ultimately be the flow that compute NASC for the new transect(s), but for now this can just be a mock flow for testing

Metadata

Metadata

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions