1 / 15

EQ2430/2440 Lecture 22/3-10

EQ2430/2440 Lecture 22/3-10. Per Zetterberg. Agenda. Project management. Project specific instructions. Project Management. Project plan due March 29 at 15.00! on web-page. Bottom up versus top-down. Top down: Divide into subtasks. Divide subtasks into sub-sub tasks. Design Implement

hiroko
Download Presentation

EQ2430/2440 Lecture 22/3-10

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. EQ2430/2440Lecture 22/3-10 Per Zetterberg

  2. Agenda • Project management. • Project specific instructions.

  3. Project Management Project plan due March 29 at 15.00! on web-page

  4. Bottom up versus top-down • Top down: • Divide into subtasks. • Divide subtasks into sub-sub tasks. • Design • Implement • Bottom Up: • Learn how to compile. • Send a pulse. • Receive the pulse. • Synchronize to the pulse • …..

  5. Recommendations • Follow bottom and top-down approaches simultaneously. • Dedicate (must) • DSP programmers. • PC programmers. • Algorithm/simulation/theory experts. • Project leader. • Let tasks run in parallel e.g. learning DSP and testing algorithm.

  6. Project plan shall contain • Background • Specification • Sketch of solution. • Description of tasks. • Allocation of people to tasks. • Time-plan. • See homepage.

  7. Weekly meetings and progress report • Weekly meetings lead by the group leader on Thursdays. • The project assistant(s) will also attend. • Progress reports are minutes of meeting. • Action items assigned. • Follow up against time-plan and old "action items“. • Who has done what the past week. • How many hours worked last week. • Shall be posted on the group web-site shortly after the meeting. www.s3.kth.se/signal/edu/projekt/examination.shtml

  8. Progress reports due • 1 April. • 8 April. • 15 April • 22 April. • 29 April • 6 May • 13 May • 20 May Check course homepage!

  9. Mid-Term Evaluation: 26April Project specific.

  10. Miscellaneous • Do not contact Texas Instruments directly. Send your enquires to perz@ee.kth.se. • Do not contact gnuradio or ettus research directly. • Do not contact support@s3.kth.se directly. Send your enquires to me perz@ee.kth.se. • All groups shall do a literature search. • Tell if you need some document printed.

  11. Lectures • DSP lecture March 30, 13.30. (CCS, EDMA, Loading of data, comparison with matlab, cache,channel boards, good advices), channel board. • RF lecture, March 30, 15.15. Basic channel model, RF non-linearity, Inter-symbol interference, phase-noise. • Webpage design. March 26, 15.15.

  12. Since 2008: Grades “If the prototype is successful, the final-report is well written and contains adequate analysis and all the other deliverables are in good shape then all members who have made significant contributions will receive the highest grade. If this is not the case, the achievements of the individual group members will be scrutinized. This can be done by examining the progress-reports and other documents produced and from observations done during the course of the project” Will be decided shortly after the grand-final

  13. Conclusion • Get started NOW. • Do literature search. • Get started with the DSP, PC and USRP. • Sketch a solution • Write project plan. See also project homepage.

  14. Code Development flow

  15. Work in lab! • I will visit the lab almost every day so be there. • This lecture 10.15-11.45 let’s stay in lab this time. • Many practical things to arrange .... I need to talk to all groups. • Use the ”idle time” to get started with your groups.

More Related