Back to the main page.
Bug 1880 - ft_componentanalysis method fastica ignores maxNumIterations (and possibly other options)
| Status | CLOSED INVALID |
| Reported | 2012-12-11 10:29:00 +0100 |
| Modified | 2019-08-10 11:56:15 +0200 |
| Product: | FieldTrip |
| Component: | core |
| Version: | unspecified |
| Hardware: | PC |
| Operating System: | Windows |
| Importance: | P3 normal |
| Assigned to: | |
| URL: | |
| Tags: | |
| Depends on: | |
| Blocks: | |
| See also: |
Jörn M. Horschig - 2012-12-11 10:29:24 +0100
ft_componentanalysis documentation states that cfg.fastica.maxNumIterations can be used. I specify: cfg_ica = []; cfg_ica.method = 'fastica'; cfg.fastica.maxNumIterations = 100; comp = []; comp = ft_componentanalysis(cfg_ica, ieegdata); But then get: IC 6 (...) Component number 6 did not converge in 1000 iterations. It's an FT problem, because before calling fastica in ft_componenanalysis, cfg.fastica looks like this: K>> dbstack > In ft_componentanalysis at 445 In iEEG_highICA at 142 K>> cfg.fastica ans = numOfIC: 7 K>> dbup In workspace belonging to iEEG_highICA at 142 K>> cfg.fastica ans = maxNumIterations: 100
Jörn M. Horschig - 2012-12-11 10:31:32 +0100
ha, how stupid, user error :/