repo scope, name, & notebooks

[gaelforget]

Hi @brorfred

I feel that originally this repo was going to be focused on the testbed and its documentation. The repo name could be changed later to reflect this better if needed.

But maybe we also want to discuss the scope of this repo? Maybe you chose ocean_clustering as your repo name because this is where you intend to put your clustering codes too? Maybe you hope that others would do that too? etc

This topic came up in a conversation with @christophernhill earlier today about Jupyter notebooks he may be working on in relation to this. I suggested to discuss this here first and maybe sending a PR later. Am linking to @muellsen @jacobbien @amishra-stats @robohyun66 @follettocean too in case they can weigh in on this discussion (what's Tom's profile name on GitHub?)

[brorfred]

Hi Gael!

The original idea was to use the repo for processing scripts, data, and clustering algorithms for the project. Mainly temporarily when we are working on it so that there is a one stop shop to find everything you need. We can and should split up the different parts in to data repositories and separate software packages when it's done.