From: Brian Gladman <brg@gladman.plus.com>
To: gsl-discuss@sourceware.org
Subject: Re: New routines for moving window statistics and filters
Date: Thu, 03 May 2018 10:36:00 -0000 [thread overview]
Message-ID: <a1b98d10-503f-073f-16cf-8e3d9e2425f2@gladman.plus.com> (raw)
In-Reply-To: <cea75970-86e7-0f72-cde7-848ab1c30077@colorado.edu>
On 02/05/2018 21:58, Patrick Alken wrote:
> Dear GSL users/developers,
>
> I have added a new module called gsl_movstat to GSL, which provides
> routines for moving window statistics (also called sliding window
> statistics, rolling statistics, running statistics, etc). Currently
> there is support for the following:
>
> moving mean, sum, min/max, variance/stddev, median, MAD, q-quantile
> range, Q_n, S_n
>
> I have also added some robust statistics routines to the gsl_stats area,
> including MAD, S_n, Q_n, Gastwirth and trimmed mean routines.
>
> Finally, I added a new module called gsl_filter, which currently
> contains a small number of common filtering routines. Currently, there
> is 1 linear filter (Gaussian smoothing) and 3 nonlinear filters (median,
> recursive median and impulse-rejection filters). I would like to
> eventually add other common filters (like Butterworth, Chebyshev) and
> possibly some routines to allow users to design their own filters with
> various criteria. This probably won't happen before the next release
> however.
>
> I have put everything into the master branch of the git with
> documentation. Any feedback/suggestions are welcome.
Hi Patrick,
I have been trying to add your new material to the Visual Studio build
of GSL and have found a very large number of errors with the Microsoft
compiler because of the assumption that a (void*) pointer points to an
object of length one. This is a non standard GCC extension.
One of many examples is on line 363 of median.c is:
state->minmax_state = vstate + sizeof(rmedian_state_t);
where vstate is defined as a (void*).
Although I could change all these (void*) to (char*), I am reluctant to
do this as it seems potentially very error prone.
Since GSL is (I believe) supposed to be written in 'standard C' I also
assume that the use of this GCC extension needs to be removed anyway.
I would hence be grateful for your advice on how to errors of this type.
best regards,
Brian Gladman
next prev parent reply other threads:[~2018-05-03 10:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 20:58 Patrick Alken
2018-05-03 10:36 ` Brian Gladman [this message]
2018-05-03 16:32 ` Patrick Alken
2018-05-03 20:08 ` Brian Gladman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a1b98d10-503f-073f-16cf-8e3d9e2425f2@gladman.plus.com \
--to=brg@gladman.plus.com \
--cc=gsl-discuss@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).