filename linenumber description
ft_appenddata.m 209 create the output from scratch and don't use the first varargin
ft_appenddata.m 213 think whether this can ever happen
ft_appenddata.m 229 is not entirely robust if the different inputs have different
ft_appendfreq.m 195 append dof
ft_appendfreq.m 198 append cumtapcnt cumsumcnt trialinfo dof
ft_appendfreq.m 266 do a check on whether the parameters are present in all datasets
ft_artifact_ecg.m 207 , at present this only works for continuous data: the assumption can
ft_channelnormalise.m 84 this can be kept, provided the scaling is built in appropriately
ft_combineplanar.m 229 ?
ft_componentanalysis.m 509 , this is not properly supported yet
ft_componentanalysis.m 519 , this is not properly supported yet
ft_connectivityanalysis.m 101 do method specific calls to ft_checkconfig
ft_connectivityanalysis.m 130 old-fashioned pcc data
ft_connectivityanalysis.m 163 do something extra here
ft_connectivityanalysis.m 165 call selectdata
ft_connectivityanalysis.m 168 check which methods require hasrpt
ft_connectivityanalysis.m 212 think of accommodating partial coherence for source data with only a few references
ft_connectivityanalysis.m 254 could also work with time domain data
ft_connectivityanalysis.m 291 throw an error if cfg.complex~='abs', and dojack==1
ft_connectivityanalysis.m 292 throw an error if no replicates and cfg.method='plv'
ft_connectivityanalysis.m 293 trial selection has to be implemented still
ft_connectivityanalysis.m 327 this is fast but throws away the trial dimension, consider
ft_connectivityanalysis.m 404 consider keeping track of which channels have been partialised
ft_connectivityanalysis.m 614 do we really need this, or is this related to how
ft_connectivityanalysis.m 642 do we really need this, or is this related to how
ft_connectivityanalysis.m 824 this needs to be implemented still
ft_connectivityanalysis.m 860 move functionality into ft_connectivity_granger
ft_connectivityanalysis.m 868 this is probably not correct
ft_connectivityanalysis.m 873 move functionality into ft_connectivity_granger
ft_connectivityanalysis.m 887 speed up code and check
ft_connectivityplot.m 52 check explicitly which channels belong together
ft_connectivitysimulation.m 208 think about this
ft_databrowser.m 81 these should be removed
ft_databrowser.m 82 document these
ft_databrowser.m 232 in case of continuous=yes the trl should be [1 hdr.nSamples*nTrials 0]
ft_databrowser.m 243 make a check for the consistency of cfg.continous, cfg.blocksize, cfg.trl and the data header
ft_databrowser.m 673 this is on
ft_databrowser.m 961 should be used
ft_databrowser.m 1067 speedup ft_prepare_layout
ft_databrowser.m 1086 needs a shift to the left for components
ft_databrowser_old.m 655 this is only for debugging
ft_databrowser_old.m 1336 implement further details
ft_denoise_pca.m 103 do compatibility check on data vs refdata with respect to dimensions (time-trials)
ft_denoise_pca.m 148 the default truncation applied by 4D is 1×10-8
ft_dipolefitting.m 563 this should be renamed (if possible w.r.t. EEGLAB)
ft_dipolefitting.m 564 this should be renamed (if possible w.r.t. EEGLAB)
ft_dipolefitting.m 569 assign Vdata to an output variable, idem for the model potential
ft_dipolefitting.m 573 assign Vdata to an output variable, idem for the model potential
ft_electroderealign.m 364 change the flow in the remainder
ft_electroderealign.m 447 interactive realigning to template electrodes is not yet supported
ft_freqanalysis.m 545 this works only if all frequencies have the same number of tapers (ancient fixme)
ft_freqanalysis_mvar.m 68 build in repetitions
ft_freqanalysis_mvar.m 135 probably the normalization for the zero Hz bin is incorrect
ft_freqgrandaverage.m 30 averaging coherence is not possible if inputs contain different amounts of data (i.e. chan/freq/time)
ft_freqstatistics.m 170 deal with channelcmb
ft_freqstatistics.m 326 squeeze out the appropriate dimords if avgoverfreq etc.
ft_headmodelplot.m 132 why is this empty setting neccessary?
ft_headmovement.m 47 ?
ft_interactiverealign.m 103 pass this as appdata
ft_interactiverealign.m 323 also plot lines?
ft_interactiverealign.m 330 also plot lines?
ft_interactiverealign.m 334 this only works for boundary element models
ft_interactiverealign.m 350 this only works for boundary element models
ft_multiplotER.m 172 rename matrixside and refchannel in more meaningful options
ft_multiplotER.m 529 dat = reshape(dat, [siz(1:2) siz(4)]);
ft_multiplotER.m 545 ?
ft_multiplotER.m 588 shouldn't this be replaced with a call to ft_plot_vector?
ft_multiplotER.m 760 this only works with label being a string
ft_mvaranalysis.m 336 think about this
ft_mvaranalysis.m 373 check which is which: X(t) = A1*X(t-1) + … + An*X(t-n) + E
ft_mvaranalysis.m 402 check which is which: X(t) = A1*X(t-1) + … + An*X(t-n) + E
ft_prepare_headmodel.m 50 list the options in the documentation to the function
ft_prepare_headmodel.m 114 input data with a gradiometer description should also be
ft_prepare_headmodel.m 177 : this will be done in ft_prepare_fdmmodel
ft_prepare_headmodel.m 284 should the output vol get a cfg?
ft_prepare_layout.m 541 there is a conflict between the use of cfg.style here and in topoplot
ft_prepare_layout.m 735 : consider changing the box-size being determined by mindist
ft_prepare_sourcemodel.m 148 move to cfg.grid
ft_prepare_sourcemodel.m 155 move to cfg.grid
ft_prepare_sourcemodel.m 161 move to cfg.grid
ft_prepare_sourcemodel.m 167 move to cfg.grid
ft_prepare_sourcemodel.m 168 move spheremesh to cfg.grid
ft_prepare_sourcemodel.m 187 move to cfg.grid
ft_prepare_sourcemodel.m 188 move spheremesh to cfg.grid
ft_prepare_sourcemodel.m 281 how to determine grid.unit here?
ft_prepare_sourcemodel.m 299 is it desirable to have this in the grid?
ft_prepare_sourcemodel.m 303 is it desirable to have this in the grid?
ft_prepare_sourcemodel.m 307 is it desirable to have this in the grid?
ft_prepare_sourcemodel.m 478 loop over all files, this should be two hemispheres
ft_prepare_sourcemodel.m 542 use inside_vol instead of this replication of code
ft_prepare_sourcemodel.m 668 should the cfg be added to the output grid?
ft_preprocessing.m 254 this should be handled by ft_checkconfig, but ft_checkconfig does not allow yet for
ft_sensorrealign.m 412 change the flow in the remainder
ft_sensorrealign.m 498 interactive realigning to template electrodes is not yet supported
ft_sourceanalysis.m 435 it was incorrect , since the
ft_sourceanalysis.m 559 , should be averaged and repeated for each trial
ft_sourceanalysis.m 560 , should be averaged and repeated for each trial
ft_sourceanalysis.m 561 , should be averaged and repeated for each trial
ft_sourceanalysis.m 936 , add the component numbers to the output
ft_sourceanalysis.m 986 , convert the source reconstruction back to a frequency representation
ft_sourceanalysis.m 988 , convert the source reconstruction back to a component representation
ft_sourcedescriptives.m 261 in the presence of a refdip and/or supdip, this does not work; leadfield is Nx3
ft_sourcedescriptives.m 263 this is a proposed dirty fix
ft_sourcedescriptives.m 348 kan volgens mij niet
ft_sourcedescriptives.m 472 this only makes sense when only a reference signal OR a dipole is selected
ft_sourcegrandaverage.m 346 also allow volume structures to be used
ft_sourceinterpolate.m 227 include other key-value pairs as well
ft_sourcestatistics.m 138 implement roi-based statistics for the new implementation
ft_sourcestatistics.m 151 only supported for old-style source representation
ft_sourcestatistics.m 198 ft_selectdata should be used for the subselection
ft_sourcestatistics.m 199 ft_selectdata has to be adjusted to work with new style source data
ft_sourcestatistics.m 479 think of how this generalizes to volumetric data (boolean inside etc)
ft_sourcestatistics.m 514 what about volumetric data?
ft_sourcestatistics.m 541 this assumes positions to be in the first dimension always
ft_sourcestatistics.m 542 what about volumetric dadta
ft_sourcestatistics.m 558 take the intersection between all inputs
ft_spikedetection.m 363 implement variable length waveforms
ft_spikedetection.m 369 implement a peak shift
ft_timelockanalysis.m 41 if input is one raw trial, the covariance is not computed correctly
ft_timelockstatistics.m 88 at this moment (=10 May) this does not work, because the input might not always have an avg
ft_volumesegment.m 386 check whether this works at all
ft_volumesegment.m 388 this may not be needed in spm8
ft_volumesegment.m 489 check this (e.g. strel_bol)
ft_volumewrite.m 149 determine the voxel index of the fiducials
ft_volumewrite.m 175 determine the voxel index of the coordinate system origin
ft_volumewrite.m 302 , this is not functional at the moment, since earlier in this function all nans have been replaced by zeros
ft_volumewrite.m 379 , this currently does not work due to all flipping and permuting
loreta2fieldtrip.m 67 the transformation matrix should be assigned properly
loreta2fieldtrip.m 110 someone should figure out how to interpret the activity
nutmeg2fieldtrip.m 126 : should Gcoef be added regardless of structin.meg.grad_order?')
nutmeg2fieldtrip.m 179 is this valid dimord?
nutmeg2fieldtrip.m 212 is this a valid field?
spm2ft.m 53 the following is not correct
statistics_stats.m 228 , the probability is returned for each factor separately
private/channelposition.m 73 : I don't know whether this works for a vector-gradiometer
private/channelposition.m 114 not sure whether this will work
private/channelposition.m 222 not sure whether this will work
private/convert_event.m 137 ?
private/csd2transfer.m 457 think about this
private/csd2transfer.m 511 check this; at least not multiplying it removes the need to correct later on
private/csd2transfer.m 610 check this; at least not multiplying it removes the need to correct later on
private/csd2transfer.m 775 build in check for hermitianity
private/denoise_artifact.m 72 , this assumes that all artifacts are equally long
private/dimlength.m 75 HACK to be fixed
private/dimlength.m 86 HACK to be fixed
private/dimlength.m 97 HACK to be fixed
private/dimlength.m 182 discuss appending label to source-like data
private/fourier2crsspctrm.m 70 ?
private/headsurface.m 201 in case of a icosahedron projected onto a localspheres model, the
private/interp_ungridded.m 120 6 is number of iterations, improve here
private/mergeconfig.m 12 also deal with configuration objects
private/mergeconfig.m 17 also deal with configuration objects
private/ndgrid.m 27 this function still only works up
private/ndgrid.m 122 this has to be done
private/parameterselection.m 101 'pos' in dimord is not OK
private/prepare_freq_matrices.m 112 this fails in case dimord=rpt_chan_freq and only 1 trial
private/prepare_mesh_manual.m 36 : control slice's cmap referred to abs values
private/prepare_mesh_manual.m 37 : clean structure slicedata
private/prepare_mesh_manual.m 38 : check function assign3dpoints
private/prepare_mesh_manual.m 46 why is this in cfg?
private/prepare_mesh_manual.m 56 give a warning or so?
private/prepare_mesh_manual.m 759 : obsolete: replaced by headshape at the beginning
private/prepare_mesh_manual.m 764 : make it work for pre-loaded meshes
private/prepare_resampled_data.m 104 for averaging the number of conditions can also be larger than 1
private/prepare_resampled_data.m 107 for randomization the number of conditions can already be larger than 2
private/read_besa_swf.m 87 , here combine the channels of the regional sources
private/read_besa_tfc.m 82 the following statement does not work for Matlab 7.2 on XP (see mail from Stephan Bickel)
private/resampledesign.m 203 allow for length(cfg.uvar)>1, does it make sense in the first place
private/smudge.m 83 this can be speeded up by using the sparse command
private/statistics_wrapper.m 489 this is old code should be removed
private/statistics_wrapper.m 511 : this was obviously wrong, because often trial-data is one-dimensional, so no dimensional information is present
private/surfaceorientation.m 40 there is a bug in solid_angle resulting in negative values where they should be positive and vice versa
private/undobalancing.m 27 check whether this is robust
private/univariate2bivariate.m 115 only works for 1 frequency
private/univariate2bivariate.m 130 come up with something reshape( repmat(data.pos(cmb,:),[nvox 1]);data.pos data.pos];
private/univariate2bivariate.m 141 this assumes only 1 freq bin
private/univariate2bivariate.m 174 this assumes dimord to be 'rpttap_…'
private/univariate2bivariate.m 184 hard coded
private/univariate2bivariate.m 200 should this be supported
private/univariate2bivariate.m 227 this assumes dimord to be 'rpttap_…'
private/univariate2bivariate.m 237 hard coded
private/wizard_base.m 79 this does not work
private/wizard_base.m 82 this does not always work correctly
reference/fixme.txt · Last modified: 2011/09/12 12:17 (external edit)

You are here: startreferencefixme
This DokuWiki features an Anymorphic Webdesign theme, customised by Eelke Spaak and Stephen Whitmarsh.
www.chimeric.de Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0