Murray Wiki - User contributions [en]

CS-EE-ME 75 Winter 2016 Homework 2

2016-01-04T19:51:29Z

Gblanqu:

{{cs/ee/me 75-fa15}}
<br>
{{CDS homework
| instructor = G. Blanquart, R. Murray
| course = CS/EE/ME 75
| semester = Winter 2016
| title = Problem Set #2
| issued = 5 Jan 2016, 8 pm
| due = 10 Jan 2016, 11:59 pm
}}

<ol>
<li>[10 points] Working with your crew, create a GOTChA chart for your activities this term, using the template shown on the [http://www.cds.caltech.edu/~murray/wiki/CS-EE-ME_75,_Fall_2015:_Sample_GOTChA course wiki]. Your GOTChA chart must include:
<ul>
<li> A list of the specific competitions in which your subsystem plays a role (under goals)</li>
<li> Specific objectives that you will accomplish by each of the Winter 2016 project deadlines</li>
<li> A list of other groups that you need to interact with to complete your design (under technical challenges)</li>
<li> A description of how the group will manage and coordinate its activities (under approach)
</ul>
Additional notes:
* Division leads should prepare a GOTChA chart for their division that is consistent with the overall team GOTChA chart and the individual group GOTChA charts.
* Project and technical leads should update project GOTChA chart to reflect any changes in plan for the fall term
* The following items should be present in your

<li> [10 points] On your crew page, document the following information (described in lecture):
<ul>
<li> Functional RevA design </li>
<li> Fabrication plan </li>
<li> Timeline with milestones </li>
<li> Budget </li>
<li> Crew Meeting Times </li>
<li> Action taken on RFAs/Reach out to external reviewer with specific questions </li>
</ul>

<li> In your personal space on Confluence, create a page titled "Homework #2" that has links to your crew GOTChA chart as well as a link to the crew page documenting the items in problem #2.
</li>
</ol>

CS-EE-ME 75 Winter 2016 Homework 1

2016-01-04T19:51:14Z

Gblanqu:

{{cs/ee/me 75-fa15}}
<br>
{{CDS homework
| instructor = G. Blanquart, R. Murray
| course = CS/EE/ME 75
| semester = Winter 2015
| title = Problem Set #1
| issued = 5 Jan 2016, 8 pm
| due = 7 Jan 2016, 11:59 pm
}}

<ol>
<li> [New students only] Using the login and password information sent to your Caltech e-mail account, log in to the [http://fsae.caltech.edu:8090/confluence/dashboard.action team wiki] and perform the following actions:
<ol type=a>
<li> Create a profile in Confluence that has a (current!) picture, short biography and your contact information (this is private to the team). Look at Richard Murray's profile for an example.</li>
<li> Your TA will assign you an action item as soon as your profile page is up. Respond to this action item.</li>
</ol>
</li>
<li> [New students only] Using the login and password information sent to your Caltech e-mail account, log in to Slack and perform the following actions:
<ol type=a>
<li> Create a profile in Slack that has a (current!) picture and a short description of who you are. Look at Richard Murray's profile for an example.</li>
<li> Join the channel corresponding to your division and accept the invitation to your system private group.</li>
<li> Post a message in your system group telling your TA that you are online.</li>
</ol>
</li>
<li> [10 points] Create a page in your personal space "Homework 1" and perform the following actions, with your answers given as a bulleted list:
<ol type=a>
<li> List the crew to which you have been assigned, with a link the the Confluence page for that crew.
<li> List the subsystems for which you and your crew are responsible, including links to documentation from Fall 2015 (either individual pages or a summary page with additional links to specific components). [This information can be copied from your crew page(s).]
</ol>
Notes:
* IPT members: replace crew with "division" or "IPT", as appropriate.
<li> [10 points] Create/modify a Confluence page for your crew that contains the following information:
<ol type=a>
<li> The names of the members of the crew, with links to their Confluence profiles
<li> A regular weekly meeting time and place for your crew
<li> A list of the subsystems for which the crew is responsible, including links to Fall 2015 documentation
</ol>
Notes:
* Division leads: you should post this same information for your divisions. Rather than listing names of division members, just list the crews in your division.
* Project/technical leads: you should post this same information for the IPT. Rather than listing names of team members, just list the divisions.
</li>
</ol>

CS/EE/ME 75, 2015-16 - Course Schedule

2016-01-04T19:50:26Z

Gblanqu:

{{cs/ee/me 75-fa15}} __NOTOC__

This page contains the schedule for the course, linked to the Formula SAE electric project schedule and deliverables. Each term is a separate section, listed here in reverse chronological order.

== Winter 2016 ==

=== Course schedule ===

{| border=1 width=100%
|-
|| Week || Date || Topic || Reading/Activities || Homework
|- valign=top
|
===== 1 =====
| 4 Jan (M)
| Organizational meeting
|
* Submit signup and scheduling sheet by Wed @ 11 am to box outside 327 Gates-Thomas
* Read Formula SAE rules and baseline design descriptions (see HW #1)
* Division assignments (required for HW #1) will be available by Wednesday (6 Jan)
| [[CS-EE-ME 75 Winter 2016 Homework 1|HW #1]] - due 7 Jan 2016
* Collaboration tools (Slack, Confluence)
* Crew (subsystem) baseline description
|-
|

===== 2 =====
| 11 Jan (M)
| Safety team presents and take facilities tour
|
Division meetings start.
| [[CS-EE-ME 75 Winter 2016 Homework 2|HW #2]] - due 10 Jan 2016
|-
|

===== 3 =====
| 18 Jan (M)
| Systems enginnering
|
| 
|-
|

===== 4 =====
| 25 Jan (M)
|
|
| 
|-
|

===== 5 =====
| 1 Feb (M)
|
|
|
|-
|

===== 6 =====
| 8 Feb (M)
|
|
|
|-
|

===== 7 =====
| 15 Feb (M)
|
|
|
|-
|

===== 8 =====
| 22 Feb (M)
|
|
|
|-
|

===== 9 =====
| 29 Feb (M)
|
|
|
|-
|

===== 10 =====
| 7 Mar (M)
|
|
|
|-
|

===== F =====
| TBD
|
|
|
|}

== Fall 2015 ==

Activities in Fall 2015 are focused on the design development phase of the competition.

=== Project GOTChA chart ===

This quad chart gives a snapshot of the planned activities for the term, at a high level. This information is presented here in the form of a [[GOTChA Chart|GOTChA chart]].

{| border=1 width=100%
|- valign=top
| width=50% |
==== Goals ====
* Build a highly effective team with the skills and insights required to build an electric vehicle from scratch
* Complete a design that is compliant with the rules and will win the Formula SAE Electric competition

| width=50% |

==== Technical Challenges ====
* Very short timeline to produce working design, with minimal FSAE experience
* Lack of expertise in assembling and welding frame (design bottleneck)
* Meeting technical inspection requirements (competition bottleneck)
* Lack of expertise in high voltage electronics (design bottleneck, safety issue)

|- valign=top
| width=50% |

==== Objectives ====
* Monitor system-level requirements and budget allocations for weight and cost of components as design is evolving
* Create compliant designs for all components and review design choices by the end of the term
** Midterms: clearly defined requirements for each component (performance, cost, weight)
** Finals: compliant design, with evidence of viability (prototype, vendor quote, etc)
* Train all CS/EE/ME 75 students in safety procedures and create protocols required for safe testing, operations
* Make enough progress in first term to build complete vehicle by end of second term
** Finalize and build plan for the vehicle frame and begin construction (mechanical)
** Complete a validated energetics design that will pass technical inspection (energetics)
** Create infrastructure required for divisions to optimize their designs with testing and simulation (operations)

| width=50% |

==== Approach ====
* Have working core equipment (eg, motors, battery pack) working to allow testing as soon as the students are ready
* Create simulation and testing environments that will allow design space exploration of mechanical and energetic systems
* Know the Formula SAE Electric rules by heart
|}
<br>

=== Course schedule ===

{| border=1 width=100%
|-
|| Week || Date || Topic || Reading/Activities || Homework
|- valign=top
|
===== 1 =====
| 28 Sep (M)
| Organizational meeting
* [http://www.cds.caltech.edu/~murray/courses/cs-ee-me-75/2015-16/pdf/L1_kickoff-28Sep15.pdf Lecture slides]
|
* Submit [http://www.cds.caltech.edu/~murray/courses/cs-ee-me-75/2015-16/pdf/signup-fa15.pdf signup and scheduling sheet] by Wed @ 11 am to box outside 327 Gates-Thomas
* Read Formula SAE rules and baseline design descriptions (see HW #1)
* Division assignments (required for HW #1) will be available by Thursday (1 Oct)
| [[CS-EE-ME 75 Fall 2015 Homework 1|HW #1]]
* Formula SAE Electric competition rules
* Collaboration tools (Slack, Confluence)
* Crew (subsystem) baseline description
|-
|

===== 2 =====
| 5 Oct (M)
| Project schedule
* Overall Formula SAE Electric schedule [TBD]
* GOTChA charts [Richard]
* [http://www.cds.caltech.edu/~murray/courses/cs-ee-me-75/2015-16/pdf/L2_planning-05Oct15.pdf Lecture slides]

|
Division meetings start.
| [[CS-EE-ME 75 Fall 2015 Homework 2|HW #2]]: Division schedules, subsystem GOTChAs
|-
|

===== 3 =====
| 12 Oct (M)*
| System specifications
* Baseline specifications
* [http://www.cds.caltech.edu/~murray/courses/cs-ee-me-75/2015-16/pdf/L3_specifications-12Oct15.pdf Lecture slides]
|
| [[CS-EE-ME 75 Fall 2015 Homework 3|HW #3]]: Specifications, documentation
|-
|

===== 4 =====
| 19 Oct (M)+
| Safety
* Review of safety for high voltage electric systems
* Safety procedures for CS/EE/ME 75
|
| [[CS-EE-ME 75 Fall 2015 Homework 4|HW #4]]: Requirements review planning
|-
|

===== 5 =====
| 26 Oct (M)
| Design reviews
* Role and purpose of design reviews
* Expectations for midterm and final reviews for Fall 2015
| Requirements review (midterms)
|
|-
|

===== 6 =====
| 2 Nov (M)+
| Requirements review (midterms)
|
|
|-
|

===== 7 =====
| 9 Nov (M)
| Review feedback
|
|
|-
|

===== 8 =====
| 16 Nov (M)*
| TBD
|
|
|-
|

===== 9 =====
| 23 Nov (M)+
| TBD
|
|
|-
|

===== 10 =====
| 30 Nov (M)
| Plans for Winter 2016 (IPT)
|
|
|-
|

===== F =====
| TBD
|
| Baseline design review (finals)
|
|}