GitLab

addition of function to limit spatial coverage of FVCOM structure variable as produced by read_FVCOM

Error in add_weights_FVCOM_nested_forcing... The weight_node variable was transposed before writing it out... no idea what sort of the surface elevation we were imposing at the boundaries when node weights were all 0.2git add fvcom_prepro/add_weights_FVCOM_nested_forcing.m

into a MATLAB datetime array.

find_nesting_region If somebody made the same mistake as me, and thought that conf.power was per boundary, raise an error rather than doing everything wrong.

Allows later lazy boolean stuff (use of &&) without error.

and finds the maximum CFL encountered during the run in each mesh element. Helpful for optimising meshes by fixing the worst triangles.

read_sms_mesh bug fix and enhancements

See merge request !1

   bathymetry file is provided, use the bathymetry in the file (with a
   warning) rather than ignoring it.

read_sms_mesh.m : rewrote the parsing of nodestrings to avoid it going wrong if the number of nodes in a string is a multiple of ten.

read_sms_mesh.m : bug fix : if we have both xy and lon/lat coords in the output stage, don't replace the lon/lat ones with zeros.

Add colour option to the quiver plotting in plot_fvcom_field.m

set_elevtide_tmd.m: made the path to the TMD toolbox an input argument, rather than it being hardcoded in the function

turbine_area_sigma.m : Removed duplicate check for water too shallow that had crept in through rebasing.