Search results
Jump to navigation
Jump to search
Page title matches
- ...s, the check file does not exist, or the changes described in the tutorial model aren't in the check files. ...the .tlf for an input file name, for example, if breakline changes are not seen, search the .tlf to ensure the input file e.g. "2d_zsh_M03_thalweg" is bein761 bytes (133 words) - 15:04, 6 January 2023
Page text matches
- |tuflow_message=ERROR 0011 - TUFLOW Build different to that specified by Model TUFLOW Build == . ...="red"><tt>==</tt></font> command. For example, if <font color="blue"><tt>Model TUFLOW Build </tt></font> <font color="red"><tt>==</tt></font><tt> 2013-12-1 KB (203 words) - 09:15, 22 December 2022
- ...egistered tutorial model. Please remove "<font color="black"><tt>Tutorial Model </tt></font><font color="black"><tt>== </tt></font><font color="black"><tt> ...be used for valid tutorial models. If this command is added to any other model, this error message is generated.826 bytes (127 words) - 10:18, 18 July 2022
- |tuflow_message=Error 3500 - Could not allocate temporary memory (RAM) for processing SGS Grid. |alt_msg=ERROR 3500 - Could not allocate temporary memory (RAM) for processing HPC weir angle.509 bytes (73 words) - 11:47, 2 October 2023
- |tuflow_message=ERROR 2146 - Could not allocate memory (RAM) for "Inside Region == Method B". ...ate memory (RAM) for TIN Interpolation Work Arrays.<br> ERROR 2146 - Could not allocate temporary memory for GRID Band information.2 KB (413 words) - 11:51, 15 March 2024
- |tuflow_message=ERROR 2308 - Event <event name> not defined by "<font color="black"><tt>Define Event </tt></font><font color="b |message_desc=The event specified when simulating the model is not defined in the .tef event file.1 KB (196 words) - 14:25, 7 February 2023
- ...main. For example a boundary location must be within the model domain (if not a [[TUFLOW_Message_2001 | ERROR 2001]] is generated).<br> ...d are simply ignored. Therefore, it is not necessary to trim a DEM to the model domain.<br>1 KB (222 words) - 21:18, 21 December 2015
- |tuflow_message=ERROR 2219 - Trying to run a double precision model with a TUFLOW single precision .exe. |alt_msg=ERROR 2219 - Trying to run a single precision model with a TUFLOW double precision .exe.1 KB (201 words) - 14:12, 7 February 2023
- |tuflow_message=WARNING 2122 - Pit or node does not connect to an active cell within any 2D domain - 2D link ignored. ...nnect to an active cell within any 2D domain, therefore the link to the 2D model has been ignored.405 bytes (69 words) - 14:59, 2 February 2023
- |tuflow_message=ERROR 2782 - Stelling 2D ADI Implicit Scheme not available on GPU Hardware. ...an implicit solver which is not suited for GPU parallel computing, and is not yet coded to run on GPU hardware.725 bytes (117 words) - 09:09, 11 September 2023
- |tuflow_message=WARNING 2074 - SA object does not select any 2D cells (active or inactive). ...tres (ZC points), in the figure below the polygon highlighted in pink does not contain any cell centres and therefore this warning message will be returne780 bytes (131 words) - 11:57, 23 December 2022
- |tuflow_message=ERROR 2828 - Nesting polygon "a" not completely within level 1 polygon. |alt_msg=ERROR 2828 - Could not find any parent for nesting polygon "a"690 bytes (110 words) - 10:01, 3 March 2023
- |tuflow_message=ERROR 2001 - 2d_bc object is outside 2D model domain |alt_msg=ERROR 2001 - GIS Object is outside 2D model domain<br>926 bytes (155 words) - 10:51, 23 December 2022
- |tuflow_message=ERROR 2024 - Could not find a 1D node snapped to CN line. |message_desc=Could not find a 1D node snapped to 2d_bc connection (CN) line.1 KB (249 words) - 21:35, 4 March 2024
- |tuflow_message=WARNING 2038 - 2D connection at pit does not fall within an active cell in any 2D domain. |message_desc=Not used as of 2007-07-AD. 2D connection at pit does not fall within an active cell in any 2D domain.411 bytes (70 words) - 11:03, 23 December 2022
- |tuflow_message=ERROR 0015 - Variable "a" not defined. ...2D_CELL_SIZE” is used to set the 2D cell size of the model under different model scenarios.<br>1 KB (206 words) - 09:23, 22 December 2022
- ...package model functionality. For more information, please see the package model documentation in the <b><u>[https://downloads.tuflow.com/_archive/TUFLOW/Re ...mmand line syntax and the ini file (if required) and runs TUFLOW's package model tool (using the TUFLOW.exe). One additional piece of functionality is added2 KB (420 words) - 11:23, 17 January 2024
- |tuflow_message=ERROR 1322 - Could not write XMDF scalar data for 1D WLLs. Check disk space. ...nd amount of free disk space at the output location. Increment TCF and run model with new name.400 bytes (65 words) - 10:31, 23 December 2022
- |tuflow_message=ERROR 1323 - Could not write XMDF vector data for 1D WLLs. Check disk space. ...nd amount of free disk space at the output location. Increment TCF and run model with new name.400 bytes (65 words) - 10:31, 23 December 2022
- ...lem). There was insufficient motherboard RAM available to build or run the model. * Change to single precision, if not already.501 bytes (73 words) - 10:20, 3 March 2023
- |tuflow_message=Error 2061 - Could not find a CN connection snapped to the end of HX line. ...e must have as a minimum a connection at each of its ends, otherwise it is not clear how to transfer the water level gradient from the 1D domain.1 KB (252 words) - 23:07, 4 March 2024
- |tuflow_message=ERROR 0420 - Could not read projection line in .prj file. ...NG 0420 - Could not find PROJCS definition. Projection of .shp file might not be Cartesian.838 bytes (131 words) - 15:40, 4 January 2024
- Some or all non-spatial messages may not appear in _messages GIS layer. ...OW messages have a spatial location (for example a cell elevation that has not been assigned), however, some messages such as <u>[[TUFLOW_Message_1298]]</2 KB (273 words) - 11:10, 22 December 2022
- |tuflow_message=WARNING 2123 - Pit or node does not connect to an active cell within any 2D domain - 2D link ignored. |alt_msg=WARNING 2123 - Pit or node is not inside any 2D domain - 2D link ignored.497 bytes (84 words) - 15:00, 2 February 2023
- |alt_msg=ERROR 2839 - Split polyline should not have more vertexes than the original polyline ...ne features, for example when PO lines or part of PO lines are outside the model area for Quadtree models.533 bytes (85 words) - 16:03, 23 February 2024
- ...PC model running with a different timeseries of timesteps to the base case model. <br> ...are a result of the development features and not a result of change in the model timestep.<br>3 KB (555 words) - 15:31, 30 May 2022
- |tuflow_message=ERROR 2206 - ZC value not initialised (exceeds 99998m) |alt_msg=ERROR 2206 - ZU value not initialised (exceeds 99998m)<br>1 KB (174 words) - 14:05, 7 February 2023
- ...gon in 2d_qnl layer or 2d_code layer if level 1 polygon in 2d_qnl layer is not used.<br> Quadtree nesting polygons can only be within the model domain.1,012 bytes (166 words) - 10:02, 3 March 2023
- ...ied with "Defaults" command set to Pre 2017. Prior to 2017 TUFLOW HPC was not released. ...UFLOW HPC was only released in 2017. Setting Defaults prior to 2017 should not be used.440 bytes (64 words) - 09:48, 3 March 2023
- |tuflow_message=CHECK 2098 - Could not find a SC connection snapped to SH boundary. ...boundary should be linked to another 2D cell or 1D node via SC connection (not CN connection). This boundary is used for modelling pumps or other water ex696 bytes (117 words) - 12:31, 23 December 2022
- |message_desc=The data in the binary (xf) version is not the same precision as the simulation. For example the .xf file has been ge <font color="blue"><tt>Model Precision </tt></font> <font color="red"><tt>==</tt></font><br>1 KB (178 words) - 16:34, 5 January 2024
- |tuflow_message=ERROR 2132 - Node is duplicated or does not exist in external 1D domain. ...thin a GIS layer read into TUFLOW must be unique and match the external 1D model exactly.570 bytes (93 words) - 13:37, 7 February 2023
- ...be used to import the check files and view the final elevations in the 2D model. ...ed). This file contains the exact elevations in the model. However, this not so easy to visualise and TUFLOW also outputs a raster (gridded) dataset in2 KB (345 words) - 13:25, 5 April 2024
- ...ocessing Reporting Location Lines. Check "Read GIS Reporting Locations" is not in a 1D block or in .ecf file. ...This error is also triggered when reporting locations are used in 2D only model.576 bytes (98 words) - 11:39, 22 December 2022
- ...be used to import the check files and view the final elevations in the 2D model. ...the model. As this point vector layer contains thousands of points and is not easy to visualise TUFLOW also outputs a raster (gridded) dataset in the .fl2 KB (328 words) - 13:26, 5 April 2024
- |tuflow_message=ERROR 2104 - CoordSys line could not be found in "<font color="black"><tt>MI Projection</tt></font>" .mif file. ...OR 2104 - "<font color="black"><tt>Mi Projection</tt></font>" command does not support Shapefile projection (.prj) file as input.1 KB (150 words) - 12:33, 23 December 2022
- ...metimes, ensuring there are no open versions of the layer when running the model may resolve this issue. <br> ...iles]], and do not create empty template files manually or copy from other model folders.709 bytes (115 words) - 15:50, 4 January 2024
- ...the solution to remain stable. There are a variety of reasons that a HPC model may require these corrections:<br> * Poorly configured 1D/2D model interface1 KB (206 words) - 09:16, 3 March 2023
- |tuflow_message=ERROR 0046 - 1D Output Interval not specified.<br> |alt_msg=WARNING 0046 - 1D Output Interval not specified. Defaulting to every timestep.<br>1 KB (234 words) - 10:04, 22 December 2022
- |message_desc=The filepath is long and some features might not work correctly. ...g copy model (-c) or package model (-pm). Shorten the file path to run the model.<br>801 bytes (119 words) - 17:21, 19 April 2024
- |tuflow_message=ERROR 0252 – <file format> is not a supported GIS file format. |message_desc=The file format specified is not a recognised file format. For example:<br>910 bytes (153 words) - 11:09, 22 December 2022
- Firstly we will update the active 2D model area near the downstream boundary. ...odel with this configuration, water will not be able to leave enter the 1D model from the floodplain. The area is shown in the image below.</li>3 KB (536 words) - 09:10, 9 January 2023
- ...le (if not the TUFLOW model domain size is used). The syntax specified is not valid. It can be specified either as:<br>692 bytes (116 words) - 09:40, 3 March 2023
- ...Since '''Project--Options''' is already included in the HDR and RNF, it is not needed in the inlet curves INP file. <br> '''Note:''' The inlet usage GeoPackage does not need to be converted to a SWMM inp file. Since it contains only one layer,2 KB (325 words) - 13:29, 1 March 2024
- ...is is that the 1D network has changed between the model simulation and the model in which the restart file was written. ...estions=If the 1D network has been changed starting from a restart file is not possible and a new restart file needs to be created.590 bytes (100 words) - 16:01, 22 December 2022
- ...be used to import the check files and view the final elevations in the 2D model. ...the model. As this point vector layer contains thousands of points and is not easy to visualise TUFLOW also outputs a raster (gridded) dataset in the .fl2 KB (347 words) - 13:26, 5 April 2024
- Firstly we will update the active 2D model area near the downstream boundary. ...odel with this configuration, water will not be able to leave enter the 1D model from the floodplain. The area is shown in the image below.</li>3 KB (550 words) - 09:09, 9 January 2023
- ==I wish to use a PO line to monitor the flow exiting a model. Should I snap the PO line to the downstream boundary for this purpose?== Plot Output (PO) Q lines report model flow results for water crossing the digitised line. Computationally, TUFLOW2 KB (370 words) - 12:22, 3 October 2023
- |tuflow_message=ERROR 2423 - Could not close XMDF file. |suggestions=Close GIS software and run the model again.289 bytes (46 words) - 16:41, 16 August 2023
- ...ms to be shared between multiple simulations. A simulation also stores the model parameters used by TUFLOW.<br> ...nent from previous module and add new components. Doing this will keep the model from module01 unchanged.4 KB (617 words) - 14:29, 6 January 2023
- ...ese cell elevations that determine whether out of bank flooding occurs and not the left/right bank elevations with the Flood Modeller 1D cross-sections. ...<b>2d_bc_empty_P.shp</b> layer from within the FMT_tutorial\FMT_M01\TUFLOW\model\gis\empty folder.</li>2 KB (400 words) - 00:24, 8 December 2018