April 12th 2018

• Transims: component for table to vectorial map conversion, meeting with UofI guys for setting up the new simulation

March 29th 2018

• Transims: meeting UofI guys to set up improvements on Transims-OMS project, created repo on ALM for developing Transims v4 source code, created shared file to work on Transims-OMS design
• Transims-OMS: project redesigned to accomodate check node to enable long computation or short computation depending on congestion

Febrauary 15th 2018

• R binding: the dependency manager downloads required packages and their dependencies into a local repo. This is a one time process because if you move the OMS project along with the local repo into a different machine (the local repo is created inside the OMS project) the docker image recognizes the repo and builds the packages, if not already built.
• Meeting with Jim: exercised RUG model

February 1st 2018

• R binding: provided the list of R packages required by R scripts, docker image downloads packages + dependencies and builds them;
• Transims/OMS/FICUS: checked the entire simulation + fixed parameter to make both two loops working

January 18th 2018

• Documentation: documentation for installing docker + git + Twitter_OMSprj on Windows. Reprojecting maps on Cholera framework
• Docker image: improved error handler on entrypoint.sh. Errors correctly trapped.
• OMS 3.5.39: improved logging messages for R components. New docker image deployed.

December 14th 2017

• Transims-FICUS: teleconference UI guys for planning next steps for integrating HISA and Transims into OMS. We are now working on two repos: FICUS_Transims for developing HISA java-code; Transims_OMSprj for testing HISA code and developing Transims graph data structure
• OMS repos: merged OMS bindings repo into OMS graph data structure repo + new docker OMS release
• Transims-FICUS: implemented the Transims-FICUS workflow into OMS through a graph data structure. The graph data structure makes easier to gather transims executables per objective (e.g. node for Trip Generation, node for Network Generation, node for Vehicle Routing, node for Simulator) plus enables implicit parallelization on independent nodes. However, Transims locks the PID so executables cannot run in parallel. How to remove this lock must be investigated. Furthermore, made several adjustments on ctl files to run the simulation. => HISA-TRANSIMS for FICUS properly works. PreTransimsProc and PostTransimsProc have been succesfully connected to transims through the OMS3 graph data structure.
• Twitter components: pushed annotations for describing @In @Out variables. I have issues in using component annotations on R OMS-compliant components. I will work on that.

November 30th 2017

Twitter model: DBaugmenter and DBanalizer are now OMS-compliant and they both properly work connected to each other

Transims-FICUS: graph data structure designed for implicitly parallelize Transims execution

R binding: it is possible to connect two R component sharing the same Object without mapping

R binding: new beta dockerized version of OMS released

Documentation for installing FICUS/OMS

November 16th 2017

R binding: improved NODATA management for raster maps OMS side

Twitter model: DB builder is now an R OMS-compliant component. stdout redirected to log file.

November 2nd 2017

Dockerized version of OMS:

• added dependencies management of R packages provided with OMS project:
  • json file for describing the dependecy tree
  • python parer for parsing the json file and installing each package
  • if json file not found, template provided by container
• few improvements on docker file and entrypoint.sh for error management

Started studying transims-ficus code

October 26th 2017

October 5th 2017

September 19th 2017

September 5th 2017

August 22nd 2017

August 8th 2017

July 25th 2017

July 11th 2017

June 27th 2017

June 13th 2017

May 30th 2017

May 16th 2017

May 6th 2017

April 18th 2017

April 4th 2017

March 21st 2017

March 7th 2017