Jump to content


Popular Content

Showing content with the highest reputation since 03/31/14 in all areas

  1. 1 point

    TUFLOW FV 2020.01 Release

    TUFLOW FV 2020.01 Release We are proud to announce the 2020.01 TUFLOW FV release is here!!! With it comes our new state-of-the-art Sediment Transport Module and Particle Tracking Modules as well as numerous updates and enhancements including: Heat module updates. Model output improvements. Python tool updates. QGIS plugin updates including the native read of TUFLOW FV NetCDF and Particle NetCDF. Changes to module licensing. Updates to the TUFLOW FV User Manual. New Sediment Transport and Particle Tracking User Manual. Release Notes: https://www.tuflow.com/Download/TUFLOW_FV/ReleaseNotes/TUFLOW_FV_Release_Notes_2020.pdf Software Download: https://www.tuflow.com/FV%20Latest%20Release.aspx Thank You Thank you for your support. We have a big year planned for TUFLOW FV and are excited to share our modelling software with you. If you have any queries concerning the release please don’t hesitate to get in contact at support@tuflow.com. Kind regards, Mitchell Smith - TUFLOW FV Product Lead
  2. 1 point

    how to define weir boundary

    Thank you very much.
  3. 1 point
    The 'expression' property of fvg objects has a few more advanced options for truly customized output. One of these is the ability to bring in a workspace variable as part of your expression. Just put a dollar sign ($) in front of the variable that you wish to include from your workspace, ie. if you have a variable a=2; and you want to offset your water levels by this then '$a+H' would be your expression string. For single scalars though it is probably better to specify it directly, ie. if you want to offset all the water levels by 2m then 'H+2' is easier than storing the 2m in a variable beforehand. The real strength of this is for vectors, keep in mind that as usual, these vector and matrix operations will have specific limitations on size, and there are no extra checks in place to account for this. A useful example of using this is to plot the difference in a variable since a particular timestep, for example the start. A quick example is plotting the total change in bed level since the beginning of the model run, it will require extracting a variable seperately first. tmp = netcdf_get_var(modfil,'names','ZB','timestep',1); %BMTWBM function that will extract ZB at the first timestep firstbedlevel = tmp.ZB; %get it out of a structure and save it to a useful variable fobj = fvgraphics; %usual, gca customsheet = fvg_sheet(fobj, modfil, 'expression', 'ZB - $firstbedlevel') There are a lot of possibilities with this, the only downside being that it does require a bit of setting up first to get the variable that you want. Keep in mind that this variable will be 'saved' into the function persistantly, so even if you clear the original 'firstbedlevel' from your workspace, or change it, only the original one will be used in the calculations. If you wish to update the variable, then you must call the 'set' method on the expression again. ie. firstbedlevel = firstbedlevel+1; %changed the variable set(customsheet,'expression','ZB - $firstbedlevel'); %now it will bring in the new version of 'firstbedlevel';
  4. 1 point
    Syntax highlighting is also possible using Notepad++ See: http://fvwiki.tuflow.com/index.php?title=NotepadPlusPlus_Highlighting
  5. 1 point
    The dat file limit does not apply to recent versions of SMS. I have no trouble opening and interacting with dat files several GB in size. Note I'm using SMS 11.x 64-bit. Older 32-bit versions may have a limit on file size.
  6. 1 point
    Question I would like to use the cell elevation input file command to overwrite the centre centre elevations in my model. Cell Elevation File == <cell elevation file (.csv), xytype, ztype> Is there an easy way to get a list of the cell IDs and the associated cell centre x,y co-ordinates? Answer Yes, you can use the echo spatial command to get this information. Echo spatial == 1 !(default == 0, off) This command will write a file to the log folder called '<run_name>_spatial_geo.csv'. The file contains a summary of the geometry data (cell ID, cell centre xy coordinates, elevation, material). The data from this echo file can easily be updated and used as a cell elevation file for future simulations.
  • Create New...