Due Friday, 04/09, midnight1.
This project is to be done by yourself.
In this warm-up project, you will solve two short problems as a way to familiarize yourself with the Go programming language. We expect you to already have a basic knowledge of the language. If you’re starting from nothing, we highly recommend going through the Golang tour before you begin this project.
We use Go’s package testing for automated testing. You’ll fetch (fork or download) the initial software with
git (a version control system). To learn
more about git, look at the git user’s
manual,
or, if you are already familiar with other version control systems,
you may find this CS-oriented overview of
git
useful.
The URL for the course git repository is https://git.gmu.edu/cs571-proj-spring21/intro-go. Refer to GitLab Setup for instructions of creating a new Private project repository on our Mason GitLab server. You’ll commit you changes locally and push them to your private GitLab repo for grading.
You will find the code in the same directory as this readme. The two
problems that you need to solve are in q1.go and q2.go. You should
only add code to places that say TODO: implement me. Do not change
any of the function signatures as our testing framework uses them.
Q1 - Top K words:
The task is to find the K most common words in a given document. To
exclude common words such as “a” and “the”, the user of your program
should be able to specify the minimum character threshold for a word.
Word matching is case insensitive and punctuation should be removed.
You can find more details on what qualifies as a word in the comments
in the code.
Q2 - Parallel sum:
The task is to implement a function that sums a list of numbers in a
file in parallel. For this problem you are required to use goroutines
(the go keyword) and channels to pass messages across the goroutines.
While it is possible to just sum all the numbers sequentially, the
point of this problem is to familiarize yourself with the
synchronization mechanisms in Go.
Our grading uses the tests in q1_test.go and q2_test.go provided to
you. To test the correctness of your code, run the following:
% cd intro-go
% go test
If all tests pass, you should see the following output:
% go test
PASS
ok /path/to/intro-go 0.009s
To run a single test (e.g., Test1), run the following:
% go test -run Test1
--- FAIL: Test1 (0.00s)
q2_test.go:11: Sum of q2_test1.txt failed: got 0, expected 499500
FAIL
exit status 1
FAIL intro-go 0.001s
Apparently, the above test fails due to a certain reason. It is your job to finish the implementation and pass the test.
Please post questions on Piazza.
| Test | Points |
|---|---|
| Q1Simple | 4 |
| Q1DeclarationOfIndependence | 4 |
| Q2_1 | 3 |
| Q2_2 | 3 |
| Q2_3 | 3 |
| Q2_4 | 3 |
You will submit your assignment using GitLab. The submission will
consist of whatever is contianed in your private
intro-go repository.
You will need to share your private repository with our GTA Michael (his GitLab ID
is the same as his mason email ID: mcrawsha).
Commit all your changes by typing:
% git commit -am 'the final awesome solution of proj0b: [Your Name] and [Your GMU ID]'
And that’s all. We will check the timestamp (your last commit timestamp) for late submission. So make sure to submit before the deadline.
1: Since we will be touching distributed
systems concepts in the second half of the semester, I give you
plenty of time to familiarize yourself with Go programming.
Hopefully, by Week 11 you will have already picked up this new
programming language. Let’s Go!