Mac analysis: Graph scale

27 views
Skip to first unread message

zkdzegede....@gmail.com

unread,
Jan 12, 2016, 2:04:11 AM1/12/16
to AutosportLabs Beta Testers

Heatmap shows so I know it recognises the speed values, but the graph below is not showing. 


When I added other values like AccelX they showed on the graph but the min and max were not visible.  I'm guessing the graph is centered around 0 and speed is just really far up out of the view.

I was able to use the mouse to scale time but not the y values.





Brent Picasso

unread,
Jan 12, 2016, 3:10:29 AM1/12/16
to AutosportLabs Beta Testers
Hi - That's a pretty heat map!

The min / max values might be wrong in your log file, causing the scale to not show up correctly in the app.  See this topic on how to fix up your data. https://groups.google.com/forum/#!topic/autosportlabs-beta-testers/JuA2MKxdN-s

Could you also zip up your data and attach here so we can inspect it?

Thanks for testing the app!

-Brent



On Monday, January 11, 2016 at 11:04:11 PM UTC-8, zkdzegede....@gmail.com wrote:

Heatmap shows so I know it recognises the speed values, but the graph below is not showing. 


When I added other values like AccelX they showed on the graph but the min and max were not visible.  I'm guessing the graph is centered around 0 and speed is just really far up out of the view.

I was able to use the mouse to scale time but not the y values.





zkdzegede....@gmail.com

unread,
Jan 12, 2016, 4:08:15 AM1/12/16
to AutosportLabs Beta Testers
Zipped up
RC_24.LOG.zip

zkdzegede....@gmail.com

unread,
Jan 12, 2016, 4:10:00 AM1/12/16
to AutosportLabs Beta Testers
This was the data from before I setup the min/max values.  I just saw it had 6.0 as the max, my bad.  I guess autoscaling would be nice :-D 

Brent Picasso

unread,
Jan 12, 2016, 4:24:47 AM1/12/16
to zkdzegede....@gmail.com, AutosportLabs Beta Testers
Here's your data, fixed with a screenshot.

Yup, extending min/max (and making them editiable) is on the big list. https://github.com/autosportlabs/RaceCapture_App/issues?q=is%3Aopen+is%3Aissue+milestone%3A1.4.2

-Brent

--
You received this message because you are subscribed to the Google Groups "AutosportLabs Beta Testers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to autosportlabs-beta-...@googlegroups.com.
To post to this group, send email to autosportlabs...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/autosportlabs-beta-testers/d5a39782-bfd1-4f80-bbbc-95ba53a30845%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
Brent Picasso
Technology for Race and Street
RC_24_fixed.zip
new_map.png

Brent Picasso

unread,
Jan 13, 2016, 11:03:08 AM1/13/16
to AutosportLabs Beta Testers
Hi - you data file is interesting. Can we include it with our list of public data files to share?

-Brent

On Monday, January 11, 2016 at 11:04:11 PM UTC-8, zkdzegede....@gmail.com wrote:

imstimpy

unread,
Jan 19, 2016, 11:23:28 PM1/19/16
to AutosportLabs Beta Testers
I had a rather perplexing issue while at the track this weekend. The analysis software in OSX displayed my data properly while WIN drew a flat line; same log, different OS. The reason? The OSX database was initialized with laguna_seca.log where WIN system was initialized with tws_jon1.log. Upon closer inspection, all the min/max values are legit in the sample log but the min/max values are seemingly random in mine. I was never given the chance to set most values, though. The values I set in LUA did not set min/max correctly. I have also confirmed the datastore is re-using the channel meta from the first log used to create the datastore (this is likely more bad, than good).

From my LUA script:
vss_chan = addChannel("VSS", 10, 0, 0, 255, "MPH")

RCP FW was 2.8.6
tws_jon3.LOG

Brent Picasso

unread,
Jan 20, 2016, 12:06:42 AM1/20/16
to imstimpy, AutosportLabs Beta Testers
That sounds about expected. 

We're releasing a 2.8.7 firmware that will fix the metadata headers in files. In the meantime, you can correct the headers manually. You can also delete the datastore.sq3 file and do a re-import after fixing the metadata headers in your file.

in 1.5.0 we're also creating the ability to manipulate the min/max values in a variety of ways, including directly editing the values.  see #772 in the list for 1.5.0 here:

Thanks,
Brent

--
You received this message because you are subscribed to the Google Groups "AutosportLabs Beta Testers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to autosportlabs-beta-...@googlegroups.com.
To post to this group, send email to autosportlabs...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Brent Picasso

unread,
Jan 20, 2016, 9:40:14 PM1/20/16
to AutosportLabs Beta Testers, jus...@gmail.com
2.8.7 released, which addresses the file header issue : https://www.autosportlabs.com/2-8-7-firmware-available-for-mk2-mk1-development-has-moved/

-Brent


On Tuesday, January 19, 2016 at 9:06:42 PM UTC-8, Brent Picasso wrote:
That sounds about expected. 

We're releasing a 2.8.7 firmware that will fix the metadata headers in files. In the meantime, you can correct the headers manually. You can also delete the datastore.sq3 file and do a re-import after fixing the metadata headers in your file.

in 1.5.0 we're also creating the ability to manipulate the min/max values in a variety of ways, including directly editing the values.  see #772 in the list for 1.5.0 here:

Thanks,
Brent
On Tue, Jan 19, 2016 at 8:23 PM, imstimpy <jus...@gmail.com> wrote:
I had a rather perplexing issue while at the track this weekend. The analysis software in OSX displayed my data properly while WIN drew a flat line; same log, different OS. The reason? The OSX database was initialized with laguna_seca.log where WIN system was initialized with tws_jon1.log. Upon closer inspection, all the min/max values are legit in the sample log but the min/max values are seemingly random in mine. I was never given the chance to set most values, though. The values I set in LUA did not set min/max correctly. I have also confirmed the datastore is re-using the channel meta from the first log used to create the datastore (this is likely more bad, than good).

From my LUA script:
vss_chan = addChannel("VSS", 10, 0, 0, 255, "MPH")

RCP FW was 2.8.6

On Wednesday, January 13, 2016 at 10:03:08 AM UTC-6, Brent Picasso wrote:
Hi - you data file is interesting. Can we include it with our list of public data files to share?

-Brent

On Monday, January 11, 2016 at 11:04:11 PM UTC-8, zkdzegede....@gmail.com wrote:

Heatmap shows so I know it recognises the speed values, but the graph below is not showing. 


When I added other values like AccelX they showed on the graph but the min and max were not visible.  I'm guessing the graph is centered around 0 and speed is just really far up out of the view.

I was able to use the mouse to scale time but not the y values.





--
You received this message because you are subscribed to the Google Groups "AutosportLabs Beta Testers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to autosportlabs-beta-testers+unsub...@googlegroups.com.
To post to this group, send email to autosportlabs-beta-testers@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages