1 / 10

Topics 2/8/2011

Topics 2/8/2011. Proposal: Using Microsoft Word Website Updates: References Section Proposal: Review of Key Items Preliminary Design Review. Microsoft Word. Track Changes, Comments, and document comb5ination Word’s built-in citation styles Figures, Equations, Captions, and Labels.

kitty
Download Presentation

Topics 2/8/2011

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Topics 2/8/2011 • Proposal: Using Microsoft Word • Website Updates: References Section • Proposal: Review of Key Items • Preliminary Design Review

  2. Microsoft Word • Track Changes, Comments, and document comb5ination • Word’s built-in citation styles • Figures, Equations, Captions, and Labels

  3. Proposal: Chapter 6 • Formal Presentation of the technical approach you plan to use to solve problems • Presents a task plan, schedule, work breakdown (who does what), and estimated cost analysis • Examine Description (online) • Examine Rubric (online)

  4. Design Philosophy • What is the overarching idea of the design: Do you want it cheap, robust, C+ get out of here level • On a philosophical basis, this will affect your design decisions • This also impacts your budget

  5. Abstracts: Chapter 12 • We use Informative Abstracts, not descriptive • Condense the information of a report to a few sentences, contain the substance, not just the outline • Compare some examples

  6. “Say Something” Abstract: a detailed summary of what is contained in the work Descriptive: In this paper, I will discuss the use of voltage only measurement to locate faults. This approach is extremely useful for locating faults. This works better than many other methods, and uses an advanced signal processing technique to accomplish our goals. In the first section I will introduce my topic, and some of the reasons why we need another fault location method. Next I will explain the theoretical aspects, then I will show the simulation data. Finally I will conclude with real-world data, that shows our method is successful. Informative: A travelling wave approach using voltage-only measurement is used to locate faults to within 1.5% of the line length. Our method is a double-ended approach, and unlike traditional travelling-wave methodologies, it does not rely on expensive GPS-synchronized recordings. For each end of the line, the travelling wave oscillation frequency is determined using Cohen’s class of time-frequency analysis, and using the ratio of these frequencies, the distance to the fault from each recorder is determined. The accuracy of our methodology is validated using an ATP fault model, as well as COMTRADE data from several real-world cases.

  7. Informative vs Descriptive Abstract: a detailed summary of what is contained in the work Informative: This proposal provides information describing our solution to the implementation of the Photonic Cannon, a type of bug zapper. This implementation of a bug zapper will include a microphone array to track the position of the bug on a one by one meter square surface. The microphone array will be fixed to the platform with the laser to reduce error. Filtering and analysis will be done by a low impedance amplifier, Butterworth filter, and LC resonant filter tuned at 1 kHz. The DSP chip, dsPIC30f4012, will analyze the phase relationship between the microphone arrays using cross correlation technique and pinpoint the location of the bug. It will then command servo motors to position a laser to zap the bug. The end result will allow the system to track the bug as it moves across a surface at a speed of one meter per second at a distance one meter away. Initial findings of components estimate the total budget to be $412.64 and be completed by December 3, 2010. Descriptive: This document will outline a clear design philosophy & concept, including task delegation and organizational structure. Included is a clear definition of the team’s goals for this project, as well as a breakdown of the system’s modular design and how it will fulfill the requirements set forth from the assignment specifications. Also, a budget and schedule is included with estimates of the monetary and time constraints to illustrate the feasibility of completing this project.

  8. Design Review Scheduling • Open Microsoft Outlook • Create a new meeting on Wednesday or Thursday that involves myself, Ryan Lukens, and any other members that may be necessary

  9. Preliminary Design Review • Presentation form of your Proposal • Begin with a top-level overview, move downward into subsystems and explain design choices in detail • Email copies of presentation to Patrick and Ryan before the meeting so we can take notes • Print off anything that may be pertinent

  10. Preliminary Design Content • Design Overview and philosophy • Subsystem Layouts and Schematics • Interaction between subsystems laid out • Power requirements • Pseudocode (if applicable): Basic plan of carrying out coding in outline format • Component Specifications (Wheel size, Materials, Dimensions) All this should already be In your proposal!!

More Related