• book’s direction: overview & community decisionspurpose, reader, content, method, authors, time line

• MATSim nomenclature

http://matsim.org/node/775

book's direction: community decisions on …

for whom?

for what?

what?

how?

who?reader + scanner

purpose

content authors & editors

when?

method

• introductory text for new MATSim users

• quick reference for new MATSim developers

• starting point for in-depth methodological discussions on MATSim & microsimulation

• main reference & marketing tool

• opportunity for clean-up & contextualization

• “communication channel” between MATSim groups: (“e.g., scenarios, projects, functionality …”)

• for the fun of it!

book's direction: for what?

reader

“scanner”

book's direction: community decisions on …

for whom?

for what?

what?

how?

who?reader + scanner

purpose

content authors & editors

when?

method

• user: • how to configure & run MATSim for a standard use case

• required framework, data and parameters• available modules & tools• scenarios & projects as examples, experiences

• API-user: • how to add to MATSim for a new use case

book's direction: for whom?

“UI” + config

available modules

visit grandma with kids …

API

• developer: • how to modify MATSim for a new use case

• code organization & interfaces• system specifics

• theorist: • where and how to use and modify MATSim

• underlying theories• relation to other methods• potential new fields• principal limitations

• external: readability

book's direction: for whom?

drive races…boost engine, change tires, add spoilers

book's direction: community decisions on …

for whom?

for what?

what?

how?

who?reader + scanner

purpose

content authors & editors

when?

method

user -> application

developer -> development

theorist -> methodology

book's direction: what?3 (+1) target reader => 3 book parts on …

book's direction: what?; content1. Intro & overview2. MATSim history3. Setting-up MATSim

PART I: User4. Transport planning theory5. MATSim basics6. MATSim scoring7. Modules: configuring and extending functionality8-24: single modules

PART II: Developer25. Development process26. Contributing code27. System characteristics and specification28. General MATSim calibration, verification and validation29. Extending MATSim’s core functionality

PART III: Theorist30. Behavior modeling31. Basic procedure of MATSim …32. Economics interpretation of MATSim33. Relation to other transport modeling frameworks34. MATSim as a Monte-Carlo engine35. Simulation-based optimization36. Research avenues

books, parts, chapterssections inconsistency?

diff to modules

conglomeration of isolated topics

concept?

user -> application

developer -> development

theorist -> methodology

book's direction: what?

Wisteria Lanecomplete in breadth not in depth -> pointers

complete in depth per (isolated) topic (?)

how to tell the story?

book's direction: what?1. Intro & overview2. MATSim history3. Setting-up MATSim

PART I: User4. Transport planning theory5. MATSim basics6. MATSim scoring7. Modules: configuring and extending functionality8-24: single modules

how to tell the story?

guided tour through MATSim:

scenarios features

features <-> scenarios

“becoming a MATSim nerdin 36 chapters”

plain reference with 3 isolated parts focused on 3 user types

PART II: Developer25. Development process26. Contributing code27. System characteristics and specification28. General MATSim calibration, verification and validation29. Extending MATSim’s core functionality

PART III: Theorist30. Behavior modeling31. Basic procedure of MATSim …32. Economics interpretation of MATSim33. Relation to other transport modeling frameworks34. MATSim as a Monte-Carlo engine35. Simulation-based optimization36. Research avenues

book's direction: community decisions on …

for whom?

for what?

what?

how?

who?reader + scanner

purpose

content authors & editors

when?

method

MATSim book 1.0

publications

book's direction: how?; embedment in MATSim docu

javadoc

presentations

implicit knowledge

tutorials

mailing lists

3 guides

FAQ

examples docu

guided

not so guided

webpage

condense & contextualizetransfer & contextualize

condense & contextualize

condense & contextualize

link & contextualize(transfer, duplicationclean-up)

book's direction: community decisions on …

for whom?

for what?

what?

how?

who?reader + scanner

purpose

content authors & editors

when?

method

book's direction: who?

editors: Horni (100% - gridlock project 80 %), Axhausen, Nagel

authors: The most competent author has priority in writing the respective chapter/section; usually this is the contributor of the respective software piece. If he/she has no time or does not feel like doing that, Horni or anybody else feeling competent will write the chapter.

book repo on matsim.org for this and next editions? ?

book's direction: community decisions on …

for whom?

for what?

what?

how?

who?reader + scanner

purpose

content authors & editors

when?

method

JUL AUG SEP OCT NOV DEC JAN FEB MAR

MATSimmeetingsSingapore

editing, lectorate, publish & print

chapter writing

conceptualmeeting

chapter planning

chaptersdue

20152014

book's direction: when?

name topic due to

??

MATSim nomenclature & clean-up stuff

nomenclature:• http://matsim.org/node/790

• what is a module? • what is a contribution? extension• what is transit? pt, flight traffic, freight rail traffic (wagonSim), “Durchgangsverkehr”

clean-up stuff: • -> bug tracker

• atomic choice modules merging: e.g., mode choice, ChangeSingleLegMod, SubtourModeChoice

• notation in config: e.g., module name=“TimeAllocationMutator vs. strategy”• config vs. code naming: e.g., strategy vs. PlanStrategy