PRE2020 4 Group5: Difference between revisions

From Control Systems Technology Group
Jump to navigation Jump to search
No edit summary
No edit summary
Line 72: Line 72:
==Milestones==
==Milestones==


To approach the project, milestones are created in hopes of setting realistic goals which can be acheived on a weekly basis. These goals will span for the entirety
To approach the project, milestones are created in hopes of setting realistic goals which can be acheived on a weekly basis. These goals will span for the entirety of the project timeline. Note, these will change throughout the project, as the type of deliverable is still not set in concrete. Once this is decided many of the milestones can be removed or ammended. Below the milestones can be found in a chronological order. These will be used later to create a project plan which can be modified throughout the project.
 
===Week 1===
===Week 1===


*Project Decision
*Project Decision
*Project Plan
*Project Plan
*Research (25 papers - 5 P.P.):
*Research (25 papers - 5 P.P.):
**Research previous/planned missions to Titan
*Complete USEr research
***Voyager 1&2
***Cassini-Huygens 1997-2005
***Dragonfly 2027-2034
**General space and orbital research
***How we plan on getting the tech into orbit of titan (or landing on titan)
**Potential scanner types:
***For Land rover:
****Thermal sensors
****GPR system (ground penetrating radar)
***For satellite:
****simple scanning software (to map surface and activity)
 


Week 2:  
Week 2:  
Before Meeting 1:
*Research (5 P.P.)
*Complete USEr research
After Meeting 1:


*List of topics for WIKI
*List of topics for WIKI
Line 111: Line 92:
*Research
*Research
*Prototype/deliverable development of idea
*Prototype/deliverable development of idea
**potential deliverable programs/software
**what would be used to create deliverable/software.
*Update project plan for prototype/deliverable
*Update project plan for prototype/deliverable


Line 139: Line 122:
*Presentation
*Presentation
*Finalize WIKI
*Finalize WIKI
--------------------------------------------
*Research:
ow thoroughly programmed the system will be.
*How much of this can be realised and hand in
*potential deliverable programs/software
*what would be used to create software.
*Conditions of life
*Deliverable:
*For technical (physical rover):
**RC cars of sorts hooked up with sensors which we can show the use of certain sensors for life detection (thermal and radiation sensors).
*Program/software:
**Show the program code and its effect on a simple arduino most notably:
**goal based decision making
**self learning system
**mapping software
*(Possible combination of both)
*Final Video:
**No further addition to this general goal as it is simply a presentation of what we have achieved.
*Make working camera mount with live feedback
*Reach xx% effectiveness in recognizing points of interest
*(Rover) Make virtual environment in which the set up can be tested (looking for patterns in a dynamic space)
**Subgoal: make database of all kind of surfaces found on Titan
**Subgoal: determine physics on the surface of Titan and how that impacts the movement of the rover.
*(Satellite) Determine ideal orbit (and adjustment propulsion) for the system
*Think of ideal camera resolution, geostatic orbit (is that possible for moons?)
*Design system to fit in a standard rocket (pretty high goal I know, but might be a fun thing to look into)
*decide on either a rover or a satellite
*For rover:
**Investigated all kinds of surfaces that are on Titan
**Rover is able to travel across the surface that has been chosen to be investigated
**a drill has been designed to obtain underground samples
**an energy source that last longer than the calculated mission length has been chosen (RTG for instance)
**the rover design fits into the rocket that will transport the rover to Titan
**the rover can be located from earth
**the rover is able to communicate with earth at certain defined intervals
*For satellite:
**The satellite can get and stay into orbit
**The satellite is able to establish its distance from the surface of Titan
**The satellite is able to obtain video in a resolution high enough to resolve objects that are 1 m long (min length can be adjusted)
**the satellite is able to obtain a heat profile of Titan in high resolution
**the satellite is able to communicate with earth at certain defined intervals
*looking for specific things of ‘life’ instead of thoroughly searching
*For the rover, material study has to be done
*Simulation with the program
*Communication with planet earth - all the time or only when necessary


==Logbook and Structure:==
==Logbook and Structure:==

Revision as of 12:54, 26 April 2021

Team:

Members Student ID Faculty E-mail
Ive Harzing 1325094 AP i.harzing@student.tue.nl
Tim Kolen 1311506 AP t.kolen@student.tue.nl
Peter Duel 1236313 ME p.m.duel@student.tue.nl
Quentin Missinne 1435957 ME q.missinne@student.tue.nl
Johan van Tien 1455788 ME f.j.m.v.tien@student.tue.nl


Topic

USEr's

(TBD)

USE

(to be edited)

User: Space agencies (NASA, ESA, JAXA, Roscosmos) astro-biologists

Society

(To be edited) Society: Satisfying our curiosity primarily: scientists Long term: Everyone


Enterprise

(to be edited) Enterprise: Space agencies Governmental: NASA, ESA, JAXA, Roscosmos) Commercial: SpaceX, Blue Origin 

astrophysicists

Project Plan

Milestones

To approach the project, milestones are created in hopes of setting realistic goals which can be acheived on a weekly basis. These goals will span for the entirety of the project timeline. Note, these will change throughout the project, as the type of deliverable is still not set in concrete. Once this is decided many of the milestones can be removed or ammended. Below the milestones can be found in a chronological order. These will be used later to create a project plan which can be modified throughout the project.

Week 1

  • Project Decision
  • Project Plan
  • Research (25 papers - 5 P.P.):
  • Complete USEr research

Week 2:

  • List of topics for WIKI
  • RPC List
  • Start looking into design solutions
  • Specify Deliverable

week 3:

  • Research
  • Prototype/deliverable development of idea
    • potential deliverable programs/software
    • what would be used to create deliverable/software.
  • Update project plan for prototype/deliverable

Week 4:

  • Additional research (if necissary)
  • Begin developping prototype
  • Addapt WIKI page with new information

Week 5:

  • Run primary test on prototype
  • Fix any issues with prototype and further develop it
  • Addapt WIKI

Week 6:

  • Complete Prototype
  • Test Prototype deliverable

Week 7:

  • Final testing of deliverable
  • Fill in missing information from WIKI

Week 8:

  • Presentation
  • Finalize WIKI

Logbook and Structure:

See the following page: Logbook Group 5

Research:

Deliverable:

State of the Art:

Retrieved from "https://cstwiki.wtb.tue.nl/index.php?title=PRE2020_4_Group5&oldid=114418"