Thanks for the kind words, although I think that you somewhat overestimate my skills and the complexity of the problem.
Hi Again
My appreciation of the contribution you give goes beyond your skill set or your ability to address the problems complexity. That said, I am not the "bluntest knife in the draw" and yet *I* am not able to provide the level of expertise in the field that you are at this point, or
any level of expertise for that matter so I think you sell yourself a little short. Perhaps this can be attributed to your exposure to the problem and experience in dealing with the variables but that is outside of my viewpoint in this thread.
Regardless of the level of expertise required and how it was obtained currently in these forums you appear to be the most practiced at it and most importantly you are willing to offer your time and that expertise on a volunteer basis. I've had more than a couple of technical pass times over the years not even touching on professions, I've been a volunteer in all of them at one time or another at one level or another. I've also managed an online community somewhat larger than these for 14 years with it's various forums and users submitting captured data for analysis and all the other facets.
That makes me well aware of the value of people who step up and offer their services, you can never find enough of them and community demands and the tendency to take them for granted over time often lead them to burn out in the end, I did on more than one occasion. You fall into this category of "people who step up" and that is what is truly golden.
I do realise I may make you a little uncomfortable highlighting your input and for that I apologise, but I think it is a good thing to underscore to the community from time to time that which all of the "people who step up" bring with them and contribute and that it is not without personal cost.
You might want to check out
Flight Controller Data Analysis - DJI
It's pretty good. But, it doesn't address the difficulties that @sar104 referred to in this post
Thankyou BudWalker
Another worthwhile contribution, I may well of got there by myself in the end but now that's time I do not need to expend finding it and can now use evaluating it instead.... "people who step up"
My own take is that incident analysis is mostly about a mental picture of the drone systems, how they work
That as a certified commercial RePL I have, I'm sure many others do also.
what the data should look like, and what it means if the data is anomalous.
That as yet is a sense I have not had time to acquire to the degree needed.
IMHO a good way, perhaps the only way, to become proficient at this is to look in depth at a few incident analyses presented in this forum.
Total agreement with the addendum that one should always take any shortcut opportunity to learn from those who have already done so. We all have a life, family and other interests and responsibilities that make it desirable to minimise "time investment" to reach a goal.
but, it is dificult to say how much of it can really apply to dji set of available metrics.
That's one thing we need to ascertain.
specific section for that is in the 'dataflash logs' section of the interface, 'review a log'. that opens up a window with some pre-configured log graphs - mosy useful ones are vibration 3.3 review, velocity vs innovation, errors, etc.
Thankyou now paulatkin73. Every "heads up" along the way reduces the learning curve and research effort for the rest of us, once again "people who step" up no matter to what degree.
Perhaps I put too much emphasis on the technical know how and abilities required, although to be honest I don't think so. My main intention probably due to my past activities in online communities as mentioned above was to highlight the value of a "people who step up" and the opportunity for the rest of us to benefit even more from them when they are willing to freely share of their particular skill set. When you see someone say "I have been writing a guide" if you are wise you encourage steps for the benefit of all.
Since my previous post in this thread I have picked up the run times for MATLAB and spent a night over at a friends place who through working in rather esoteric and somewhat classified areas of drone applications is far more across the subject than I am. Over the obligatory Australian mateship ritual of "having a few beers" he has run me through "drift mapping 101" and that brings me full circle.
sar104 has taken the time out to develop a skill set that I admire and would like to at least try to acquire myself and I'm sure I'm not the only one. I'm likewise sure many of us could arrive at that point ourselves and get it "one piece at a time" as the man in black said but I'll take any push along towards the right direction I can get from those who have already made the journey.
It's been my experience that it will only be once you become proficient with the tools and techniques required for the job that you can then as BudWalker rightly suggests "look in depth at a few incident analyses presented in this forum" with full appreciation.
sar104, it's fully accepted that there is "no magic recipe to draw detailed conclusions from most flight logs, especially when they describe unusual events."as you put it. It was always going to about "Tools, Techniques and Practice/Experience". Your guide when completed and input from others like above can only help those motivated enough acquire the first two parts of that formula allowing them to build the last as they must by themselves. It'll be no different for me.
Once again, sorry for any discomfort engendered sar104, I did want to "shine the spotlight" a little, "Render unto Ceaser" as they say. I also apologise for the thread hijack, I do that sometimes sadly, probably a byproduct of overthinking. I do admit to a veiled attempt to encourage others to follow your example.
Perhaps at some time a subsection in the forums devoted to log and data analysis might be desirable. The owners/chief moderators will have to look at that.
Perhaps I should stop meddling, in this community I'm no one in particular (and quite happy to be that lol). I just can't abide with letting something that should be said left unsaid I suppose.
I'll shut up now.
Regards
Ari
