Class point_mode
Defined in File point_mode.hpp
Inheritance Relationships
Base Type
public module_base
(Class module_base)
Class Documentation
-
class point_mode : public module_base
Use this module to enable using CHM in point mode. This module does not to any spatial interpolation. Instead, it passes input met through to the per-triangle variables storages. This is suitable for using CHM like a point scale model, such as at a research site. Specifically this sets
depends_from_met(...)
inputs such thatdepends(...)
in other modules can work.Depends from met::
Air temp “t” [ \( {}^\circ C \)]
Relative humidity “rh” [%]
Wind speed “u” [ \( m \cdot s^{-1} \) ]
Precipitation “p” [mm]
Incoming longwave radiation “Qli” [ \( W \cdot m^{-2}\)]
Incoming shortwave radiation “Qsi” [ \( W \cdot m^{-2}\)]
Incomging shortwave radiation, diffuse beam “iswr_diffuse” [ \( W \cdot m^{-2}\)]
Incomging shortwave radiation, direct beam “iswr_direct” [ \( W \cdot m^{-2}\)]
Wind direction @2m “vw_dir” [degrees]
Ground temperature “T_g” [ \( {}^\circ C \)]
Provides:
Air temp “t” [ \( {}^\circ C \)]
Relative humidity “rh” [%]
Wind speed @2m “U_2m_above_srf” [ \( m \cdot s^{-1} \) ]
Wind speed @reference height “U_R” [ \( m \cdot s^{-1} \) ]
Precipitation “p” [mm]
Incoming longwave radiation “ilwr” [ \( W \cdot m^{-2}\)]
Incoming shortwave radiation “iswr” [ \( W \cdot m^{-2}\)]
Incomging shortwave radiation, diffuse beam “iswr_diffuse” [ \( W \cdot m^{-2}\)]
Incomging shortwave radiation, direct beam “iswr_direct” [ \( W \cdot m^{-2}\)]
Wind direction @2m “vw_dir” [degrees]
Ground temperature “T_g” [ \( {}^\circ C \)]
Configuration:
"provide":{ "t": true, "rh": true, "U_R": true, "U_2m_above_srf": true, "p": true, "ilwr": true, "iswr": true, "vw_dir": true, "iswr_diffuse": false, "iswr_direct": false, "T_g": false, "override": { "svf":0.8 } }
- override.svf
Allows for setting the sky view factor at the point to be different than what was calculated from the mesh.
Note
The configuration allows for fine-tuning what is passed through. So although
Depends from met
below lists all of the possible depends, whatever is set in the configuration will be what is required at runtime.Public Functions
-
point_mode(config_file cfg)
-
~point_mode()
-
virtual void run(mesh_elem &face)
Needs to be implemented by each data parallel module. This will be called and executed for each timestep
- Parameters:
face – The terrain element (triangle) to be worked upon for an element parallel domain
global_param – A pointer to the shared global paramter space with domain-wide paramters