arrow-left

All pages
gitbookPowered by GitBook
1 of 6

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

name (management.sch)

Name of the management schedule

The name of the management schedule is a primary key referenced by mgt in landuse.lum. All names in the management.sch file must be unique.

op_data1

Operation data 1

Operation
Use of variable

pcom

???

plnt

Plant in the plant community to be planted

harv

Plant in the plant community () to be harvested

hvkl

Plant in the plant community () to be harvested and killed

op_data3

Operation data 3

Operation
Use of variable

pcom

plnt

harv

hvkl

management.sch

This file is used to schedule management operations.

Management operations can be scheduled by heat units/dates or by Decision Tables.

The structure of the management.sch file is different than that of most other SWAT+ input files. The first line for each management schedule specifies the name of the schedule and the number of scheduled and/or automatic operations. When using scheduled operations, it is followed by one line per operation listing operation-specific data. The operations must be scheduled by date (Heat Unit scheduling must be done using a Decision Table) listed in chronological order. For automatic operations, the names of the Decision Tables in lum.dtl are listed (one name per line). Behind the name of a Decision Table, the user may list the crop(s) used in the Decision Table, which can be useful when the same Decision Table is used for different crop rotations (see xxx in yyy).

The user may use both scheduled operations and Decision Tables for the same land use. If doing so, the names of the DTs should be listed first.

Field
Description
Type

op_typ

Type of management operation

Code
Operation
Description

pcom

Plant community

This operation initializes the plant community in the HRU

plnt

Planting/beginning of growing season

This operation initializes the growth of a specific land cover/plant type in the HRU

harv

Harvest

kill

mons

till

irrm

irra

fert

frta

frtc

pest

pstc

graz

burn

swep

prtp

skip

This operation harvests the portion of the plant designated as yield and removes the yield from the HRU, but allows the plant to continue to grow (e.g. hay cuttings)

hvkl

Harvest and kill

This operation harvests the portion of the plant designated as yield, removes the yield from the HRU and converts the remaining plant biomass to residue on the soil surface

kill

Kill

This operation kills the plant and converts the plant biomass to residue on the soil surface

till

Tillage

This operation mixes the upper soil layers and redistributes the nutrients/chemicals within those layers

irrm

Scheduled irrigation

This operation applies water to the HRU on the specified day

fert

Fertilizer application

This operation adds nutrients to the soil in the specified day

pest

Pesticide application

This operation applies a pesticide to the plant and/or soil on the specified day

graz

Grazing

This operation removes plant biomass at a specified rate and allows simultaneous application of manure

burn

Burning

This operation records the biomass, residue and phosphorus that is burned

swep

Street sweeping

This operation removes sediment and nutrient build-up on impervious areas in the HRU; can only be used when the urban build-up/wash-off routines are activated for the HRU

skip

Skipping

This operation skips to the end of the year

kill

Plant in the plant community (plant.ini) to be killed

mons

???

till

Name of tillage type in tillage.til database

irrm

Name of irrigation operation in irr.ops file

irra

Name of irrigation operation in irr.ops file

fert

Name of fertilizer in fertilizer.frt database

frta

Name of fertilizer in fertilizer.frt database

frtc

Name of fertilizer in fertilizer.frt database

pest

Name of pesticide in pesticide.pes database

pstc

Name of pesticide in pesticide.pes database

graz

???

burn

???

swep

???

prtp

???

skip

not used

plant.ini
plant.ini

day

Day operation is scheduled for

integer

hu_sch

Currently not used

real

Operation data 1

string

Operation data 2

string

Operation data 3

real

name

Name of the management schedule

string

numb_ops

Number of scheduled management operations

integer

numb_auto

Number of automatic operations

integer

op_typ

Type of management operation

string

mon

Month operation is scheduled for

integer

op_data2

Operation data 2

Operation
Use of variable

pcom

plnt

harv

hvkl

kill

mons

till

irrm

irra

fert

frta

frtc

pest

pstc

graz

burn

swep

prtp

skip

op_data1
op_data2
op_data3