File structure

[ndem0]

Is your feature request related to a problem? Please describe.
The list of module file in pydmd is becoming quite difficult to handle in a unique folder. Moreover, several classes are implemented on the same file, making the global structure difficult to easily explore.

Describe the solution you'd like
I'm thinking at least having the dmds and utils submodule, with all the DMD variants and the utility classes, but probably there are better solutions.

[fandreuz]

I was thinking a few days ago that we could have a separate directory for each DMD variant (dmd, spdmd, ...), and each dir should contain:

• DMDOperator implementation (if different than the standard one)
• DMDBase implementation
• Utils (if any)
• Tests

Having tests in the same directory as the code would be nice, for instance Dask does something like this. In PyDMD we usually need fast iterations on the code to check if tests are still passing, and I think this would simplify the development. Also it would be nice as an additional reference on how a variant is supposed to be used.

What do you think @mtezzele @ndem0 ?

[ndem0]

Dask it's a very large project, I'm not that sure that putting all the variants in subfolders is the cleanest way. Especially because I would to have only one util and one DMDOperator. Maybe some hybrid version? For example:

pydmd
 - dmds
 |--- dmd
 |  |--- dmd.py
 |  |--- test_dmd.py
 |--- dmdc
 |--- ...
 - utils
 |--- ...
 - dmd_dict.py
 - other global files