Separate research code from PING portal code - Githubissues

guruucsd / PING

This is a Python framework for accessing and analyzing PING data.

1 stars 2 forks source link

Separate research code from PING portal code #8

Open bcipolli opened 9 years ago

bcipolli commented 9 years ago

Right now, they're inter-mixed. Make the PING set of tools into a separate package (ping).

Move scripts into ping/scripts/
Make a generic, but simple, framework for computing derived measures.

bcipolli commented 9 years ago

Current architecture:

ping/apps - generic
ping/tests - research
ping/access - mixed; can be generalized
ping/asymmetry - research-only
ping/computed_measures.py - mixed; can be generalized
ping/export.py - generic
ping/multivariate.py - mixed; can be generalized
ping/similarity.py - generic
base directory is ALL research.

New architecture:

have a function that collects all derived measures, that can be called by generic methods like PCA.
How to do it? object-oriented programming :)

Object design:

PINGData(just ping)
PINGUserData(only derived)
PINGAllData(ping PLUS derived)

Package design:

ping/apps/ - remote access. move session to init
ping/data/ - data objects
ping/analysis/ - data analysis (PCA, similarity, etc)

bcipolli commented 9 years ago

This is pretty far along. Module redesign is done, but object model is still lagging.