strm2oas should read --lefdef-lefs and --lefdef-lef-layouts only once
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start by running the provided command from klayout/testdata/lefdef/multi_def and compare the output for each DEF file. Investigate how strm2oas handles --lefdef-lefs and --lefdef-lef-layouts during that run. Done means each listed LEF is read only once rather than being reread for every DEF file.
Written by the indexing model from the issue text.
Description
https://github.com/KLayout/klayout/issues/2041 was closed for 0.30.2, reopening
changing --lefdef-macro-resolution-mode=2 to =1 is also a good testcase for the open https://github.com/KLayout/klayout/issues/1506
cd klayout/testdata/lefdef/multi_def
strm2oas --version
0.30.3 r681d7eeb4
strm2oas \
--debug-level=11 \
--lefdef-macro-resolution-mode=2 \
\
--lefdef-no-implicit-lef \
--lefdef-map=layers.map \
--lefdef-lefs=\
tech.lef,\
comp_a.lef,\
comp_b.lef,\
comp_c.lef \
\
comp_a.def,\
comp_b.def,\
comp_c.def,\
main.def \
\
strm2oas.oas
Total: started
Reading LEF/DEF map file klayout/testdata/lefdef/multi_def/layers.map
Reading tech.lef
Reading LEF/DEF file klayout/testdata/lefdef/multi_def/tech.lef
Reading comp_a.lef
Reading LEF/DEF file klayout/testdata/lefdef/multi_def/comp_a.lef
Reading comp_b.lef
Reading LEF/DEF file klayout/testdata/lefdef/multi_def/comp_b.lef
Reading comp_c.lef
Reading LEF/DEF file klayout/testdata/lefdef/multi_def/comp_c.lef
Reading comp_a.def
Reading LEF/DEF file klayout/testdata/lefdef/multi_def/comp_a.def
Reading LEF/DEF map file klayout/testdata/lefdef/multi_def/layers.map
Reading tech.lef
Reading LEF/DEF file klayout/testdata/lefdef/multi_def/tech.lef
Reading comp_a.lef
Reading LEF/DEF file klayout/testdata/lefdef/multi_def/comp_a.lef
Reading comp_b.lef
Reading LEF/DEF file klayout/testdata/lefdef/multi_def/comp_b.lef
Reading comp_c.lef
Reading LEF/DEF file klayout/testdata/lefdef/multi_def/comp_c.lef
Reading comp_b.def
Reading LEF/DEF file klayout/testdata/lefdef/multi_def/comp_b.def
Reading LEF/DEF map file klayout/testdata/lefdef/multi_def/layers.map
Reading tech.lef
Reading LEF/DEF file klayout/testdata/lefdef/multi_def/tech.lef
Reading comp_a.lef
Reading LEF/DEF file klayout/testdata/lefdef/multi_def/comp_a.lef
Reading comp_b.lef
Reading LEF/DEF file klayout/testdata/lefdef/multi_def/comp_b.lef
Reading comp_c.lef
Reading LEF/DEF file klayout/testdata/lefdef/multi_def/comp_c.lef
Reading comp_c.def
Reading LEF/DEF file klayout/testdata/lefdef/multi_def/comp_c.def
Reading LEF/DEF map file klayout/testdata/lefdef/multi_def/layers.map
Reading tech.lef
Reading LEF/DEF file klayout/testdata/lefdef/multi_def/tech.lef
Reading comp_a.lef
Reading LEF/DEF file klayout/testdata/lefdef/multi_def/comp_a.lef
Reading comp_b.lef
Reading LEF/DEF file klayout/testdata/lefdef/multi_def/comp_b.lef
Reading comp_c.lef
Reading LEF/DEF file klayout/testdata/lefdef/multi_def/comp_c.lef
Reading main.def
Reading LEF/DEF file klayout/testdata/lefdef/multi_def/main.def
Total: 0 (user) 0 (sys) 0.002995738 (wall) 47.11M (mem)
- Dominant language
- C++
- Stars
- 1.2k
- Forks
- 305
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 11
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from KLayout/klayout
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
KLayout/klayout#2554 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
KLayout/klayout#2412 · 3 comments ·
Maintainers usually reply within 1 day
-
DRC functions not working properly with clip in placePossibly taken @klayoutmatthias claimed this today. Openbug
KLayout/klayout#2553 · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 50/100
Maintainers usually reply within 1 day
-
Deep DRC can miss violations when a cell has many shapesMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 4/5 3-5 days Newbie friendliness 52/100
KLayout/klayout#2546 · 5 comments ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
LaneDibello/Kotor-Patch-Manager#375 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day