Changes

'''Daedalus''' is an SSI program to teach design principles of high power rocketry with hands-on experience. Teams will design and launch novel rocket concepts iteratively, starting with L1, L2 and finally ending with an L3 rocket that successfully flies the thoroughly tested design. The technology coming out of this project will benefit the Rockets Team’s flagship rocketry project.<br />

 

To teach design principles of high power rocketry with hands-on experience. Teams will design and launch novel rocket concepts iteratively, starting with L1, L2 and finally ending with an L3 rocket that successfully flies the thoroughly tested design. The technology coming out of this project will benefit the Rockets Team’s flagship rocketry project.<br />

Documentation of the process is a crucial aspect of Daedalus. Explaining pitfalls, triumphs, and the minutiae of designing a fully functional rocket will aid and speed up the process for future teams. Each team will go through a five stage development cycle: 1. research, 2. preliminary design, 3. critical design, 4. testing and documentation review, 5. build and launch. The milestones will focus on providing hardware - not presentations.<br />

Documentation of the process is a crucial aspect of Daedalus. Explaining pitfalls, triumphs, and the minutiae of designing a fully functional rocket will aid and speed up the process for future teams. Each team will go through a five stage development cycle: 1. research, 2. preliminary design, 3. critical design, 4. testing and documentation review, 5. build and launch. The milestones will focus on providing hardware - not presentations.<br />

# See appendix for all the rest of the details.<br />

# See appendix for all the rest of the details.<br />

“Daedalus was a skilled craftsman and artist... Daedalus set to work to fabricate wings for himself and his young son Icarus. He tied feathers together, from smallest to largest so as to form an increasing surface. He secured the feathers at their midpoints with string and at their bases with wax, and gave the whole a gentle curvature like the wings of a bird. When the work was done, the artist, waving his wings, found himself buoyed upward and hung suspended, poising himself on the beaten air. He next equipped his son in the same manner, and taught him how to fly.&quot; [https://en.wikipedia.org/wiki/Daedalus]<br />

After many hours of thought, the team decided on the name Daedalus. The justification can be understood from reading this highly relevant wikipedia quote: “Daedalus was a skilled craftsman and artist... Daedalus set to work to fabricate wings for himself and his young son Icarus. He tied feathers together, from smallest to largest so as to form an increasing surface. He secured the feathers at their midpoints with string and at their bases with wax, and gave the whole a gentle curvature like the wings of a bird. When the work was done, the artist, waving his wings, found himself buoyed upward and hung suspended, poising himself on the beaten air. He next equipped his son in the same manner, and taught him how to fly.&quot; [https://en.wikipedia.org/wiki/Daedalus]<br />

 

= Phases =

= Phases =

The project will be broken up into three phases.<br />

The project will be broken up into three phases.<br />

== Phase 1. Research and Preliminary Design Review of Concept ==

== Phase 1. Research and Preliminary Design Review of Concept ==

This process of figuring out a PDR will speed up as more and more people graduate from Daedalus.<br />

This process of figuring out a PDR will speed up as more and more people graduate from Daedalus.<br />

== Phase 2. Hardware Testing and Critical Design Reviews ==

== Phase 2. Hardware Testing and Critical Design Reviews ==

All the work in Phase 2 will have built up to this point. At this stage your team should be confident in its data and ability to have a safe L3 flight.<br />

All the work in Phase 2 will have built up to this point. At this stage your team should be confident in its data and ability to have a safe L3 flight.<br />

= Design Reviews =

= Design Reviews =

## Timeline

## Timeline

## Budget<br />

## Budget<br />

Calculations and graphs are required to be included in your PDR. LaTeX is also strongly encouraged! Many examples of Latex documents have been generated (including this document) by the Rockets team. It should also be noted that for every plot, the required code/mathematics behind the plot should be included at the end of the presentation version of the PDR.<br />

Calculations and graphs are required to be included in your PDR. LaTeX is also strongly encouraged! Many examples of Latex documents have been generated (including this document) by the Rockets team. It should also be noted that for every plot, the required code/mathematics behind the plot should be included at the end of the presentation version of the PDR.<br />

Whenever a test of the concept is conducted on a smaller rocket, those rockets will also require a PDR. For example, if a team is planning to test a part of their system on an L1 rocket, they must write a text PDR for that specific L1 with the same sections. These do not have to be as in-depth however since a team will most likely be using a kit and modifying it slightly. The Systems Integration section will probably not be necessary as well, since it encompasses the entirety of the project (not a single test). Furthermore, L1 and L2 launches already have a Risk Management plan approved by Stanford, so the sections on Risk Management can be ignored.<br />

Whenever a test of the concept is conducted on a smaller rocket, those rockets will also require a PDR. For example, if a team is planning to test a part of their system on an L1 rocket, they must write a text PDR for that specific L1 with the same sections. These do not have to be as in-depth however since a team will most likely be using a kit and modifying it slightly. The Systems Integration section will probably not be necessary as well, since it encompasses the entirety of the project (not a single test). Furthermore, L1 and L2 launches already have a Risk Management plan approved by Stanford, so the sections on Risk Management can be ignored.<br />

== Critical Design Review ==

== Critical Design Review ==

Each team will conform to the NASA Drawing standards (a document that will be provided). Any part that is created or modified will need to pass through two checks: the project manager, Ian Gomez, and the manufacturing lead, Chris May.<br />

Each team will conform to the NASA Drawing standards (a document that will be provided). Any part that is created or modified will need to pass through two checks: the project manager, Ian Gomez, and the manufacturing lead, Chris May.<br />

== Analysis of Rocketry Problems: Methodology ==

== Analysis of Rocketry Problems: Methodology ==

# ''Analysis:'' Begin your analysis by applying appropriate laws, and introduce equations as needed. Develop the analysis as completely as possible before substituting numerical values. Perform the calculations needed to obtain the desired results.

# ''Analysis:'' Begin your analysis by applying appropriate laws, and introduce equations as needed. Develop the analysis as completely as possible before substituting numerical values. Perform the calculations needed to obtain the desired results.

# ''Discussion:'' Discuss your results. Such a discussion may include a summary of key conclusions, a critique of the original assumptions, and an inference of trends obtained by performing additional what-if and parameter sensitivity calculations.<br />

# ''Discussion:'' Discuss your results. Such a discussion may include a summary of key conclusions, a critique of the original assumptions, and an inference of trends obtained by performing additional what-if and parameter sensitivity calculations.<br />

== Question Checklist ==

== Question Checklist ==

Every team will have a team lead and a concept design lead. Team lead responsibilities have been outlined above in the Phase 1 section. They will be in close contact with the current project managers. Concept design leads will maintain domain over the integration of the advanced concept. Work to be divided up as each team sees fit. The designation for this mission is ARES, which stands for Advanced Rocketry and Experimental Systems.<br />

Every team will have a team lead and a concept design lead. Team lead responsibilities have been outlined above in the Phase 1 section. They will be in close contact with the current project managers. Concept design leads will maintain domain over the integration of the advanced concept. Work to be divided up as each team sees fit. The designation for this mission is ARES, which stands for Advanced Rocketry and Experimental Systems.<br />

== ARES-1 ==

== ARES-1 ==

ARES-1, code name ''Talos'', is the designation for the rocket which will be at testbed for the avionics suite.<br />

ARES-1, code name ''[[Talos]]'', is the designation for the rocket which will be a testbed for the avionics suite.<br />

 

== ARES-2 ==

== ARES-2 ==

ARES-2, code name ''Pegasus'', is the designation for the rocket which will test a parafoil descent system.<br />

ARES-2, code name ''[[Pegasus]]'', is the designation for the rocket which will test a parafoil descent system.<br />

 

== ARES-3 ==

== ARES-3 ==

ARES-3, code name ''Charybdis'', is the designation for the rocket which will use canted fins.<br />

ARES-3, code name ''[[Charybdis]]'', is the designation for the rocket which will use canted fins.<br />

 

== ARES-4 ==

== ARES-4 ==

ARES-4, code name ''Prometheus'', is the designation for the rocket with PID controlled descent system.<br />

ARES-4, code name ''[[Prometheus]]'', is the designation for the rocket with PID controlled descent system.<br />

 

 

[[Category:Rockets]]

[[Category:Rockets]]