A two-dimensional triangular mesh generator with pre- and post-processing utilities written in pure MATLAB (no toolboxes required, some support for Octave) designed specifically to build models that solve shallow-water equations or wave equations in a coastal environment (ADCIRC, FVCOM, WaveWatch3, SWAN, SCHISM, Telemac, etc.).
Home Page: https://github.com/sponsors/krober10nd
License: GNU General Public License v3.0
Hi @krober10nd and @WPringle,
I am wondering if oceanmesh2D can handle mixed (tri and quad) grids and curved lines for open boundaries (instead of a rectangular box) as done in SMS? or is there any idea to make it possible?
Thanks a lot :)
Cheers,
Huy
If a mesh grossly violates the cfl condition, let's output a warning when writing.
I noticed that errors with traversability even after passing Make_Mesh_Traversable can occur, but this typically only happens after complicated processes such as mesh merging and never from a mesh that has been just generated by meshgen.build.
I found that this traversability problem seems to becoming from the fact that a triangle is specified as being made up only two unique nodes (i.e., one of the nodes is entered twice in a triangle).
As Keith has mentioned previously, I agree that we need to introduce some sort of parser/listener to automatically deal with and/or notify about such strange triangulations or NaNs being introduced into the mesh.
Hi @krober10nd and @WPringle,
I am following the typical workflow provided in the userguide to create input files (fort.15) for ADCIRC simulation. When I type the code m = Calc_tau0(m), an error occurs and prompts "No bathymetry data in the grid to calculate the tau0 coefficients". However, I have complete the interpolation by carrying out the previous step m = interp(m, DEMFILE, 'type', 'depth'). In the msh class, the attribute of b is not empty and the value of b is not always 0. I don't know why this happened. The following is my code,
% Example: Mesh the PRD
clearvars; clc;
addpath(genpath('utilities/'))
addpath(genpath('datasets/'))
addpath(genpath('m_map/'))
%% STEP 1: set mesh extents and set parameters for mesh.
bbox = [111.5 116.5; % lon_min lon_max
18 24]; % lat_min lat_max
min_el = 150; % minimum resolution in meters.
max_el = 5e4; % maximum resolution in meters.
max_el_ns = 200; % maximum resolution nearshore in meters.
grade = 0.3; % mesh grade in decimal percent.
R = 3; % number of elements to resolve feature width.
%% STEP 2: specify geographical datasets and process the geographical data
%% to be used later with other OceanMesh classes...
dem = 'topo15_compressed.nc'; coastline = 'GSHHS_f_L1';
gdat = geodata('shp',coastline,'dem',dem,'h0',min_el,...
'bbox',bbox);
% NOTE: You can plot the shapefile with bounding box by using the
% overloaded plot command:
% plot(gdat,'shp'); plot(gdat,'dem');
%% STEP 3: create an edge function class
fh = edgefx('geodata',gdat,...
'fs',R,'max_el_ns',max_el_ns,...
'max_el',max_el,'g',grade);
%% STEP 4: Pass your edgefx class object along with some meshing options and
% build the mesh...
mshopts = meshgen('ef',fh,'bou',gdat,'plot_on',1,'nscreen',1);
mshopts = mshopts.build;
m = mshopts.grd;
% plot(m,'tri');
DT = 2 ; % Stable timestep
TS = '01-Aug-2012 00:00' ; % start time of simulation
TE = '31-Nov-2012 00:00' ; % end time of simulation
DEMFILE = 'topo15_compressed.nc';
BUOYFILE = 'Gridded_N_values.mat';
TPXO9 = 'h_tpxo9.v1.nc';
CONST = 'major8';
m = interp(m, DEMFILE, 'type','depth');
plot(m,'b')
m = CheckTimestep(m,DT);
m = renum(m);
m = make_bc(m,'auto',gdat); % make the nodestring boundary conditions
% plot(m,'bd',0);
% makens(m,'outer',1)
m = Calc_tau0(m);
Looking forward to your reply.
Best wishes.
Jiangchao
Currently the msh class contains fixed points (m.pfix) and fixed edges (m.egfix) variables.
m.pfix variables are just coordinates that presumably also exist in the main mesh point space (m.p). And m.edgfix refer to indices of m.pfix.
This is a somewhat clumsy way of treating fixed points and edges which makes it a bit annoying to manage them, and may require us to do a knnsearch to find the indices that match between m.p and m.pfix. For the meshgen it makes sense that we pass fixed points coordinates, but as an output into the msh class, the fixed points should just refer to indices in m.p.
I propose that we eliminate m.pfix and only keep m.egfix which should just be indices of m.p. That way we can also use the m.egfix in the constraints option for the DelaunayTriangulation class directly as is. m.pfix can be trivially recovered by m.p(unique(m.egfix(:)),:). This change will require us to treat the fixed points differently in the cleaning and merging routines etc, but it will be much neater imo.
In \subsection{Around the world: \textit{Example\_1\_NZ.m}} code example, you call the variable min_res wich does not exist.
In \subsubsection{Methods}, the third element in list has a broken reference Section \ref(sec:).
Increasing the multiplier on dx and dy makes resolution transitions smoother between nests appeasing some our our more critical users.
plot).simpplot?dem = geodata('dem',DEMNAME,'h0',min_el);
plot(gdat,'dem');
hello,my friend:
I downloaded the compression package and unzipped it under my MATLAB/Toolbox folder. I opened MATLAB and added the path. The software showed an error: the folder starting with @ could not be added to the path.
So I changed all the folder names with @ (such as @ann to Ann), but could not add them, showing that MATLAB could not save the changes to the modified path,pathdef.m may be a read-only file.I added each folder separately and found that it was the Ann folder that made the error.
I tried many methods but could not solve it. I installed other MATLAB tools normally, and the MATLAB I used was 2017A version. Hope to get your answer or email, thank you very much.
It should be something like this:
% Generate triangulation
dtr = delaunayTriangulation(x,y);
% 1. Get all the triangles attached to a particular vertex in the
% triangulation.
attachedTriangles = vertexAttachments(dtr);
for i = 1: size(x,1)
% 2. Use the connectivity list to get the vertex indices of all these
% triangles
verticesOfTI = dtr.ConnectivityList(attachedTriangles{i},:);
% 3. Find all the unique vertices and remove the current vertex
neighbours{i} = setdiff(unique(verticesOfTI), i);
end
Hi,
I have been trying to create the mesh boundaries using "makens" at the end of mesh workflow and noticed too issues/glitches , may be you guys can take a look at it.
For the entire North Atlantic mesh we noticed that it create 1200+ mainland nodestrings using the "auto" option and the only possible way around we figured out was to use "islands" option. That way we will load the mesh in SMS and delete the most outer island to recreate mainland and ocean boundary only.
Using the interpFP interpolation scheme and later assigning the mesh boundaries using "makens" for the small rivers like Potomac, it will not recognize the ocean and mainland boundary. And it assigns only the island boundaries by using "auto" or "islands".
meshFull_FP = interpFP(meshFull,gdatovFull,muwFull,gdatuwFull,0.05,0);
It will be great if you kindly take a look at it.
Thanks
Hi,
I have been following the guide and I am trying to run through the examples.
I have installed m_map in the root folder and put the 'GSHHS_f_L1' shapefile in the datasets/ folder.
However I am running into an issue, the following error occurs when running Example_1_NZ.m:
Reading shapefile with m_shaperead
179837 Records in file, by 500:
.......................................................................................................................................................................................................................................................................................................................................................................Partitioning the boundary into islands, mainland, ocean
Smoothing coastline with 5 point window
Reading shapefile with m_shaperead
5706 Records in file, by 500:...........Partitioning the boundary into islands, mainland, ocean
'Read in meshing boundary: ' 'GSHHS_f_L1'Building feature size function...
Warning: No mainland or innerIn edgefx/featfx (line 262)
In edgefx (line 212)
In Example_1_NZ (line 20)
Error using &
Matrix dimensions must agree.Error in edgefx/finalize (line 775)
hh_m(nearshore & hh_m > obj.max_el_ns) = obj.max_el_ns;Error in edgefx (line 246)
obj = finalize(obj,feat);Error in Example_1_NZ (line 20)
fh =edgefx('geodata',gdat,...
Hi, an idea for your consideration--
I'm wondering if it could be useful to do multi-pass mesh generation by:
The idea being to better focus the mesh effort into areas of known high flow that the M2 shallow water wave eq. might not specifically capture, e.g. tidal straits or the inlet of an estuary which includes a large river flow as a boundary condition.
i.e. use a 'real' value for |u| in the CFL calculation instead of just estimating it.
At minimum it could be used to simply plot a map view highlighting areas where your mesh is either too coarse or needlessly fine, based on initial fort.64 results.
Would be nice to have plot have one more option to ‘hold on’. By default all plot options should create a new figure but sometimes you want to plot on top of different plots.
I am testing out the mesh generation software and I am getting the following error when running Example_1_NZ using m_map 1.4 and Matlab 2017a on a windows laptop. Any help is much appreciated.
.......................................................................................................................................................................................................................................................................................................................................................................Partitioning the boundary into islands, mainland, ocean
Index exceeds matrix dimensions.
Error in Read_shapefile (line 149)
tmpCC{nn,2} = tmpC{ii,2};
Error in geodata/ParseShoreline (line 276)
polygon_struct = Read_shapefile( obj.contourfile, [], ...
Error in geodata (line 240)
obj = ParseShoreline(obj) ;
Error in Example_1_NZ (line 17)
gdat = geodata('shp',coastline,'bbox',bbox,'h0',min_el);
Hi,
In the pdf user guide's Typical Workflow Example (sec. 6.9), line 30 of the listing says:
m = Calc_IT_Fric(m,'Nfname',BUOYFILE) ;
but the current version of the function does not have 'Nfname' as a varargin pair, it's mandatory. So if you try to run the code as presented it looks for a file called 'Nfname.mat', unsuccessfully.
Also TPXO is now up to version 10, you may want to update that link in the text of the section.
(by the way, the final version of WOA 2018 is now available for download since Aug 29th, I don't think it is announced anywhere but the netCDF internal metadata will show it)
In the 7.1.2 Methods help for write() it says:
however, the user can optionally decide
to write only a select few of these files by passing a comma-delimited list of the post-fix name
types (e.g., 14,15 to denote fort.14 or fort.15).
it looks for a string not an int, so: e.g '14','15' to denote fort.14 or fort.15 helps the reader avoid a few moments of confusion.
thanks,
Hamish
Hi my friend,
I was wondering if OceanMsh2D can generate mesh file that can be read by WAVEWATCH III directly? Or I need to revise the mesh format (fort.14) to fit WAVEWATCH III mesh format (.msh)? Thanks.
Kind regards,
Jin
If you execute msh.clean, the routine will not correctly map you bathymetry back onto the msh vertices correctly.
(latest checkout)
>> plot(m, 'b')
Cell contents reference from a non-cell array object.
Error in setProj (line 52)
projtype = projtype{1};
Error in msh/plot (line 274)
del = setProj(obj,proj,projtype) ;
@msh/msh.m line 245 should catch this, but doesn't.
if proj && isempty(projtype)
In my test m.coord=[] and proj=1.
m was generated with m = msh('mesh14file');
thanks,
Hamish
Hi,
I know this software is mainly designed for circulation model, but I want use it for SWAN that mainly refines the mesh nearshore. Hence, I only turn on distance function and closed options of wavelength, slope and polyline.
After that, the software mainly refines mesh with 20 km offshore (from red line to blue line), how can I extend such refinement to 50 km offshore (from red line to green line)? I know it can be refined in a small rectangular region, but not like offshore distance-based region in the figure. I also try to revise d-value in distance function, but it doesn't work. Could you help me to fix it? Thanks for your help.
Kind regards,
Jin
Pits in the bathymetry can make the wetting/drying portion go unstable.
Here's a little code contribution to replace pits with the average bathymetry
of the neighboring nodes, if it may be useful.
% find pits in OceanMesh2D mesh bathymetry
% Hamish Bowman 10 Sept. 2020
m = msh('fort14_with_pits');
m_orig.b = m.b;
% find node points likely to see some wetting and drying
% may want to get rid of upper bound (here 5m above MSL)
intertidal = find(m.b < 3 & m.b > -5);
sz = size(m.t);
is_pit = zeros(size(m.b)); % init array
mean_neighbors = nan(size(m.b)); % init array
% brute force
% note: this modifies along the way, not atomically at the end
% so pits may come and go as the neighboring pit nodes get filled
tic
for n = [intertidal']
idx = find(m.t == n);
[rows cols] = ind2sub(sz, idx);
hits = m.t(rows, :);
neighbors = unique(hits(find(hits ~= n)));
% ignore spur nodes along the boundary (maybe skip all bdy nodes?)
% or run QA code to nuke spur elements first?
if(length(neighbors) > 2 & m.b(n) > max(m.b(neighbors)))
disp(['node ' num2str(n) ' (' num2str(m.b(n), '%.3f') ...
') is an intertidal pit with ' ...
num2str(length(neighbors)) ' neighbors who average ' ...
num2str(mean(m.b(neighbors)), '%.3f') ' meters depth'])
is_pit(n) = 1;
mean_neighbors(n) = mean(m.b(neighbors));
% replace if pit is more than 10 cm deep (does size of pit matter?)
if(m.b(n) - max(m.b(neighbors)) > 0.10)
disp([' * diff: ' num2str(m.b(n) - max(m.b(neighbors)))])
m.b(n) = mean(m.b(neighbors));
end
end
end
toc
disp([num2str(length(find(is_pit))) ' pits found in mesh bathymetry'])
% or to fill in pits after the scan, (e.g. if scan is multi-threaded)
%for n = [find(is_pit)']
% % replace if pit is more than 10 cm deep (does size of pit matter?)
% if(m.b(n) - mean_neighbors(n) > 0.10)
% m.b(n) = mean_neighbors(n);
% end
%end
%%% you may want to iterate through this 2-10 times.
As in meshgen with the formation of points, it’d be useful to read in the DEM in blocks in geodata based on say an assumption the user has 8 gab of RAM and downsample to avoid overloading the RAM each block as they are read in
Hi Keith, William, Joannnes,
Thanks for the smart mesh generator in coastal region. I was wondering if there is any program to sort the vertices ? Since when run swan using the generated mesh, it shows "numbering of vertices is not sequential in Triangle file". Vertices and triangles file in SWAN have to meet its numbering requirement. Thanks a lot for your patient explanation.
Kind regards,
Jin
hi @krober10nd
I am confused about the method of automatically determining the time step.
In Example_3_ECGC, the time step was set to 0.
When I followed this setting, I found that the time step dt calculated based on the nearshore resolution is very small.
Therefore, the mesh resolution calculated according to the original code of Example 3 is very small, and it runs very slowly.
When I set dt to 2, as in Example_2_NY (Encourage mesh to be stable at a 2 s time step), It turned out to look good.
If using the automatic step size method, is such a small value of dt reasonable to use in the simulation? Or should I specify it myself?
Best wishes
Jiangchao
I propose to rename the msh method makens to make_boundaries for easier understanding.
Need to add BoundCr method details and updated details about MakeBC...
On termination, it's possible to repeatedly project only the boundary vertices back onto the 0-level set for better boundary conformity.
See here what I did in Python.
Here's the function call:
https://github.com/krober10nd/SeismicMesh/blob/fa4cbc97a987d3468e6362fce6c76efe05f47bdf/SeismicMesh/generation/mesh_generator.py#L629
bbox = [0, 1; 0,1];
boubox = [0,0; 1,0; 1,1; 0,1; 0,0; NaN NaN ];
min_el = 1e3;
gdat1 = geodata('pslg',boubox,'bbox',bbox,'h0',min_el);
fh1 = edgefx('geodata',gdat1,'g',0.15);
bbox2 = [-1, 2; -1,2];
boubox2 = [-1,-1; 2,-1; 2,2; -1,2; -1,-1; NaN NaN ];
min_el2 = min_el*5;
gdat2 = geodata('pslg',boubox2,'bbox',bbox2,'h0',min_el2);
fh2 = edgefx('geodata',gdat2,'g',0.10);
mshopts = meshgen('ef',{fh2, fh1},'bou',{gdat2,gdat1},'plot_on',1,'itmax',5,'cleanup',0);
mshopts = mshopts.build;
m = mshopts.grd;
plot(m)
Whether or not I comment out the call to smooth_outer in meshgen produces the same results. There should be a smooth transition out of the nest.
A new file format for write should be added called vtu and vtk. This enables users to visualize their meshes inside Paraview and for solvers like FireDrake. The former visualization software is quite efficient compared to MATLAB's visualization capabilities.
For example this MathWork's submission is particularly good. https://www.mathworks.com/matlabcentral/fileexchange/47814-vtkwrite-exports-various-2d-3d-data-to-paraview-in-vtk-file-format
(Sorry for being so annoying - I only want to improve this project)
When the program reads the netCDF DEM file, only checks for the existence of 'lon', 'lat', 'x' or 'y' variables. In some datasets (including the SRTM 15 Plus), those variables are called 'longitude' and 'latitude'.
geodata.m at line 161 must try to find those nomenclatures before throwing an error.
Apparently it dies every 30 days unless we pay?!
Mainly for functionality for SCHISM, it seems that it would be good to include the inverse of the current 'dt' function in edgefx and CheckTimestep functionality that will make the mesh finer where the CFL is too small (They suggest something like CFL > 0.5 everywhere for SCHISM so that the Lagrangian advection scheme stays accurate).
Ideally we can should be able to set a band so that CFL should be at least 0.5 and less than say 6 or whatever.
For example in CheckTimestep we can add points somewhere close to where the CFL is too small in addition to deleting points where CFL is too high like we do now.
First of all, thank you very much for this tool you developed! It is great!
I am trying to generate my first grid to later be used in SWAN. Everything is working great so far. However, I am a bit confused about the meaning of the colors when the program shows the mesh. For example the difference between the red and blue here:
I tried to find this information in the manual without success. Hopefully, I am not missing something obvious.
Thanks again.
Almir
Hi,
Apologies for raising another issue, so far I have been pretty impressed with the adaptability, I have read through the manual and cannot seem to find anything that I think might help other than perhaps using pfix in meshgen at the corners.
So I started by using example_2_NY as a starting point and have been progressively worked from there add elements I want. However all the nested meshes I produce either one or both of the eastern boundaries seem to end up with some sort of error, whereby the coordinates for those elements seem to be 0,0.
Attached is my matlab file:
mesh_build_gc_nest.txt
The reason I think that it is a coordinate error is when I import the file to Blue Kenue it looks like the below.
Thanks,
Drak
[dev BRANCH]
Using a shapefile containing a single poligon, I get some coastline areas better smoothed than others. A picture is worth a thousand words:
Is there any way to fix it?
Hi @krober10nd and @WPringle,
I was wondering if you guys would be interested in adding the ability to input user-defined edge functions. I wrote a bit of crude code to do this in OceanMesh2D and am happy to share it back to the repo. If you're interested, I can open a PR. If not, no big deal at all!
Hi Keith, William,
I am making a mesh over the wharf like the land, but I want to keep its shape (e.g. straight line, not weirs) An example is attached. Is OceanMesh2D capable of doing that?
Thanks, mates
Huy
Some shapefiles for example those from grass can be made 3D. In this case, they contain a 3rd dimension height. However, triggers the usage of toolbox functionality in geodata ('polybool') which is incredibly slow. Can we activate this through some other means?
...to highlight the patching idea rather than using the multiscale approach.
In this example, we should highlight the lock_dis parameter to show that the outside region is unchanged.
It needs some comments on the logic applied as it's nearly impossible to tell how things are working after taking a break and coming back to it.
Is there any way to force the program to mesh a selected side of the shapefile?
In some cases, I got meshed the land surface instead of the water one.
The test to determine whether a given point is in/out of the meshing domain does not require the densified PSLG. Because the PSLG is by definition linear, the densification of points to h0/2 along the PSLG can only create new straight lines between two of the original points on the pslg.
With this said, the densified PSLG is still necessary for the nearest distance calculation. However, a large savings may be obtained through the suggested optimization by reducing the inpoly execution time. This could especially benefit the multiscale method.
SRTM15+ changed version, from v2, to v2.1. You may correct the link in your README.md to:
ftp://topex.ucsd.edu/pub/srtm15_plus/SRTM15+V2.1.nc
Hi @WPringle and @krober10nd,
Thanks for continuing to develop OceanMesh2D! I just started using it recently and noticed some distorted elements in a simple mesh I was making. I thought I'd ask for your advice. Maybe you have experienced something similar.
I modified Example 7 to create a constant resolution 50km global mesh and noticed that there some areas where elements get distorted. See below for examples. Other than these regions, the mesh looks great. I'm using ee76beadd.
New Zealand:
Fiji:
Alaska:
South Africa:
Hi guys,
I was attempting to run CheckTimestep on a mesh without any fixed points. This gives me an error when it tries to clean up the mesh:
Error in msh/CheckTimestep (line 1962)
obj = clean(obj,'passive','proj',0,'pfix',pf,'con',con);
I fixed this on my own by just adding a
if ~isempty(obj.pfix)
[pf(:,1),pf(:,2)] = m_ll2xy(obj.pfix(:,1),obj.pfix(:,2));
else
pf = [];
end
around line 1936 as a quick fix, but I'm not sure if this is going to mess anything up within the code.
Hi,
two small cosmetic issues with the generation of the fort.15 files, the first is mostly cosmetic, the second has functionality implications.
diff --git a/@msh/private/writefort15.m b/@msh/private/writefort15.m
index 0d536df..6e108a0 100644
--- a/@msh/private/writefort15.m
+++ b/@msh/private/writefort15.m
@@ -148,7 +148,7 @@ end
% Open boundary harmonic forcing
for k = 1: f15dat.nbfr
fprintf(fid, '%s \n', f15dat.opealpha(k).name ) ;
- fprintf(fid, '%16.9e %16.9e \n', f15dat.opealpha(k).val' ) ;
+ fprintf(fid, '%16.9e %16.10g \n', f15dat.opealpha(k).val' ) ;
end
% ANGINN
The phase angle is given in engineering style, which makes it annoying to parse as regex in Perl. As engineering units are nice for values which vary over many orders of magnitude, but don't really add much for values which are evenly distributed over the range of 0-360, it's nice for humans reading it to see the regular floating point representation and easier to parse as well.
%16.10g preserves all the precision of %16.9e.
I don't know if anyone else beyond me has to deal with the Perl regex matching, but the human readability aspect might make the change of general interest.
diff --git a/utilities/Make_f15.m b/utilities/Make_f15.m
index 1893f37..aad52be 100644
--- a/utilities/Make_f15.m
+++ b/utilities/Make_f15.m
@@ -192,7 +192,7 @@ obj.f15.dtdp = dt ;
% Runday
obj.f15.rndy = datenum(te)-datenum(ts);
-obj.f15.extraline(10).msg = ts;
+obj.f15.extraline(10).msg = datestr(ts, 'yyyy-mm-dd HH:MM:SS UTC');
% Checking f11
if ~isempty(obj.f11)
The ts and te time variables are suggested to be in the format of '01-Jan-2018 03:00' in the Make_f15.m header-help and LaTeX docs* and that gets written to the NetCDF footer in fort.15. The parameter notes at adcirc.org state:
NCDATE = The format of NCDATE must be as follows so that ADCIRC can create netcdf files that comply with the CF standard: yyyy-MM-dd hh:mm:ss tz. For example, if the cold start date/time of the run is midnight UTC on 1 May 2010, the NCDATE parameter should be set to 2010-05-01 00:00:00 UTC.
and besides that it means you can't use GNU date to do timestep math on the result, e.g.:
$ date -u -d '2018-01-01 00:00:00 UTC + 3600 sec'
works but
$ date -u -d '01-Jan-2018 03:00 + 3600 sec'
doesn't.
(the above trick with date is a very handy for making time stamps for animations of fort.63 frames, given the start time from the .nc file and 1680000 or whatever seconds of the output timestep)
Matlab's datestr() does not like time zone info like "UTC" or "+0000", so that has to be added by hand. (and assumed to be true!)
[*] n.b. the underscores of Make_f15 links in the LaTeX doc have been UTF-8'd and so become hard to ctrl-f searched for
thanks,
Hamish
Hi, on the commit 3 weeks ago " is used for quoting error message strings not ', and matlab is unhappy with that.
Error using msh
Error: File: /.../@msh/msh.m Line: 1176 Column: 23
Creating a string using double quotes is not supported. Use the string function.
the following patch fixes it:
diff --git a/@msh/msh.m b/@msh/msh.m
index 71b3c97..673490f 100644
--- a/@msh/msh.m
+++ b/@msh/msh.m
@@ -1173,7 +1173,7 @@ classdef msh
% varargins:
% none
if nargin < 2
- error("Needs type: one of 'auto', 'outer', 'inner', 'delete', or 'weirs'")
+ error('Needs type: one of "auto", "outer", "inner", "delete", or "weirs"')
end
if iscell(varargin{1})
varargin = varargin{1};
@@ -1183,11 +1183,11 @@ classdef msh
case('auto')
% automatically applies elevation and no-flux bcs to mesh based on geodata class
if isempty(varargin)
- error("must supply a geodata class for 'auto' as third input")
+ error('must supply a geodata class for "auto" as third input')
end
gdat = varargin{1};
if ~isa(gdat,'geodata')
- error("third input must be a geodata class for 'auto'")
+ error('third input must be a geodata class for "auto"')
end
depth_lim = -10;
dist_lim = 10*gdat.gridspace;
@@ -1202,14 +1202,14 @@ classdef msh
end
case('depth')
if isempty(gdat.Fb)
- error("No DEM info to use 'depth' classification criteria")
+ error('No DEM info to use "depth" classification criteria')
end
if length(varargin) > 2 && ~isempty(varargin{3})
depth_lim = -varargin{3};
end
case('both')
if isempty(gdat.Fb)
- error("No DEM info to use 'both' classification criteria")
+ error('No DEM info to use "both" classification criteria')
end
if length(varargin) > 2 && ~isempty(varargin{3})
dist_lim = varargin{3};
@@ -1224,7 +1224,7 @@ classdef msh
Le = find(obj.p(:,1) < -179, 1);
Ri = find(obj.p(:,1) > 179, 1);
if ~isempty(Le) && ~isempty(Ri)
- error("Detected global mesh, cannot apply 'auto' makens. Try 'inner' option")
+ error('Detected global mesh, cannot apply "auto" makens. Try "inner" option')
end
% Get the boundary edges and mid-points
@@ -1391,7 +1391,7 @@ classdef msh
Le = find(obj.p(:,1) < -179, 1);
Ri = find(obj.p(:,1) > 179, 1);
if ~isempty(Le) && ~isempty(Ri)
- error("Detected global mesh, cannot apply 'auto' makens. Try 'inner' option")
+ error('Detected global mesh, cannot apply "auto" makens. Try "inner" option')
end
% Get the boundaries
G'day @krober10nd and @WPringle,
I have bathymetry (*.mat) data in scatter points (xyz, three columns) , now I want to use it in geodata instead of using "dem" as *.nc file.
Is there any way to handle it?
Thank you very much!
Huy
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.