cmello
cmello
About
- Username
- cmello
- Location
- United States
- Joined
- Visits
- 21
- Last Active
- Roles
- Member
- Location
- United States
Comments
-
I realize it's been quite some time since this thread was active; however, I find @wjcroft's responses particularly frustrating. It's clear that the original poster isn’t focused on making a 'fair' comparison—they simply want to determine if detecti…
-
A pull request was made; however, to get at fixes now, you can go to my fork: https://github.com/cmello418/OpenBCI_Python
-
Changes that will soon be available in the git repository: (1) Scale factor bug fix according to https://docs.openbci.com/Hardware/03-Cyton_Data_Format#cyton-data-format-binary-format (2) OpenBCIWiFi now applies the sample rate passed into the const…
-
Ok. Got things working. I'll follow up in a day or so, submit new code to repository, and close out issue 117. Two issues with wifi.py and one major problem on my side. All are fixed.
-
So, it looks like wifi.py is only half-baked, after all this time I thought I was doing something wrong. It was never fully tested, nor was it completed - and I think whoever left it is such a state should apologize - not for being half-assed (alth…
-
Yeah, I saw that, too; it's wrong. I have the latest wifi.py from the git repository, and it comes through as floats. It's been rather frustrating... outdated documentation, NO documentation in some cases, no good examples to go by (at least regar…
-
Ah! That could explain why I see similar-looking waves in the GUI when I turn off all filters... I must be applying my filters incorrectly in python, because I tried applying a bandpass before. Let me test this theory a bit more. If this is the …
-
wjcroft, you may be right. Values coming in from wifi.py are very small numbers - probably volts. I went into the parser.py code and turned "micro-volts" on in the raw parser's constructor. wifi.py does not allow you to do this directly, so by de…
-
@Billh: So, I experimented in several ways - one way is just dumping incoming data into a queue, and then displaying it. The other way is going from little endian to big endian. None of these made a difference. This is because it doesn't matter ho…
-
The data is coming over as floats from wifi.py. As I wrote in the original post, the data samples, as they come in, are in the form of .02388495, .00485866, etc. I think we might be chasing rabbits. I'll graph the data as it comes in, without sav…
-
Here is some additional info (const):num_channels=8 rec_size = (num_channels * 9) #9 (8-byte) doubles. 1: timestamp, 2-9: one sample for each channel win_seconds = 10 sample_rate = 250 dc_offset = 4.5 gain = 24 #sample+(offset*gain) win_size = sam…
-
I suppose I could be doing something stupid, but I doubt reading the file in incorrectly will produce nearly perfect graphs like I show on the screenshot. I read the data into memory the same way I write it out, little-endian. See code below, and …
-
This is not a serious piece of code yet. I'm just writing to a binary file irrespective of where the data comes, and just chose little-endian for the time being. Anyone wanting to read this file would simply have to know this. Ultimately, this fi…
-
Done. Thank you!
-
In case it's helpful, here are a couple of simple routines I'm using to initiate and handle wifi streaming. Note that wifi_init() is called on a background thread, and I'm not concerned with skipped samples at the moment - it works well for the mos…