Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1
  • 2

TOPIC: Tidal flats

Tidal flats 6 years 10 months ago #28649

  • Vittel
  • Vittel's Avatar
Hi Riadh,

So I got that to work and tried different heights of water depth for ZSTAR. Unfortunately, the same error message came again and again.

================================================================================
ITERATION 0 TIME 0 D 0 H 0 MN 0.0000 S ( 0.0000 S)
================================================================================
MASS BALANCE
INITIAL MASS OF WATER IN THE DOMAIN : 1605157.6100554552

SOURCE POINT 1 PUT ON POINT
3535825.5000000000 AND 5721378.5000000000
LOCATED AT 2.4152879747031890 METRES

SOURCE POINT 1 PUT ON PLANE 1
LOCATED AT 0.46296203613280795 METRES
USING STREAMLINE VERSION 7.2 FOR CHARACTERISTICS
CALCOT: PLANES 1 AND 2
INTERCROSS AT POINT 1867
LOWER POINT : 99.712623596191406
HIGHER POINT: 99.712065230069811
DIFFERENCE : -5.5836612159509968E-004
DEPTH : -5.5836612159612262E-002

PLANTE: PROGRAM STOPPED AFTER AN ERROR
RETURNING EXIT CODE: 2


I followed your advice and looked at the examples. I even took the same steering files where tidel flat = 0. I could run the examples, but if I again indicated my data (grid, tracer, ...), the error message comes again as above.
Is Tidal Flats=on, the simulation works, but unfortunately I get then at the edges of the river these higher water levels and thus incorrect concentration information.

Do you have any other ideas?

Best regards,
Vittel
Attachments:
The administrator has disabled public write access.

Tidal flats 6 years 9 months ago #28680

  • SDAC
  • SDAC's Avatar
Hi Vittel,

I noticed you mentioned that you cannot refine your grid because your base data in your troublesome region is very bad. Do you mean you have a sparse data-set in that area? If so have you tried using a spatial prediction method? Velocity and surface errors can increase with distance between cross-sectional data. In river channels it is common practice to linearly interpolate between measured cross-sections and increase the resolution of your topographic data. The flip-side to this is that you're effectively smoothening off elevation values by introducing artificial data when in natural rivers you'll have a high variation.

Also, check your initial conditions for the initial elevation. When I got errors about intersecting layers at the beginning of my runs it was usually because my initial water elevation was too low.

Cheers,
SDAC
The administrator has disabled public write access.
  • Page:
  • 1
  • 2
Moderators: pham

The open TELEMAC-MASCARET template for Joomla!2.5, the HTML 4 version.