Assignment: Warm-up Project

We will begin with a very simple warm-up, to confirm we all have everything we need to tackle simulations later. The objectives of this exercise will be 1) to give you an opportunity to form teams, 2) to confirm you have access to appropriate tools and compiler, 3) to confirm you can submit your project and I can read it (and compile it if necessary), and 4) to give preliminary feedback on coding style and documentation. This should be very simple.

Teams - You should form teams of two or three people.1 If you don't have much experience with C++ find team members who do. If you have experience with C++, take a poor Pythonista or Java coder under your wing. Teams should be stable.

Project description - Write, document, compile and test a program that calculates the number of dies per wafer. Your program should take die dimensions (width, height, in mm) and wafer diameter (again, in mm) and calculate dies per wafer. You can take in parameters from the command line or from a text file (or both). Format of text file is up to you, but simple is best.

width mm, height mm, wafer diameter mm -> number of dies per wafer

There's no need to get fancy, but if you choose to you can add parameters for spacing and edge clearance (totally optional).

Try to use best practices for organizing and documenting your code. This is not a course on software engineering, but it's always a good idea, even for a simple project. Also, there's the question of partial credit. In future projects, graders won't be wading into any spaghetti code. If things don't work as expected, the only way you'll get any partial credit will be if your code easily readable and well-documented.

Language - C++. You may use standard libraries. Please do not use any third-party/external libraries. You will not need them for any projects and any projects submitted that require third-party/external libraries will be rejected.

Readme - Every submission should include a readme with 1) instructions for build and use, 2) sample input and output, and 3) a very brief statement of how each team member contributed to the project. If you have set boundaries on inputs, please make a note of it in this file. If there are any special instructions with regard to build, please include them in this file. You should feel free to include other observations or comments as well.