Changes between Initial Version and Version 1 of Ticket #209


Ignore:
Timestamp:
09/24/08 20:33:32 (16 years ago)
Author:
arango
Comment:

Yes, this one was nasty. First, the out-of-bounds was because the logic to initialize the floats in grid_coords.F has some problems. The conditional statement to compute MyThread(:) needs to be the same that we have in step_floats.F. We also have couple of parallel bugs in step_floats.F. We were not getting the exact trajectories in different tile partitions. This happened when an isobaric float was moving to another tile.

I cleaned the code a little and now three types of floats are allowed:

  • 3D Lagrangrian floats (Ftype=1; flt_Lagran)
  • Isobaric floats, p=g*(z+zeta)=constant, (Ftype=2; flt_Isobar)
  • Geopotential floats, constant depth, (Ftype=3; flt_Geopot)

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #209

    • Property Resolution → Fixed
    • Property Status new → closed

  • Ticket #209 – Description

    initial v1  
    1 When running FLT_TEST with SOLVE3D defined, with MPI and bounds-checking enabled, an out of bounds error is triggered in step_floats_tile in the code that keeps the floats at their initial depth. The specific statement where the out-of-bounds error occurs is at line 292 in step_floats.F and the failure occurs for float l=231 (i.e. near the top of the grid). The reason it occurs is the horizontal locations, track(ixgrd,nfp1,l) and track(ixgrd,nfp1,l), appear not to have been initialised.
     1When running '''FLT_TEST''' with '''SOLVE3D''' defined, with MPI and bounds-checking enabled, an out of bounds error is triggered in step_floats_tile in the code that keeps the floats at their initial depth. The specific statement where the out-of-bounds error occurs is at line 292 in '''step_floats.F''' and the failure occurs for float '''l=231''' (i.e. near the top of the grid). The reason it occurs is the horizontal locations, '''track(ixgrd,nfp1,l)''' and '''track(ixgrd,nfp1,l)''', appear not to have been initialised.
    22
    33I will look into this further when I can.