more cleanup

README.md

@@ -1,6 +1,5 @@
 <!-- Improved compatibility of back to top link: See: https://github.com/othneildrew/Best-README-Template/pull/73 -->
 <a name="readme-top"></a>
-
 <!-- PROJECT LOGO -->
 <br />
 <div align="center">
@@ -24,8 +23,6 @@
   </p>
 </div>
 
-
-
 <!-- TABLE OF CONTENTS -->
 <details>
   <summary>Table of Contents</summary>
@@ -52,6 +49,7 @@ Here's a blank template to get started: To avoid retyping too much info. Do a se
 This is an example of how you may give instructions on setting up your project locally.
 To get a local copy up and running follow these simple example steps.
 
+<p align="right">(<a href="#readme-top">back to top</a>)</p>
 
 <!-- USAGE EXAMPLES -->
 ## Usage

README1.md

@@ -1,64 +0,0 @@
-# Chirp detection - GP2023
-## Git-Repository and commands
-
-- Go to the [Bendalab Git-Server](https://whale.am28.uni-tuebingen.de/git/) (https://whale.am28.uni-tuebingen.de/git/)
-- Create your own account (and tell me ;D)
-  * I'll invite you the repository
-- Clone the repository
-- 
-```sh
-git clone https://whale.am28.uni-tuebingen.de/git/raab/GP2023_chirp_detection.git
-```
-
-## Basic git commands
-
-- pull changes in git
-```shell
-git pull origin <branch>
-```
-- commit chances
-```shell
-git commit -m '<explaination>' file  # commit one file
-git commit -a -m '<explaination>'    # commit all files
-```
-- push commits
-```shell
-git push origin <branch>
-```
-
-## Branches
-Use branches to work on specific topics (e.g. 'algorithm', 'analysis', 'writing', ore even more specific ones) and merge
-them into Master-Branch when it works are up to your expectations.
-
-The "master" branch should always contain a working/correct version of your project.
-
-- Create/change into branches
-```shell
-# list all branches (highlight active branch)
-git banch -a           
-# switch into existing          
-git checkout <existing branch>   
-# switch into new branch
-git checkout master
-git checkout -b <new branch>     
-```
-
-
-- Re-merging with master branch
-1) get current version of master and implement it into branch
-```shell
-git checkout master
-git pull origin master
-git checkout <branch>
-git rebase master
-```
-This resets you branch to the fork-point, executes all commits of the current master before adding the commits of you 
-branch. You may have to resolve potential conflicts. Afterwards commit the corrected version and push it to your branch.
-
-2) Update master branch master
-- correct way: Create
-```shell
-git checkout master
-git merge <branch>
-git push origin master
-```

recs.csv

@@ -1,29 +0,0 @@
-recording
-2020-03-13-10_00
-2020-03-16-10_00
-2020-03-19-10_00
-2020-03-20-10_00
-2020-03-23-09_58
-2020-03-24-10_00
-2020-03-25-10_00
-2020-03-31-09_59
-2020-05-11-10_00
-2020-05-12-10_00
-2020-05-13-10_00
-2020-05-14-10_00
-2020-05-15-10_00
-2020-05-18-10_00
-2020-05-19-10_00
-2020-05-21-10_00
-2020-05-25-10_00
-2020-05-27-10_00
-2020-05-28-10_00
-2020-05-29-10_00
-2020-06-02-10_00
-2020-06-03-10_10
-2020-06-04-10_00
-2020-06-05-10_00
-2020-06-08-10_00
-2020-06-09-10_00
-2020-06-10-10_00
-2020-06-11-10_00

requirements.txt

@@ -1,11 +1,13 @@
-cmocean==2.0
+audioio==0.10.0
+cmocean==3.0.3
 cycler==0.11.0
 ipython==8.12.0
-matplotlib==3.7.0
-numpy==1.23.5
-pandas==1.5.3
-paramiko==2.11.1
+matplotlib==3.7.1
+numpy==1.24.2
+pandas==2.0.0
+paramiko==3.1.0
 PyYAML==6.0
 scipy==1.10.1
 scp==0.14.5
-tqdm==4.64.1
+thunderfish==1.9.10
+tqdm==4.65.0