CFP CAC ISSCC25 #98
Merged
CFP CAC ISSCC25 #98
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bmurmann
reviewed
Oct 12, 2024
| @@ -26,7 +26,7 @@ | |||
| ## Program Logistics | |||
| - The notebooks must be submitted through a [GitHub Pull Request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) at the [SSCS Open-Source Ecosystem Code-a-Chip](https://github.com/sscs-ose/sscs-ose-code-a-chip.github.io) (OSE) GitHub portal. | |||
| - Fork the source repo https://github.com/sscs-ose/sscs-ose-code-a-chip.github.io to your local repo. | |||
| - Create a new directory `VLSI24/submitted_notebooks/<my_project_name>` in your local repo. | |||
| - Create a new directory `ISSC25/submitted_notebooks/<my_project_name>` in your local repo. | |||
bmurmann
reviewed
Oct 12, 2024
| @@ -26,7 +26,7 @@ | |||
| ## Program Logistics | |||
| - The notebooks must be submitted through a [GitHub Pull Request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) at the [SSCS Open-Source Ecosystem Code-a-Chip](https://github.com/sscs-ose/sscs-ose-code-a-chip.github.io) (OSE) GitHub portal. | |||
| - Fork the source repo https://github.com/sscs-ose/sscs-ose-code-a-chip.github.io to your local repo. | |||
| - Create a new directory `VLSI24/submitted_notebooks/<my_project_name>` in your local repo. | |||
| - Create a new directory `ISSC25/submitted_notebooks/<my_project_name>` in your local repo. | |||
| - Add your Jupyter notebook to the directory. | |||
| - Create a pull request from your local repo to the source repo. | |||
| - Notebooks submissions must follow guidelines in the **[How to Apply](howtoapply.md)** section. | |||
There was a problem hiding this comment.
The how to apply info needs updating
bmurmann
reviewed
Oct 12, 2024
| - April 14, 2024: Announcement of [winners](VLSI24/README.md) | ||
| - April 17-21, 2024: Register for the conference, and obtain a letter for visa application (if needed) | ||
| - June 16-20, 2024: Attend conference | ||
| - October 24, 2025, 8:00 AM Pacific Time: Info Session [Zoom meeting link TBD](https://us06web.zoom.us/j/84811963095?pwd=11Cqzcb4T5bPoQeLhHQxqtQ46cFz6k.1 ) |
There was a problem hiding this comment.
I'll be traveling that day. Should we skip the info session this year? Not sure if it's all that valuable.
bmurmann
reviewed
Oct 12, 2024
| - Applicants must submit an **open-source Jupyter notebook** detailing an innovative circuit design using **open-source** tools. The objective is to disseminate the main ideas and design choices using **open-source tools and PDKs** in a **reproducible** manner. Generating a final layout of your circuit is encouraged but not required. | ||
| - Examples: [inverter](https://developers.google.com/silicon/guides/digital-inverter-openlane), [temperature sensor](https://github.com/idea-fasoc/OpenFASOC/blob/main/docs/source/notebooks/temp-sense-gen/temp_sense_genCollab.ipynb) | ||
| - Submissions of previous winners: [ISSCC'24](ISSCC24/README.md), [ISSCC'23](ISSCC23/README.md) and [VLSI'23](VLSI23/README.md) | ||
| - Submissions of previous winners: [ISSCC'24](ISSCC24/README.md), [ISSCC'23](ISSCC23/README.md), [VLSI'24](VLSI24/README.md) and [VLSI'23](VLSI23/README.md) | ||
| - Each submission must contain a suitable **open-source license** (e.g., Apache 2.0). | ||
| - Travel arrangements must comply with the [IEEE Travel and Expense Reimbursement Guidelines](https://www.ieee.org/content/dam/ieee-org/ieee/web/org/travel-expense-reimbursement-guidelines.pdf) and awardees must attend the conference in person to qualify for reimbursement. | ||
| - <span style='color: skyblue;'>❗️Starting from the ISSCC 2025 grant, the submission categories and criteria for selecting finalists will be expanded to include creative educational purposes of chip design. This can include: |
There was a problem hiding this comment.
Do we have any examples that we can point people to? I think Kwantae had some examples? Also, it would be good to merge this text with the stuff on top ("applicants must submit..."), rather than an add-on at the bottom, below the logistics.
There was a problem hiding this comment.
@KwantaeKim
do you have any examples handy?
There was a problem hiding this comment.
Hello all, I do not have a good example in IC design field, but I have an animated GIF in Computer Architecture field that I shared before. Let me point it out in Slack again.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.