3rd International Symposium on Image and Signal Processing and Analysis, 2003. ISPA 2003. Proceedings of The
DOI: 10.1109/ispa.2003.1296456
|View full text |Cite
|
Sign up to set email alerts
|

A kroneeker DFT multi-beamforming implementation approach

Abstract: This ivork presents a new methodology for the hardware implementation of Multi-beurwforming algorithms based on Kronecker products compositions. This new melhodology is based on a signal algebra operator-theoretic approach for the mathematical formulation of signal processing algorithms and efticient systematic procedures for mapping these algorithms to target hardware computing strucrures through iconic and firnctional programming techniques, and automatic core generation efforts. Kronecker products algebra i… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Publication Types

Select...
1

Relationship

0
1

Authors

Journals

citations
Cited by 1 publication
(1 citation statement)
references
References 9 publications
0
1
0
Order By: Relevance
“…This is mainly blamed on scalability (19,46): icon-based programming was fine for small sized programs but for commercial sized software with large scale architecture and much more complex logic, the iconic programs became too difficult to understand and work with: program readability was the limiting issue (20). Iconic programming was therefore relegated to the introductory teaching of computer programming where only small programs are attempted (21,22,23,24,25,26,27,10,28,29,30,31,32) and also to specialist programming areas such as distributed process control (33), databases (34,35,36,37,38), image processing (39,40), testing (27,41), distributed systems (42), signal processing (43) and robotics (28,44) where only relatively small coding changes are made. The scalability problem (19) is that large iconic programs became too difficult to design and understand with large amounts of complex code represented as icons connected by lines in large 2D diagrams: the diagrams became too confusing with so many connecting lines.…”
Section: Introductionmentioning
confidence: 99%
“…This is mainly blamed on scalability (19,46): icon-based programming was fine for small sized programs but for commercial sized software with large scale architecture and much more complex logic, the iconic programs became too difficult to understand and work with: program readability was the limiting issue (20). Iconic programming was therefore relegated to the introductory teaching of computer programming where only small programs are attempted (21,22,23,24,25,26,27,10,28,29,30,31,32) and also to specialist programming areas such as distributed process control (33), databases (34,35,36,37,38), image processing (39,40), testing (27,41), distributed systems (42), signal processing (43) and robotics (28,44) where only relatively small coding changes are made. The scalability problem (19) is that large iconic programs became too difficult to design and understand with large amounts of complex code represented as icons connected by lines in large 2D diagrams: the diagrams became too confusing with so many connecting lines.…”
Section: Introductionmentioning
confidence: 99%