Scheduled Employment Events Model (SEEM)
Objective
The Scheduled Employment Events Model (SEEM) handles employment events (projects) that are scheduled to happen in specified simulation years.
Algorithm
It modifies the jobs table according to specified action of each events in the scheduled_employment_events table. See the sample scheduled_employment_events table below for actions that are supported.
Configuration
OPUS path to model code
urbansim.models.scheduled_events_model
Model Parameters
The configuration of the SEEM in the zone model system is summarized in the following table:
Data
scheduled_employment_events table is used by the Scheduled Employment Events Model. Below is a sample scheduled_employment_events table that demonstrates the functions of scheduled_employment_events_model. The optional
notes column explains what each event does. Column year, action, attribute, and amount is required; users can remove one or all columns sector_id, zone_id,building_type_id or add extra columns that are primary or computed attributes of job dataset.
| year |
action |
attribute |
amount |
sector_id |
zone_id |
building_type_id |
building_id |
__notes__ |
| 2010 |
add |
not_used |
5000 |
4 |
100 |
-1 |
-1 |
add 5000 jobs of sector 4 to zone 100 |
| 2010 |
remove |
not_used |
1000 |
3 |
-1 |
-1 |
1001 |
remove 1000 jobs of sector 3 with building_id equal to 1001 |
| 2011 |
set_value |
building_id |
1011 |
3 |
-1 |
-1 |
1001 |
relocate all sector 3 jobs from building_id 1001 to 1011 |
| 2011 |
target |
not_used |
3000 |
5 |
-1 |
-1 |
1002 |
set number of sector 5 jobs in building 1002 to 3000 (add or remove jobs to meet the target) |
Topic revision: r2 - 26 Jan 2010 - 12:30:43 -
LimingWang