ARTS built-in documentation server

Workspace Method psdFieldEtAl19


The Field [2019] particle size distribution for hail.

Reference: Field, Normalized hail particle size distributions from the T-28
storm-penetrating aircraft, JAMC, 2019

This is a 1-parmater PSD i.e. pnd_agenda_input shall have one column and
pnd_agenda_input_names shall contain a single string.
The input data in pnd_agenda_input shall be hail mass content in
unit of [kg/m3]. The naming used is pnd_agenda_input_names is free
but the same name must be used in particle_bulkprop_names and
The parameters assume a constant effective density, i.e. scat_species_b pprox 3

Derivatives are obtained analytically.

The validity range of mass content is not limited. Negative mass
contents will produce negative psd values following a distribution
given by abs(HWC), ie. abs(psd)=f(abs(HWC)).

If temperature is outside [*t_min*,*t_max*] psd=0 and dpsd=0 if
picky=0, or an error is thrown if picky=1.

Authors: Stuart Fox


psdFieldEtAl19( psd_data, dpsd_data_dx, psd_size_grid, pnd_agenda_input_t, pnd_agenda_input, pnd_agenda_input_names, dpnd_data_dx_names, scat_species_a, scat_species_b, t_min, t_max, picky )


OUTpsd_data(Matrix)Particle size distribution values for a set of points.
OUTdpsd_data_dx(Tensor3)Partial derivates of psd_data.
INpsd_size_grid(Vector)The particle sizes associated with psd_data.
INpnd_agenda_input_t(Vector)Temperature input to one element of pnd_agenda_array.
INpnd_agenda_input(Matrix)The variable input to one element of pnd_agenda_array.
INpnd_agenda_input_names(ArrayOfString)Naming of (existing or expected) data in pnd_agenda_input.
INdpnd_data_dx_names(ArrayOfString)Selection of partial derivatives of pnd_data.
INscat_species_a(Numeric)Mass-size relationship parameter, for one scattering species.
INscat_species_b(Numeric)Mass-size relationship parameter, for one scattering species.
GINt_min(Numeric)Low temperature limit to calculate a psd.
GINt_max(Numeric)High temperature limit to calculate a psd.
GINpicky(Index, Default: 0)Flag whether to be strict with parametrization value checks.