Since scripting becomes increasingly important in our projects, the rules of software development also start to apply to us. This has the downside that it requires extra effort from us, scientists, to learn new tools, but the upside is that there already is a wealth of properly tested tools and documentation available from the software development world. Having reproducible code is one of these important things, for which version control systems have been developed. It is very useful to use these systems in our projects, since they provide the following advantages:

  • You keep track of the history of a project. In this way you keep a journal of decisions made in a project.
  • If you mess up something, you can always revert to a previous state.
  • It allows for collaborative development, where individuals can create their own branch to safely work on new developments and later merge their changes.


SVN and Git are two common version control systems, both used within Deltares. These VCSs differ in implementation: SVN is a centralized version control system, whereas Git is a distributed version control system. This means that the project history in SVN only exists on a central server, whereas each Git user has a clone of the project history on their machine. Git has multiple advantages over SVN:

  • Mistakes introduced in the version control are not immediately sent to the server, so are less likely to affect others
  • Larger userbase, so more documentation and more auxiliary applications available. The editor VSCode, for example, has direct Git integration.
  • Smoother development between multiple organizations, as no central server is required at one organization. Repositories can be easily shared via platforms such as GitHub or Gitlab.


However, Git by itself has one major downside: It is not suited for large and/or binary files. Furthermore, platforms GitHub and Gitlab usually only allow storing of files up to 1 GB. To solve this, DVC (Data Version Control) was developed, which is built on top of Git and uses similar commands. This program allows storing and distributing data in the cloud (e.g., Google Drive, Google Cloud, Amazon S3 and Microsoft Azure) and at network drives (e.g., our N: - or P: -drive).


A thorough tutorial of how to use Git and DVC can be found here: https://deltares.github.io/iMOD-Documentation/practical_git_dvc.html

Request you own Github repository

If you require a repository in the Deltares space on Github then follow these steps:

  1. First you need to define what type of repository you require: PRODUCTION or RESEARCH / DEVELOPMENT. This will define the organization in which your repository will be located:

    PRODUCTION:          https://github.com/Deltares
    RESEARCH / DEVELOPMENT: https://github.com/Deltares-research

    Go to request form

  2. Secondly check if you require a PUBLIC, INTERNAL or PRIVATE repository. The table below shows what implications this choice has for your repository:


    		PUBLICINTERNALPRIVATE
    Visibilityeveryoneall organization membersselected members

    Collaborating with

    external members

    Add as many a you like as 'Outside Collaborator'.

    These users cannot be managed in teams.

    No license consumed.


    Alternatively your repository can accept 'Pull requests'.

    Then you do not need add members.

    Requires external members to become 

    actual members by adding them to the

    Deltares identity provider (Active Directory).

    Each member consumes 1 license.


    Alternatively your repository can accept 'Pull requests'.

    Then you do not need to add members. This way no

    license is consumed.

    		Same as INTERNAL
    Using ActionsFree of charge

    Shared limit of 50000 minutes / month. In near future

    each repository will receive a 'budget' in minutes according

    to a fair use policy.

    		Same as INTERNAL
    Using Issue trackerFree to use either TeamCity or Github Issues

    Free to use either TeamCity or Github Issues

    		Same as INTERNAL
    Using WIKI

    Free to use Deltares Publicwiki, Github WIKI or

    Github Pages

    Free to use Deltares Publicwiki, Github WIKI or

    Github Pages

    		Same as INTERNAL
  3. Thirdly collect the following information and send your request to the Software Support helpdesk: software.support@deltares.nl
    • Your name
    • Repository name
    • Owner (by default is requester)
    • PRIVATE, INTERNAL or PUBLIC
    • Related PMT and PMT contact for verification: Only if PRIVATE or INTERNAL

  4. Once your repository is ready, it is up to the new owner to configure the repository and manage the users.
  • No labels

Disclaimer