Leaderboard

Hooovahh: LAVA/NI EDIT: Also I don't know how I feel about coming out of the closet...on LAVA that is.

crelf: LAVA / NIDevZone

Or Shift + right click in an empty area to bring up the palette and Shift + Tab to go back to the auto-tool.

Kudos, Ben! Oh wait, wrong forum... -Scott

I love the Lounge. Congrats, Ben.

So how's all the climate change workin' out for ya? Actually, I put little stock in brutal winters when it comes to "climage change". It just might be a brutal winter. I remember winter of 2003 being very mild. My family and I taking a walk in 50 degree weather on Christmas Day. That's unheard of. And the last two winters here in MI have been brutal. Cold and lots of snow. This winter has been a little cold and very dry. I'm not complaining. Drive one rush hour in the snow with the Motor City nutcases and I think you would understand. I feel bad for my east coast and midwest friends (You and Ben off the top of my head) and my folks and daughter got hit pretty hard and often down in Ohio for the last couple of weeks. But I've been getting a real kick out of the fact that DC was SHUT DOWN for a week and all those politicians had to deal with all that snow. If DC is shut down they can't do any harm. God has a sense of humor.

Can you change the format of your data? Strings aren't that efficient, and CAN packets are fixed-size. You could convert to a cluster of numeric values, where the first element is the ID. Then, one route would be to use that ID as an index into an array, where each element of the array contains a cluster that contains an array of all data found for that ID. Ideally you would pre-allocate each array, since one reason your example is slow is the use of build array in your loop. What output do you actually need? Instead of moving your CAN data around, you could build arrays of indices into the original data, one per ID. This would give you a quick way to retrieve all the data for one ID without making a large number of copies. I've attached a quickly-written sample that demonstrates this, then uses the generated array of indices to extract the data into separate arrays for each node. Oops, forgot the attachment - and the "Use Full Editor" button doesn't seem to be working, so I couldn't attach it to the previous post. Sorting array-1.vi