Coastal-Imaging-Research-Network / cBathy-Toolbox

Routines needed to run cBathy + demos
https://github.com/Coastal-Imaging-Research-Network/cBathy-toolbox/wiki/cBathy-User-Manual
GNU General Public License v3.0
25 stars 23 forks source link

Issue democBathy #31

Closed ApuliaMonitoringNetwork closed 6 years ago

ApuliaMonitoringNetwork commented 6 years ago

Dears,

it seems that from version 1.1 to 1.2 there is an issue and several errors appears, most probably related to the introduction of the cams ID variable in v.1.2.

Regards.

KateBrodie commented 6 years ago

Hi! Thanks for your response - could you please provide some additional details and specific documentation on the issues and errors you are experiencing with v1.2? We'd be happy to help address any of your concerns if you could provide some specifics! Thank you! @mpalmsten @jstanleyx

ApuliaMonitoringNetwork commented 6 years ago

Here's the error: Error using analyzeBathyCollect (line 37) Not enough input arguments.

Error in analyzeSingleBathyRunNotCIL (line 22) bathy = analyzeBathyCollect(xyz, t, data, bathy);

Error in democBathy (line 10) bathy = analyzeSingleBathyRunNotCIL(stackName, stationStr);

Thanks!

jstanleyx commented 6 years ago

Found missing params. Should be fixed as soon as cam-fix is merged.

On Thu, 2018-02-15 at 07:00 -0800, Apulia Monitoring Network wrote:

Here's the error: Error using analyzeBathyCollect (line 37) Not enough input arguments.

Error in analyzeSingleBathyRunNotCIL (line 22) bathy = analyzeBathyCollect(xyz, t, data, bathy);

Error in democBathy (line 10) bathy = analyzeSingleBathyRunNotCIL(stackName, stationStr);

Thanks!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

KateBrodie commented 6 years ago

Hi @ApuliaMonitoringNetwork, this issue has been fixed in the development version. We will also merge into master and update the release of v1.2. Thanks so much for your feedback!

KateBrodie commented 6 years ago

@ApuliaMonitoringNetwork the issue has been resolved and v1.2 re-released with the updates. Thanks for pointing this out!