evolvablehardware / evolvablehardware/BitstreamEvolutionPico

Update Columns Constraints on the UP5K device

Open
#11 0 comments 0 reactions 1 assignee Claimed by @tbioren View on GitHub
Dominant language
C
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Description

In the past we were using a subset of the available programmable logic cells during evolution.
We were not certain all of the evolvable bits were even being used, this should be readdressed

Similarly, we will need to make sure the correct columns can be specified when evolving on the UP5K devices.

We may also want to use this as an opportunity to generalize the software to enable different numbers of available components. This could then be used as an opportunity to answer questions about the size of the fabric and the evolution of our basic benchmarking fitness functions:

Research Question 1: What is the relationship between circuit size and the speed of evolutionary improvement/the plateau (peak) of fitness for the variance maximization and frequency match experiments?

Research Question 2: Is there a shift in transferability or robustness of differently sized circuits?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.