Scribd
Upload
12 views

Conference Project

Uploaded by

Mbmjay
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
12 views

Conference Project

Uploaded by

Mbmjay
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

AE 667: Conference Project

Weightage: 20% of the total grades

Absolute deadline: 27th October (Sunday) 11:59 PM


(Submissions after this deadline will attract 5% penalty for all group members for each 30 minutes
delay. For example, 15% will be deducted from the assignment grades if the submission happens at
1:30 AM)

This is a group project. Plagiarism of any kind will attract zero marks for all members of the group.

Outline
1. Select an effect/phenomenon affecting rotary winged vehicles that has not been extensively
covered/modelled in the class, but would be good to incorporate in a full-fledged flight
simulator.
(A few potential topics are shared in the google sheet)
2. Study the topic, read relevant material (books, internet articles, papers, etc.) specifically on
techniques to model the phenomenon
3. Write a report on the topic explaining the effect/phenomenon, the surveyed technique(s) to
model the phenomenon, and the strategy to implement the technique in the group’s code.
4. Up to10% bonus (10% of the 20%) for successful implementation and demonstration of
one or more techniques in own code.
5. Present the work to the class in engaging fashion.
6. All (except the group members) evaluate the report and the presentation. 5% penalty for
each missed assessment.
7. All students will take a quiz on the topic presented by the group (5% weightage in the final
exam). The quiz questions and their solutions will be made by the presenter group (and
kept secret from other groups).

Topic selection:
Each team must select a unique topic. Topic change is permitted only until October 6th. Teams must
list their team members and topics on the shared google sheet (using IITB credentials) so that
everybody is aware of what other teams are doing, to avoid repetition. Please do not steal topics
and team members from the other teams!!

Deliverables (by the submission deadline):


1. Report explaining the effect/phenomenon, the surveyed technique(s) to model the
phenomenon, and the strategy to implement (<= 5 pages, excluding reference list).
2. Presentation slides (plan for 15 minutes of presentation and 10 minutes of question
answers)
3. 5 questions: Conceptual questions that test whether the others have truly understood what
you presented. Avoid questions that are only fact based (requires memorizing a detail). You
are not allowed to ask something that you haven’t covered at all in your presentation and
report. Separate Word File
[Assume that each question should take not more than 2-3 minutes to answer]

Report Structure:
1. Introduction to the effect/phenomenon covering when does it occur and how does it affect
vehicle operations/performance/safety/etc.
2. Modelling technique(s) in the literature to account for the phenomenon
3. About the targeted modelling technique in more detail
4. Implementation strategy to incorporate the technique in own code
5. Demonstration / Test of implementation (Optional)
6. References

Presentation Structure
1. Title and Team Information
2. Introduction
3. Modelling techniques
4. Targeted technique
5. Implementation strategy
6. Demonstration (optional)
7. References

Grading Rubrics (Considering Report & Presentation Combined):


1. Introduction: How well has the team introduced the phenomenon on the aspects of
• occurrence of the phenomenon? [10]
• its effect on operations/performance/safety/etc.? [10]
2. Modelling techniques: Has the team
• done a thorough search for the literature on the topic? [10]
• covered the technique(s) to sufficient detail? [10]
• explained at least one technique well enough to be understood well? [10]
3. Implementation Strategy: Does the team
• have a fair idea how to implement the technique? [10]
• do a good job explaining the strategy? [10]
4. Overall quality of the report [15]
5. Overall quality of the presentation [15]
6. Demonstration (bonus):
• How well has the team demonstrated implementation? [5]
• Has the implementation captured the phenomenon as expected? [5]

More details on schedule of the presentations will be shared later.

You might also like