You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 23, 2024. It is now read-only.
If youll notice, I have printed the length to verify that the length of the Y-axis data is the same as the X(time) axis data. it prints 482980 482980 so they are the same.
If I use a pixel width per second of 4 (like in the example above) everything comes out ok, like this example file: (sorry, GH will not accept the file, and it is about 15mb)
sorry for the confusing title, but I have a strange situation where I am setting the width by the number of data points I have...
I have 30 reading from an accelerometer every second so I am making each second of data 4 pixels wide (I believe)
Here is the code that I am using:
If youll notice, I have printed the length to verify that the length of the Y-axis data is the same as the X(time) axis data. it prints
482980 482980
so they are the same.If I use a pixel width per second of 4 (like in the example above) everything comes out ok, like this example file: (sorry, GH will not accept the file, and it is about 15mb)
http://s000.tinyupload.com/index.php?file_id=25360982963139220109
but if I change the number to 8 or 16 which is where I want it, the time axis stops at a certain point.
http://s000.tinyupload.com/index.php?file_id=02149796522295593801
The text was updated successfully, but these errors were encountered: