Changes between Initial Version and Version 1 of Ticket #843


Ignore:
Timestamp:
02/25/20 16:55:17 (5 years ago)
Author:
arango
Comment:

Yes, the HSIMT needs three ghost points as MPDATA. I was not able to reproduce the error in my testing application. I need lots of rivers to get one at a specific tile partition.

I added the following statement to read_phypar.F: 

!
!  Set switch for three ghost-points in the halo region.
!
      ThreeGhostPoints=ANY(Hadvection(:,:)%MPDATA).or.                  &
     &                 ANY(Hadvection(:,:)%HSIMT)
#ifdef UV_VIS4
      ThreeGhostPoints=.TRUE.
#endif

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #843

    • Property Resolution → Fixed
    • Property Status new → closed
    • Property Summary Subscript out of bounds on river tracer source → Subscript out of bounds on river tracer source when using HSIMT

  • Ticket #843 – Description

    initial v1  
    1 
     1The following error is issued when using '''HSIMT''' tracer advection:
    22{{{
    33forrtl: severe (408): fort: (2): Subscript #2 of the array HVOM has value 73 which is greater than the upper bound of 72
    … …  
    88oceanG             00000000014622DA  step3d_t_mod_mp_s          78  step3d_t.f90
    99}}}
    10 On this particular tile, Hvom is dimensioned (0:326,0:72), but the test goes out to Jendp3 which is 73:
     10On this particular tile, '''Hvom''' is dimensioned (0:326,0:72), but the test goes out to Jendp3 which is 73:
    1111
    1212{{{
    … …  
    1818       &                      (Jsrc.le.Jendp3)
    1919}}}
    20 I have HSIMT set for the advection type in this case. This is probably not a new bug and I in fact stumbled on it when trying to track something else down.
     20I have '''HSIMT''' set for the advection type in this case. This is probably not a new bug and I in fact stumbled on it when trying to track something else down.
    2121