[MINC-users] RMINC v0.4

Jason Lerch jason at bic.mni.mcgill.ca
Wed Feb 13 22:31:38 EST 2008


Hi Alex and others,


On 13-Feb-08, at 10:16 PM, Alex Zijdenbos wrote:

> Hi Jason,
>
> There appear to be a few glitches with the configure/build process of
> this version revolving around libz - I belief Claude will get in touch
> with you to fix these.

OK, great.

>
> As for the repository, some folks at the BIC (somehow including me)
> have started to use Google Code for projects. I can't judge the
> relative merits of this vs launchpad at the moment, but perhaps others
> have thoughts? Using one of these types of services makes sense to me,
> but if that is where we want to go it would also be nice to
> standardize on one.

Google code was my second choice. The reasons why I opted for  
launchpad were the following:

* Bazaar rather than subversion: it makes it easier for somebody to  
contribute code without being given write access to the central  
repository. I.e. I can branch the code, make my changes (committing  
to my branch as needed), write them back to my own space on  
launchpad.net, and then register them with the project. The owners of  
the project can then decide to merge those changes at their leisure.  
Even if the owners don't merge immediately my branch will be listed  
with the project as one of the branches were work is ongoing. Of  
course creating patches, etc., is possible with subversion too, but  
the process is not as convenient.
* The "ask a question facility" is really nice - anyone who is  
registered to receive questions with a project will get them emailed,  
and they can answer by email, which in turn will show up on the web- 
site under that question.
* Ditto for blueprints - makes planning features and requesting  
features pretty easy, and, importantly, makes it trivial to  
communicate to the outside world what is planned for each particular  
project.
* The ability to group separate projects - i.e. various MINC tools  
could exist in separate projects but be grouped under one larger MINC  
meta-project.
* integration with debian/ubuntu packaging. Andrew liked this reason  
in particular, given that debian packages appear to be our most  
reliable binary packaging system at the moment.

Those are some of my reasons - but that being said, I agree that it's  
better to standardize on one place, and if the consensus is for  
google code or something else I'm willing to follow along.

Cheers,

Jason


>
> -- A
>
> On Feb 3, 2008 6:18 PM, Jason Lerch <jason at bic.mni.mcgill.ca> wrote:
>> Greetings all,
>>
>> RMINC v0.4 is available for those who care. A quick summary of what's
>> new:
>>
>> * easier to use linear models and file writing utilities.
>> * descriptive statistics (mean, standard deviation, etc.) that can be
>> split by random groupings.
>> * better incorporation of False Discovery Rate thresholding.
>>
>> (For those who've never heard of RMINC: it is a package to allow
>> voxel-wise statistics to be performed inside R, an open source
>> statistics program/toolbox).
>>
>> The code is available here:
>>
>> https://code.launchpad.net/rminc/1.0/0.4
>>
>> To install, download the tarball, and run 'R CMD INSTALL
>> RMINC_0.4.tar.gz --configure-args=/path/to/minc2' If you want to
>> install it a nondefault location, set the R_LIBS environment variable
>> first.
>>
>> You'll also find a PDF file in the same place which is an early stage
>> version of a mini-booklet describing how to use RMINC. Plenty of
>> examples in there to help you get started, though the actual text is
>> still, um, rather incomplete.
>>
>> The RMINC project is now hosted on Ubuntu's launchpad site:
>>
>> https://launchpad.net/rminc
>>
>> There are tools there for asking questions, reporting bugs, and
>> suggesting blue-prints for wanted functionality. Please do use them -
>> I'd love to hear about bugs and am quite happy to listen to  
>> suggestions
>> (i.e. blueprints) for what RMINC should be able to do. Though I won't
>> promise to get it all done by tomorrow!
>>
>> For all those MINC developers out there: how about moving some of the
>> other public MINC tools and libraries to launchpad? Seems to make  
>> code
>> sharing, bug reporting, etc. quite easy without requiring us to
>> reinvent the wheel on some server in Montreal. Thoughts?
>>
>> Cheers,
>>
>> Jason
>>
>> _______________________________________________
>> MINC-users at bic.mni.mcgill.ca
>> http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-users
>>
>>
> _______________________________________________
> MINC-users at bic.mni.mcgill.ca
> http://www2.bic.mni.mcgill.ca/mailman/listinfo/minc-users



More information about the MINC-users mailing list