joheinze/PriNCe

How to deal with support packages.

Closed this issue · 2 comments

The suggestion is to rename analyzer to prince-analysis-tools and the utils folder to prince-utils.

The analyzer gets a setup.py and becomes pip install-able, because some examples in prince depend on it. The pip installation may be not the recommended way, but it will be easy to maintain on clusters and containers if stuff is consistent. To accomplish this will be fairly easy once prince is on pip.

  • The stuff from data and utils will go into the package prince-data-utils. The package doesn't need to be pip install-able, but can be if needed. The data tables will be checked into git to maintain strict consistence and means for reproduction of previous results.
  • The data-utils will be structured in a way that it will gather different resources (files) and construct a consistent single database file in HDF that can be used by prince. This datafile will get a version and will be distribu

ted as binary as part of a github release.

The data stuff is priority 1 the analyzer is 2 and you can use it as a training case to bring it to pypi.
If you agree with this plan, please create a project named prince-data-utils and gimme access. I will implement 1.

Sounds good!

I created the repo and invited you

I already renamed the analysis tools and created a setup.py

The tools are now found at https://github.com/joheinze/PriNCe-analysis-tools