Back to the main page.
Bug 1695 - events are not shown in ft_databrowser
| Status | CLOSED WORKSFORME |
| Reported | 2012-09-04 16:17:00 +0200 |
| Modified | 2013-01-17 10:37:29 +0100 |
| Product: | FieldTrip |
| Component: | core |
| Version: | unspecified |
| Hardware: | PC |
| Operating System: | Linux |
| Importance: | P3 normal |
| Assigned to: | Roemer van der Meij |
| URL: | |
| Tags: | |
| Depends on: | |
| Blocks: | |
| See also: |
Diego Lozano Soldevilla - 2012-09-04 16:17:35 +0200
Created attachment 305 toy data one trial Hi I cannot see the events in ft_databrowser when I call cfg.ploteventlabels = 'type=value'; cfg = []; cfg.continuous = 'no'; cfg.ploteventlabels = 'type=value'; cfg.trl = ft_findcfg(meog.cfg,'trl'); cfg.viewmode = 'vertical'; artif = ft_databrowser(cfg,meog); attached a data toy exmple. Diego
Roemer van der Meij - 2012-09-04 16:20:03 +0200
Thanks for reporting with attachement! I'll take this one as well
Roemer van der Meij - 2012-09-06 11:09:58 +0200
Hi Diego, The reason no events are plotted is that there are no events present in the data-structure anymore. When looking into meog.cfg.previous{1}.event, it says 'empty - this was cleared by checkconfig'. This occurs as far as I know when you a field is too big according to ft_checkconfig. Did you change ft_default.checksize to a very low number? Could you read in the data again, making sure ft_default.checksize = inf? (or at least larger to what you have now).
Diego Lozano Soldevilla - 2012-09-06 12:32:51 +0200
(In reply to comment #2) Hi Roemer, Now I understand but solution will be problematic given that at the begining of each ft function there's a call on ft_defaults functions which defines some options like: if ~isfield(ft_default, 'trackconfig'), ft_default.trackconfig = 'off'; end % cleanup, report, off if ~isfield(ft_default, 'checkconfig'), ft_default.checkconfig = 'loose'; end % pedantic, loose, silent if ~isfield(ft_default, 'checksize'), ft_default.checksize = 1e5; end % number in bytes, can be inf if ~isfield(ft_default, 'showcallinfo'), ft_default.showcallinfo = 'yes'; end % yes or no, this is used in ft_postamble_callinfo Do you know how could I "bypass" the ft_defaults? It's problematic when you exceed this ft_default.checksize = 1e5; threshold when your data is too big... Thanks a lot! Diego
Roemer van der Meij - 2012-09-06 13:03:15 +0200
Hi Diego, Hmmm, I assumed you had set you ourself, accidentally to a too low number. Maybe something went wrong with your events and the structure is too large, the default cfg.checksize shouldn't remove stuff like this. Could you do global ft_defaults ft_default.checksize = inf; (this is how you set these, I thought you already did, hence me skipping the global ;))
Diego Lozano Soldevilla - 2012-09-06 14:46:38 +0200
(In reply to comment #4) Hi Roemer, In my last try I missed the "global" call but I did what you told me and doesn't work: global ft_defaults; ft_default.checksize = inf; ft_default.trackconfig = 'report'; ft_default.checkconfig = 'pedantic'; ... However, if I save the cfg.event after the ft_definetrial call and I "inlay" in the meog.cfg.event=cfg.event, everything works fine. I've 4204 "events" but I don't know if they're a lot or not. Do you know a most "elegant way" to solve the issue? Thanks Roemer
Roemer van der Meij - 2012-09-06 15:18:01 +0200
My bad, it should be: global ft_default And not: global ft_defaultS Could you try again without the S?
Diego Lozano Soldevilla - 2012-09-06 21:55:31 +0200
(In reply to comment #6) Yes indeed was the typo: Sorry for that. Now it works perfectly! Diego