How to separate the laps

[Cram3r95]

This application is quite good. Im wrapping your ldparser to get some variables of interest. As you have mentioned in previous issues, you dont need a temporal reference to synchronize the data, but just to know the frequency and then upsampel and downsample. Nevertheless, for one thing it is required:

How can I read the vertical red dashed lines which separate the different laps in the data? I want to avoid taking into account both In and Out laps.

On the other hand, it would be really helpful to explain something else about the different fields in your structures. Otherwise, it is difficult to follow-up.

Moreover, your field unit it is incorrect I think, because at least in my case, the field which is returning the unit is short name:

[gotzl]

Hi,
in case of the data I have (from racing games) there is always a .ldx file next to the .ld file which contains information on laps. Do you have those as well?
Handling of the .ldx files is not (yet) integrated into the ldparser. However, I've implemented decoding of this information in the acctelemetry project. I guess this code could as well be integrated into ldparser...

Moreover, your field unit it is incorrect I think, because at least in my case, the field which is returning the unit is short name:

Yes, could very well be wrong. I'll look into it.

[Cram3r95]

Yes, I have both the .ld and .ldx for the corresponding runs. I have seen your acctelemetery and actually it is calling the ldparser, and separating the information:

Exactly what I need to finish the preparation of my dataloader for deep learning. Again, it is wonderful to have these repos, but no proper documentation.

Given an .ld and .ldx, how could I get some channels (just the official laps, without In and Out)? Which specification files should I use?

For now, this is my code:

And it is working totally fine. But before resampling the output from 1000 Hz to 100 Hz, and the inputs from 20/25 to 100, first I want to remove unnecesary data.

How could I do it?

[gotzl]

The .ldx contains the start time of each lap. If you want to cut eg. the out lap, you've to take the first timestamp, iterate over each channel, take the channel frequency to calculate the number of samples in this first period and discard these samples.

In acctelemetry, I first resample all channels to the same frequency. Then, I add 'artifical channels', like the lap number. The samples in this channel is just a constant which increments whenever a new lap begins. Like this, I can get the data for a each lap with a 'group-by lap number'.

Hope this helps a bit. I don't have enough time to give a more elaborate answer right now ...

[Cram3r95]

Thanks a lot. This is an example of my .ldx file:

However, I cannot explicitly see the start and end of each lap. It is weird, but somewhere it must be contained in the .ld because when I visualize the data with MoTec, as I stated in previous messages, you can see the vertical red dashed lines.

[gotzl]

Ah, okay. Yes, it seems to get the lap information from somewhere else in your case. Maybe one of the other channels? If not, then it could also be in the meta data section in the LD file... Then we'd have to look for it with a hex editor.

[Cram3r95]

Nice my friend. Must not be difficult. In MoTec, it is reflected here:

So, somehow, with your parser, I should get this info.

[gotzl]

Hmm.. And what's the output of s.t. like print([x for x in ldData.fromfile(f)])?

[Cram3r95]

This represents the channels of your .ld, i.e. the data, but I cannot see how to get the specific lap times.

[gotzl]

Could you post the list as a text string instead of a picture? I'm hoping that one of the channels has the data you're looking for.

[Cram3r95]

['Beacon (Internal)', 'gLat_Motec', 'gLong_Motec', 'gVert_Motec', 'Drive Speed', 'Ground Speed', 'nGear', 'Lap Distance', '5V Aux Supply', '8V Aux Supply', 'Lap Time', 'Lap Gain/Loss Running', 'Lap Number', 'Running Lap Time', 'Lap Speed', 'Wheel Slip (Percent)', 'Laps Remaining', 'Lap Gain/Loss Final', 'Trip Distance', 'Odometer', 'Lap Time Predicted', 'CAN 1 Receive Error Count', 'CAN 1 Transmit Error Count', 'Lap Speed Predicted', 'CAN 3 Transmit Error Count', 'CAN 3 Receive Error Count', 'CAN 4 Transmit Error Count', 'CAN 4 Receive Error Count', 'CAN 1 Bus Utilization', 'CAN 3 Bus Utilization', 'CAN 4 Bus Utilization', 'Reference Lap Time', 'Fastest Lap Time', 'Dash Temp', 'Bat Volts Dash', 'rThrottle', 'rAPS', 'pBrakeF', 'pBrakeR', 'nABSswitch', 'BABSactivFA', 'BABSactivRA', 'BChronoswPBX', 'BPitentryGPSdetect', 'BChronosw', 'BABSactivFL', 'BABSactivFR', 'BABSactivRL', 'BABSactivRR', 'nLaptrigGPS', 'Tservo', 'nMappos', 'gLong', 'pClutch', 'uBatt', 'nTCstage', 'mFuelrem', 'Tint', 'pTireFL', 'pTireFR', 'pTireRL', 'pTireRR', 'xDamperFL', 'xDamperFR', 'xDamperRL', 'xDamperRR', 'BABSlampON', 'BABSlampON1', 'BJerk', 'nYaw', 'nLap', 'TtireFL', 'TtireFR', 'TtireRL', 'TtireRR', 'gVert', 'pServo', 'Tamb', 'nEngine', 'vCar', 'rThrottle2', 'vWheelFL', 'vWheelFR', 'vWheelRL', 'vWheelRR', 'nPPart L3B', 'nDPart L3B', 'nPPart L2B', 'nDPart L2B', 'nPPart L1B', 'nDPart L1B', 'adc aDpo Active L3B', 'nDpo Active L3B', 'adc aDpo3 L3B', 'adc aDpo2 L3B', 'adc aDpo1 L3B', 'hx aDpo L3B', 'adc aDpo Active L2B', 'nDpo Active L2B', 'adc aDpo3 L2B', 'adc aDpo2 L2B', 'adc aDpo1 L2B', 'hx aDpo L2B', 'adc aDpo Active L1B', 'nDpo Active L1B', 'adc aDpo3 L1B', 'adc aDpo2 L1B', 'adc aDpo1 L1B', 'hx aDpo L1B', 'hx aMpo L3B', 'adc aMpo Active L3B', 'nMpo Active L3B', 'adc aMpo3 L3B', 'adc aMpo2 L3B', 'adc aMpo1 L3B', 'adc iMotor2 L3B', 'adc iMotor1 L3B', 'iMotor2 L3B', 'iMotor1 L3B', 'pwm uOutput L3B', 'pwm uPreFilteredOutput L3B', 'BMotorDir L3B', 'hx aMpo L2B', 'adc aMpo Active L2B', 'nMpo Active L2B', 'adc aMpo3 L2B', 'adc aMpo2 L2B', 'adc aMpo1 L2B', 'adc iMotor2 L2B', 'adc iMotor1 L2B', 'iMotor2 L2B', 'iMotor1 L2B', 'pwm uOutput L2B', 'pwm uPreFilteredOutput L2B', 'BMotorDir L2B', 'hx aMpo L1B', 'adc aMpo Active L1B', 'nMpo Active L1B', 'adc aMpo3 L1B', 'adc aMpo2 L1B', 'adc aMpo1 L1B', 'adc iMotor2 L1B', 'adc iMotor1 L1B', 'iMotor2 L1B', 'iMotor1 L1B', 'pwm uOutput L1B', 'pwm uPreFilteredOutput L1B', 'BMotorDir L1B', 'Log Data Available', 'Log Time Remaining', 'CPU Usage', 'Device Up Time', 'USB Drive Status', 'mFuelcons lastlap', 'mFuelcons stint', 'cp nDampingActiveReturn FFB3', 'cp nPPartActiveReturn FFB3', 'cp nDampingActiveReturn FFB2', 'cp nPPartActiveReturn FFB2', 'cp nDampingActiveReturn FFB1', 'cp nPPartActiveReturn FFB1', 'cp nControlValue FFB3', 'cp nActiveReturn FFB3', 'cp nControlValue FFB2', 'cp nActiveReturn FFB2', 'cp nControlValue FFB1', 'cp nActiveReturn FFB1', 'adc iMotorExt2 FFB3', 'adc iMotorExt1 FFB3', 'adc iMotorExt2 FFB2', 'adc iMotorExt1 FFB2', 'adc iMotorExt2 FFB1', 'adc iMotorExt1 FFB1', 'cp nPPartFeedback FFB3', 'cp nIPartFeedback FFB3', 'cp nIPartFeedback FFB2', 'cp nPPartFeedback FFB2', 'cp nPPartFeedback FFB1', 'cp nIPartFeedback FFB1', 'cp iMotor FFB3', 'cp iDevice FFB3', 'cp iMotor FFB2', 'cp iDevice FFB2', 'cp iMotor FFB1', 'cp iDevice FFB1', 'adc iDeviceExt2 FFB3', 'adc iDeviceExt1 FFB3', 'adc iMotor2 FFB3', 'adc iMotor1 FFB3', 'iMotor2 FFB3', 'iMotor1 FFB3', 'pwm uPartiallyFilteredPWM FFB', 'pwm uOutput FFB3', 'pwm uPreFilteredOutput FFB3', 'BMotorDir FFB3', 'adc iDeviceExt2 FFB2', 'adc iDeviceExt1 FFB2', 'adc iMotor2 FFB2', 'adc iMotor1 FFB2', 'iMotor2 FFB2', 'iMotor1 FFB2', 'pwm uPartiallyFilteredPWM (2)', 'pwm uOutput FFB2', 'pwm uPreFilteredOutput FFB2', 'BMotorDir FFB2', 'adc iDeviceExt2 FFB1', 'adc iDeviceExt1 FFB1', 'adc iMotor2 FFB1', 'adc iMotor1 FFB1', 'iMotor2 FFB1', 'iMotor1 FFB1', 'pwm uPartiallyFilteredPWM (3)', 'pwm uOutput FFB1', 'pwm uPreFilteredOutput FFB1', 'BMotorDir FFB1', 'tSTR_ecu', 'tFFB_ecu', 'tSTR_motor', 'tFFB_motor', 'tResistance', 'GPS Sats Used', 'GPS Altitude', 'GPS Latitude', 'GPS Longitude', 'GPS Heading', 'GPS Time', 'GPS Date', 'GPS Speed', 'GPS Quality', 'GPS HDOP', 'GPS DOP', 'GPS VDOP', 'GPS Valid', 'CAN 2 Receive Error Count', 'CAN 2 Transmit Error Count', 'CAN 2 Bus Utilization', 'Comms RS232 Diag', 'gLat', 'nSWacon', 'BFuelLow', 'BFuelLow1', 'pOil', 'pWat', 'Tgear', 'Toil', 'Ticing', 'pAircond', 'pFuel', 'pGear', 'pGearair', 'iMainpump1', 'iMainpump2', 'iPrepump1', 'iPrepump2', 'qSteer', 'FToerodFL', 'FToerodFR', 'tPitstop', 'tmot', 'tStromsensor', 'overCurrent L3B', 'limiter L3B', 'limitedVoltage L3B', 'requestedVoltage L3B', 'overCurrent L2B', 'limiter L2B', 'limitedVoltage L2B', 'requestedVoltage L2B', 'limiter L1B', 'overCurrent L1B', 'limitedVoltage L1B', 'requestedVoltage L1B', 'DidSensorTimeout CCT', 'DidSensorImplaus CCT', 'DidSensorError CCT', 'DmpSensorTimeout CCT', 'DmpSensorImplaus CCT', 'DmpSensorError CCT', 'VsmSTRSafetyDriverTimeout CCT', 'VsmSteeringTimeout CCT', 'VsmSteeringSNV CCT', 'VsmSteeringSafetyDriverSNV CC', 'VsmGBSafetyDriverTimeout CCT', 'VsmGasBrakeTimeout CCT', 'VsmGasBrakeSNV CCT', 'VsmGasBrakeSafetyDriverSNV CC', 'ErrCodeGifTimeout CCT', 'ErrCodeGifOutput2 CCT', 'ErrCodeGifOutput1 CCT', 'ErrCodeGifInput2 CCT', 'ErrCodeGifInput1 CCT', 'ErrCodeGifComp2 3 CCT', 'ErrCodeGifComp1 3 CCT', 'ErrCodeGifComp1 2 CCT', 'DpoHandBrakeActive CCT', 'TadOperatingHoursOverdue CCT', 'TadOperating30DaysOverdue CCT', 'VsmNoReturnSpeed CCT', 'VsmNoReturnMiddle CCT', 'VdaSignalError CCT', 'TmpTooHigh CCT', 'TmpCriticalLow CCT', 'TmpCriticalHigh CCT', 'TadOperatingHoursExpired CCT', 'SvsNegSupply3 CCT', 'SvsNegSupply2 CCT', 'SvsNegSupply1 CCT', 'Svs5VSupply3 CCT', 'Svs5VSupply2 CCT', 'Svs5VSupply1 CCT', 'Svs33VSupply2 CCT', 'Svs33VSupply1 CCT', 'STMotWinding2Defective CCT', 'STMotWinding1Defective CCT', 'SchRuntime CCT', 'ResetAfterPowerUp CCT', 'PswWrongPassword CCT', 'MpoSensorPlaus CCT', 'MpoSensor3Defective CCT', 'MpoSensor2Defective CCT', 'MpoSensor1Defective CCT', 'MotOverCurrent CCT', 'MemRamError CCT', 'MemFlashError CCT', 'LogLogFull80 CCT', 'LogLogFull100 CCT', 'HBridgeError3 CCT', 'HBridgeError2 CCT', 'HBridgeError1 CCT', 'GBMotWinding2Defective CCT', 'GBMotWinding1Defective CCT', 'ErrGasinterface CCT', 'ErrDiagnosticTesterPresent CC', 'ErrCriticalError CCT', 'DsuSwitchOff CCT', 'DsuSensorPlaus CCT', 'DsuSensor3Defective CCT', 'DsuSensor2Defective CCT', 'DsuSensor1Defective CCT', 'DsuRemoved CCT', 'DsuPluggedAfterInit CCT', 'DpoSensorPlaus CCT', 'DpoSensor3Defective CCT', 'DpoSensor2Defective CCT', 'DpoSensor1Defective CCT', 'DiaSystemModuleError CCT', 'DiaBootError CCT', 'ChkNoEngagedSwitch CCT', 'ChkInconsistentSWVersions CCT', 'ChkEngingRun CCT', 'ChkConfigError CCT', 'BatRtcTooLow CCT', 'BatReserveTooLow CCT', 'BatReserveTooHigh CCT', 'BatMainTooLow CCT', 'BatMainTooHigh CCT', 'ArbCompareError2 CCT', 'ArbCompareError1 CCT', 'Log Memory Busy', 'Log Unloading', 'Logging Running']

I think these are the variables that you can see in "Channels", when you click on (1) Driver -> Channels:

I think with your functions from the other repo, it is possible to get the indices to get the start and end point of the laps.

[gotzl]

As I wrote in the previous comment, I create an 'artificial channel' with the current lap number.
To me it looks like you already have such a channel called 'Lap Number', or the 'nLap' channel. I would expect either one of these to contain the current lap number which you can use to create the indices ie whenever the value changes, a new lap begins. Similarly I would expect that 'Lap Distance' and 'Lap Time' start from 0 at these positions.
How the sector times are acquired I don't understand yet, though...

[Cram3r95]

I found this channel:

The signals are a little bit different (obviously the red one just represents the estimated value of the previous lap), but I understand the green signal is the lap time, and the other one a predicted value, even though there is a little bit of difference.

[Cram3r95]

My friend, I think that I found the signal which determines when a lap starts and ends. It is the beacon!

[Cram3r95]

Even with that, still not 100 % perfect. I have not identified any single signals which starts exactly when the vertical dashed red line does. It is strange. Even these beacon signals start the trigerring around 0.3 s after.

For example, this is "Running time" and "Beacon" (which acts as a trigerring):

Theoretically, these variables should start approximately around the vertical red dashed line. However, if we take a look:

It can be appreciated how it starts a little bit later.

[gotzl]

Hmm .. if it is also not among the channels, then this information has to be somewhere in the meta portion of the LD file. And we've to figure out how to find and decode it ^^. Can you share a sample file so that I can have a look?