-
Notifications
You must be signed in to change notification settings - Fork 134
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
WiP: NF: Utility command to make surface renderings #401
base: master
Are you sure you want to change the base?
Conversation
we need one, but not only as cmdline utility, but also as a regular python function advantage of @nno's one though is that it doesn't require any fancy 3d libraries, and theoretically could be improved to work on surfaces loaded straight from FS |
I assume you are referring to the flat surface plotter? I think these those are somewhat complementary. I rarely use flat maps and often prefer inflated (or partially inflated) surfaces, because I think they are easier to read. Turning this whole thing into a big function is trivial. Dependency issue is, and remains, a big bummer -- not much to argue... |
yeap -- meant flat surface plotter. @nno -- any chance to get it fixed? as for this one -- I don't mind any new functionality ;) |
Thanks for the reminder @yarikoptic; I'll try to look into this in the next few days. |
See #415 for improved surface plotting functionality. |
@yarikoptic @nno What about this one? Merge or reject? |
does it work for you? for travis? ;-) |
Works for me. Does travis come with Freesurfer? Should we install it prior
|
for now we could adopt what pysurfer itself is doing:
|
That gives us minimal data, but if you run this command you'll see that it executes actual Freesurfer commands. It needs a full install. Maybe it could be worked around somehow with some effort, but for the 20 lines of plain pysurfer code, I'd rather close this PR unmerged than to spend a day figuring this out. TBH. No worries. |
For those of us who are mentally incompatible with SUMA ;-)
Lots of docs missing, obviously. Question is: do we want such thing in PyMVPA at all?