You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to include these renderings as supplemental material to the paper. However, I think the rendering looks much better when it uses "trilinear" interpolation, instead of nearest neighbor interpolation. Is there a way to make this the default interpolation when you make the static webpage using cortex.webgl.make_static?
Cheers,
Gilles
The text was updated successfully, but these errors were encountered:
Hey folks -- so afaik there's no config setting for this, but you should be able to control it programmatically. That means you could add a line to your template HTML file that sets the sampler as soon as the brain is loaded (i.e. in the onload event). It should look something like this: viewer.ui.set("surface.{subject}.sampler", "trilinear")
where {subject} is replaced by your subject identifier.
This works for me on a test viewer, but unfortunately doesn't seem to work on the viewer @Gilles86 linked because your subject identifier (odc.tr) has a period in it, and dat.gui uses periods as separators. There might be a workaround for this, but in the meantime I'd recommend either using a different subject identifier or setting the parameter anonymize=True when you call cortex.webgl.make_static, which should change the subject identifier to "S1".
Hi,
I'm a big fan of PyCortex and used it at lot for a 7T fMRI data set we collected, visualizing ocular dominance columns.
You can see some results for example here:
http://aeneas.labs.vu.nl/odc/sub-06/
I want to include these renderings as supplemental material to the paper. However, I think the rendering looks much better when it uses "trilinear" interpolation, instead of nearest neighbor interpolation. Is there a way to make this the default interpolation when you make the static webpage using
cortex.webgl.make_static
?Cheers,
Gilles
The text was updated successfully, but these errors were encountered: