diff options
author | Logan Hunt <loganhunt@simponic.xyz> | 2022-05-23 16:48:11 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2022-05-23 16:48:11 -0700 |
commit | 34a6516a220b391c7269c736e66e6fd3bdfe7d4d (patch) | |
tree | fe9adaba5bf909978e976d952c7b928fe52bd7be | |
parent | 598b23f1045f1dcb3a62882ce93149dfef5cf3e9 (diff) | |
download | gol-34a6516a220b391c7269c736e66e6fd3bdfe7d4d.tar.gz gol-34a6516a220b391c7269c736e66e6fd3bdfe7d4d.zip |
Update Readme.org
Oof my grammar was not on point at whatever time I was writing this.
-rw-r--r-- | Readme.org | 6 |
1 files changed, 2 insertions, 4 deletions
@@ -3,18 +3,16 @@ * CS 5030 Final Project [[./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]] 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 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): |