Closed jovo closed 9 years ago
Yah. LONI has a library containing modules and workflows, both a "personal" library for things that are locally stored and a "server" library for things on a distributed server. Dean and I settled on the library -> modules, workflows organization awhile back, which seems to work well. We are consistent across i2g and ocpMatlab (which has basic data access modules, not algorithms)
Does that make sense?
I2G currently has the following folder structure:
data: very small files are committed; else a place for the result of data downloads via wget documentation: how to use I2G. This is where the examples will go as we build external: tools that others have built that we use, like gala or vlfeat or ilastik library: LONI modules and workflows packages: subfolders containing each algorithm test: unit/system tests for QA/QC
(old is deprecated and will disappear as the new workflows are built.)
Best, Will
On Wed, Mar 11, 2015 at 9:11 AM, joshua vogelstein <notifications@github.com
wrote:
i2g has a directory called 'library', which has subfolders, 'modules' and 'workflows'. i'm not sure why it is called 'library' instead of 'LONI', but regardless, i'd like a folder in m2g called either 'library' or 'LONI' which contains all the LONI stuff. @willgray https://github.com/willgray can perhaps opine on why we'd call it library vs. LONI. note that i haven't just done it myself because i was unsure if moving such stuff would break something.
— Reply to this email directly or view it on GitHub https://github.com/openconnectome/m2g/issues/57.
ok, great, @gkiar please make it so.
@willgray - all the stuff currently in 'src' in 'm2g', where does that belong in your organization? packages?
That's right, packages. As a suggestion, I find it easier to have the code for each module in a subdirectory, although that may be more trouble than it's worth for m2g right now.
Best, Will
On Wed, Mar 11, 2015 at 9:54 AM, joshua vogelstein <notifications@github.com
wrote:
ok, great, @gkiar https://github.com/gkiar please make it so.
@willgray https://github.com/willgray - all the stuff currently in 'src' in 'm2g', where does that belong in your organization? packages?
— Reply to this email directly or view it on GitHub https://github.com/openconnectome/m2g/issues/57#issuecomment-78266533.
Great, thanks for clarification, guys. @willgray there is only one script per module and they're all named very similarly to the modules - so I don't think that is necessary now either. On Mar 11, 2015 10:01 AM, "William Gray" notifications@github.com wrote:
That's right, packages. As a suggestion, I find it easier to have the code for each module in a subdirectory, although that may be more trouble than it's worth for m2g right now.
Best, Will
On Wed, Mar 11, 2015 at 9:54 AM, joshua vogelstein < notifications@github.com
wrote:
ok, great, @gkiar https://github.com/gkiar please make it so.
@willgray https://github.com/willgray - all the stuff currently in 'src' in 'm2g', where does that belong in your organization? packages?
— Reply to this email directly or view it on GitHub https://github.com/openconnectome/m2g/issues/57#issuecomment-78266533.
— Reply to this email directly or view it on GitHub https://github.com/openconnectome/m2g/issues/57#issuecomment-78267763.
i2g has a directory called 'library', which has subfolders, 'modules' and 'workflows'. i'm not sure why it is called 'library' instead of 'LONI', but regardless, i'd like a folder in m2g called either 'library' or 'LONI' which contains all the LONI stuff. @willgray can perhaps opine on why we'd call it library vs. LONI. note that i haven't just done it myself because i was unsure if moving such stuff would break something.