Presentation is loading. Please wait.

Presentation is loading. Please wait.

Book’s direction: overview & community decisions purpose, reader, content, method, authors, time line MATSim nomenclature

Similar presentations


Presentation on theme: "Book’s direction: overview & community decisions purpose, reader, content, method, authors, time line MATSim nomenclature"— Presentation transcript:

1 book’s direction: overview & community decisions purpose, reader, content, method, authors, time line MATSim nomenclature http://matsim.org/node/775

2 book's direction: community decisions on … for whom? for what? what? how? who? reader + scanner purpose content authors & editors when? method

3 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”

4 book's direction: community decisions on … for whom? for what? what? how? who? reader + scanner purpose content authors & editors when? method

5 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

6 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

7 book's direction: community decisions on … for whom? for what? what? how? who? reader + scanner purpose content authors & editors when? method

8 user -> application developer -> development theorist -> methodology book's direction: what? 3 (+1) target reader => 3 book parts on …

9 book's direction: what?; content 1.Intro & overview 2.MATSim history 3.Setting-up MATSim PART I: User 4.Transport planning theory 5.MATSim basics 6.MATSim scoring 7.Modules: configuring and extending functionality 8-24: single modules PART II: Developer 25.Development process 26.Contributing code 27.System characteristics and specification 28.General MATSim calibration, verification and validation 29.Extending MATSim’s core functionality PART III: Theorist 30.Behavior modeling 31.Basic procedure of MATSim … 32.Economics interpretation of MATSim 33.Relation to other transport modeling frameworks 34.MATSim as a Monte-Carlo engine 35.Simulation-based optimization 36.Research avenues books, parts, chapters sections inconsistency? diff to modules conglomeration of isolated topics concept?

10 user -> application developer -> development theorist -> methodology book's direction: what? Wisteria Lane complete in breadth not in depth -> pointers complete in depth per (isolated) topic (?) how to tell the story?

11 book's direction: what? 1.Intro & overview 2.MATSim history 3.Setting-up MATSim PART I: User 4.Transport planning theory 5.MATSim basics 6.MATSim scoring 7.Modules: configuring and extending functionality 8-24: single modules how to tell the story? guided tour through MATSim: scenarios features features scenarios “becoming a MATSim nerd in 36 chapters” plain reference with 3 isolated parts focused on 3 user types PART II: Developer 25.Development process 26.Contributing code 27.System characteristics and specification 28.General MATSim calibration, verification and validation 29.Extending MATSim’s core functionality PART III: Theorist 30.Behavior modeling 31.Basic procedure of MATSim … 32.Economics interpretation of MATSim 33.Relation to other transport modeling frameworks 34.MATSim as a Monte-Carlo engine 35.Simulation-based optimization 36.Research avenues

12 book's direction: community decisions on … for whom? for what? what? how? who? reader + scanner purpose content authors & editors when? method

13 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 & contextualize transfer & contextualize condense & contextualize link & contextualize (transfer, duplication clean-up)

14 book's direction: community decisions on … for whom? for what? what? how? who? reader + scanner purpose content authors & editors when? method

15 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? ?

16 book's direction: community decisions on … for whom? for what? what? how? who? reader + scanner purpose content authors & editors when? method

17 MATSim meetings Singapore editing, lectorate, publish & print chapter writing conceptual meeting chapter planning chapters due 2015 2014 book's direction: when? nametopicdue to ? ?

18 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


Download ppt "Book’s direction: overview & community decisions purpose, reader, content, method, authors, time line MATSim nomenclature"

Similar presentations


Ads by Google