Reorganize Repository Structure

[valentina-s]

@TGAmbra @Devdoot57 Currently the repo is quite messy. Could you reorganize the structure so one can easily navigate through folders, and find code and documentation for your work?

• [ ] at the upper level you could have only a few folders: such as denoising, gui, model-training (you come up with the names) and a Readme.md explaining that this is a GSoC project, and the objectives on a conceptual level, and explanation of where one needs to look for more details.
• [ ] within each subfolder have a Readme.md with more details on what you have done there: how to use the code, what data you are using, references to papers, links to outcomes etc.

• [ ] Below are some examples you can learn from:

  • basic structure

.
+-- data
|   +-- raw
|   +-- processed
|
+-- src
|   +-- PythonModules
|   +-- tests
|   
+-- notebooks
|   +-- exploratory
|   +-- expositionary
|
+-- references
|   +-- papers
|   +-- tutorials
|
+-- results 
+-- README.md
+-- LICENSE.txt

• Data Science CookieCutter structure
• Previous GSoC students repos:
  • Kunal's repo
  • Diego's repo

[valentina-s]

@TGAmbra you can propose your structure here so we can review it before you decide on a final version.

[TGAmbra]

+-- Dataset generator	+-- Model comparison

+-- Assets	+-- data

+-- models	+-- notebook

+-- GUI	+--orca_background	+--processing (change name to GUI)	+--plots	+--screencapture	+--transforms +-- Analysis	+-- jupyter notebooks of ft and dwt	+-- code for fourier transforms (trial)	+-- preprocessing_techniques (copy of transforms)

+-- results +-- README.md +-- LICENSE.txt Dear @valentina-s what do you think of this one?

[Rish-it]

I will re-structure this repo @valentina-s