Ignore:
Timestamp:
Mar 21, 2016 4:50:28 PM (6 years ago)
Author:
raasch
Message:

Introduction of different data transfer modes; restart mechanism adjusted for nested runs; parameter consistency checks for nested runs; further formatting cleanup

File:
1 edited

Legend:

Unmodified
Added
Removed
  • palm/trunk/SOURCE/time_integration.f90

    r1792 r1797  
    1919! Current revisions:
    2020! ------------------
    21 !
     21! introduction of different datatransfer modes
    2222!
    2323! Former revisions:
     
    258258    USE pmc_interface,                                                         &
    259259        ONLY:  client_to_server, nested_run, nesting_mode,                     &
    260                pmci_ensure_nest_mass_conservation, pmci_client_datatrans,      &
    261                pmci_client_synchronize, pmci_server_datatrans,                 &
     260               pmci_client_synchronize, pmci_datatrans,                        &
     261               pmci_ensure_nest_mass_conservation,                             &
    262262               pmci_server_synchronize, server_to_client
    263263
     
    673673
    674674          IF ( nested_run )  THEN
    675 !
    676 !--          TO_DO: try to give more meaningful comments here
    677 !--          Domain nesting
    678 !--          Note that the nesting operations are omitted intentionally on the
    679 !--          first two RK-substeps.
     675
    680676             CALL cpu_log( log_point(60), 'nesting', 'start' )
    681677!
    682 !--          From server to client commmunication ( direction=SERVER_TO_CLIENT )
    683              CALL pmci_server_datatrans( server_to_client )
    684              CALL pmci_client_datatrans( server_to_client )
     678!--          Domain nesting. The data transfer subroutines pmci_server_datatrans
     679!--          and pmci_client_datatatrans are called inside the wrapper
     680!--          subroutine pmci_datatrans according to the control parameters
     681!--          nesting_mode and nesting_datatransfer_mode.
     682!--          TO_DO: why is nesting_mode given as a parameter here?
     683             CALL pmci_datatrans( nesting_mode )
    685684
    686685             IF ( nesting_mode == 'two-way' )  THEN
    687 !
    688 !--             From client to server commmunication ( direction=CLIENT_TO_SERVER )
    689                 CALL pmci_server_datatrans( client_to_server )
    690                 CALL pmci_client_datatrans( client_to_server )
    691686!
    692687!--             Exchange_horiz is needed for all server-domains after the
Note: See TracChangeset for help on using the changeset viewer.