If basic sleeplog is provided with an odd number of columns or when coln1 is incorrectly specified such that an odd number of columns is read then GGIR may still run but treats wakeup as onset and onset as wakeup leading to cleaningcode 5. To address this I think an error should be generated when the number of columns after considering parameter coln1 is not even.
If basic sleeplog is provided with an odd number of columns or when
coln1
is incorrectly specified such that an odd number of columns is read then GGIR may still run but treats wakeup as onset and onset as wakeup leading to cleaningcode 5. To address this I think an error should be generated when the number of columns after considering parametercoln1
is not even.