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

ENH #443 Callosal Group Example #476

Merged
merged 9 commits into from
Oct 7, 2020

Conversation

bloomdt-uw
Copy link
Collaborator

@bloomdt-uw bloomdt-uw commented Sep 25, 2020

Baseline commit. There are several other enhancements requests and issues that will follow from work on this pull request. I think the main concern I have at the moment is whether the descriptive text is sufficiently accurate and any additional recommended text that would enhance the interpretive value the anatomical images, ROIs, or streamline density maps. I will add few comments in the pull request to address specific areas of interest and concern. From this conversation, I will open separate issues and enhancement requests where needed.

@36000 36000 mentioned this pull request Oct 1, 2020
f'afq_{bundle}_density_map.nii.gz'))
show_anatomical_slices(tractogram_img.get_fdata(),
f'Cleaned {bundle} Density Map')

Copy link
Collaborator

Choose a reason for hiding this comment

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

Maybe add an html/plotly visualization with the resulting segmented bundle?

Copy link
Collaborator

Choose a reason for hiding this comment

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

Use AFQ.viz.plotly_backend function for showing streamlines. This should generate an HTML file that you can then incorporate here using:

plotly.io.show(html_file_name)

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Addressed, but depends on #513

Copy link
Collaborator

Choose a reason for hiding this comment

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

Looks like that's been merged. Could you please rebase on top of master one more time?

Copy link
Collaborator

Choose a reason for hiding this comment

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

Oh - nevermind. Looks like it's working. I'll go ahead and merge.

@arokem
Copy link
Collaborator

arokem commented Oct 5, 2020

Looks like a few other commits got convolved in with your commits. Could you please rebase?

@bloomdt-uw bloomdt-uw force-pushed the enh/443-callosal-group-example branch 3 times, most recently from 61cc797 to d9dd200 Compare October 6, 2020 17:02
@pep8speaks
Copy link

pep8speaks commented Oct 6, 2020

Hello @bloomdt-uw! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻

Comment last updated at 2020-10-06 23:52:31 UTC

@bloomdt-uw bloomdt-uw force-pushed the enh/443-callosal-group-example branch 11 times, most recently from defe752 to f1cd095 Compare October 6, 2020 21:29
@bloomdt-uw bloomdt-uw force-pushed the enh/443-callosal-group-example branch from 56d740d to 2ed4d85 Compare October 6, 2020 23:52
@arokem arokem merged commit b60a25b into yeatmanlab:master Oct 7, 2020
@bloomdt-uw bloomdt-uw deleted the enh/443-callosal-group-example branch October 7, 2020 01:33
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

Successfully merging this pull request may close these issues.

None yet

5 participants