Back to the main page.
Bug 1616 - Add dimord for every numerical field in datastructures
| Status | NEW |
| Reported | 2012-07-25 13:51:00 +0200 |
| Modified | 2017-12-06 15:34:59 +0100 |
| Product: | FieldTrip |
| Component: | core |
| Version: | unspecified |
| Hardware: | PC |
| Operating System: | Windows |
| Importance: | P3 normal |
| Assigned to: | |
| URL: | |
| Tags: | |
| Depends on: | |
| Blocks: | |
| See also: | http://bugzilla.fcdonders.nl/show_bug.cgi?id=2513 |
Boris Reuderink - 2012-07-25 13:51:24 +0200
During the FT meet we reopened discussion about defining a dimord for the different numerical fields. For example: .field .field_dimord, and *remove* the global dimord (think of backward compatability). First step: - inventorize where (and how) dimord is used - think of transparant mechanism for implementation (like ft_datatype*) This would help to prevent guessing and special cases in the code. Extra: - dims vs dim_ord - scales (.1, .2 .3), and units (sec), for dimensions in dim_ord. - labels -> sensors/channels?