[Eeglablist] nfreqs / padratio warning when running newtimef
Ramón Martinez
nucleuscub at gmail.com
Wed Aug 20 11:25:13 PDT 2014
Hi Oman,
Thanks for reporting this issue. Yep, you are right, and this is the way
the newtimef function actually works, when 'nfreq's ' is provided it
should use that number of output frequencies and not the one defined by
using the 'padratio' option. We've fixed this message.
You can find the function with the fix here:
https://sccn.ucsd.edu/svn/software/eeglab/functions/timefreqfunc/newtimef.m
Thanks,
Ramon
On Wed, Aug 20, 2014 at 9:53 AM, Omar Mian <omian88 at gmail.com> wrote:
> Hi,
>
> When using newtimef without the nfreqs parameter, the following warning
> gets printed to the workspace:
>
> Warning: 'nfreqs' input overwrite 'padratio'
>
> However, when using newtimef with the nfreqs parameter, the warning is not
> present.
>
> Shouldn't this happen the other way around (warning generated when nfreqs
> is used)?
>
> Omar
>
> _______________________________________________
> Eeglablist page: http://sccn.ucsd.edu/eeglab/eeglabmail.html
> To unsubscribe, send an empty email to
> eeglablist-unsubscribe at sccn.ucsd.edu
> For digest mode, send an email with the subject "set digest mime" to
> eeglablist-request at sccn.ucsd.edu
>
--
_____________________________________________________
Ramon Martinez-Cancino
Swartz Center for Computational Neuroscience
Institute for Neural Computation, University of California San Diego
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sccn.ucsd.edu/pipermail/eeglablist/attachments/20140820/5a22feea/attachment.html>
More information about the eeglablist
mailing list