Examples
The repo includes LNA_1 to LNA_4 and PA_1 to PA_3. This lines up with the paper's LNA and PA evaluation story, so these directories are the right starting points for real usage.
Common Files
| File | Meaning |
|---|---|
config.json | Main user control file for the full flow |
<design>.sp | Unsized input netlist provided by the user |
<design>_optimized.sp | Sized netlist generated after stage 1 mapping |
lna_stage_1_config.json or pa_stage_1_config.json | Design-class-specific stage 1 constants |
stage_1_map.json | Mapping from stage 1 design output to netlist annotations |
net_weights.json | Net and branch priority file for RF-critical paths |
placement_constraint.json | Placement constraint file |
router_constraints.json | Routing priority and layer-control file |
Generated Output Directory
Each example includes a generated directory such as lna_1/ or pa_1/. That directory contains:
stage_1/: best design JSON and sweep CSVstage_2/: generated primitive GDS plus design and net JSONstage_3/placement/: placement JSON and GDSstage_3/routing/: LEFs, DEF, route logs, routed GDSstage_3/pdn/: final GDS after PDN insertion
File Meaning Summary
config.json: the top-level interface between the user and the framework.sp: the user-provided initial netlist_optimized.sp: the stage 1 sized netlist used by parsingstage_1_map.json: maps stage 1 output keys to actual netlist instance valuesplacement_constraint.json: place halo, symmetry, matching, or keepouts hererouter_constraints.json: place net order, width, and layer priorities here