Ignore:
Timestamp:
Oct 25, 2016, 9:23:21 AM (8 years ago)
Author:
emillour
Message:

Further work on full dynamics/physics separation.

LMDZ.COMMON:

  • added phy_common/vertical_layers_mod.F90 to store information on vertical grid. This is where routines in the physics should get the information.
  • The contents of vertical_layers_mod intialized via dynphy_lonlat/inigeomphy_mod.F90.

LMDZ.MARS:

  • physics now completely decoupled from dynamics; the physics package may now be compiled as a library (-libphy option of makelmdz_fcm).
  • created an "ini_tracer_mod" routine in module "tracer_mod" for a cleaner initialization of the later.
  • removed some purely dynamics-related outputs (etot0, zoom parameters, etc.) from diagfi.nc and stats.nc outputs as these informations are not available in the physics.

LMDZ.GENERIC:

  • physics now completely decoupled from dynamics; the physics package may now be compiled as a library (-libphy option of makelmdz_fcm).
  • added nqtot to tracer_h.F90.
  • removed some purely dynamics-related outputs (etot0, zoom parameters, etc.) from diagfi.nc and stats.nc outputs as these informations are not available in the physics.

LMDZ.VENUS:

  • physics now completely decoupled from dynamics; the physics package may now be compiled as a library (-libphy option of makelmdz_fcm).
  • added infotrac_phy.F90 to store information on tracers in the physics. Initialized via iniphysiq.
  • added cpdet_phy_mod.F90 to store t2tpot etc. functions to be used in the physics. Initialized via iniphysiq. IMPORTANT: there are some hard-coded constants! These should match what is in cpdet_mod.F90 in the dynamics.
  • got rid of references to moyzon_mod module within the physics. The required variables (tmoy, plevmoy) are passed to the physics as arguments to physiq.

LMDZ.TITAN:

  • added infotrac_phy.F90 to store information on tracers in the physics. Initialized via iniphysiq.
  • added cpdet_phy_mod.F90 to store t2tpot etc. functions to be used in the physics.
  • Extra work required to completely decouple physics and dynamics: moyzon_mod should be cleaned up and information passed from dynamics to physics as as arguments. Likewise moyzon_ch and moyzon_mu should not be queried from logic_mod (which is in the dynamics).

EM

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/LMDZ.MARS/libf/phymars/initracer.F

    r1617 r1621  
    11      SUBROUTINE initracer(ngrid,nq,qsurf)
    22
    3 #ifndef MESOSCALE
    4        use infotrac, only: tname
    5 #endif
    63       use tracer_mod
    74       USE comcstfi_h
     
    5451c-----------------------------------------------------------------------
    5552
    56 ! Initialization: allocate arrays in tracer_mod
    57       allocate(mmol(nq))
    58       allocate(radius(nq))
    59       allocate(rho_q(nq))
    60       allocate(alpha_lift(nq))
    61       allocate(alpha_devil(nq))
    62       allocate(igcm_dustbin(nq))
    63       allocate(nqdust(nq))
    64 
    65 #ifndef MESOSCALE
    66       allocate(noms(nq))
    67 ! Initialization: get tracer names from the dynamics and check if we are
    68 !                 using 'old' tracer convention ('q01',q02',...)
    69 !                 or new convention (full tracer names)
    70       ! check if tracers have 'old' names
    71 
    72       count=0
    73       do iq=1,nq
    74         txt=" "
    75         write(txt,'(a1,i2.2)') 'q',iq
    76         if (txt.eq.tname(iq)) then
    77           count=count+1
    78         endif
    79       enddo ! of do iq=1,nq
    80      
    81       if (count.eq.nq) then
    82         write(*,*) "initracer: tracers seem to follow old naming ",
    83      &             "convention (q01,q02,...)"
    84         write(*,*) "you should run newstart to rename them"
    85         stop
    86       endif
    87 
    88       ! copy tracer names from dynamics
    89       do iq=1,nq
    90         noms(iq)=tname(iq)
    91         write(*,*) "initracer names : ", noms(iq)
    92       enddo
    93 #endif
    9453
    9554c------------------------------------------------------------
Note: See TracChangeset for help on using the changeset viewer.