|Anonymous | Login | Signup for a new account||2017-03-29 03:26 UTC|
|Main | My View | View Issues | Roadmap | Repositories|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000833||OLV||General Features||public||2013-03-13 13:00||2013-03-13 13:36|
|Target Version||0.0.3||Fixed in Version|
|Summary||0000833: MegaSquirt and Adaptronic CSV data logs contain non-numeric data, and we don't handle it well.|
|Description||Another user and I separately encountered the same issue last night while attempting to load two different logs (one from MegaSquirt and one from Adaptronic).|
When attempting to open the log, the log silently fails to open.
This seems to be due to non-numeric data that is present in the logs. Once removed, they opened fine.
Example of non-numeric data:
|Tags||No tags attached.|
We have four options IMO. Possibly moving from one solution to another as dev time permits.
1) We can detect the issue and reject loading the log with a notice to the user.
2) We can load the log but ignore the numeric data and notify the user of this.
3) We can dynamically convert the non-numeric data to numeric data and notify the user of the change.
4) We can update OLV to handle non-numeric data properly, somehow.
|We can add a ms specific log parser, too. It would be legitimate to convert YES to 1 and NO to 0 in that.|
|However it should currently fail, and isn't. That should be addressed too.|
|Copyright © 2000 - 2011 MantisBT Group|