Skip to content
Snippets Groups Projects
Adriaens, Ines's avatar
Adriaens, Ines authored
af1703e0
History

BAIT - a tool for breakpoint analysis and inference of time series

  • Created by: Ines Adriaens (adria036)
    • Collaborators: Harmen Doekes, Malou van der Sluis
  • Created on: April 15, 2022

For questions, please contact ines.adriaens@wur.nl

Project description

[to be added]

Furthermore, we refer to following sources:

Project structure + roadmap

  1. Project initialisation and plan
  2. Code modules:
    • Preprocessing (+ generalisation / requirements)
    • Segmentation (changepoint analysis)
    • Classification (ML - decision trees or more)
  3. Validation of the tool
    • Dataset 1
    • Dataset 2
  4. Documentation + dissemination
    • Manuals
    • Code documentation / docstrings
    • Presentation

Scripts - files

  • README.md (this file)
  • .gitignore (local files not version controlled)
  • CHANGELOG.md (can also contain #todo or roadmaps)
  • Tool module:
    • Input & preprocessing
      • Data quality + structure
      • Requirements and environment (code)
    • Segmentation
    • Classification
  • Validation scripts:
    • Dataset I
    • Dataset II
  • Manual and documentation

Using this repo (development only)

Initialisation

  • on your local computer: go to project folder (in my case: C:\Users\adria036\OneDrive - Wageningen University & Research\iAdriaens_doc\Projects\iAdriaens\bait\code)
  • open git Bash (Git Bash Here)
  • git clone this repo (a new folder "bait" will appear)
git clone https://git.wur.nl/iadriaens/bait.git
cd bait
  • make changes locally and commit them
  • this will only keep track of your changes locally (on your own pc)
  • git status = which changes have or have not been committed
git status  
git add .
git commit -m "meaningful_message"
  • to make changes without interference with other people's work
    • BEFORE starting to work: pull last version of the project in "main"
    • create + checkout your local branch
    • "git add ." + "git commit -m "message""
  • the changes in your local branch need to be merged into main in the remote
    • push local branch and ask for merge (or merge yourself)
git pull
git checkout -b new_branch_name
  • to push your local changes to the remote, depending whether you worked in 'main' branch or a local branch
git push origin new_branch_name (or main)

Contributing

Once the tool is developed, we will be open for collaborations:

  • to test the tool on new applications / validation
  • to point out bugs / generalisation issues
  • any other comments are always welcome

License

TBD