Skip to content
This repository has been archived by the owner on May 14, 2021. It is now read-only.

How to deal with multiple views and hemi #26

Open
OlehKSS opened this issue Jun 22, 2018 · 7 comments
Open

How to deal with multiple views and hemi #26

OlehKSS opened this issue Jun 22, 2018 · 7 comments
Projects

Comments

@OlehKSS
Copy link
Collaborator

OlehKSS commented Jun 22, 2018

In PySurfer you can do hemi='lh' | 'rh' | 'both' | 'split', as well as views='lat' or views=['lat', 'med'].

Hopefully IPyvolume gives you some way of having multiple sub-panels/sub-scenes in a single rendering context (i.e., a 2x2 grid where each panel in the grid has its own objects and camera controls). If it already has these mechanisms the translation should be straightforward.

If it does not, then please open an IPyvolume issue discussing this use case so we can discuss potential solutions.

@OlehKSS OlehKSS added this to To do in GSOC-2018 via automation Jun 22, 2018
@agramfort
Copy link
Member

agramfort commented Jun 23, 2018 via email

@larsoner
Copy link
Member

I think it might fit within that. I frequently use hemi='split', views=['lat', 'med'] to look at data. You see the whole brain (approximately) at once), rather than 1/4 of it.

If it's not supported easily in ipyvolume, though, I agree that it should be a low priority because of the amount of work likely necessary to make it work.

@OlehKSS
Copy link
Collaborator Author

OlehKSS commented Jul 24, 2018

Do you think this can be closed, since in pull request #25 support for multiple views and hemi='split' were added?

@larsoner
Copy link
Member

Let's wait until the views actually works. IPyvolume needs some camera fix, right?

@OlehKSS
Copy link
Collaborator Author

OlehKSS commented Jul 24, 2018

Yes, there is a bug
widgetti/ipyvolume#156

@larsoner
Copy link
Member

Is it worth you looking into it to see if you can fix it?

@OlehKSS
Copy link
Collaborator Author

OlehKSS commented Jul 24, 2018

I have no idea how hard can it be. As far as I understand, the bug appeared due to the switch to threejs camera. I will ask whether anyone working on it right now.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
GSOC-2018
  
To do
Development

No branches or pull requests

3 participants