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

thin ANTs #158

Closed
stnava opened this issue Jan 26, 2015 · 10 comments
Closed

thin ANTs #158

stnava opened this issue Jan 26, 2015 · 10 comments
Assignees

Comments

@stnava
Copy link
Member

stnava commented Jan 26, 2015

@armaneshaghi and @bkandel

make a lean/mean branch of ANTs that compiles only the most used functions i.e. what it takes to run the scripts in antsCorticalThickness and compile ANTsR

this should be as minimally different from master branch as possible ....

@stnava
Copy link
Member Author

stnava commented Jan 26, 2015

thinants is also related to: ANTsX/ANTsR#9 ... i've done some testing in antsr and it was fairly easy to go from over 1GB to 300MB in terms of the antsr build. if i rm'd the ANTS-build/lib directory then dropped to 20MB ... of course, we need that directory for ANTsR. so, ideally, it would contain a minimal set of programs. we could ID these programs in ANTsR alone but why waste time building what we don't need? ... anyway, that is a 2nd goal for this issue, in additional to generally thinning down ANTs. might mention that @ntustison and i also discussed "quieting" ANTs ie adding --verbose 0/1 options to relevant programs. programs in thin ants would be good candidates that add as well.

@stnava
Copy link
Member Author

stnava commented Feb 7, 2015

closing because i implemented this option last night in commit
1f059ed
specifically to help travis antsr builds.

@stnava stnava closed this as completed Feb 7, 2015
@ntustison
Copy link
Member

This is great, Brian.

@stnava
Copy link
Member Author

stnava commented Feb 7, 2015

this is a weight off my shoulders ( i just needed to see the green )
antsr_passing

@armaneshaghi
Copy link
Collaborator

Congrats this is great.

On Saturday, February 7, 2015, stnava notifications@github.com wrote:

this is a weight off my shoulders ( i just needed to see the green )
[image: antsr_passing]
https://cloud.githubusercontent.com/assets/324222/6093607/471dae74-aed4-11e4-93a4-14a8b1d42ab2.jpg

Reply to this email directly or view it on GitHub
#158 (comment).

@stnava
Copy link
Member Author

stnava commented Feb 7, 2015

yeah - no longer green but i'll get it back .... it's very borderline re:
the memory limits on travis

brian

On Sat, Feb 7, 2015 at 2:37 PM, Arman Eshaghi notifications@github.com
wrote:

Congrats this is great.

On Saturday, February 7, 2015, stnava notifications@github.com wrote:

this is a weight off my shoulders ( i just needed to see the green )
[image: antsr_passing]
<
https://cloud.githubusercontent.com/assets/324222/6093607/471dae74-aed4-11e4-93a4-14a8b1d42ab2.jpg

Reply to this email directly or view it on GitHub
#158 (comment).


Reply to this email directly or view it on GitHub
#158 (comment).

@armaneshaghi
Copy link
Collaborator

If it keeps failing, we need to remove make -j 2, in which case we will
exceed 50-minute limit. I will then need to build an ITK and put it on
Amazon S3 on a permanent link. This ITK build needs to be updated every
week or so (which I'm happy to do) so that we will always get an updated
ITK for development...

On Sat, Feb 7, 2015 at 11:10 PM, stnava notifications@github.com wrote:

yeah - no longer green but i'll get it back .... it's very borderline re:
the memory limits on travis

brian

On Sat, Feb 7, 2015 at 2:37 PM, Arman Eshaghi notifications@github.com
wrote:

Congrats this is great.

On Saturday, February 7, 2015, stnava notifications@github.com wrote:

this is a weight off my shoulders ( i just needed to see the green )
[image: antsr_passing]
<

https://cloud.githubusercontent.com/assets/324222/6093607/471dae74-aed4-11e4-93a4-14a8b1d42ab2.jpg

Reply to this email directly or view it on GitHub
#158 (comment).

Reply to this email directly or view it on GitHub
#158 (comment).

Reply to this email directly or view it on GitHub
#158 (comment).

@armaneshaghi
Copy link
Collaborator

Brian, could you give me write access for ANTsR?

On Sat, Feb 7, 2015 at 11:32 PM, Arman Eshaghi arman.eshaghi@gmail.com
wrote:

If it keeps failing, we need to remove make -j 2, in which case we will
exceed 50-minute limit. I will then need to build an ITK and put it on
Amazon S3 on a permanent link. This ITK build needs to be updated every
week or so (which I'm happy to do) so that we will always get an updated
ITK for development...

On Sat, Feb 7, 2015 at 11:10 PM, stnava notifications@github.com wrote:

yeah - no longer green but i'll get it back .... it's very borderline re:
the memory limits on travis

brian

On Sat, Feb 7, 2015 at 2:37 PM, Arman Eshaghi notifications@github.com
wrote:

Congrats this is great.

On Saturday, February 7, 2015, stnava notifications@github.com wrote:

this is a weight off my shoulders ( i just needed to see the green )
[image: antsr_passing]
<

https://cloud.githubusercontent.com/assets/324222/6093607/471dae74-aed4-11e4-93a4-14a8b1d42ab2.jpg

Reply to this email directly or view it on GitHub
#158 (comment).

Reply to this email directly or view it on GitHub
#158 (comment).

Reply to this email directly or view it on GitHub
#158 (comment).

@stnava
Copy link
Member Author

stnava commented Feb 7, 2015

yes, sure .

brian

On Sat, Feb 7, 2015 at 3:45 PM, Arman Eshaghi notifications@github.com
wrote:

Brian, could you give me write access for ANTsR?

On Sat, Feb 7, 2015 at 11:32 PM, Arman Eshaghi arman.eshaghi@gmail.com
wrote:

If it keeps failing, we need to remove make -j 2, in which case we will
exceed 50-minute limit. I will then need to build an ITK and put it on
Amazon S3 on a permanent link. This ITK build needs to be updated every
week or so (which I'm happy to do) so that we will always get an updated
ITK for development...

On Sat, Feb 7, 2015 at 11:10 PM, stnava notifications@github.com
wrote:

yeah - no longer green but i'll get it back .... it's very borderline
re:
the memory limits on travis

brian

On Sat, Feb 7, 2015 at 2:37 PM, Arman Eshaghi <notifications@github.com

wrote:

Congrats this is great.

On Saturday, February 7, 2015, stnava notifications@github.com
wrote:

this is a weight off my shoulders ( i just needed to see the green )
[image: antsr_passing]
<

https://cloud.githubusercontent.com/assets/324222/6093607/471dae74-aed4-11e4-93a4-14a8b1d42ab2.jpg

Reply to this email directly or view it on GitHub
#158 (comment).

Reply to this email directly or view it on GitHub
#158 (comment).

Reply to this email directly or view it on GitHub
#158 (comment).


Reply to this email directly or view it on GitHub
#158 (comment).

@armaneshaghi
Copy link
Collaborator

yes memory problem again, I'm working on this...

On Sun, Feb 8, 2015 at 12:20 AM, stnava notifications@github.com wrote:

yes, sure .

brian

On Sat, Feb 7, 2015 at 3:45 PM, Arman Eshaghi notifications@github.com
wrote:

Brian, could you give me write access for ANTsR?

On Sat, Feb 7, 2015 at 11:32 PM, Arman Eshaghi arman.eshaghi@gmail.com
wrote:

If it keeps failing, we need to remove make -j 2, in which case we
will
exceed 50-minute limit. I will then need to build an ITK and put it on
Amazon S3 on a permanent link. This ITK build needs to be updated every
week or so (which I'm happy to do) so that we will always get an
updated
ITK for development...

On Sat, Feb 7, 2015 at 11:10 PM, stnava notifications@github.com
wrote:

yeah - no longer green but i'll get it back .... it's very borderline
re:
the memory limits on travis

brian

On Sat, Feb 7, 2015 at 2:37 PM, Arman Eshaghi <
notifications@github.com

wrote:

Congrats this is great.

On Saturday, February 7, 2015, stnava notifications@github.com
wrote:

this is a weight off my shoulders ( i just needed to see the
green )
[image: antsr_passing]
<

https://cloud.githubusercontent.com/assets/324222/6093607/471dae74-aed4-11e4-93a4-14a8b1d42ab2.jpg

Reply to this email directly or view it on GitHub
<#158 (comment)
.

Reply to this email directly or view it on GitHub
#158 (comment).

Reply to this email directly or view it on GitHub
#158 (comment).

Reply to this email directly or view it on GitHub
#158 (comment).

Reply to this email directly or view it on GitHub
#158 (comment).

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

4 participants