Assignment 2: FFT and Zero-padding SUBMISSION DEADLINE Friday 03 March 2020 at 5pm Electronic submission (only) through Brightspace
Task1: Spectrum of a truncated cosine wave
Consider the following analogue sinusoid x(t) = Acos(2πft) where A = 5.0 and f = 2 kHz.
• Starting from t = 0 and assuming the sampling frequency fs = 8 kHz, generate N = 128 samples of the above sine wave. Let x denote the
EECS 1570 Winter 2020 Assignment 4 Due: Thursday March 19, 2020 by 10:55 p.m. 1. This assignment is worth 6% of your final grade. 2. Submit your solution files electronically through the course Moodle. 3. A list of the files to submit is found at the end of this assignment. Questions: 1. (8 points) Write…This content is for IT & Web programming task members only.Log In Register
Create a console ‘C’ application to perform the following three input logic functions. Your application should be user friendly.
- Logic Functions
- Shift Left
- Shift Right
All of the above binary functions has two inputs (AND,OR etc.) except Shift operations and the output must be displayed as binary number format. User could be asked to enter binary numbers to proceed with the specific operation. Error messages may be displayed,
Project 2: Range Average Query
Due: Tuesday, October 8, before 9:00 pm
- You may find it easier to store sums (rather than averages) in the RAQ and BlockRAQ data structures. If you choose to do this, your query() function must convert sums to averages. Also, your dump() function should print sums, not averages.
- You will need to include the cmath library in raq.cpp to use the sqrt() function. You may also include iostream (needed by dump()) and iomanip (optional, but allows for formatting of output).
In this project, you will implement two different solutions for the Range Average Query problem, each with different asymptotic running times.
In this lesson, we will cover:● The importance of having a methodology.● Six-step troubleshooting methodology.
Having a troubleshooting methodology is important, especially in the IT arena. I like this quote by Stone Gossard from Pearl Jam, “My methodology is not knowing what I’m doing and making that work for me.” While this is a great quote, not everybody can do this, especially in the technology world. Due to the complexity of modern computing systems, a wise technician will have and follow a troubleshooting methodology. A formal methodology gives the technician a starting place and a logical sequence of steps to follow. If you do not have a methodology in place, you are much more likely to waste time and effort and create frustration—not only for yourself but also for your end user.
CompTIA recommends using a six-step troubleshooting methodology. The first step in their methodology is to identify the problem. Step two is to establish a theory of probable cause. The third step is to test that theory of probable cause. Step four is to develop an action plan and implement that plan. The fifth step is to verify complete system functionality. And step six is to document the process. In the section below, each of these steps is covered in more detail.
The first thing that you need to be aware of when troubleshooting a problem is that the symptoms are not the problem. When troubleshooting, it is critical that you actually identify the underlying problem—what’s actually causing the symptoms to manifest themselves. To do that, you should question the user. Ask detailed questions about when the symptoms occurred and why they may have occurred. If the user can re-create the issue for you, this can be extremely helpful. Determine what, if anything, has changed, which may have caused the problem. Importantly, before you take any action, make a backup copy of the system, so that you can preserve everything as it is.
● Question the user.● Remember that the symptoms are not the underlying problem.● Determine what has changed.● Make a backup of the system before moving on.
Once you have identified the base problem that is causing the symptoms, you will establish a list of probable causes. Once you have a list of all of the probable causes, use your technical knowledge to prioritize that list. Your list should have the probable causes listed from most likely to least likely. Incidentally, be sure to question the obvious. For instance, if the symptom is a power situation at the workstation, is the power cord plugged in and, if it is plugged in, is the outlet actually getting power? Additionally, if no probable cause can be determined, you will need to escalate the problem to a higher level.
● Make a list of probable causes.● Using your knowledge, prioritize the list.● Question the obvious (i.e., if the symptom is a power issue at the workstation, first check to make sure that the power cord is plugged in).● Escalate to a higher level if a probable cause cannot be determined.