General > General Technical Chat
Signals and systems class, why?
<< < (3/5) > >>
coppercone2:
because if you can do it in a program you are useful as a data processor

a job that pays might literary be someone draws a ladder filter and tells you that he wants that in labview working smooth

(probobly high end technology job that you need to sell yourself extremely well to get)
ataradov:

--- Quote from: prophoss on October 22, 2020, 01:52:26 am ---DSP(digital signal processing) is basically like sampling a continuous wave form.

--- End quote ---
This is the most basic thing you can do. Most DSP courses just assume that you have correctly sampled digital representation of the signal. The fun starts from that.


--- Quote from: prophoss on October 22, 2020, 01:52:26 am ---The idea of that is just to do what then? Make sure there is no aliasing?

--- End quote ---

To be able to implement thing like mp3 compression. Or implement Zoom and make millions on the pandemic. Or understand how "Ok, google" or "Alexa, what time is that?" works. All of that requires deep understanding of the DSP.

And time-frequency transforms come in handy for a lot of reasons. Once of them is that not every part of the signal in the time domain carries useful information, and neural networks have much easier time dealing with the frequency domain information.

Or even more benign example that virtually any EE would have faced in their life time. You get a microcontroller and it reads ADC samples. Those samples are noisy. What is the best way to filer out the noise for a given scenario and a type of input signal?

And if you get into digital communications (Bluetooth, Wi-Fi, low power networks), you won't get anywhere without solid understanding of the DSP and transforms.

It is hard to understate just how important those concepts are in real life.
bd139:
This stuff pops up in the business end of computing as well. We implement digital filters (usually IIR) regularly. 95% of stuff is putting and getting shit from databases. Without the additional knowledge things get boring.

Obviously if you go in the hard EE end, perhaps 90% of the interesting problems are signal processing.
bd139:
Or you just do the comp sci thing and double-buffer it :)

(I spent the last few years writing high volume aggregators)
tggzzz:

--- Quote from: prophoss on October 22, 2020, 12:15:15 am ---You may actually be correct there. Most of what I have been looking toward is the programing not so much of the how it all works from a signal standpoint.

--- End quote ---

The danger is you will correctly implement something that cannot work due to fatal high-level flaws.

Understand the difference between validation and verification!

Both top-down and bottom-up design and implementation are necessary.


--- Quote ---Part of the reason I went the direction I did was to understand how things work from the bottom up. I have learned all about circuits from the electron up.

--- End quote ---

Good for you; such cross-disciplinary knowledge will stand you in good stead over the years.

But, of course, you haven't "learned all about circuits" :) Nobody can.
Navigation
Message Index
Next page
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod