Identify the .tlog files that were from an actual flight, not just the bench

[iskess]

I spend a too much time digging through .tlog files trying to weed out the useless ones and locate the ones from an actual flight. Since I am frequently bench testing, I generate far more tlogs than I need.
Is there a way that the names of the .tlog files can somehow be annotated based on whether the APM actually flew? I'll let you guys decide the best triggers since they are likely to be different for Copters and Planes.
What if every .tlog file name included the total distance traveled and highest altitude reached. It might look like this:
2013-08-22 12-23-21 1200m125m.tlog
This flight's trip distance was 1200 meters, and the max altitude achieved was 125 meters.
This is just an idea, perhaps others have better ideas of what data to include in the file names to help identify the logs we need.

[meee1]

this is a chicken and egg issue. as the logs filename is create as you connect.

[foobarbecue]

I've been thinking for a long time that we need some form of note taking integrated into mission planner. I was mostly thinking about having a box where you could put comments in when you download dataflash logs, but there could also be a box where you put notes for the current telemetered data. I'm afraid there may not be a good way to store notes in the existing .tlog format... the dataflash logs are self-documenting so seems like it should be OK

[iskess]

Ok, so changing the file names won't work. What about a small program that acts as a log browser. It accesses all that logs and extracts certain key pieces of information from them. Then you can search and sort your logs with this data. Sort of like what metadata or ID3 tags do for photo and music files. There could be a place for the notes that @footbarbecue requested above.

[meee1]

check out logindex. control-f