Closed pipitone closed 8 years ago
See voxel based memory and time estimate branch.
https://github.com/CobraLab/antsRegistration-MAGeT/tree/voxel-based-memory-time
Fun fact, ants is nicely linear with voxel count
Also see https://github.com/gdevenyi/antsRegistration-benchmarking for source of my data
Okay. So I should use that branch?
On Jul 28, 2016, at 9:24 PM, "Gabriel A. Devenyi" notifications@github.com wrote:
See voxel based memory and time estimate branch.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
Okay, I tried that branch. Looks nice, but I get a qsub error when the memory is < 1G (apparently our version of pbs doesn't like non-integer sizes for memory (man pbs_resources
). Not sure if this is a qbatch problem or an mb issue. ;-)
Okay, good to know.
I think putting a floor of 1GB of ram is probably reasonable anyways, even if we end up using less. I can roll that in after the maths transition to python.
I wouldn't call it a qbatch problem. I think we decided that qbatch shouldn't check the format of inputs for the batch system, it's the batch system that should error out.
I think we're good with the latest merge.
Do you think a memory floor still makes sense?
Oh :+1:
I looked at that and was confused why there was a max call in there.... makes sense now.
I created an extremely low resolution (step size 10) test case to play with this by resampling the winterburn atlases like so:
I'm using the atlas images as templates and subjects as well.
mb.sh b0rks when computing the memory requirements for qbatch by returning a negative number, and then failing when calling qbatch:
Perhaps lower bounds on memory/walltime estimates?