act_typ

The actions that can be triggered using the lum.dtl file are defined in the SWAT+ code. For each action, the type and ID of the object it is applied to, and a user-defined name have to be specified. Certain actions require additional information, which has to be specified in the fields option, const, const2, and fp. The use of these four fields depends on the action. The table below lists the actions implemented in the SWAT+ code, a short description, and the additional fields needed.

ActionDescriptionAdditional fields needed

irrigate

Irrigation

irr_demand

fertilize

Fertilizer application

fert_future

manure_demand

till

Tillage

plant

Planting

harvest

Harvest

kill

Kill

harvest_kill

Harvest and kill

rot_reset

Reset to beginning of rotation

pest_apply

Pesticide application

graze

Grazing

grow_init

Initiate growing season for HRU-lte

grow_end

End growing season for HRU-lte

drain_control

Drainage water management

divert

Divert water

res_demand

Demand from a reservoir

flow_control

Flow control for water allocation

tile_control

Tile flow control for saturated buffers

impound_off

Turn off impounded water (paddy or wetland)

impound_on

Turn on impounded water (paddy or wetland)

weir_height

Adjust weir height (paddy)

puddle

hru_fr_update

HRU area fraction change

lu_change

Land use change

p_factor

Update USLE P factor

contour

Contouring

stripcrop

Strip cropping

terrace

Terracing

tile_install

Install tile drainage

septic_install

Install septic tank

fstrip_install

Install filterstrip

grassww_install

Install grass waterway

user_def_bmp

User user-defined BMP reductions

chan_change

burn

Burning

cn_update

Update Curve Number

pheno_reset

Last updated

#1315: katie.mendoza's Oct 3 ET chapter

Change request updated