MOOSE to PyMOOSE: Interfacing MOOSE with Python Subhasis Ray - PowerPoint PPT Presentation

MOOSE to PyMOOSE: Interfacing MOOSE with Python Subhasis Ray National Centre for Biological Sciences Tata Institute of Fundamental Research Bangalore, Karnataka, India

The People Upi Niraj Raamesh

Genesis of MOOSE GEneral NEural SImulation System has been serving for neuronal and biochemical simulations for last 20 years. It employed the idea of connecting the simulation entities through messages. The scripting language is dynamic – you can add and delete fields to/from objects at runtime. Imitated UNIX file-system tree convention to organize and traverse objects ( which are called elements). All object access is path-based.

Genesis of MOOSE “They did it by making the single “All repairs tend to destroy the worst strategic mistake that structure, to increase the any software company can entropy and disorder of the make: system.” They decided to rewrite the code -Frederick P. Brooks, "The from scratch.” Mythical Man-Month” - Joel Spolsky, Things You Should Never Do, Part I The need for modernization was pressing, with obvious limitations of the scripting language. Some aspects of the GENESIS source code are problematic.

Problems with GENESIS Messaging: implemented as linked list in genesis – forces sequential traversal. Scheduling: the scheduler looks through all objects to check if it should be processed. Encapsulation: Object safety was lacking – receiver of a message would actually peep into the memory allocated to the sender object to get message values. Extension: To introduce a new object type one has to prepare three as sociated files – C header, C source and a genesis script. A preprocessor would look into the header and create a mapping between object names and c pointers.

The creation of MOOSE Another misuse of Michelangelo's work : with due apology

GENESIS of MOOSE  MOOSE ( Multiscale Object Oriented Simulation Environment) started as a backward compatible successor of GENESIS.  The core system has been written from scratch.  The underlying architecture changed completely.  MOOSE inherits GENESIS parser and can run GENESIS scripts.

A sample session create compartment /squid useclock /squid 0 setfield /squid Ra 7.6e6 \ useclock /Vm 1 Rm 4.2e4 Cm 7.8e-9 \ reset Em -0.07 setfield /squid inject 0 create table /Vm step 0.005 -t call /Vm TABCREATE \ setfield /squid inject {INJECT} {RUNTIME / PLOTDT} 0 1 step 0.040 -t setfield /Vm step_mode 3 setfield /squid inject 0 addmsg /squid /Vm INPUT Vm step 0.005 -t setclock 0 {SIMDT} tab2file squid.plot /Vm setclock 1 {PLOTDT} table quit

Architecture of MOOSE  Three types of objects - System objects constitute the backbone of the engine, e.g. Shell, ClockJob, ClockTick etc. Simulation entities representative of biophysical / biochemical objects that represent the states / parameters we are studying Utility objects provide various other functionalities like inspecting data, interpolation, etc.

MOOSE Architecture user Command line/scripting interface The command line / scripting interface is where modeler interacts with MOOSE. file database SBW/ other model system Derived from: http://moose.ncbs.res.in/images/stories/architecture_65.jpg

MOOSE Architecture user Command line/scripting interface The user interface talks to Shell - the single point of shell access to all functionalities file available to the user database Not to be confused with the idea of UNIX shell SBW/ other model system Derived from: http://moose.ncbs.res.in/images/stories/architecture_65.jpg

MOOSE Architecture user Command line/scripting interface shell Simulation entities file database Shell creates, deletes and queries other MOOSE objects. It also executes the built-in SBW/ functionalities like file I/O. other model system Derived from: http://moose.ncbs.res.in/images/stories/architecture_65.jpg

MOOSE Architecture user Command line/scripting interface shell Simulation entities file database scheduler SBW/ At start-up, the scheduling other model system is initialized system Derived from: http://moose.ncbs.res.in/images/stories/architecture_65.jpg

MOOSE Architecture user Command line/scripting interface shell Simulation entities file database scheduler SBW/ other model system Derived from: http://moose.ncbs.res.in/images/stories/architecture_65.jpg

MOOSE Architecture user Command line/scripting interface shell Simulation entities file database ClockJob SBW/ other model system Derived from: http://moose.ncbs.res.in/images/stories/architecture_65.jpg

MOOSE Architecture user Command line/scripting interface shell Simulation entities file ClockTick 0 ClockTi database ClockJob SBW/ other model system Derived from: http://moose.ncbs.res.in/images/stories/architecture_65.jpg

MOOSE Architecture user Command line/scripting interface shell Simulation entities file solvers database scheduler SBW/ Solvers can take over the other model calculation of simulation system entities Derived from: http://moose.ncbs.res.in/images/stories/architecture_65.jpg

Solvers: Avoid the penalty of object orientation Compartment 1 Compartment 2 Compartment 3 Compartment 4 Tick0

Solvers: Avoid the penalty of object orientation Compartment 1 Compartment 2 Compartment 3 Compartment 4 Solver Tick0

MOOSE to PyMOOSE: Interfacing MOOSE with Python Subhasis Ray - PowerPoint PPT Presentation

MOOSE to PyMOOSE: Interfacing MOOSE with Python Subhasis Ray National Centre for Biological Sciences Tata Institute of Fundamental Research Bangalore, Karnataka, India The People Upi Niraj Raamesh Genesis of MOOSE GEneral NEural

UNBC Terrace 19 October 2016 Ted Binnema The Moose Enigma Moose swept the province in the

. Linux/Moose endangered or extinct? An update on this atypical embedded Linux botnet by

MOOSE Multi level Origin Organised Scalable Ethernet draft malc armd moose

Moose Lake Utilities Repair P r e p a r e - D e p l o y - E n a b l e 1 Overview Project

A Moose Once Bit My Honeypot A Story of an Embedded Linux Botnet by Olivier Bilodeau (

Multi-compartmental and multi-scale modeling in MOOSE via Python Subhasis Ray National Centre

MOOSE JAW, SASKAT CHE WAN HOME T O T HE SNOWBIRDS!! Not these kind of Snowbirds.

Moose Management Review Listening Sessions May 2019 Big Game Management Advisory Committee 1

What Can The ICTR Do For You? Gerald Moose Stacy, Administrative Director The Johns Hopkins

LCCMR ID: 009-A1 Project Title: Determining Causes of Death in Declining Moose Populations

Moose Drool Watershed Restoration Phase I III, 2012 - 2015 Restoration Reestablishment of

HUMANE ASSESSMENT WITH MOOSE tudorgirba.com humane assessment with moose tudorgirba.com

Moose e Wilshire Strea eam R Restor oration Easement Conservation Easement Transaction

Addressing the Scalability of Ethernet with MOOSE Malcolm Scott, Andrew Moore and Jon Crowcroft

Ice Roads on the James Bay Coast Community and Mining Challenges 1 Moose Cree First Nation

Moose Drool Watershed Restoration Project TMDL Implementation and the North Fork Coeur dAlene

Another view Hidden Input CEC is constant error Hidden carrousel No vanishing gradients

Port au Port/Bay St. George Fracking Awareness Group. Who are we? Jessica Ernst Port au Port

1 Topics (cont) Loop Transformations VI. Parallelism and Locality (*) Original code

VisTrails: Visualization meets Data Management Erik Anderson, Steven Callahan, Juliana Freire,

Scalable, Good, Cheap a tale of sexiness, puppets, shell scripts, and python From this...

Speaker Movement Correlates with Prosodic Indicators of Engagement Rob Voigt, Robert J. Podesva,

Overview 1 Course Information Course

Autonomous Drone Tool Lanier Watkins, PhD Chair of Computer Science and Cybersecurity Programs