Back to the main page.

Bug 1363 - subplots sometimes not plot in ft_artifact_zvalue

Status CLOSED WORKSFORME
Reported 2012-03-08 18:50:00 +0100
Modified 2019-08-10 11:55:44 +0200
Product: FieldTrip
Component: core
Version: unspecified
Hardware: PC
Operating System: Windows
Importance: P3 normal
Assigned to:
URL:
Tags:
Depends on:
Blocks:
See also:

Johanna - 2012-03-08 18:50:15 +0100

After I run 1 subject (possibly with multiple calls to ft_artifact_zvalue) it works fine. I 'close all' and 'clear all global' and delete(h) any remaining figures. Then I load the data for the second subject. Then the subplots don't plot the data in the interactive GUI of ft_artifact_zvalue. The reason is that on line 853, get(opt.h2,'children') is not empty. Closing out Matlab and restarting solves it. Is this a bug, or an unsolvable Matlab weirdness, or is there some other command I can use to clear hidden variables?


Jörn M. Horschig - 2012-03-09 10:21:04 +0100

I ran my analysis pipeline quite often the last weeks, in which multiple calls to ft_artifact_zvalue occur for each subject. I never encountered the error you get. However, I never close all or clear all global - did you try without these calls?


Johanna - 2012-03-09 11:38:23 +0100

Hi Joern, thanks for this info. I tried it again, with only doing 'clear all', and then it worked fine to load the next subject. I had actually been calling 'nut_fresh' which has this in it: clear all; try close all hidden; end clc; set(0,'ShowHiddenHandles','on'); delete(get(0,'Children')); So maybe something there was doing it. Works for me.


Robert Oostenveld - 2019-08-10 11:51:48 +0200

This closes a whole series of bugs that have been resolved (either FIXED/WONTFIX/INVALID) for quite some time. If you disagree, please file a new issue describing the issue on https://github.com/fieldtrip/fieldtrip/issues.


Robert Oostenveld - 2019-08-10 11:55:44 +0200

This closes a whole series of bugs that have been resolved (either FIXED/WONTFIX/INVALID) for quite some time. If you disagree, please file a new issue describing the issue on https://github.com/fieldtrip/fieldtrip/issues.