search

ucsb-coast-lab / moos-ivp-ucsb

A collection of MOOS applications and IvP behaviors developed by the COAST Lab at UCSB
6 stars 1 forks source link

splitting up uSimROMS #8

Closed sgillen closed 9 years ago

sgillen commented 9 years ago

it seems like checking bathymetry for safety and simulating salinity etc. data should be seperate processes?

nidzieko commented 9 years ago

agreed.

On Jan 11, 2015, at 11:54 PM, Sean Gillen notifications@github.com wrote:

it seems like checking bathymetry for safety and simulating salinity etc. data should be seperate processes?

— Reply to this email directly or view it on GitHub.

nidzieko commented 9 years ago

Seems like the right way to do this might be to transition the ROMS read to a library function and then have processes (or behaviors?) that utilize that information. Publishing salinity and velocity fields might be a process while (potentially) avoiding upcoming bathymetric changes might be best as a behavior?

On Jan 11, 2015, at 11:54 PM, Sean Gillen notifications@github.com wrote:

it seems like checking bathymetry for safety and simulating salinity etc. data should be seperate processes?

— Reply to this email directly or view it on GitHub.