SeaBee-no / documentation

Repo for all SeaBee documentation
https://seabee-no.github.io/documentation/
0 stars 0 forks source link

Discuss requirements/linkages with WP3 #3

Open knl88 opened 2 years ago

knl88 commented 2 years ago

What does WP3 need/expect from WP4? Will NR deploy their algorithms directly on Sigma2 and, if so, how close are they to doing this? Will they use their own infrastructure initially? This may have been clarified already by Kristoffer or Daniel (?).

KristofferKa commented 2 years ago

Daniel has had a bit of dialogue with Jarle at NR (jarlehr), but so far NR has been developing their ML stuff on their in-house infrastructure. Software/code to be deployed currently sits with NR and I know Daniel has asked if they could add/include this in SeaBee-no (GitHub).

  1. I suspect it is necessary to sync with @danielborseth to get up to speed on this.
  2. Also, there is a need to meet up with NR in order to clarify further (e.g. based on where we are now).

Wrgds to expectations across WPs (e.g. WP3 <> WP4) the project originally set up this overview (accessible in the SeaBee Teams site): "WP interactions and deliverables" ...but this is very high-level and not necessarily up-to-date anymore.

Snapshot: image

KristofferKa commented 2 years ago

To the specific questions above:

What does WP3 need/expect from WP4?

See comment above.

We need to... a) sync with Daniel, and... b) meet up/discuss/clarify and agree with NR... ...accordingly.

Will NR deploy their algorithms directly on Sigma2 and, if so, how close are they to doing this?

Yes, the idea was that they should (be able to) deploy their "ML processing chains/pipelines" directly on SeaBee@Sigma2, and that these (ideally) should pick up (e.g. be triggered) by new data (from drone missions) being uploaded (and "pipelined") into Sigma2.

I don't think this has been tested (again, see comments above), but should definitely be in focus this year (e.g. testing/piloting this).

Will they use their own infrastructure initially?

a) Up and till now; yes, they're developing on their own infrastructure (either due to preference/simplicity and/or limited access to Sigma2 so far).

b) Looking forward; unsure (presumably no?). Still, they might be using their own infrastructure to develop new stuff, but deploy (test and run) on Sigma2 for the project, but this needs to be discussed with NR.

This may have been clarified already by Kristoffer or Daniel (?).

Too some degree, but far from exhausted. (See all of the above.)