Home
Replace invalid UTF8 characters with replacement character
Thanks for the example, I see now what the problem is. I've accepted your patches. However, renamed the function to jsonheader(), and kept header() for backwards compatiblity. You can check demo2.py how to use it. Thanks for your contribution .
I see. That explains a little more. I checked the CFS specfication, and it does not indicate which locale string encoding is used. Is it always latin-1 or can it be some other string encoding ? Do you know which software was used to produce that file ? Based on your description, your new suggestion do not seem to be the "right" solution. Please provide the data, and the script. You can upload these here https://seafile.ist.ac.at/u/d/dbb0ca54e965484aad19/ Then, we can see what to do about this.
Lukas, thanks for your submission. I reviewed your suggestion. 1) according to the documentation [1], the function PyUnicode_DecodeUTF8() ",,,Create a Unicode object by decoding size bytes of the UTF-8 encoded string str..." that is the opposite of what you describe . https://docs.python.org/3/c-api/unicode.html#c.PyUnicode_DecodeUTF8 I'm afraid that your changes might break other platforms. 2) I can not reproduce the problem. I renamed a valid file such that its name contains umlaut, and the current...
Installation
Dear Freya, I believe I provided a fair and balanced assessment what the method can and can not provide. Whether this is "convincing", or in other words good enough for your purpose, is not up to me to decide.
For most pratical purposes, the method described in [1] as good as you can get. Make sure that the EOG channel are close to the eyes so that it does not pick up to much EEG activity. If you want to improve on that, you might try some subspace methods (ICA, PCA, etc.) but you need a large number of electrodes (at least 20, probably more) in order to identify a 3rd spatial EOG component. Concering the 1/f analysis, you should take into account that this might be conflated by other artifact sources,...