search

OSOceanAcoustics / echodataflow

Orchestrated sonar data processing workflow
https://echodataflow.readthedocs.io/en/latest/
MIT License
4 stars 1 forks source link

Deployment naming #112

Open valentina-s opened 2 months ago

valentina-s commented 2 months ago

Currently deployments in the dashboard are named based on the service that has initiated them.

Screenshot 2024-07-12 at 12 59 51 PM

Thus if we have two different deployments using the same service: for example, edf_data_transfer can be called both for file download or upload, or echodatadlow can be called both for the MVBS pipeline or the hake ml pipeline.

It can be very confusing in the dashboard which one corresponds to which processing steps.

Investigate if we can add some additional tag/nickname to indicate that, or modify to have services with a new name for the different components.

leewujung commented 2 months ago

I think we can have an option argument for main.py being the name of the service. This way we are not bound by the names that is hardcoded in main.py.

We were just talking about for Lasker we would need to spin up 2 file-monitor for the two folders with the 18kHz .raw and the 5-channel .raw files, so this will be handy in that use case.