Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

isettools and isettools/data #46

Open
DavidBrainard opened this issue Dec 30, 2014 · 1 comment
Open

isettools and isettools/data #46

DavidBrainard opened this issue Dec 30, 2014 · 1 comment

Comments

@DavidBrainard
Copy link
Contributor

I think that the isettools directory should be renamed 'code' and that 'isettools/data' should come out of 'isettools' and live on its own at the top level.

Then we will have code, data, scripts, tutorials, and validation/scripts all of which can contain parallel subdirectory structure. How cool is that.

This proposed change requires fixing up some functions that define where stuff lives in the isetbio directory. Brian indicated he is the one who can make these changes most efficiently, so we'll leave this in his lap for a rainy day activity.

@DavidBrainard
Copy link
Contributor Author

There are also data in places under scripts color (e.g. cMatch) and scripts/optics (e.g. chromAb) that might be converted into isetbio format and moved into the data dir. Or made to go away, if they are obsolete. It would be nice to have all of the isetbio data files collected in one place.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant