Description
Problem 1: Ant and seeds (50 pts)
(www.projecteuler.net) A laborious ant walks randomly on a 5×5 grid. The walk starts from the central square.
At each step, the ant moves to an adjacent square at random (up, down, left, right), without leaving the grid;
thus there are 2, 3 or 4 possible moves at each step depending on the ant’s position.
At the start of the walk, a seed is placed on each square of the lower row. When the ant isn’t carrying a seed
and reaches a square of the lower row containing a seed, it will start to carry the seed. The ant will drop the
seed on the first empty square of the upper row it eventually reaches.
1) What’s the expected number of steps until all seeds have been dropped in the top row?
Give your answer rounded to 6 decimal places.
2) How many total runs did it take for your answer to converge? (Or you can just do a total of 10 million
runs and output the expected number)
Write a program using std::thread to solve this problem.
Your program needs to detect the number, N, of threads that can be run concurrently on the system being
used and create N threads to answer the two questions above. Your program should then generate an output
file called ProblemOne.txt that contains the following:
Number of threads created: #
Expected number of steps: #.######
Total number of runs needed for solution convergence: #
4
Problem 2: Numerical Integration (50 pts)
Write a C++ program that uses OpenMP to compute the integral of:
οΏ½ 14 β ππ7π₯π₯ππππ
ln(2)
7
0
β οΏ½πΉπΉ(π₯π₯) β βπ₯π₯
ππ
ππ=0
= 2.0
using the midpoint rule. The midpoint rule divides the region to be integrated into N evenly spaced segments.
The value of the function is determined at each location and then multiplied by the size of the subsection.
This product is then summed for all the subsections to get an estimate of the actual value.
Your program needs to take a single command line argument that is the number of subdivisions (N) to use in
the calculations. Your program needs to output to the text file Lab2Prob2.txt the estimation of the integral,
overwriting any previous results.
Make sure to use doubles in your program.
5
Appendix A: Coding Standards
Indentation:
When using if/for/while statements, make sure you indent 4 spaces for the content inside those. Also make sure that
you use spaces to make the code more readable.
For example:
for (int i; i < 10; i++)
{
j = j + i;
}
If you have nested statements, you should use multiple indentions. Each { should be on its own line (like the for loop) If
you have else or else if statements after your if statement, they should be on their own line.
for (int i; i < 10; i++)
{
if (i < 5)
{
counter++;
k -= i;
}
else
{
k +=1;
}
j += i;
}
Camel Case:
This naming convention has the first letter of the variable be lower case, and the first letter in each new word be
capitalized (e.g. firstSecondThird). This applies for functions and member functions as well! The main exception to this is
class names, where the first letter should also be capitalized.
Variable and Function Names:
Your variable and function names should be clear about what that variable or function is. Do not use one letter variables,
but use abbreviations when it is appropriate (for example: βimag" instead of
βimaginaryβ). The more descriptive your variable and function names are, the more readable your code will be. This is
the idea behind self-documenting code.
6
File Headers:
Every file should have the following header at the top
/*
Author:
Class: ECE4122 or ECE6122
Last Date Modified:
Description:
What is the purpose of this file?
*/
Code Comments:
1. Every function must have a comment section describing the purpose of the function, the input and output
parameters, the return value (if any).
2. Every class must have a comment section to describe the purpose of the class.
3. Comments need to be placed inside of functions/loops to assist in the understanding of the flow of the code.
