Neronet

Neronet is a framework designed to facilitate the specification, submission, monitoring, control, analysis and management of many different computational experiments. The tool is ment to be used by computational researchers that have access to a computing cluster with several nodes accessible via SSH and SSH keys.

Neronet was born as a software development project undertaken by Team 11 of the Aalto University course CSE-C2610 Software Project of semestern 2015-16 for Pyry Takala from the Aalto deep learning research group. The project was started on October 19th 2015 and finished on April 13th 2016. The project was conducted in seven sprints and Scrum was employed.

This project is under the MIT License.

To start using Neronet, follow the instructions at the Neronet start guide. A more extensive manual is also available. The shortest intro available is the briefly commented CLI demo script.

We also have a user group at Google for possible future user community creation and user support.

Branches

The project repo contains two main branches:

• stable -- the stable state of the product as per the latest finished increment. It's content should be production ready, and it has passed our definition of done.
• sprint -- the work in progress of the currently ongoing increment (sprint).

During active development the sprint branch is used for active development work and is merged to stable once each sprint increment gets done.

General information

The files listed below offer lots of project related information:

• Project Introduction -- original project proposal by the PO
• Project Information -- notes by the team help in planning and directing development work
• Product Vision -- A scrum instrument answering the why, what, and for whom questions regarding this project
• Process Overview -- how in practice that is the schedule and development practices
• Technical Overview -- what in practice (architecture, etc.)
• Definition of Done -- a Scrum tool to help us ensure high quality
• Project report -- the project report presented at the end of the project for our evaluators

Notes on related themes

• Evaluation -- a summary of course evaluation criteria
• Meetings -- a chronology of meetings history with related notes
• Teamwork -- notes to improve teamwork
• Tools -- notes on selected or candidate tools
• Scrum -- some notes on Scrum
• Architecture -- notes about the initial sketching of the product system architecture

Team

The project team consisted of

• Samuel Marisa (smarisa) -- scrum master
• Teemu Blomqvist (blomqvt1) -- developer
• Joona Marjakangas (AbleCable1) -- developer
• Tuomo Perä (ltukezl) -- developer
• Matias Pitkänen (Matte27) -- developer
• Iiro Tähkä (Donkeyhead) -- developer
• Eero Laukkanen (ecimon) -- agile coach
• Pyry Takala -- product owner

To learn more about us, you can check this repository's IO page which we prepared for our PO when applying for this project.