When you are properly "provoked" with questions; you give phenomenally good and easy to understand answers!
Just the kind of answers, written in a way that suits laymen and is easy to understand.
This is exactly the style you should use when writing books.
Because with your two explanatory posts; I learned more easily and quickly than if I had read 200 posts by other "experts" or some highly technical book written by someone (nerd) and aimed at people like him.
I think you were born to be a good teacher. You just need to adapt your narrative to the wider population.
To get out of the box of a strict techno-nerd (I don't think you are one, but there are plenty of them around us).
I mean this honestly and I'm very serious this time, I'm not kidding. Use that gift of yours and this suggestion of mine and you will write the best books.
I've never delved too much into the details of PI detectors. And now in a couple of posts I have learned a lot of what I was interested in.
Admittedly, it would be too ambitious to say now that everything is clear to me, of course it is not.
But I finally understood some things and now I understand some methods, processes and techniques better.
Further... let me tell you what I would like to see explained in more detail,
not so much from the theory side; but from the side of practical performance.
"...Their curvatures are different. Iron targets exhibit a collapsing B-H curve response, which also looks different. If you grab a minimum of 3 points then you can distinguish these curves..."
That process will happen mostly in the processor code.
Well, you can answer me by giving an example of program "filters", procedures and functions that will do it. But that's not the point.
It won't mean much to me at this point, later maybe, probably will do, once I figure out my development&prototyping system and start dealing with code solutions.
Imagine that you have to do the same task from your quoted text in a completely analog technique, using opamps and cmos chips and explain it that way.
Thanks in advance!
Just the kind of answers, written in a way that suits laymen and is easy to understand.
This is exactly the style you should use when writing books.
Because with your two explanatory posts; I learned more easily and quickly than if I had read 200 posts by other "experts" or some highly technical book written by someone (nerd) and aimed at people like him.
I think you were born to be a good teacher. You just need to adapt your narrative to the wider population.
To get out of the box of a strict techno-nerd (I don't think you are one, but there are plenty of them around us).
I mean this honestly and I'm very serious this time, I'm not kidding. Use that gift of yours and this suggestion of mine and you will write the best books.
I've never delved too much into the details of PI detectors. And now in a couple of posts I have learned a lot of what I was interested in.
Admittedly, it would be too ambitious to say now that everything is clear to me, of course it is not.
But I finally understood some things and now I understand some methods, processes and techniques better.
Further... let me tell you what I would like to see explained in more detail,
not so much from the theory side; but from the side of practical performance.
"...Their curvatures are different. Iron targets exhibit a collapsing B-H curve response, which also looks different. If you grab a minimum of 3 points then you can distinguish these curves..."
That process will happen mostly in the processor code.
Well, you can answer me by giving an example of program "filters", procedures and functions that will do it. But that's not the point.
It won't mean much to me at this point, later maybe, probably will do, once I figure out my development&prototyping system and start dealing with code solutions.
Imagine that you have to do the same task from your quoted text in a completely analog technique, using opamps and cmos chips and explain it that way.
Thanks in advance!

Comment