We use cookies to make your experience of our website better. You can delete or block cookies, but some parts of this website won't work without them. By using this website you accept our use of cookies.

apeech

24/02/2016 18:03:05

I can run a 1d-2d simulation completely fine if I do an "east" or "west" side of my river. Once I add both link lines to the 2d simulation, and create two domains, I get the error as stated in the topic title.

Any ideas on what the issue is?

Bothe of the link lines are separate from eachother, and are strictly associated with data on opposite sides of the river.

 

Below is the entire log file: 

 

INFO: No log file specified, using C:\Users\Aaron\Documents\Flood Modeller Projects\Portage East Floodway\Portage_floodway_1d-2d_Sim_Combined.log
Using Flood Modeller 2D version: 4.1.1.575, build date: 2015-10-05
64-bit, Single Precision version

Using input control file: C:\Users\Aaron\Documents\Flood Modeller Projects\Portage East Floodway\Portage_floodway_1d-2d_Sim_Combined.xml
Unit system: metric

Number of domains: 2

Using 1D Link
Linked 1D simulation file: C:\Users\Aaron\Documents\Flood Modeller Projects\Portage East Floodway\Portage_diversion_1d_unsteady.ief
Link lines:
C:\Users\Aaron\Documents\Flood Modeller Projects\Portage East Floodway\portage_diversion_1d-2d_WEST_LINK_LINE_MODIFIED.shp
C:\Users\Aaron\Documents\Flood Modeller Projects\Portage East Floodway\portage_diversion_1d-2d_EAST_LINK_LINE_MODIFIED.shp

Processing domain id 1 - Domain 1
Simulation time: 72.00 hrs

Solution scheme: ADI
Run parameters being used...
Model timestep : 100.000
Wetting/drying depth : 0.01000
Beta : 1.000
Number of iterations : 2
Calculation depth : 0.50000
Friction depth : 100.000
Eddy Viscosity : 0.000
Velocity head threshold : 0.500
Rainfall accumulation depth: 0.100E-03
Negative depth threshold : -0.00100
Friction depth threshold : 0.1000

Note: Velocity Head Threshold changed from v3.7 default (0.1m)

Active Area shapefile found: C:\Users\Aaron\Documents\Flood Modeller Projects\Portage East Floodway\portage_diversion_1d-2d_EAST_ACTIVE_AREA.shp
Reading computational extents from Active Area shapefile
Recalculated extents:
Lower left coordinates : ( 544343.38,5533142.00)
Rotation angle : 0.0 degrees
Active area grid size (C x R) : 89 x 162
Grid cell size : 200.0m
Memory use estimate for this domain is 32. MB

Reading boundary conditions ... 1 found
Boundary # 1 @ C:\Users\Aaron\Documents\Flood Modeller Projects\Portage East Floodway\portage_diversion_1d-2d_EAST_BOUNDARY.shp
Boundary type: qhbdy
Using constant boundary value of .01

Reading topography...
Applying ground elevations from layer C:\Users\Aaron\Documents\Flood Modeller Projects\Portage East Floodway\PORTAGE_FLOODWAY.asc
WARNING: DX and DY different in file C:\Users\Aaron\Documents\Flood Modeller Projects\Portage East Floodway\PORTAGE_FLOODWAY.asc - not supported, using DX only.
Resampling topography (ascii layer) onto grid...

Applying initial conditions ...
No initial conditions specified - setting global depth = 0

Setting roughness values...
Applying default roughness of 0.100

Processing domain id 2 - Domain 2
Simulation time: 72.00 hrs

Solution scheme: ADI
Run parameters being used...
Model timestep : 100.000
Wetting/drying depth : 0.01000
Beta : 1.000
Number of iterations : 2
Calculation depth : 0.50000
Friction depth : 100.000
Eddy Viscosity : 0.000
Velocity head threshold : 0.500
Rainfall accumulation depth: 0.100E-03
Negative depth threshold : -0.00100
Friction depth threshold : 0.1000

Note: Velocity Head Threshold changed from v3.7 default (0.1m)

Active Area shapefile found: C:\Users\Aaron\Documents\Flood Modeller Projects\Portage East Floodway\portage_diversion_1d-2d_WEST_ACTIVE_AREA.shp
Reading computational extents from Active Area shapefile
Recalculated extents:
Lower left coordinates : ( 537054.75,5533022.50)
Rotation angle : 0.0 degrees
Active area grid size (C x R) : 53 x 135
Grid cell size : 200.0m
Memory use estimate for this domain is 29. MB

Reading boundary conditions ... 1 found
Boundary # 1 @ C:\Users\Aaron\Documents\Flood Modeller Projects\Portage East Floodway\portage_diversion_1d-2d_WEST_BOUNDARY.shp
Boundary type: qhbdy
Using constant boundary value of .01

Reading topography...
Applying ground elevations from layer C:\Users\Aaron\Documents\Flood Modeller Projects\Portage East Floodway\PORTAGE_FLOODWAY.asc
WARNING: DX and DY different in file C:\Users\Aaron\Documents\Flood Modeller Projects\Portage East Floodway\PORTAGE_FLOODWAY.asc - not supported, using DX only.
Resampling topography (ascii layer) onto grid...

Applying initial conditions ...
No initial conditions specified - setting global depth = 0

Setting roughness values...
Applying default roughness of 0.100

--- Data read complete ---

Flood Modeller running in Free mode; using 13946 cells
WARNING: Zero time not set in ISIS1D - defaulting to same Zero time as 2D domain

Processing link lines...
Taking link type from attribute type
Taking 1D node labels from attributes node1, node2
ERROR: link vector spans 2 domains - stopping.
Spatial diagnostic output written to C:\Users\Aaron\Documents\Flood Modeller Projects\Portage East Floodway\Portage_floodway_1d-2d_Sim_Combined_01\output_diagnostics.sdd

Konrad

Flood Modeller Support

25/02/2016 15:42:29

Best answer

Hi apeech,

This can only happen if one vertex of a link line segment is in one domain and the other vertex is detected in a different one.

Things to note:

There is a tolerance of 1 cell's width as to whether it's deemed in or not.

Your grid cells I note are rather large (200m).

So your link line vertex could be as much as 400m away (possibly more if on the diagonal) from your domain boundary and detected as belonging (e.g. your domain boundary just cuts the bottom right corner of one cell and your link line vertex is in the top left corner of the cell above; the bottom cell is in the domain and the top one is within the tolerance of one cell away)

Konrad

 

apeech

25/02/2016 22:12:55

This was exactly the issue, thanks for the reply! I lowered the grid cell size and it runs properly.

Sign in to create or reply to forum posts.

Privacy & Terms

Copyright