simponic/gol
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update Readme.org

Browse Source 
Oof my grammar was not on point at whatever time I was writing this.
This commit is contained in:
Logan Hunt 2022-05-23 16:48:11 -07:00 committed by GitHub
parent 598b23f104
commit 34a6516a22
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Readme.org
View File

@ -3,18 +3,16 @@
* CS 5030 Final Project * CS 5030 Final Project
[[./report/report.pdf][Report]] (you may need to download it to view the links in the document). [[./report/report.pdf][Report]] (you may need to download it to view the links in the document).
This is GOL. That's it.
[[https://youtu.be/N_aUWYNqpeY][A Video Example]] [[https://youtu.be/N_aUWYNqpeY][A Video Example]]
There are multiple implementations in this project. Each one uses the same code, just modified slightly. Each directory contains a Makefile which will build that implementation. For most, a simple ~cd~ into each directory and ~make~ will do (see build instructions). There are multiple implementations in this project. Each one uses the same code, just modified slightly. Each directory contains a Makefile which will build that implementation. For most, a simple ~cd~ into each directory and ~make~ will do (see build instructions).
Every ~make~ will end you up with a ~gol~ binary. However, each implementation takes a different number of arguments (the Cuda one needs to be run in a slightly different fashion). Every ~make~ will finish with a ~gol~ binary. However, each implementation takes a different number of arguments. The Cuda implementation needs to be run in a slightly different fashion.
** Compiling binary output to a video ** Compiling binary output to a video
Every implementation produces file I/O exactly the same. When logging is turned on, each iteration in the output directory is labelled ~iteration-XXXXXXX.bin~ where iteration number is padded by 7 zeros. Every implementation produces file I/O exactly the same. When logging is turned on, each iteration in the output directory is labelled ~iteration-XXXXXXX.bin~ where iteration number is padded by 7 zeros.
There is a script in ~graphics~ that converts a raw ~unsigned char~ data binary into a .bmp where a zero is black and (with some help from [[https://stackoverflow.com/a/47785639/15819675][this Stack Overflow post]]). This program is utilized by ~make-movie.sh~ to convert every .bin in a directory to a .bmp. Then, these .bmps can be compiled into a video file with the arguments that are described in ~make-movie.sh~ (just provide none and a usage string will be ~echo~ed). There is a script in ~graphics~ that converts a raw ~unsigned char~ binary dump into a .bmp (with some help from [[https://stackoverflow.com/a/47785639/15819675][this Stack Overflow post]]). ~make-movie.sh~ converts a directory of ordered binary dumps to a video file with the arguments that are described in ~make-movie.sh~ (just provide none and a usage string will be ~echo~ed).
For example to make a movie of the outputs generated in ~cuda-global/output~ where each binary file is a grid of size 1920x1080 (at 8fps to a file named output-1920.mp4): For example to make a movie of the outputs generated in ~cuda-global/output~ where each binary file is a grid of size 1920x1080 (at 8fps to a file named output-1920.mp4):