How curry0622/vlsi-physical-design-automation works
Project Type and Purpose
• This is a course‐project omnibus repository for “VLSI Physical Design Automation” homeworks 1–5.
• Each homework (HW1..HW5) is an independent command‐line tool or script collection that implements a different P&R, partitioning, floorplanning or legalization algorithm.
• There is no single “monolithic” application; instead you have five standalone pipelines, each with:
• Specification and report (PDF)
• Source code (C++, Python, shell scripts)
• Build artifacts (bin/hwX)
• Input testcases (various file formats)
• Output results (floorplan .floorplan, .def files, .csv, etc.)
• A verifier folder or grading wrapper
High‐Level File Structure Analysis
Top level:
• README.md (course overview)
• HW1 … HW5 directories
• .gitignore
Inside each HWn:
• CS6135_HWn_spec.pdf & report.pdf
• HWn/
– src/ (C++ sources, Makefile, judge.sh)
– python/ or scripts/ (for drawing or DEF writers)
– bin/hwX (compiled binary)
– output/ (result files)
– testcases/ (input nets, .cells, .hardblocks, .pl, etc.)
– verifier/ (scripts & executables to check correctness)
• HWn_grading/ (testcases + grading wrapper)
Key Insights from README
• HW1 uses an external P&R tool (Cadence Innovus).
• HW2..HW5 implement academic algorithms (FM partitioning, slicing floorplan, legalization, analog P&R) in C++/Python.
Detail Checklist
• One block per top‐level directory (HW1…HW5).
• Subblocks: src, bin, testcases, output, verifier.