You read my mind... although perhaps not all of the code :) That is how it
is implemented in this PR, resetting it for single or double, not resetting
for short (see reset_dict).
On Jan 31, 2013 12:37 AM, "Alexandre Gramfort" <notifications@github.com>
wrote:

> In mne/fiff/meas_info.py:
>
> > @@ -322,7 +326,9 @@ def write_meas_info(fid, info, data_type=None):
> >          #   Scan numbers may have been messed up
> >          c = deepcopy(c)
> >          c['scanno'] = k + 1
> > -        c['range'] = 1.0
> > +        # XXX WHY WAS THIS SET?
> > +        if reset_range is True:
> > +            c['range'] = 1.0
>
> because it was done so in the matlab code:
>
>
> https://github.com/mne-tools/mne-matlab/blob/master/matlab/fiff_start_writing_raw.m#L156
>
> :)
>
> what do you think of automatically resetting the range if saving float32
> and not resetting it saving as short?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/mne-tools/mne-python/pull/419/files#r2840053>.
>
>