Reply by Rune Allnor June 17, 20092009-06-17
On 17 Jun, 00:35, Junoexpress <MTBrenne...@gmail.com> wrote:
> On Jun 16, 4:44&#4294967295;pm, Rune Allnor <all...@tele.ntnu.no> wrote: > > > > > > > On 16 Jun, 22:22, Junoexpress <MTBrenne...@gmail.com> wrote: > > > > On Jun 16, 4:32&#4294967295;am, Rune Allnor <all...@tele.ntnu.no> wrote: > > > > > If you consider this from a math point of view, the basic fact is that > > > > > the notion of a "signal subspace" and a "noise subspace" are fiction. > > > > > There is a lot about this simple picture that from a mathematical > > > > > point of view is not well understood, and probably should be > > > > > investigated more. > > > > > No, there isn't. The terms are well-defined, the maths simple. > > > > As long as one is comfortable with N-dimensional complex-valued > > > > vector spaces. But those are just a matter of familiarization, > > > > like i = sqrt(-1). A big hurdle for the newbie, second nature > > > > to the somewhat more experienced. > > > > I doubt it. I'm a PhD in math and I know from my experience that there > > > is a fair amount of algebraic geometry involved in understanding array > > > manifolds. I've corrected the errors of many engineers who don't > > > understand what a complex Steifel manifolds (or even a manifold for > > > that matter), let alone its topology, so I know this from experience > > > to be the case. > > > Still, you don't undrestand the trivial basics of vector spaces. > > > > > If your clients hire me to review your system after a > > > > failure, I will waste no time in suggest you might be > > > > guilty of professional misconduct or fraud, if I find > > > > you used MUSIC and only assumed (as opposed to ensured) > > > > that the D < P. > > > > You have to be very clear what the limitations of your method are. I > > > don't know your background, but I don't know any professionals who > > > don't spell these type of things out up front. > > > You claim to be a professional. You actively disregard > > precise and clear warnings about trivial pathologies > > of the method you claim to build a business on. > > > That's gross professional misconduct at the best of times, > > and pretty close to fraud. > > > Rune > > I've made no "claims", as my standard disclaimer clearly shows: > > STANDARD DISCLAIMER
You might want to be very careful about how you apporach the business side of your activities. Legal details probably differ from location to location, but at least in my neck of the woods, you approach 'fraud' in the legal sense when 1) Money change hands. 2) There is a certain discrepancy between what the user/buyer *thinks* he gets and what he *actually* gets. There are also quite strict damage compensation clauses, where the manufacturer (or a representative, such as importer or retail outlet) of a product is held legally responsible for damages that are caused by the product. Do note that this has nothing to do with unsafe or uncorrect use of a product: The manufacurer or his representative is held responsible for damages, no matter what. A disclaimer doesn't change any of this, as local banks are in the process of finding out. Over the past few years they sold 'financial products' to customers, where the customers took up loans, at some interest rate, and placed the money in the market, at some other interst rate. Details in the press are a bit vague as to exactly what was sold, but problems arose when interest rates on the loans exceeded profits from the market. Lots of people lost hundreds of thousands of dollars on this, and sued the banks. There are several legal processes at work over these questions right now, so the end result remains to be seen. However, you might want to note that - The banks issue standard disclaimers no matter what product they sell their customers - The product in question was based on the *assumption* that the financial market would not collapse - The courts hold product brokers responsible for informing the users 'sufficiently well' about the products, their benefits, and particularly the risks. Again, the Norwegian legal system probably differs in the details from systems in other coutries. The main principles should be the same, throughout the western world. Rune
Reply by Rune Allnor June 17, 20092009-06-17
On 17 Jun, 07:56, Junoexpress <MTBrenne...@gmail.com> wrote:
> On Jun 16, 9:33&#4294967295;pm, dbd <d...@ieee.org> wrote: > > > On Jun 16, 5:27 pm, Junoexpress <MTBrenne...@gmail.com> wrote: > > > Ok, so you are a mathematician without applications experience. > > > Dale B. Dalrymple > > I develop the theory you apply. &#4294967295; ;>)
You might think so, but the fact of the matter is that you don't understand the theory that has been standard in the DSP community for 35 years (It is common to trace MUSIC-type methods to Pisarenko's 1973 paper.) Not only have this theory been around for decades, it is so simple that it can be explained to a reasonably bright 12-year-old without much difficulty, using only a piece of paper and a couple of sticks. Rune
Reply by Junoexpress June 17, 20092009-06-17
On Jun 16, 9:33&#4294967295;pm, dbd <d...@ieee.org> wrote:
> On Jun 16, 5:27 pm, Junoexpress <MTBrenne...@gmail.com> wrote: > > Ok, so you are a mathematician without applications experience. > > Dale B. Dalrymple
I develop the theory you apply. ;>)
Reply by dbd June 16, 20092009-06-16
On Jun 16, 5:27 pm, Junoexpress <MTBrenne...@gmail.com> wrote:
> On Jun 16, 5:49 pm, dbd <d...@ieee.org> wrote: > > > > > On Jun 15, 4:35 pm, Junoexpress <MTBrenne...@gmail.com> wrote: > > > > On Jun 14, 6:23 am, Rune Allnor <all...@tele.ntnu.no> wrote: > > ... > > > > ... If you don't > > > > believe me, just look around for yourself and try and find > > > > out how many real-world applications actually use these > > > > sorts of methods. > > > > > There aren't too many - I'm not aware of a single one. > > > > > Rune > > > > Good to hear: that's what keeps me in business. ;>) > > > > M > > > Are there any such systems that have been tested in use by the actual > > practitioners and remained in use after test? Or are you saying that > > it is your business to protect practitioners from such systems? > > > Dale B. Dalrymple > > I don't do "systems" (which is why I am so amused by this thread). I > solve math problems that scientists and engineers can't solve. > > Some of my work has been the basis for entire new fields, some of it > has remained a curiosity. But to tell the truth, I could care less > either way and I've enjoyed doing both equally well. I do what I do, > because I enjoy it, and I enjoy the challenge. > > Regards, > > Matt > > Matt
Ok, so you are a mathematician without applications experience. Dale B. Dalrymple
Reply by Junoexpress June 16, 20092009-06-16
On Jun 16, 5:49&#4294967295;pm, dbd <d...@ieee.org> wrote:
> On Jun 15, 4:35 pm, Junoexpress <MTBrenne...@gmail.com> wrote: > > > On Jun 14, 6:23 am, Rune Allnor <all...@tele.ntnu.no> wrote: > ... > > > ... &#4294967295; &#4294967295;If you don't > > > believe me, just look around for yourself and try and find > > > out how many real-world applications actually use these > > > sorts of methods. > > > > There aren't too many - I'm not aware of a single one. > > > > Rune > > > Good to hear: that's what keeps me in business. ;>) > > > M > > Are there any such systems that have been tested in use by the actual > practitioners and remained in use after test? Or are you saying that > it is your business to protect practitioners from such systems? > > Dale B. Dalrymple
I don't do "systems" (which is why I am so amused by this thread). I solve math problems that scientists and engineers can't solve. Some of my work has been the basis for entire new fields, some of it has remained a curiosity. But to tell the truth, I could care less either way and I've enjoyed doing both equally well. I do what I do, because I enjoy it, and I enjoy the challenge. Regards, Matt Matt
Reply by Junoexpress June 16, 20092009-06-16
On Jun 16, 4:44&#4294967295;pm, Rune Allnor <all...@tele.ntnu.no> wrote:
> On 16 Jun, 22:22, Junoexpress <MTBrenne...@gmail.com> wrote: > > > > > On Jun 16, 4:32&#4294967295;am, Rune Allnor <all...@tele.ntnu.no> wrote: > > > > If you consider this from a math point of view, the basic fact is that > > > > the notion of a "signal subspace" and a "noise subspace" are fiction. > > > > There is a lot about this simple picture that from a mathematical > > > > point of view is not well understood, and probably should be > > > > investigated more. > > > > No, there isn't. The terms are well-defined, the maths simple. > > > As long as one is comfortable with N-dimensional complex-valued > > > vector spaces. But those are just a matter of familiarization, > > > like i = sqrt(-1). A big hurdle for the newbie, second nature > > > to the somewhat more experienced. > > > I doubt it. I'm a PhD in math and I know from my experience that there > > is a fair amount of algebraic geometry involved in understanding array > > manifolds. I've corrected the errors of many engineers who don't > > understand what a complex Steifel manifolds (or even a manifold for > > that matter), let alone its topology, so I know this from experience > > to be the case. > > Still, you don't undrestand the trivial basics of vector spaces. > > > > If your clients hire me to review your system after a > > > failure, I will waste no time in suggest you might be > > > guilty of professional misconduct or fraud, if I find > > > you used MUSIC and only assumed (as opposed to ensured) > > > that the D < P. > > > You have to be very clear what the limitations of your method are. I > > don't know your background, but I don't know any professionals who > > don't spell these type of things out up front. > > You claim to be a professional. You actively disregard > precise and clear warnings about trivial pathologies > of the method you claim to build a business on. > > That's gross professional misconduct at the best of times, > and pretty close to fraud. > > Rune
I've made no "claims", as my standard disclaimer clearly shows: STANDARD DISCLAIMER This product is meant for educational purposes only. Any resemblance to real persons, living or dead is purely coincidental. This is work in progress and subject to change. Void where prohibited. Some assembly required. List each check separately by bank number. Batteries not included. Contents may settle during shipment. Use only as directed. COUNT YOUR CHANGE. No other warranty expressed or implied. Do not use while operating a motor vehicle or heavy equipment. Postage will be paid by addressee. Subject to regulatory approval. This is not an offer to sell securities. Apply only to affected area. May be too intense for some viewers. Do not stamp. Use other side for additional listings. For recreational use only. Do not disturb. All models over 18 years of age. Not recommended for children. Prerecorded for this time zone. Reproduction strictly prohibited. No solicitors. Shake well before using. No user-serviceable parts inside. For external use only. If condition worsens, discontinue use and consult a physician. Freshest if eaten before date on carton. Subject to change without notice. Times approximate. No substitutions. Simulated picture. Use for the prevention of disease only. No postage necessary if mailed in the United States. Please remain seated until the ride has come to a complete stop. Breaking seal constitutes acceptance of agreement. For off-road use only. As seen on TV. One size fits all. Many suitcases look alike. Contains a substantial amount of non-tobacco ingredients. Colors may, in time, fade. We have sent the forms which seem right for you. Slippery when wet. For office use only. Not affiliated with the American Red Cross. Drop in any mailbox. Edited for television. Keep cool; process promptly. No breakfast after 10 am. Post office will not deliver without postage. List was current at time of printing. Return to sender, no forwarding order on file, unable to forward. Not responsible for direct, indirect, incidental, or consequential damages resulting from any defect, error, or failure to perform. At participating locations only. Not the Beatles. Penalty for private use. See label for sequence. Substantial penalty for early withdrawal. Do not write below this line. Falling rock. Lost ticket pays maximum rate. Your canceled check is your receipt. Add toner. Place stamp here. Avoid contact with skin. Sanitized for your protection. Be sure each item is properly endorsed. Sign here without admitting guilt. Slightly higher west of the Mississippi. Employees and their families are not eligible. Beware of dog. Contestants have been briefed on some questions before the show. You must be present to win. No passes accepted for this engagement. No purchase necessary. Some restrictions apply. Limited time offer, call now to ensure prompt delivery. Celebrity voices impersonated. Processed at location stamped in code at top of carton. Shading within a garment may occur. Use only in a well-ventilated area. Keep away from fire or flames. Replace with same type. Approved for veterans. Keep out of reach of children. Booths for two or more. Check here if tax deductible. Some equipment shown is optional. Price does not include taxes. No Canadian coins. No alcohol, dogs, or horses. No anchovies unless otherwise specified. Restaurant package, not for resale. List at least two alternate dates. First pull up, then pull down. Call toll free number before digging. Take only as directed. Driver does not carry cash. Some of the trademarks mentioned in this product appear for identification purposes only. Objects in mirror may be closer than they appear. Record additional transactions on back of previous stub. Unix is a registered trademark of AT&T. Do not fold, spindle, or mutilate. No transfers issued until the bus comes to a complete stop. Package sold by weight, not volume. This page left intentionally blank. I just work here. Your mileage may vary. These materials have been prepared for informational purposes only and are not legal advice. Transmission of the information is not intended to create, and receipt does not constitute, an attorney-client relationship. Internet subscribers and online readers should not act upon this information without seeking professional counsel. Use at your own risk. All rights reserved. Close cover before striking. No bills over $20 after dark. Additional charges may apply. Customer voluntarily assumes all risks, known and unknown, of any injury, however caused, even if caused in whole or in part by the action, inaction, or negligence of any party, to the full extent allowed by California law. This supersedes all previous notices. The information contained in this transmission is attorney privileged and/or confidential information intended for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. " OK Rune, it's been a whole lotta fun, but I've had enough cloak and dagger bullshit for a while. Best Regards, M
Reply by dbd June 16, 20092009-06-16
On Jun 15, 4:35 pm, Junoexpress <MTBrenne...@gmail.com> wrote:
> On Jun 14, 6:23 am, Rune Allnor <all...@tele.ntnu.no> wrote:
...
> > ... If you don't > > believe me, just look around for yourself and try and find > > out how many real-world applications actually use these > > sorts of methods. > > > There aren't too many - I'm not aware of a single one. > > > Rune > > Good to hear: that's what keeps me in business. ;>) > > M
Are there any such systems that have been tested in use by the actual practitioners and remained in use after test? Or are you saying that it is your business to protect practitioners from such systems? Dale B. Dalrymple
Reply by Rune Allnor June 16, 20092009-06-16
On 16 Jun, 22:22, Junoexpress <MTBrenne...@gmail.com> wrote:
> On Jun 16, 4:32&#4294967295;am, Rune Allnor <all...@tele.ntnu.no> wrote:
> > > If you consider this from a math point of view, the basic fact is that > > > the notion of a "signal subspace" and a "noise subspace" are fiction. > > > There is a lot about this simple picture that from a mathematical > > > point of view is not well understood, and probably should be > > > investigated more. > > > No, there isn't. The terms are well-defined, the maths simple. > > As long as one is comfortable with N-dimensional complex-valued > > vector spaces. But those are just a matter of familiarization, > > like i = sqrt(-1). A big hurdle for the newbie, second nature > > to the somewhat more experienced. > > I doubt it. I'm a PhD in math and I know from my experience that there > is a fair amount of algebraic geometry involved in understanding array > manifolds. I've corrected the errors of many engineers who don't > understand what a complex Steifel manifolds (or even a manifold for > that matter), let alone its topology, so I know this from experience > to be the case.
Still, you don't undrestand the trivial basics of vector spaces.
> > If your clients hire me to review your system after a > > failure, I will waste no time in suggest you might be > > guilty of professional misconduct or fraud, if I find > > you used MUSIC and only assumed (as opposed to ensured) > > that the D < P. > > You have to be very clear what the limitations of your method are. I > don't know your background, but I don't know any professionals who > don't spell these type of things out up front.
You claim to be a professional. You actively disregard precise and clear warnings about trivial pathologies of the method you claim to build a business on. That's gross professional misconduct at the best of times, and pretty close to fraud. Rune
Reply by Junoexpress June 16, 20092009-06-16
On Jun 16, 4:32&#4294967295;am, Rune Allnor <all...@tele.ntnu.no> wrote:
> On 16 Jun, 01:35, Junoexpress <MTBrenne...@gmail.com> wrote: > > > > > On Jun 14, 6:23&#4294967295;am, Rune Allnor <all...@tele.ntnu.no> wrote: > > > > On 14 Jun, 05:30, Junoexpress <MTBrenne...@gmail.com> wrote: > > > > > On Jun 13, 4:00&#4294967295;pm, Rune Allnor <all...@tele.ntnu.no> wrote:> On 13 Jun, 21:33, junoexpress <MTBrenne...@gmail.com> wrote: > > > > > > > Hi, > > > > > > > In the literature, there is a common claim made that the performance > > > > > > of MUSIC for direction of arrival estimation (DOA) is affected when > > > > > > the wrong number of directional sources is assumed. There is no > > > > > > argument presented to support this claim, nor any references given, > > > > > > just the claim. > > > > > > The claims may or may not be true, depending on exactly > > > > > how &#4294967295;they are phrased. Do you have any pointers to where > > > > > such claims are made? > > > > > This claim is found in a good many papers on the topic of signal > > > > enumeration. Two that make the statement clearly are: > > > > 1) IEEE Trans Acc, Speech, and Signal Processing, vol. 38, no. 11, > > > > 1990 > > > > "On Information Theoretic Criteria...." by Wong, Zhang, Reilly, and > > > > Yip > > > > (see text after eqn 5 in article) > > > > 2) IEEE Trans Signal Processing, vol. 39, no. 8, 1991 > > > > "A Parametric Method for Determining the Number of Signals in Narrow- > > > > Band Direction Finding" > > > > by Wu and Fuhrman (see first paragraph) > > > > > > There are several causes for inaccuracies in the MUSIC-type > > > > > estimators. One is the SNR, others are related to wrong order > > > > > estimates, like if there in reality are 4 signals present, > > > > > but the order estimator only finds 3 of them. In such cases, > > > > > it is likely that at least some of the DoAs are off, either > > > > > because the SNR is low or the 'missing' signal lies very close > > > > > to one of the others. If the 'missing' signal has a significantly > > > > > smaller amplitude than the others, the remaining DoA estimates > > > > > might be accurate anyway. > > > > > Your line of reasoning is pretty much what makes me doubt this claim. > > > > A source that is missed, is most likely missed because its SNR is very > > > > small. > > > > Not necesarily. There can be any number of reasons why a > > > source is missed. Small SNR is just one of them. > > > > There is one aspect of order estimators you need to be > > > aware of: For AR models, order estimators are formally > > > are derived from statistical analyses of the reflection > > > coefficients that represent signal residuals during the > > > Levinson recursion. > > > > MUSIC can not be represented as a Levinson recursion, > > > it's based on eigenvector decompositions. So the *formal* > > > statistical analysis, which works on the reflection > > > coefficients, don't work with the eigenvalues. > > > > Now, this does *not* mean that oprder estimators do not > > > work with eigenvector decompositions - they do. It means > > > that one has bodged a tool to work in a context it was > > > not designed for. Which also goes a long way to explain > > > why order estimates might be off from time to time, with > > > no apparent reason. > > > If you consider this from a math point of view, the basic fact is that > > the notion of a "signal subspace" and a "noise subspace" are fiction. > > There is a lot about this simple picture that from a mathematical > > point of view is not well understood, and probably should be > > investigated more. > > No, there isn't. The terms are well-defined, the maths simple. > As long as one is comfortable with N-dimensional complex-valued > vector spaces. But those are just a matter of familiarization, > like i = sqrt(-1). A big hurdle for the newbie, second nature > to the somewhat more experienced. >
I doubt it. I'm a PhD in math and I know from my experience that there is a fair amount of algebraic geometry involved in understanding array manifolds. I've corrected the errors of many engineers who don't understand what a complex Steifel manifolds (or even a manifold for that matter), let alone its topology, so I know this from experience to be the case.
> > > > The components of the stronger sources on the evr that gets > > > > dropped from the signal subspace and gets put into the noise sub-space > > > > cannot be that large, so when you run say Spectral MUSIC, > > > > Spectral MUSIC is...? If you are talking about the MUSIC > > > pseudo spectrum, keep in mind that there is no information > > > about the signal spectrum encoded in the pseudo spectrum. > > > There are two basic types of MUSIC: "spectral" MUSIC (which is what > > was originally proposed by Schmidt) and "ROOT" MUSIC (which is a > > simple extension of spectral MUSIC that works a bit better). > > Estimates about the source AOAs can be made (if again we make a boat- > > load full of assumptions ;>)) from both. > > MUSIC is Scmhidt's original method that in principle works > with arrays of any geometry. The Root MUSIC is an ad-hoc > adaption for the case of Uniform Linear Arrays. It might have > been an interesting alternative, were it not for other methods > that addressed the ULA directly, which turned out to be far > more computationally efficient. > > > > > > > the location > > > > where the reciprocal of the projection of the steering vectors onto > > > > the noise subspace has its max value should not change appreciably. > > > > Remember, you are working D-manifolds in an P-dimensional > > > complex-valued vector space. Don't expect your intuition > > > to be of the best help... > > > > > > No easy answers. > > > > > > > Does this reasoning sound like the justification for the claim about > > > > > > MUSIC I presented, or is there something else I am missing? > > > > > > Yes, there is. > > > > > > MUSIC-type estimators (meaning all estimators which > > > > > implicitly or explicitly use a covariance matrix of > > > > > order P to estimate the parameters of D signals) *fail* > > > > > *unconditionally* when D >=P. > > > > > The noise in the system (i.e. AWGN in the channels) will guarantee > > > > that the covariance matrix has full rank. This condition is certainly > > > > satisfied in all of the professional treatments of MUSIC you see in > > > > the lit. > > > > You need to think one step further: The basis for the > > > noise subspace needs to be of rank at least 1 for MUSIC > > > and friends to work. Once you have a signal that contains > > > P (or P/2) or more sinusoidals, this no longer holds and > > > MUSIC fails unconditionally. > > > > > I am assuming the are are less sources than antennas here. > > > > You can certainly do that for academic purposes. That's > > > a very stupid thing to do in the real world. > > > Not really. In many applications the cost of the array alone prohibits > > you from using a large array size and you have to make that > > assumption. > > That's the blunder you and everybody else who try to use these > methods make: The fact that you assume that the sensor will > never see more than a small number of sources, does not > prevent that from happening. > > So when (not if) the case of D >=P happens, the system breaks > down. Your clients are left in a void where nothing works, and > you don't understand why. > > Before you try and make a living out of this (your lack > of historical knowledge and the statement above are > certain give-aways), take some time to think through the > legal obligations that are activated once you charge > somebody for your advice or systems: You might very well > be liable to damage compensations for any glitch or problem > that are caused by your advice or system. > > If your clients hire me to review your system after a > failure, I will waste no time in suggest you might be > guilty of professional misconduct or fraud, if I find > you used MUSIC and only assumed (as opposed to ensured) > that the D < P. >
You have to be very clear what the limitations of your method are. I don't know your background, but I don't know any professionals who don't spell these type of things out up front.
> > > > > > And there are other problems of course that could arise (such as the > > > > presence of correlated sources, or an array whose antenna spacings are > > > > greater than half a wavelength, or signals which are wide-band, etc > > > > which will also act to screw up MUSIC), > > > > Most of those can be handled. Tedious, but not very > > > difficult. > > > > > but neither I, nor the > > > > articles to which I am referring, assume any of these conditions hold. > > > > > > If you want to, repeat the excercise with various SNRs, > > > > > and with different MUSIC implementations. > > > > > Been there, done that. > > > > > > Rune > > > > > Thanks for your input Rune. It seems that you're the only person who > > > > responds to array signal processing questions. I kinda thought there > > > > would be some people on the group who could understand this stuff. > > > > I am sure there are. > > > > > Maybe few professionals post here or are in another group. > > > > Nope. The academics who ask about MUSIC react exactly like > > > yourself: they just don't want to learn about the > > > pathological shortfalls of these types of methods. > > > Unfortunately, there are people on both sides of the fence who are > > biased and insecure, which really does make it difficult for the two > > sides to communicate in a meaningful and respectful manner. > > There isn't. The only problem is that most people don't > know the excercise I pointed out for you earlier on. > If everybody did, everybody would agree with me. > > > But I'm > > sure neither of us wants to contribute to such counter-productive > > exchanges. I know that I don't. Personally I find the real-life > > problems you' re talking about exciting and I do think they have to be > > addressed to get a real understanding of how things work. > > Not what MUSIC is concerned. Just run the excercise I showed > you, and contemplate what would happen if a similar situation > occured after you installed and accepted payment for one of > your systems. > > > > The 'professionals' - people who work for DSP for a living > > > in the real world - just don't use MUSIC. For the very > > > reasons I've done my best to point out for you. If you don't > > > believe me, just look around for yourself and try and find > > > out how many real-world applications actually use these > > > sorts of methods. > > > > There aren't too many - I'm not aware of a single one. > > > > Rune > > > Good to hear: that's what keeps me in business. ;>) > > If you say so. Just make sure you are well insured against > claims of professional misconduct, if you decide to sell > these kinds of things. > > Rune
I do math, not engineering. All of my equations have worked so far, and consulting has never been better. ;>) M
Reply by Rune Allnor June 16, 20092009-06-16
On 16 Jun, 01:35, Junoexpress <MTBrenne...@gmail.com> wrote:
> On Jun 14, 6:23&#4294967295;am, Rune Allnor <all...@tele.ntnu.no> wrote: > > > > > On 14 Jun, 05:30, Junoexpress <MTBrenne...@gmail.com> wrote: > > > > On Jun 13, 4:00&#4294967295;pm, Rune Allnor <all...@tele.ntnu.no> wrote:> On 13 Jun, 21:33, junoexpress <MTBrenne...@gmail.com> wrote: > > > > > > Hi, > > > > > > In the literature, there is a common claim made that the performance > > > > > of MUSIC for direction of arrival estimation (DOA) is affected when > > > > > the wrong number of directional sources is assumed. There is no > > > > > argument presented to support this claim, nor any references given, > > > > > just the claim. > > > > > The claims may or may not be true, depending on exactly > > > > how &#4294967295;they are phrased. Do you have any pointers to where > > > > such claims are made? > > > > This claim is found in a good many papers on the topic of signal > > > enumeration. Two that make the statement clearly are: > > > 1) IEEE Trans Acc, Speech, and Signal Processing, vol. 38, no. 11, > > > 1990 > > > "On Information Theoretic Criteria...." by Wong, Zhang, Reilly, and > > > Yip > > > (see text after eqn 5 in article) > > > 2) IEEE Trans Signal Processing, vol. 39, no. 8, 1991 > > > "A Parametric Method for Determining the Number of Signals in Narrow- > > > Band Direction Finding" > > > by Wu and Fuhrman (see first paragraph) > > > > > There are several causes for inaccuracies in the MUSIC-type > > > > estimators. One is the SNR, others are related to wrong order > > > > estimates, like if there in reality are 4 signals present, > > > > but the order estimator only finds 3 of them. In such cases, > > > > it is likely that at least some of the DoAs are off, either > > > > because the SNR is low or the 'missing' signal lies very close > > > > to one of the others. If the 'missing' signal has a significantly > > > > smaller amplitude than the others, the remaining DoA estimates > > > > might be accurate anyway. > > > > Your line of reasoning is pretty much what makes me doubt this claim. > > > A source that is missed, is most likely missed because its SNR is very > > > small. > > > Not necesarily. There can be any number of reasons why a > > source is missed. Small SNR is just one of them. > > > There is one aspect of order estimators you need to be > > aware of: For AR models, order estimators are formally > > are derived from statistical analyses of the reflection > > coefficients that represent signal residuals during the > > Levinson recursion. > > > MUSIC can not be represented as a Levinson recursion, > > it's based on eigenvector decompositions. So the *formal* > > statistical analysis, which works on the reflection > > coefficients, don't work with the eigenvalues. > > > Now, this does *not* mean that oprder estimators do not > > work with eigenvector decompositions - they do. It means > > that one has bodged a tool to work in a context it was > > not designed for. Which also goes a long way to explain > > why order estimates might be off from time to time, with > > no apparent reason. > > If you consider this from a math point of view, the basic fact is that > the notion of a "signal subspace" and a "noise subspace" are fiction. > There is a lot about this simple picture that from a mathematical > point of view is not well understood, and probably should be > investigated more.
No, there isn't. The terms are well-defined, the maths simple. As long as one is comfortable with N-dimensional complex-valued vector spaces. But those are just a matter of familiarization, like i = sqrt(-1). A big hurdle for the newbie, second nature to the somewhat more experienced.
> > > The components of the stronger sources on the evr that gets > > > dropped from the signal subspace and gets put into the noise sub-space > > > cannot be that large, so when you run say Spectral MUSIC, > > > Spectral MUSIC is...? If you are talking about the MUSIC > > pseudo spectrum, keep in mind that there is no information > > about the signal spectrum encoded in the pseudo spectrum. > > There are two basic types of MUSIC: "spectral" MUSIC (which is what > was originally proposed by Schmidt) and "ROOT" MUSIC (which is a > simple extension of spectral MUSIC that works a bit better). > Estimates about the source AOAs can be made (if again we make a boat- > load full of assumptions ;>)) from both.
MUSIC is Scmhidt's original method that in principle works with arrays of any geometry. The Root MUSIC is an ad-hoc adaption for the case of Uniform Linear Arrays. It might have been an interesting alternative, were it not for other methods that addressed the ULA directly, which turned out to be far more computationally efficient.
> > > the location > > > where the reciprocal of the projection of the steering vectors onto > > > the noise subspace has its max value should not change appreciably. > > > Remember, you are working D-manifolds in an P-dimensional > > complex-valued vector space. Don't expect your intuition > > to be of the best help... > > > > > No easy answers. > > > > > > Does this reasoning sound like the justification for the claim about > > > > > MUSIC I presented, or is there something else I am missing? > > > > > Yes, there is. > > > > > MUSIC-type estimators (meaning all estimators which > > > > implicitly or explicitly use a covariance matrix of > > > > order P to estimate the parameters of D signals) *fail* > > > > *unconditionally* when D >=P. > > > > The noise in the system (i.e. AWGN in the channels) will guarantee > > > that the covariance matrix has full rank. This condition is certainly > > > satisfied in all of the professional treatments of MUSIC you see in > > > the lit. > > > You need to think one step further: The basis for the > > noise subspace needs to be of rank at least 1 for MUSIC > > and friends to work. Once you have a signal that contains > > P (or P/2) or more sinusoidals, this no longer holds and > > MUSIC fails unconditionally. > > > > I am assuming the are are less sources than antennas here. > > > You can certainly do that for academic purposes. That's > > a very stupid thing to do in the real world. > > Not really. In many applications the cost of the array alone prohibits > you from using a large array size and you have to make that > assumption.
That's the blunder you and everybody else who try to use these methods make: The fact that you assume that the sensor will never see more than a small number of sources, does not prevent that from happening. So when (not if) the case of D >=P happens, the system breaks down. Your clients are left in a void where nothing works, and you don't understand why. Before you try and make a living out of this (your lack of historical knowledge and the statement above are certain give-aways), take some time to think through the legal obligations that are activated once you charge somebody for your advice or systems: You might very well be liable to damage compensations for any glitch or problem that are caused by your advice or system. If your clients hire me to review your system after a failure, I will waste no time in suggest you might be guilty of professional misconduct or fraud, if I find you used MUSIC and only assumed (as opposed to ensured) that the D < P.
> > > And there are other problems of course that could arise (such as the > > > presence of correlated sources, or an array whose antenna spacings are > > > greater than half a wavelength, or signals which are wide-band, etc > > > which will also act to screw up MUSIC), > > > Most of those can be handled. Tedious, but not very > > difficult. > > > > but neither I, nor the > > > articles to which I am referring, assume any of these conditions hold. > > > > > If you want to, repeat the excercise with various SNRs, > > > > and with different MUSIC implementations. > > > > Been there, done that. > > > > > Rune > > > > Thanks for your input Rune. It seems that you're the only person who > > > responds to array signal processing questions. I kinda thought there > > > would be some people on the group who could understand this stuff. > > > I am sure there are. > > > > Maybe few professionals post here or are in another group. > > > Nope. The academics who ask about MUSIC react exactly like > > yourself: they just don't want to learn about the > > pathological shortfalls of these types of methods. > > Unfortunately, there are people on both sides of the fence who are > biased and insecure, which really does make it difficult for the two > sides to communicate in a meaningful and respectful manner.
There isn't. The only problem is that most people don't know the excercise I pointed out for you earlier on. If everybody did, everybody would agree with me.
> But I'm > sure neither of us wants to contribute to such counter-productive > exchanges. I know that I don't. Personally I find the real-life > problems you' re talking about exciting and I do think they have to be > addressed to get a real understanding of how things work.
Not what MUSIC is concerned. Just run the excercise I showed you, and contemplate what would happen if a similar situation occured after you installed and accepted payment for one of your systems.
> > The 'professionals' - people who work for DSP for a living > > in the real world - just don't use MUSIC. For the very > > reasons I've done my best to point out for you. If you don't > > believe me, just look around for yourself and try and find > > out how many real-world applications actually use these > > sorts of methods. > > > There aren't too many - I'm not aware of a single one. > > > Rune > > Good to hear: that's what keeps me in business. ;>)
If you say so. Just make sure you are well insured against claims of professional misconduct, if you decide to sell these kinds of things. Rune