Guido Groeseneken

Name: dblp XML data dump
Creator: Schloss Dagstuhl - Leibniz Center for Informatics
Published: 1993
License: https://creativecommons.org/publicdomain/zero/1.0/
Keywords: dblp, XML, computer science, scholarly publications, metadata

◀ ▶ joint publications with Romain Ritzenthaler

> Home > Persons > Guido Groeseneken

Publications

2015
[c24]
- view
  authority control:
- export record
  dblp key:
  - conf/irps/FrancoKRBMRGHTG15
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/conf/irps/FrancoKRBMRGHTG15
Jacopo Franco, Ben Kaczer, Philippe J. Roussel, Erik Bury, Hans Mertens, Romain Ritzenthaler, Tibor Grasser, Naoto Horiguchi, Aaron Thean, Guido Groeseneken:
NBTI in Si0.55Ge0.45 cladding p-FinFETs: Porting the superior reliability from planar to 3D architectures. IRPS 2015: 2
2013
[c12]
- view
  authority control:
- export record
  dblp key:
  - conf/essderc/AoulaicheSRSACKGHTFCSCFNSN13
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/conf/essderc/AoulaicheSRSACKGHTFCSCFNSN13
Marc Aoulaiche, Eddy Simoen, Romain Ritzenthaler, Tom Schram, Hiroaki Arimura, Moonju Cho, Thomas Kauerauf, Guido Groeseneken, Naoto Horiguchi, Aaron Thean, Antonio Federico, Felice Crupi, Alessio Spessot, Christian Caillat, Pierre Fazan, Hyuokju Na, Y. Son, K. B. Noh:
Impact of Al2O3 position on performances and reliability in high-k metal gated DRAM periphery transistors. ESSDERC 2013: 190-193
2012
[c10]
- view
  authority control:
- export record
  dblp key:
  - conf/essderc/RitzenthalerSBMRGHTSCSF12
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/conf/essderc/RitzenthalerSBMRGHTSCSF12
Romain Ritzenthaler, Tom Schram, Erik Bury, Jérôme Mitard, L.-Å. Ragnarsson, Guido Groeseneken, N. Horiguchi, Aaron Thean, Alessio Spessot, Christian Caillat, V. Srividya, Pierre Fazan:
Low-power DRAM-compatible Replacement Gate High-k/Metal Gate stacks. ESSDERC 2012: 242-245

a service of

manage site settings

To protect your privacy, all features that rely on external API calls from your browser are turned off by default. You need to opt-in for them to become active. All settings here will be stored as cookies with your web browser. For more information see our F.A.Q.