Jump to content

Search the Community

Showing results for tags 'mesh'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • About this forum
    • How to use this forum
    • Forum Feedback
    • Announcement
  • TUFLOW FV Modelling
    • Dongles/Licensing/Installation
    • Mesh Building
    • Numerical Scheme
    • Model Building
    • Initial Conditions
    • Boundary Conditions
    • Turbulence
    • Structures
    • 3D Module
    • AD Module
    • Atmospheric Module
    • ST + MORPH Module
    • Post Processing
    • Other
    • Errors
  • Other 3rd party products
    • SMS
    • MatLab
    • Excel
    • GIS
    • Text Editors

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 6 results

  1. When I visualise the 2D model outputs in Matlab it doesn't show any results at some of the elements. The elements are not getting dry as the water depth at the elements is enough to be wet during the entire simulation period. Over the simulation period some of these elements have result at some time steps but most of the time steps there is no result at these elements in the 2d view. Some of these elements result in zero value over the entire simulation period. I am not sure whether these elements are not resolved (e.g due to the shape of the mesh) or the resolved current speeds are less than the model precision. Would you please let me know how I can rectify this issue?
  2. During the process of converting the "map" into "mesh" and merging some of the triangles, SMS (11.2.11) removes some arcs ( to merge the triangles) but remains a few nodes which are related to the removed arcs. The nodes are eventually just connecting two arcs and will result in error in Tuflow as they create some invalid elements in the mesh. previously I had the same issue but it resolved when I used an older SMS version ( Can't recall what version I had at that time) Would you please advise which versions of SMS could be used? or alternatively if there is any other way to fix this issue. Regards, Hamid
  3. FVG objects construct a matlab patch object for the actual image that is presented on screen. Each face of the patch object represents the cells of the model, and the corners of these faces represent the vertices. The handle to this patch object is stored as a property of the fvg objects, which allow us to customize various aspects of the visualisation. Just a few of the options for this: If you want to apply a slight transparency to the entire mesh equally, you can edit the patch object's facealpha property. sheet1 = fvgsheet(fobj, modfil) patchhandle = sheet1.PatchObj; set( patchhandle , 'FaceAlpha', 0.5) This sets all the faces of the patch to be 50% transparent. Be careful when setting these patch properties as some of them will be updated by moving the slider bar, and all your hard work will be erased. for more info on patches and their properties, see MathWorks documentation on patches. http://www.mathworks.com.au/help/matlab/ref/patch.html http://www.mathworks.com.au/help/matlab/ref/patch_props.html
  4. Guest

    switching off cells

    Question: How can I quickly turn off sections of a model? For example if I only want to look at one lake or estuary which is located in a wider model mesh? Answer: In SMS, set the material type of areas you do not want to simulate to zero. Then include the following command in the tuflowfv control file: material == 0 inactive == 1 end material All cells with material zero will now be excluded from model calculations.
  5. Guest

    Sizing function in SMS

    Hi Check out an interesting forum discussion: http://forum.aquaveo.com/topic/1403-sizing-function/ This discussion details the use of sizing functions in mesh generation, where a paved mesh area can be generated where mesh transitions are controlled according to user specified constraints. Very handy. Chris
  6. When generating a mesh in SMS, I notice that the element and node numbers aren't always consecutive. This is especially the case if I am editing an existing mesh, or delete specific sections, etc. Does this have any consequence on running TUFLOW FV?
  • Create New...