Skip to content

Commit

Permalink
fix readme typo
Browse files Browse the repository at this point in the history
  • Loading branch information
asyms committed Nov 25, 2024
1 parent ff3c046 commit e9bb0d3
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion lab1/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ The goal of this lab is to perform the first run of the Stream framework. You wi

## Inputs
There are three main inputs defined in the `inputs/` folder:
1. **Workload**: Four back-to-back convolutional layers. The layer names are `Layer0`, `Layer`, etc. You can use [Netron](https://netron.app) to visualize the model.
1. **Workload**: Four back-to-back convolutional layers. The layer names are `Layer0`, `Layer1`, etc. You can use [Netron](https://netron.app) to visualize the model.
2. **Hardware**: A sample accelerator is encoded in `hda_bus.yaml`. There are three computing cores, `accelerator1.yaml` through `accelerator3.yaml`. These cores are defined using the ZigZag architecture definition (more information on the ZigZag architecture representation can be found [here](https://kuleuven-micas.github.io/zigzag/hardware.html)). Additionally, there is an `offchip_core` field which specifies the description of the offchip core. This offchip core also uses the ZigZag description, of which only the memory information is used (as no computations can be allocated to the offchip core). The cores are interconnected using the `core_connectivity` field of the HDA description. This specifies on each line a communication channel between two or more cores. A link is automatically added from the offchip core to the different compute cores.
3. **Mapping**: The mapping specifies for the `Layer0`-`Layer3` which core they can be allocated to, and whether the workload allocation is fixed or not. In this first run, we fix the allocation of the layers to a single core to get a baseline of the execution.

Expand Down

0 comments on commit e9bb0d3

Please sign in to comment.