Defining the scope of the package

[EiffL]

The purpose of this issue is to discuss the scope of the package

Here are some thoughts abnout the strucvture

pycs:
-sparsity.sparse2d
-sparsirt.sparse1d
-sparsity.mrs
-sparsity.pygmcalab
-stats
-stats.inverse_problem (probablement base sur mod_opt)
-tools (probablement inclue modopt)
-astro.lenspack
-astro.psf
-astro.

cxx:
-libsparse2d
-....

Dependence sur pysap
-> We want to have all the binary tools available

[EiffL]

Plan from moving forward:

• Build sapdev C++ with current official sparse2d

  • grab old code from SVN
  • Setup cmake for sapdev
  • Compile all the binaries

• Infrastructure for Python bindings

  • Reuse the ideas from Pysap
  • Universal binding strategy
  • The resulr:

from cosmostat.sparse import 2DWavelet
wt = 2DWavelet(np.array([10,.])) 

- pip installable hopefully

• At that point we can start to engage with people
  • recruit testers
  • see what else can be retrieved from other packages and added there

[sfarrens]

@EiffL do you want to keep this issue open?