(only used in post-precessing for determining max. amplitudes)

by constructing a custom taperd window (more smooth at nyquist than the previously used tapered cosine)

----
Also: one implementation to remove the Gibbs Phenomenon. But will not be useful here since the signal will be padded with zeros --> not sufficient --> commented out
Source: http://ieeexplore.ieee.org/document/902128

works really great!

Sources of inspiration:
https://www.dsprelated.com/showthread/comp.dsp/15995-1.php
http://ieeexplore.ieee.org/document/1450934/

Since we are in the frequency domain anyway, make direct use of it's advantages (and speed up)

--> new config setting: config.FFT_filt

e.g.:
 - optimizing the interval of the adaptive-interval reate decay plot - to include remaining events in last bin
 - various fixes
 - beautifications

GMT scripts: new theme: Basel with pressure data, but no histogram + fixes
SQL script: output publicid as eventid in first column

make it identical to non-mpi version

This allow the application to resume the processing if something went wrong

- using statsmodels for regression
     --> better statistical analysis
     --> enable Weighted LS (if desired)
            (plotted by scaling scatter plot size)
- plotting confidence + prediction intervals
- plot a line with slope = 1
- improve residual plot

- take binning as argument
- visualize non-cumulative bins as bar histogram(s)
- proper adjustment of non-cumulative bins

- if variant=='adaptive-interval', report about last (incomplete rate interval)

 - more beautiful:
    - label doesn't overlap with waveform anymore
    - use transparencies
- revamp setting of channel name
- memory improvement
- misc fixes

 - plot blubbles correctly at the borders using gmtselect
 - one more time range category: "one month to 6 months"
 - misc fixes

 - revamped FDSN settings
 - set FLOAT32 encoding correctly
 - revamped other/plot_waveform.py
 - update MPI readme

... which means that the config instance got smarter!

Now making use of station meta:
1. config.load_station_info(): loads all available channels and their infos
   (sampling rate, active period, channel name, etc.)
     - either from FDSN, or from file if specified
2. config.set_channels() to set preferred channel group ... OR let it determine
   automatically with '*' (i.e. auto-select the channel group with the highest
   sampling rate - per active period)
3. config.set_resampling() to specify the ultimate (re)sampling rate. Either
   automatically or manually. Many outcomes are possible, which might depend on
   the actual case and the set upper BP filter limit. Esp. when the sampling rate
   changes over time, it tries to solve certain issues by making compromises;
   7 cases are implemented (for certain periods under certain circumstances,
   it might result into UPSAMPLING).
   It always reports about the taken action and warns in one case (if BP limit
   is not appropriate for any period).

All of these steps report the available/remaining channel groups to give the user
an overview of the automatic (or his/her) actions.

As a consequence, reorganized Setup class (and thus config instance)
 - e.g. no 'channel' parameter anymore since may vary in time.
   The channel at a certain time can be determined with
       config.get_channels_at_time()  
         --> made use and replaced old style throughout the project
 - NEW: config.get_sensitivity_at_time()
 - NEW: config.select_fastest_approach() (moved from TM.utils module)

allow upsampling in waveform_processing if resample parameter differs from the waveform stats

+ other minor things in TM.waveformops

Fixed: correctly set length of IFFT size: make dependent on FFT size (again)
       ... to not strech the resampled signal!

New:
 - case separation:
    1. if factor is an integer, resampling can be speed up for BOTH FFT and IFFT
       (optimized by 5-smooth number length padding)
    2. if factor is non-integer, optimize the longer signal (input for downsampling)
 - also consider UPsampling - the above optimization applies as well:
    1. optimize both FFT and IFFT length with optimal padding
    2. if factor is non-integer, optimize the longer signal (the output)
 - use pyfftw for non-integer resampling to not get stuck infinitely
 
 - for the future: might woth exploring 'scipy.signal.resample_poly()'

... to allow ANY resampling factor (even non-integer).

tl;dr: resampling is now a lot faster than before.

How did I advance:

1. I split the _process_mask() function into two separate  functions
   (one for resampling, one for extending the chunks)

2. I updated my mask resampling approach.
Idea: instead of
       mask[::factor]
now do :
       np.interp(np.linspace(0, old_len, new_len), range(old_len), mask)
Quite slow.

3. Discovered my old lines of code that made use of obspy's .merge(fill_value=None)
   function to generate a resampled mask (& merged trace) right away. But this
   approach seemed slower than mine before.
   While reviewing the _waveform_processing_trace() function, I reorganized it 
   and made it more compact.
   
4. All in all, I compared speeds again and it's considerably FASTER now!