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
tried plotting some things and I don't see anything obviously wrong. Since the lines you added back only address the threshold part of the masking (not the vmin/vmax parts of the _threshold function I added), I don't think it would break anything. However, it might be confusing/not optimal to have 2 places in a function where thresholding/masking is done? I checked and the reason why I moved the thresholding further down in that function is because, for glass brain plotting with custom vmin, the thresholding needed to be done after we take the absolute value of the data if plot_abs is True (otherwise we incorrectly lose whatever is lower than vmin), but for some reason the absolute value is only taken in GlassBrainAxes.transform_to_2d, which gives the 2D views to be plotted in each panel. It doesn't look like there is currently an easy way to take the absolute value of the whole 3D data (possibly because plot_abs is only for glass brain plots?), but maybe we can add a plot_abs parameter to the slicer objects and do the absolute value handling inside _map_show?
Anyway if this needs to be fixed as soon as possible I think your fix should be fine, but in the future we might want to consider not having the double thresholding/masking part.
tried plotting some things and I don't see anything obviously wrong. Since the lines you added back only address the threshold part of the masking (not the
vmin
/vmax
parts of the_threshold
function I added), I don't think it would break anything. However, it might be confusing/not optimal to have 2 places in a function where thresholding/masking is done? I checked and the reason why I moved the thresholding further down in that function is because, for glass brain plotting with customvmin
, the thresholding needed to be done after we take the absolute value of the data ifplot_abs
isTrue
(otherwise we incorrectly lose whatever is lower thanvmin
), but for some reason the absolute value is only taken inGlassBrainAxes.transform_to_2d
, which gives the 2D views to be plotted in each panel. It doesn't look like there is currently an easy way to take the absolute value of the whole 3D data (possibly becauseplot_abs
is only for glass brain plots?), but maybe we can add aplot_abs
parameter to the slicer objects and do the absolute value handling inside_map_show
?Anyway if this needs to be fixed as soon as possible I think your fix should be fine, but in the future we might want to consider not having the double thresholding/masking part.
Originally posted by @michellewang in #4256 (comment)
The text was updated successfully, but these errors were encountered: