Changes between Version 29 and Version 30 of doc/app/radiation_parameters


Ignore:
Timestamp:
Sep 28, 2018 10:49:59 AM (7 years ago)
Author:
moh.hefny
Comment:

Further changes will follow upon the release of RTM vers. 3.0

Legend:

Unmodified
Added
Removed
Modified
  • doc/app/radiation_parameters

    v29 v30  
    22[[TracNav(doc/app/partoc|nocollapse)]]
    33
    4 For revision r1551 onwards, an interface for use of radiation models is available in PALM. Currently, PALM offers one built-in radiation model for clear-sky conditions, calculating the net radiation at the surface.
    5 
    6 All parts of the radiation code (and the interface of the radiation code) are modularized in module [/browser/palm/trunk/SOURCE/radiation_model.f90 radiation_model_mod]. In this context, a new Fortran NAMELIST {{{radiation_parameters}}} was added, containing all radiation-related steering parameters. The radiation module is automatically activated if a {{{radiation_parameters}}} is set in the parameter file ({{{_p3d}}}).
    7 
    8 When using the RRTMG radiation model, it is required to [wiki:doc/tec/radiation#Installation compile the radiation code] first as a library. Moreover, the use of netCDF is mandatory.
     4PALM offers radiation simulation using a radiation model chosen by the user from these three integrated radiation models:
     5* Constant radiation
     6* Simple clear sky
     7* RRTMG
     8In addition to these radiation models, a Radiative Transfer Model (RTM) is implemented in PALM to describe the radiative transfer processes within the urban canopy layer, including multiple reflections between buildings and other surfaces located in the domain. The model treats direct and diffuse radiation separately.
     9
     10Current RTM (Version 2.0) involves the following processes
     11* Calculation of the incoming/outgoing shortwave radiation components on each surface element in the domain
     12* Estimation of longwave thermal emission/absorption for all surfaces
     13* Reflections of shortwave and longwave radiation by all surfaces (finitely iterated)
     14* Partial absorption of shortwave radiation by vegetation (trees)
     15
     16All parts of the radiation code (and the interface of the radiation code) are modularized in module radiation_model_mod. In this context, a new Fortran NAMELIST radiation_parameters was added, containing all radiation-related steering parameters. The radiation module is automatically activated if a radiation_parameters is set in the parameter file (_p3d).
     17
     18When using the RRTMG radiation model, it is required to compile the radiation code first as a library. Moreover, the use of netCDF is mandatory.
    919
    1020\\\\\\\\\\\\\\\\\\\\\\\\\\
     
    268278When using RRTMG, shortwave radiation calls can be switched off by setting {{{sw_radiation = .F.}}}. Note that shortwave radiation is automatically switched off during nighttime.
    269279}}}
     280|----------------
     281{{{#!td style="vertical-align:top"
     282[=#unscheduled_radiation_calls '''unscheduled_radiation_calls''']
     283}}}
     284{{{#!td style="vertical-align:top"
     285L
     286}}}
     287{{{#!td style="vertical-align:top"
     288.T.
     289}}}
     290{{{#!td
     291Parameter to allow additional calls of the radiation code.
     292
     293Usually the radiation is called each [#dt_radiation], however in case of fast changes in the skin temperature, it is recommended to update the radiative fluxes independently from the prescribed radiation call frequency to prevent oscillations. The value of the temperature threshold used is 0.2 °K.
     294}}}
     295|----------------
     296{{{#!td style="vertical-align:top"
     297[=#max_raytracing_dist '''max_raytracing_dist''']
     298}}}
     299{{{#!td style="vertical-align:top"
     300R
     301}}}
     302{{{#!td style="vertical-align:top"
     303-999.0
     304}}}
     305{{{#!td
     306Maximum distance for raytracing (in meters).
     307
     308It is used to set the maximum distance allowed to consider the radiative exchange between two surfaces. This limits the number of surfaces view factors (VF) and hence save much memory by neglecting the very small VF resulting from the mutually visible far surfaces. At the end of VF calculations, the values will be scaled so that energy is conserved.
     309
     310If not set, the model will assume a value equal to double the urban surface layer height.
     311
     312Please note that the calculated FV needs to be higher than the threshold value set in [#min_irrf_value] in order to be considered.
     313}}}
     314|----------------
     315{{{#!td style="vertical-align:top"
     316[=#min_irrf_value '''min_irrf_value''']
     317}}}
     318{{{#!td style="vertical-align:top"
     319R
     320}}}
     321{{{#!td style="vertical-align:top"
     3221e-6
     323}}}
     324{{{#!td
     325Minimum potential irradiance factor value for raytracing.
     326
     327It is used to set the threshold to consider any view factor (VF) calculated between two surfaces. This limits the number of VF and hence save much memory by neglecting the very small VF resulting from the low mutual visiblity. At the end of VF calculations, the values will be scaled so that energy is conserved.
     328
     329Please note that this parameter will neglect any VF smaller than [#min_irrf_value] even though the coressponing surfaces are within the [#max_raytracing_dist].
     330}}}
     331|----------------
     332{{{#!td style="vertical-align:top"
     333[=#nrefsteps '''nrefsteps''']
     334}}}
     335{{{#!td style="vertical-align:top"
     336I
     337}}}
     338{{{#!td style="vertical-align:top"
     3390
     340}}}
     341{{{#!td
     342Number of reflection steps to be performed to accound for the refelcted short- and longwave between musually visible surfaces.
     343
     344Although the effect of reflection depends on the surface characteristics (albedo, emissivity, etc.), however for typical urban areas it is recommended to set {{{nrefsteps = 3}}} because the effect of reflection after 3 reflections is negligible.
     345}}}
     346|----------------
     347{{{#!td style="vertical-align:top"
     348[=#mrt_factors '''mrt_factors''']
     349}}}
     350{{{#!td style="vertical-align:top"
     351L
     352}}}
     353{{{#!td style="vertical-align:top"
     354.F.
     355}}}
     356{{{#!td
     357Parameter to generate extra view factors for specific surfaces to calculate MRT during the post processing.
     358
     359Please note: if set to TRUE, then extra input file (MRT_TARGETS) is needed to set the ID of the surface as well as its coordinates. The model will write out unformated file contains all the mutually visible surfaces for each requested surface along with its type, coordinates, view factor, and transparency.
     360}}}
     361|----------------
     362{{{#!td style="vertical-align:top"
     363[=#rma_lad_raytrace '''rma_lad_raytrace''']
     364}}}
     365{{{#!td style="vertical-align:top"
     366L
     367}}}
     368{{{#!td style="vertical-align:top"
     369.F.
     370}}}
     371{{{#!td
     372Parameter to use One-sided communication (MPI-RMA) to access LAD array for raytracing.
     373
     374For large domain it is recommended to use MPI-RMA to access LAD array for raytracing instead of allocating the global array for each processor. This saves memory and allow for simulations of large domains.
     375
     376Please note: For Intel compiler, if you observe performance degradation with an MPI application that utilizes the RMA functionality (i.e. {{{rma_lad_raytrace = .TRUE.}}}), you are recommended to set {{{I_MPI_SCALABLE_OPTIMIZATION = 0}}} to get a performance gain.
     377}}}
     378|----------------
     379{{{#!td style="vertical-align:top"
     380[=#surface_reflections '''surface_reflections''']
     381}}}
     382{{{#!td style="vertical-align:top"
     383L
     384}}}
     385{{{#!td style="vertical-align:top"
     386.T.
     387}}}
     388{{{#!td
     389Parameter to consider surface-surface reflections.
     390
     391It is not recommended to set {{{surface_reflections = .F.}}} because When it switched to off, only the effect of building and tree shadows will be considered and all reflection processes will be disabled. However fewer no surface-surface VFs are caclulated and less memory requirement is expected.
     392}}}
     393|----------------
     394{{{#!td style="vertical-align:top"
     395[=#svfnorm_report_thresh '''svfnorm_report_thresh''']
     396}}}
     397{{{#!td style="vertical-align:top"
     398R
     399}}}
     400{{{#!td style="vertical-align:top"
     4011e21
     402}}}
     403{{{#!td
     404thresholds of surface view factors normalization values to report.
     405
     406This array contains 30 values of the histogram steps of logged VF normalization values to show the VF distribution.
     407}}}
     408|----------------
     409{{{#!td style="vertical-align:top"
     410[=#radiation_interactions_on '''radiation_interactions_on''']
     411}}}
     412{{{#!td style="vertical-align:top"
     413L
     414}}}
     415{{{#!td style="vertical-align:top"
     416.T.
     417}}}
     418{{{#!td
     419Parameter to force RTM activiation regardless to vertical urban/land surface and trees.
     420
     421RTM is usually set according to the existance of vertical urban/land surface or trees. If set to FALSE, no RTM is used even when there are vertical urban/land surface or trees in the domain. This simply means that all surfaces will receive radiation fluxes directly from the radiation model without considering other radiation processes such as reflections.
     422}}}