Skip to content

Conversation

pintohutch
Copy link
Contributor

Minor fix to allow multiple nodes with the same timestamp (start or finish) to be plotted in the Gantt chart without raising an exception

@chrisgorgo
Copy link
Member

BTW could you add a smoke test for draw_resource_bar()? Maybe by switching one of the workflows to using MultiProc https://github.com/nipy/nipype/blob/master/circle.yml#L67 and then generate a gantt plot for them (and preferably keep it in artefacts so we could eyeball it).

@pintohutch
Copy link
Contributor Author

Ok, I added what little I know about the smoke tests for the draw gantt chart functionality

@chrisgorgo
Copy link
Member

Awesome! This is exactly what we needed!

@satra
Copy link
Member

satra commented Jun 12, 2016

@dclark87 - could you please merge with current master and push?

@pintohutch
Copy link
Contributor Author

Added some tolerance to the runtime profiler tests and re-based with nipy's master

@coveralls
Copy link

coveralls commented Jun 17, 2016

Coverage Status

Coverage decreased (-0.004%) to 72.207% when pulling 748bce3 on FCP-INDI:resource_multiproc into dbd5b65 on nipy:master.

@coveralls
Copy link

coveralls commented Jun 17, 2016

Coverage Status

Coverage decreased (-0.01%) to 72.201% when pulling 748bce3 on FCP-INDI:resource_multiproc into dbd5b65 on nipy:master.

@satra
Copy link
Member

satra commented Jun 18, 2016

@dclark87 - we can't even look at the output log on circle because the workflow debug statements happen every couple of ms. can we reduce the debug statements?

160617-22:21:59,543 workflow DEBUG: Free memory (GB): 51, Free processors: 2 
@pintohutch
Copy link
Contributor Author

Hey I made some fixes here to check for pandas (which is why the CI was failing) for the smoke tests. I also re-based with lastest nipy-master. Does this look all good to merge?

circle.yml Outdated
timeout: 1600
- docker run -i -v /etc/localtime:/etc/localtime:ro -v ~/scratch:/scratch -w /scratch nipype/testbench test_spm Linear /root/examples/ workflow4d :
timeout: 1600
<<<<<<< HEAD
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this file contains git differences. should be resolved and re-committed

@pintohutch
Copy link
Contributor Author

ah crap - will fix those, thanks

@coveralls
Copy link

coveralls commented Aug 1, 2016

Coverage Status

Coverage decreased (-0.007%) to 72.318% when pulling ba90842 on FCP-INDI:resource_multiproc into 3ed411b on nipy:master.

@pintohutch
Copy link
Contributor Author

@satra - this all g2g?

Copy link
Contributor

@oesteban oesteban left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Please merge with upstream/master
  • Shouldn't nipype/interfaces/tests/test_runtime_profiler.py go in nipype/pipeline/plugins/tests/test_runtime_profiler.py instead?

logger.debug('Free memory (GB): %d, Free processors: %d',
free_memory_gb, free_processors)
if len(jobids) > 0:
Copy link
Contributor

@oesteban oesteban Sep 15, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think @satra protected this trace printing with the runtime_profile boolean as well.

if toappend:
self.pending_tasks.extend(toappend)
num_jobs = len(self.pending_tasks)
logger.debug('Number of pending tasks: %d' % num_jobs)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This trace appeared too often, maybe it's ok to remove it. But I ask @satra first.

try:
mem_mb = max(mem_mb, _get_ram_mb(pid, pyfunc=pyfunc))
num_threads = max(num_threads, _get_num_threads(psutil.Process(pid)))
except psutil.AccessDenied as exc:
Copy link
Contributor

@oesteban oesteban Sep 15, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe disable the runtime_profile here?

@pintohutch pintohutch closed this Sep 16, 2016
@oesteban
Copy link
Contributor

Hi @dclark87, can I ask the reason to close this PR? I think it is really valuable.
If it is something derived from my comments, please accept my apologies.

@pintohutch
Copy link
Contributor Author

Hey @oesteban - I closed the PR because I am no longer actively developing or pushing to the FCP-INDI/nipype repo - so I am not able to rebase and make those changes. The maintainers there can open the pull request back up, rebase and address your comments.

@oesteban
Copy link
Contributor

Cool thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

5 participants