This repo awesome-AI4EDA contains the source for the webpage: https://ai4eda.github.io, which is a curated paper list of awesome AI for EDA.
It can automatically render the plain bibtex
file into html
for display on the webpage.
bibtex
-> html
By email or By github PR.
Method 1: send your bibtex
to Guojin Chen by email [email protected]
Following this format. Example: 👇🏻
Required Fields
The title
, author
, _venue
, and year
Fields are required. You publication will be displayed into the corresponding topic.
Optional Fields
You can also add url
or link
field to attach the paper link.
Add the abstract
field to show the paper abstract.
Add the topic
field as a topic.
Add the code_url
, slides_url
, video_url
, talk_url
, project_url
field for link to your codes, slides, video, talks, or project pages.
@inproceedings{DAC23_Nitho,
title={Physics-Informed Optical Kernel Regression Using Complex-valued Neural Fields},
author={Chen, Guojin and Pei, Zehua and Yang, Haoyu and Ma, Yuzhe and Yu, Bei and Wong, Martin},
booktitle={ACM/IEEE Design Automation Conference, (\textbf{DAC '23})},
_venue={DAC}, # Required field,
year={2023}, # Required field,
url = {link to your paper}, # Optional field,
topic = {topic of your paper} # Optional field,
abstract = {abstract of your paper}, # Optional field,
code_url = {link to your codes}, # Optional field,
slides_url = {link to your slides}, # Optional field,
talk_url = {link to your talk video}, # Optional field,
video_url = {link to your video}, # Optional field,
project_url = {link to your project page}, # Optional field,
}
🚧 Warning
- You should separate the names in
author
field with "and".
Method 2: Submit a github PR to https://github.com/ai4eda/awesome-AI4EDA
We provide different categories according to the EDA flow, please copy your bibtex to the corresponding category.
The categories are defined in pub.yaml
of repo: awesome-AI4EDA, you can also submit new categories to pub.yaml
or contact [email protected] to help you add the categories.
# pub.yaml
categories_publications:
name: "All publications"
categories:
-
heading: "High Level Synthesis"
file: hls.bib
-
heading: "Logic Synthesis"
file: logicSyn.bib
-
heading: "Circuit Verification"
file: circuit.bib
-
heading: "Placement"
file: place.bib
-
heading: "Clock Tree Synthesis"
file: CTS.bib
-
heading: "Routing"
file: routing.bib
-
heading: "Timing"
file: timing.bib
-
heading: "Layout Verification"
file: layoutVer.bib
-
heading: "Mask Optimization"
file: opc.bib
-
heading: "Analog Layout Synthesis"
file: analog.bib
-
heading: "Testing"
file: testing.bib
-
heading: "Dataset and Tools"
file: data.bib
Follow the bibtex
format above. Add your bibtex
to the corresponding file.
Step3: Submit a PR or email to Guojin Chen ([email protected])
Submit a PR to repo: awesome-AI4EDA.
Or send your plain text bibtex
to Guojin Chen ([email protected])
Thank you.
Toggle to see how this work
-
generate.py creates a website from a shared YAML source by using Jinja templates.
-
The publications are rendered from a single BibTeX file. The abstracts are displayed in the website output and the selected publications here are highlighted.
-
The YAML source links to all author websites, which will automatically be added to the publication lists in the website and PDF.
-
GitHub stars are automatically scraped and cached on disk.
Dependencies are included in requirements.txt
and can be installed
using pip
with pip3 install -r requirements.txt
.
make
will call generate.py and
build the LaTeX documents with latexmk
and biber
.
The Makefile can also:
- Stage to my website with
make stage
, - Start a local jekyll server of my website with updated
documents with
make jekyll
, and - Push updated documents to my website with
make push
.
Change the content in pub.yaml
.
You should also look through the template files to make sure there isn't any
special-case code that needs to be modified.
The Makefile
can also start a Jekyll server and push the
new documents to another repository with make jekyll
and make push
.
- Strings in
pub.yaml
should be LaTeX (though, the actual LaTeX formatting should be in the left in the templates as much as possible). - If you do include any new LaTeX commands, make sure that one of the
REPLACEMENTS
ingenerate.py
converts them properly. - The LaTeX templates use modified Jinja delimiters to avoid overlaps with
normal LaTeX. See
generate.py
for details.
Thanks for the contribution and support from Prof. Bei Yu, Prof. Yibo Lin, Dr. Keren Zhu and Mr.Jing Mai