Personal tools

Difference between revisions of "Ternary Weights Engine For Efficient Many Channels Spike Sorting Applications"

From iis-projects

Jump to: navigation, search
(Literature)
Line 41: Line 41:
  
 
==Literature==
 
==Literature==
[adimauro] A. Di Mauro, F. Conti and L. Benini, "An ultra-low power Address-Event sensor interface for energy-proportional time-to-information extraction," 2017 54th ACM/EDAC/IEEE Design Automation Conference (DAC), Austin, TX, 2017, pp. 1-6.
+
* [Stevenson2011] How advances in neural recording affect data analysis [https://www.nature.com/articles/nn.2731.pdf]
doi: 10.1145/3061639.3062201
+
* [Rovere2017] A 2.2 µW Cognitive Always-On Wake-Up Circuit for Event-Driven Duty-Cycling of IoT Sensor Nodes [https://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=8341765]
 +
* [Liu2018] Event-driven processing for hardware-efficient neural spike sorting [https://iopscience.iop.org/article/10.1088/1741-2552/aa9124/meta]
  
 
==Links==  
 
==Links==  

Revision as of 18:06, 5 September 2019

Introduction

Project description

Required Skills

To work on this project, you will need:

  • to have worked in the past with at least one RTL language (SystemVerilog or Verilog or VHDL) - having followed the VLSI1 / VLSI2 courses is recommended
  • basic familiarity with a scripting language for deep learning (Python or Lua…)
  • a lot of patience!
  • to be strongly motivated for a difficult but super-cool project

If you want to work on this project, but you think that you do not match some the required skills, we can give you some preliminary exercise to help you fill in the gap.

Status: In progress

Supervision: Alfio Di Mauro
Supervision: Francesco Conti

Professor

Luca Benini

↑ top

Practical Details

Meetings & Presentations

The students and advisor(s) agree on weekly meetings to discuss all relevant decisions and decide on how to proceed. Of course, additional meetings can be organized to address urgent issues.

Around the middle of the project there is a design review, where senior members of the lab review your work (bring all the relevant information, such as prelim. specifications, block diagrams, synthesis reports, testing strategy, ...) to make sure everything is on track and decide whether further support is necessary. They also make the definite decision on whether the chip is actually manufactured (no reason to worry, if the project is on track) and whether more chip area, a different package, ... is provided. For more details confer to [1].

At the end of the project, you have to present/defend your work during a 15 min. presentation and 5 min. of discussion as part of the IIS colloquium.


Literature

  • [Stevenson2011] How advances in neural recording affect data analysis [2]
  • [Rovere2017] A 2.2 µW Cognitive Always-On Wake-Up Circuit for Event-Driven Duty-Cycling of IoT Sensor Nodes [3]
  • [Liu2018] Event-driven processing for hardware-efficient neural spike sorting [4]

Links

  • The EDA wiki with lots of information on the ETHZ ASIC design flow (internal only) [5]
  • The IIS/DZ coding guidelines [6]↑ top