jack/website
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update image, fix image name spelling, fix some formatting

Browse Source
This commit is contained in:
Jack Bond-Preston 2019-02-14 21:26:08 +00:00
parent 2c700d78ed
commit b8d4b14bca
3 changed files with 16 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
images/potato-libary.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 56 KiB

BIN
images/potato-library.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 100 KiB

18
index.html
View File

@ -10,6 +10,7 @@
<link rel="icon" type="image/png" href="images/favicon-32x32.png" sizes="32x32">
<link rel="icon" type="image/png" href="images/favicon-96x96.png" sizes="96x96">
</head>
<body>
<script src="js/uikit.min.js"></script>
<script src="js/uikit-icons.min.js"></script>
@ -44,9 +45,9 @@
</div>
<div>
<div class="uk-tile uk-tile-muted">
<p class="uk-h4">
<a href="https://www.linkedin.com/in/jack-bond-preston-922706150/">LinkedIn</a>
</p>
<p class="uk-h4">
<a href="https://www.linkedin.com/in/jack-bond-preston-922706150/">LinkedIn</a>
</p>
</div>
</div>
</div>
@ -93,7 +94,7 @@
<div>
<div class="uk-inline">
<a href="https://gitlab.com/spe-potato/potato-library">
<img src="images/potato-libary.png" alt="Potato Library Screenshot">
<img src="images/potato-library.png" alt="Potato Library Screenshot">
</a>
<div class="uk-overlay uk-overlay-primary uk-position-bottom">
<h3 class="uk-heading">
@ -133,10 +134,11 @@
This game of life implementation was written in
<a href="https://en.wikipedia.org/wiki/XC_(programming_language)">XC</a>
and designed to run on the XMOS xCORE-200 eXplorer. The program runs concurrently across tiles, utilising
channels for cross-thread communication. Hardware memory limitations posed interesting challenges, with solutions
such as packing the individual "cells" into individual bits of 32/16-bit integers to be as memory-efficient as
possible. Each turn, the board is split up into rows of these packed cells which are then distributed across
workers for processing, then returned to the distributor and consolidated back into a single board each turn.
channels for cross-thread communication. Hardware memory limitations posed interesting challenges, with
solutions such as packing the individual "cells" into individual bits of 32/16-bit integers to be as
memory-efficient as possible. Each turn, the board is split up into rows of these packed cells which are then
distributed across workers for processing, then returned to the distributor and consolidated back into a single
board each turn.
</p>
</div>
</div>