In PyAudioAnalysis > audioFeatureExtraction.py, there is stEnergyEntropy.

I can not understand what is the difference between 'Eol' and 'numpy.sum(sub_wins ** 2.)'

Plz let me know, the differece of two things( 'Eol' and 'numpy.sum(sub_wins ** 2.)')

Gamma correction is among the things most often done wrong by graphics programming novices. It's almost as bad as missing scene-related color transforms and linear volume sliders in the average video game. The code example in the readme should definitely mention to adjust.Gamma(img, 1/2.2) before doing any color mixing and adjust.Gamma(img, 2.2) before saving back to file (for as long as _bild

Acurite TXR, 5n1, 6045 and possibly others like the new Atlas weather station use parity in addition to checksums for integrity checking.

Currently the parity isn't verified, it's only looked at in verbose mode.

I've noticed I seem to get messages for non-existent devices from time to time. I suspect the message is mangled but the checksum still passes. The parity check in addition to the

I recently stumbled upon a bothering fact when using the pywt. When we use the default "symmetric" padding, the inverse wavelet transform is not the adjoint of the wavelet transform (and it's not the mathematical inverse of the wavelet transform, "only in one direction").

However, if you use the "zero" padding the adjoint property is verified (not the inverse property). And if you use the

I noticed that the docs for EvaluationStatus indicate that "reported" is an acceptable value, but the code for EvaluationStatus itself will not accept it.

obspy.core.event.Pick(time=time, waveform_id=wid, phase_hint="P", evaluation_status="reported")

returns

`ValueError: Setting attribute "evaluation_status" failed. Value "reported" could not be converted to type "Enum(["preliminary

I noticed since v0.0.10 release, GNSS-SDR supports Enabled extended coherent integration times. How can I do that? for example, if I am going to use coherent_integration_time_ms=5, besides the following configurations,

Acquisition_1C.coherent_integration_time_ms=5
Acquisition_1C.doppler_step=150

what else should I do?

And how can I configure the non-coherence integration coun

https://www.python.org/dev/peps/pep-0257/ lists some conventions how dostrings should be formatted. Most of the docstrings are compatible already, some are not.

Some are descriptive which violate the rule that a docstring should prescribe the function or method's effect as a command "Do this", "Return that", instead of "Returns the pathname ...".

In utils.random_fraction, I find the following code,

   # copy because shuffle works in place
    aux = copy.deepcopy(indx)

    # shuffle
    np.random.shuffle(indx)

    # select
    use = aux[:nb]
    unuse = aux[nb:]

About the shuffle, should it shuffle aux instead of index?

Consider using the Pint package for Units and Quantities

http://pint.readthedocs.org/en/0.6/

It seems well developed and tested. I've used it in several projects and cross-checked it with Wolfram Mathematica.

EDIT: it's also deeply integrated with numpy and scipy

Currently, it is sometimes obscure how latency, sustain, delta interact for samples and for synths. We need an overview and if necessary a fix in the implementation.

Community graph has a fixed epsilon-NN graph embedded in the construction of the classes.

We should replace 1e-3 by a parametrized value, potentially even depending on Nc and N.

In the Anomaly detection example a FeatureExtractor object is made with one of the properties being "ngrams", however "ngrams" is not on the list of properties in documentation.

Function parameters like time_samples and timestamps are used in multiple places varyingly, but they mean the same thing. Secondly, many distributions don't accept sampling frequency as an input. This needs to be clarified in all generators and processors.

• Also add corresponding unittest that runs an example of each
  This might help address issues such as in #3159