Back to the main page.
Bug 344 - ensure consistent handling of balancing throughout the code
| Status | CLOSED FIXED |
| Reported | 2010-12-24 14:21:00 +0100 |
| Modified | 2011-05-05 21:24:28 +0200 |
| Product: | FieldTrip |
| Component: | core |
| Version: | unspecified |
| Hardware: | PC |
| Operating System: | Mac OS |
| Importance: | P3 normal |
| Assigned to: | Jan-Mathijs Schoffelen |
| URL: | |
| Tags: | |
| Depends on: | |
| Blocks: | |
| See also: |
Jan-Mathijs Schoffelen - 2010-12-24 14:21:32 +0100
e.g. in ft_denoise_synthetic the balancing is handled in a principled way, i.e. grad.balance.xxx grad.balance.current = 'G3BR' or so. grad.tra etc investigate whether this can be consistently implemented also for 'ad-hoc' balancing, e.g. based on ft_denoise_pca, ft_componentanalysis/ft_rejectcomponent. what whould be checked is the possibility of sequentially applying montages and keeping track of this, in order to be able to invert them, if necessary
Jan-Mathijs Schoffelen - 2011-04-22 18:17:00 +0200
Hi Stephen, I made some updates to the handling of the different 'balancings' throughout the code. The issue with ft_megplanar on timelocked data after rejectcomponent should now work. Could you check whether the pipeline now works for you? (but please begin at the begin of the pipeline, i.e. with raw data).