Back to the main page.
Bug 1045 - add ft_checkconfig option: forbiddenval or unusedval
Status | CLOSED FIXED |
Reported | 2011-10-17 11:50:00 +0200 |
Modified | 2012-02-03 22:09:18 +0100 |
Product: | FieldTrip |
Component: | core |
Version: | unspecified |
Hardware: | PC |
Operating System: | Windows |
Importance: | P4 enhancement |
Assigned to: | Eelke Spaak |
URL: | |
Tags: | |
Depends on: | |
Blocks: | |
See also: |
Roemer van der Meij - 2011-10-17 11:50:36 +0200
In some situations it is handy to warn/error when an option is used that has no effect, when you kinda expect it to. Example: statistics_montecarlo has cfg.correctial. This can be 'tail', 'prob' and 'no'. 'yes' is not an option, even though it is easily expected at the user level.
Boris Reuderink - 2011-11-17 10:46:48 +0100
Changed the status of bugs without a specific owner to UNCONFIRMED. I'll try to replicate these bugs (potentially involving the submitter), and change confirmed bugs to NEW. Boris
Boris Reuderink - 2012-01-03 14:37:23 +0100
Sounds like a sensible thing to do, confirmed.
Jan-Mathijs Schoffelen - 2012-01-27 08:46:11 +0100
assigned bug to get all bugs lined up before the grand bug binge
Eelke Spaak - 2012-01-27 08:50:42 +0100
Suggestion: make an option 'allowedval' instead. In the case of statistics_montecarlo, it makes more sense to specify that only tail/prob/no is allowed. If the only forbidden value=yes, then the user might still specify cfg.correcttail = 'yesplease' or something.