#2215 closed Enhancement (duplicate)

report on communications is not clear when BDY is used

Reported by: clem Owned by: smasson
Priority: low Milestone:
Component: LBC Version: trunk
Severity: minor Keywords:
Cc: Review:
MP ready?:
Progress:

Description

The file communication_report.txt sum up the number of communications that are done at the second time step of a simulation.
Usually the report is clear and ressembles at that:

  lbc_lnk called
 -  209 times by subroutine dynspg_ts

But when using BDY, it messes up the report:

lbc_lnk called
 -    2 times by subroutine dynspg_ts
 -    1 times by subroutine bdydyn2d
 -    2 times by subroutine dynspg_ts
 -    3 times by subroutine bdydyn2d
 -    2 times by subroutine dynspg_ts
 -    1 times by subroutine bdydyn2d
 -    2 times by subroutine dynspg_ts
 -    3 times by subroutine bdydyn2d
 -    2 times by subroutine dynspg_ts
 -    1 times by subroutine bdydyn2d
etc

The report should be able to deal with mixed up calls

Commit History (0)

(No commits)

Change History (1)

comment:1 Changed 12 months ago by smasson

  • Resolution set to duplicate
  • Status changed from new to closed

duplicated with #2281

Note: See TracTickets for help on using tickets.