Back to the main page.
Bug 1515 - databrowser with viewmode=vertical should get better vertical ticks
| Status | CLOSED FIXED |
| Reported | 2012-06-11 16:46:00 +0200 |
| Modified | 2013-01-17 10:42:20 +0100 |
| Product: | FieldTrip |
| Component: | plotting |
| Version: | unspecified |
| Hardware: | PC |
| Operating System: | Mac OS |
| Importance: | P5 normal |
| Assigned to: | Roemer van der Meij |
| URL: | |
| Tags: | |
| Depends on: | |
| Blocks: | |
| See also: |
Robert Oostenveld - 2012-06-11 16:46:15 +0200
Created attachment 275 screen shot from the connectivity tutorial Right now the vertical limits are probably (max(abs)) of the data, causing the ticks between the channels to be rather arbitrary and have a lot of decimal numbers. See attached example with values of 5.17106. Better would be round up to the nearest larger "nice value". In this case I think 5.5 or 6 would be nice values for the vertical scaling. It should be easy to replicate this with any data, but I used the following from the connectivity tutorial. cfg = []; cfg.ntrials = 500; cfg.triallength = 1; cfg.fsample = 200; cfg.nsignal = 3; cfg.method = 'ar'; cfg.params(:,:,1) = [ 0.8 0 0 ; 0 0.9 0.5 ; 0.4 0 0.5]; cfg.params(:,:,2) = [-0.5 0 0 ; 0 -0.8 0 ; 0 0 -0.2]; cfg.noisecov = [ 0.3 0 0 ; 0 1 0 ; 0 0 0.2]; data = ft_connectivitysimulation(cfg); cfg = []; cfg.viewmode = 'vertical'; ft_databrowser(cfg, data);
Robert Oostenveld - 2012-06-11 16:47:31 +0200
(In reply to comment #0) Please note that we should not simply round to the nearest larger integer. Imagine plotting data that is 0.482521 *10-12 Tesla... You don't want that to be plotted from -1 to +1 Tesla.
Roemer van der Meij - 2012-07-04 16:10:01 +0200
I changed the maxabs to now round off to two significant numbers. Was this what you had in mind?
Robert Oostenveld - 2012-07-04 18:54:33 +0200
(In reply to comment #2) Yup
Roemer van der Meij - 2012-07-05 17:12:40 +0200
changing to fixed