Jump to content
TUFLOW FV

Toby Devlin

Administrators
  • Content Count

    25
  • Joined

  • Last visited

  • Days Won

    1

Toby Devlin last won the day on September 25 2014

Toby Devlin had the most liked content!

About Toby Devlin

  • Rank
    TUFLOW-FV user
  • Birthday 07/22/1992

Profile Information

  • Gender
    Male
  • Location
    Brisbane
  • Interests
    Music, food, answering forum posts

Recent Profile Visitors

1870 profile views
  1. Toby Devlin

    Version

    Hi Xixi, We have not compatibility tested the full toolbox on Matlab 2013b in quite some time. I can confirm that it works on 2017b - onward at this stage with certainty. However, that error makes it appear as though it is to do with the input datatype. It appears that one of the inputs is a cell array which is not expected. Its possible that whatever script is calling this function is treating variables in a different way in 2013b compared to 2019b. Do you require 2013b for a particular reason? or are you able to proceed using 2019b (or later)?
  2. Hi Keith, The atmospheric calculations for albedo (used in the incident radiation calculations) require a day of the year and a time of day at this stage. There is an item on the development list to calculate an average for users simulating in hours, or to specify a 'start date'. In the mean time unfortunately you will have to convert your model over to isodate to use the atmospheric calculations. I will update the documentation to reflect this limitation. -Toby
  3. Hi Keith, You can specify either 'surface sigma layers', or 'sigma layers' as both are accepted. Toby
  4. Hi Keith, You can specify either 'surface sigma layers', or 'sigma layers' as both are accepted. Toby
  5. Hi Ale, The bc default will be set to NaN. You can specify bc default == 20, etc. If you wish to apply a constant value. However, builds from 2014.01.024 onward will take the surface water temperature when the model finds NaN for precipitation temperature. Toby
  6. Hi Rohan, Most likely the output path name either has a typo in it, or not all of the folders have been created yet. Double check that the path exists exactly as specified in the error log.
  7. Hi Rohan, The error is most likely to you having two (or more) BCs specified on grids, but the grids have been given the same name. Double check the names of the grids you have specified and make sure they are all unique.
  8. Hi Keith, There are also alternative update options for cell-centered bathymetry such as polylines and polygons. These are all specified in the TUFLOWFV manual section 4.2.2 Toby
  9. Hi Keith, You are correct that the elevations of the model may need to be changed. The extreme case is when the cells adjacent to the culvert are so high as to not get wet at all, then there can be no flow through the structure. Even if they are wet however, the flow will be limited as the culvert appears cut off by the bathymetry. Have you specified the mesh elevations within the .2dm file or through a separate cell-centered csv? If you have specified through the .2dm, keep in mind that as TUFLOWFV is cell-centered, the true elevation internal to the model will be interpolated from the mesh vertices to the centroid of each cell. This can make things difficult in situations such as yours when attempting to control that cell without changing others. If not, then it should be a simple method to adjust the elevation of the relevant cells to be equal to or less than the culvert invert, and not affect any other cells.
  10. Hi PHA, It seems what you are most likely looking for is an 'initial condition 2D' specification. Initial condition 2D == my_initial_2d_file.csv Where the csv has a header line that is ID, TRACE_1, and corresponding values below. The first column is the cell ids, you don't need all of them, just the ones that you wish to change, though you can specify all if you wish, and the second column is the tracer concentration you want to initialise the model with, ie. 100. You can also use these files to set the water level (WL) current velocity (U, V), salinity (SAL), temperature (TEMP) and any other tracers you are modelling (TRACE_2, TRACE_3, etc) if you wish. We are also working on improving our BCs with FC_POLY boundaries, allowing users to have scalar inflows over all the cells within a user-specified polygon.
  11. Hi Lei, Thanks for posting. There are a few options to fixing your problem. The key is that the model by default will extrapolate internal water levels into the 'ghost cells' downstream of your weir. This means that the weir has the same water level either side causing complications. There are three options to force the model to do what you want. 1. You can add extra cells downstream of your weir and set a water level boundary around those cells to ensure they are always lower than your weir crest. 2. You can just add a water level boundary to the same nodestring as your weir is on. This is the same as solution 1 except the water level boundary will apply to the ghost cells so you cannot extract results from the ghost cells to confirm, though it doesn't require changing your mesh. 3. Instead of a weir structure you can specify an HQ bc boundary on your nodestring. HQ bcs require a comma delimited file of water levels and corresponding flow rates (make sure that you use negative flows for outflows). You can specify a range of water levels H and then use flows specified by Q = CBhd2/3 where hd is the height of water above your weir crest, not necessarily the same as the H column. The model will then interpolate the flows linearly between the water levels that you choose. ie. for a 100m wide channel with a weir crest at -2m and a weir coefficient of 1. H,Q -2,0 -1.98,-7.368062997 -1.96,-11.69607095 -1.94,-15.32618865 -1.92,-18.56635533 -1.9,-21.5443469 -1.88,-24.32880798 -1.86,-26.961995 -1.84,-29.47225199 -1.82,-31.87975708
  12. Hi Lei, without seeing your control file i would assume that the directory ../output/ may not exist? TuflowFV assumes that to be the default output directory, if you wish to have the output written to a different location then please use the command output dir == /my/output/directory/ If this isnt your problem, then I will need to see your control file.
  13. Hi Welcome to the forum, There is an existing post for installation of TuflowFv on a linux system: If you are referring to the process of actually running the software, you can call the command with the control file as the argument, ie. user@linuxmachine: ~> /home/software/tuflowfv/trunk/platform/linux_ifort/tuflowfv my_control_file.fvc or if you have used a link to shortcut the command user@linuxmachine: ~> tuflowfv my_control_file.fvc
  14. This problem can often be caused by the IDs column in you cell-centres file being inconsistent with the actual IDs of the elements in the 2dm. The upcoming release of TUFLOWFV will have a bathymetry from TIN option. This allows users to save their bathymetry set as an SMS .TIN file, and TUFLOWFV will do the interpolation and bathymetry inspection internally
  15. Hi Hamid, I have not come across this issue that I can recall, and I am using version 11.2.8 currently. Can you please post a screen grab of what this looks like before and after the change? Toby
×
×
  • Create New...