Skip to content

Instantly share code, notes, and snippets.

@crvineeth97
Last active August 13, 2018 22:32
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save crvineeth97/cd5a2843dacd6012cd376e8d639d0a45 to your computer and use it in GitHub Desktop.
Save crvineeth97/cd5a2843dacd6012cd376e8d639d0a45 to your computer and use it in GitHub Desktop.
GSoC 2018 Final Report

Links

Project Description - https://summerofcode.withgoogle.com/projects/#5946345282600960

Project Proposal - https://drive.google.com/open?id=1sIdofA7lpvK0BcGRYNjFdvHPEgH0vZn5gHhSlls5Ja4

Blog - https://crvineeth97.github.io/

Pull Request - sys-bio/roadrunner#489

Work done

  • Array support has been successfully implemented for an array of Compartments, Parameters, Reactions, Species, Species References, Assignment Rules and Initial Assignments
  • Basic testing has been done on all of the above
  • Before the end of the official coding period of GSoC, no code has been merged. Once the PR is stable (i.e., passes all tests, including array tests), it will be merged with the codebase

Work to be done

  • Array support for an array of events and rate rules
  • Thorough testing with all the above modules combined
  • Code optimizations to improve efficiency and clarity
  • Thorough documentation explaining every step and the reasons for choosing a particular method

Challenges

  • The project proposal was based on a paper and hence my understanding of the codebase before the actual coding phase, was very poor
  • Setting up the environment for the project created a lot of problems. Being a Linux user, I was adamant on getting it working on a Linux environment. Once I did successfully set it up, it was hard to understand the code because there was no debugging available. Switching to Visual Studio helped a lot and made me progress at a much faster rate due to the excellent debugging tool
  • The code had good documentation except for a few parts where it took some time to understand what was happening. This was especially true for the LLVM part, where a lot of things were a haze during the first few code runs
  • Due to a medical emergency, I could not work much for almost a month. Also, I was on the wrong track and was trying something that inherently would have been very diffcult (almost impossible) to implement

Overall, the GSoC train has been a fun one and I hope to keep contributing to open source in the foreseeable future

Signing out,

Vineeth

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment