The Case Study Challenge.

March 14, 2020 IST

Introduction

To all the Aerospace and Rocket scientists out there!

AstraX '20 brings you an opportunity to apply your engineering marvels towards a mini-satellite design case study: The Mission CanXat. The motive of this event is to encourage the engineering of cheaper rockets and satellites that collect data, and minimize expenditure, thus boosting satellite efficiency. It aims to accomplish this by challenging you to brainstorm ideas and use the same for modelling a case study.
If nothing else, it will help you appreciate empty soda-cans more, and better, transform them into rockets thorough your scientific pursuits.

The Motive

The CanXat mission calls for a team of 3 aero-enthusiasts who are willing to devote to the fabrication of a blueprint model of a CanSat that collects telemetry data and other similar operations for further data analysis and processing.The model would be an abstract presented in the form of a case study.

This contest would be primarily focusing on fetching data for the below mentioned categories.
  • Measurement of pressure variation on descent.
  • Creating a 3-D map of the area surrounding the launch (preferably the highest ascent).
The CanSat will be composed of a container and payload and for case study purposes is supposed to be designed for an ascent of 1 kilometer, from wherein it will decent through a parachute system. The rate of descent may be decided by the team itself, however, the model must satisfy the minimum number of required readings for the first task.

Requirements

  • The CanSat should be approximately 66mm x 115mm, the dimension of a typical 330 ml soda can.
  • The weight of the CanSat should be approximately 700 gm.
  • On descent, the CanSat must collect a total of 10 readings for pressure variation: one in each interval gap of 100 meters.
  • It is mandatory that the parachute mechanism is implemented for the drop.
  • The descent must be smooth and normal (or close enough) to the point of steepest ascent.
  • The dimensions and weights of all the components must be clearly stated.

Note: Due to the abstract nature of the case study, the validity of the CanSat cannot be judged based on the data to be collected. Instead, it will be judged on the implementation of various components, code and programs required to bear the results. Hence, these must be listed out clearly in the case study if necessary.

Scoring and Rules

  • The teams need to send an initial document describing their complete model in detail at team@astrax.in. The due date for this document is 10th March, 11:59 pm.
  • There would also be a presentation round on 14th March in which teams would be required to present their model to the judges. The allotted time for the presentation is 15 minutes for each team.
  • Both the document and the presentation would be taken into consideration for marking the final score.
  • Scoring will be done based on overall clarity, detail in approach and presentation of the model.
  • No marks will be awarded for addressing solutions to problems other than those mentioned in the motive.
  • Marking is relative.
  • Any references and/or resources used for research and implementation purposes must be mentioned clearly.
  • Teams will be penalized for plagiarism.
For any queries regarding the event, either contact the coordinators or write an email to all@astrax.in.

Tips

  • The teams don't have to design an actual CanSat. They only need to present an abstract showcasing their understanding and implementation of various components of the CanSat.
  • The teams are encouraged to get creative as there is no upper cap on how technical the model can be.
  • Since the marking is relative a more detailed and wholesome approach will be given more weightage.
  • The teams may send a more detailed and tech heavy report for the online submission, while reserving the presentation for the more important highlights and a question round.
  • The emphasis should be on addressing the motive. Avoid getting too involved in any other aspect of the case study.
  • If you tend to get stuck on something too complicated or technical, remember the primary purpose is to showcase your understanding of the model. Be clear and concise with what you implement.
  • As far as you cite your references, including research and other helpful resources is fully encouraged.
  • Even though the allotted time for the presentation is 15 mins, it is encouraged that the contestants reserve a few extra minutes for a brief question round. This would help the judges better understand your model in aspects you might have missed.
  • Enjoy the event!

Event Coordinators