Back to the main page.
Bug 1711 - implement cfg.verbose option, together with ft_default.verbose
| Status | CLOSED DUPLICATE |
| Reported | 2012-09-13 10:50:00 +0200 |
| Modified | 2013-01-17 10:37:09 +0100 |
| Product: | FieldTrip |
| Component: | core |
| Version: | unspecified |
| Hardware: | All |
| Operating System: | All |
| Importance: | P3 enhancement |
| Assigned to: | Roemer van der Meij |
| URL: | |
| Tags: | |
| Depends on: | |
| Blocks: | |
| See also: |
Roemer van der Meij - 2012-09-13 10:50:26 +0200
Came up on the mailinglist again, though I think we discussed this before. Wouldn't be a bad idea. I couldn't find a bug immediately so I thought I'd make one for the sake of remembering it. Maybe start small with a cfg.verbose option in some main functions. Easiest way I can think of now would be to implement this in ft_progress. If we do, all disp/sprintf statements would have to go via ft_progress. Options could be: cfg.verbose = 'no' cfg.verbose = 'yes' cfg.verbose = 'very' Where for most functions 'yes' would equal 'very'. 'very' could be useful when putting together a pipeline or so, when as much fieldtrip-output as possible is desired (e.g. every iteration, more statistics of algorithms, etc).
Robert Oostenveld - 2012-09-14 12:38:03 +0200
this was previously discussed in the context of helping users to debug problems *** This bug has been marked as a duplicate of bug 1686 ***