-
Notifications
You must be signed in to change notification settings - Fork 74
Bug fix/interp and cleaning #283
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…t and wetdry velocity control namelist name
…re present in the mesh (hill-climbing smoothing does not work with fixed points
… > 300. Changing namelists to be added by the user in the function call to Make_f15
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't see anything that looks problematic.
Just remember to delete your branch after you're done. We have a lot branch rot. |
Title: Sample Code to Create fort.15 Using makefort15 with a Given fort.14 Mesh. Hi, I am working on ADCIRC for a tidal simulation. I have already created the fort.14 mesh file, and I now need to generate the corresponding fort.15 file. I understand that the makefort15 subroutine can be used for this purpose. Could you please share a sample script or example code showing how to use makefort15 to create fort.15 when fort.14 is available. |
Hi, this is a pull request (that's closed). Use the issue tab to post an issue. The user guide shows how to use the makefort15 function and there's an extensive help docstring. |
make_bc
call with empty varargin, e.g., when callinginner
ourKNNsearch
innanfill
option withGriddata
(msh.interp
)m_map
link insetup.sh
Error setup.sh link m_map #277Make_offset
with constant offset (length 1 time_vector)ds=1
) when fix points are present insidemsh.clean
.Make_f15.m
fort.15 generatorfort.15
namelists from the default setup and addingnamelist
as an argument toMake_f15
. User provides the list of namelists desired.Make_f15
help for all available input arguments.NWS > 300
for SWAN wave coupling. In this case theRSTIMNC
wave timestep must be supplied and this is written out into theWTIMNC
line infort.15