Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing polygons in output GDS #268

Open
Rishabhgoyal07 opened this issue Aug 2, 2024 · 5 comments
Open

Missing polygons in output GDS #268

Rishabhgoyal07 opened this issue Aug 2, 2024 · 5 comments

Comments

@Rishabhgoyal07
Copy link

Hii @heitzmann, I am reading a GDS of a layout and creating a GDS of a leaf cell of that layout using command ### lib.write_gds, but in the output GDS, some polygons are missing from the output GDS which were present in the input GDS, why is this happening, Is GDSTK deleting some polygons?

@Rishabhgoyal07
Copy link
Author

Rishabhgoyal07 commented Aug 7, 2024

@nmz787-intel @heitzmann I debugged the issue and found that some flexpath are not being read while, i am getting all the polygons using get_polygons(include_paths=True, layer= layer_number) function, can you tell me why it is happening, other flex path are being read properly, but some flex path are not being read. Is it a ### bug in the gdstk?

@heitzmann
Copy link
Owner

Did you also set the datatype appropriately in the get_polygons call?

I can only help if you send me a minimal reproducible example. Just by inspecting the code or looking at the current tests, I cannot find any problem.

@Rishabhgoyal07
Copy link
Author

Rishabhgoyal07 commented Aug 14, 2024

Hii @heitzmann, This is a screenshot of the paths placement, similarly at other places the same kind of path is not being read. Kindly please resolve this issue
If you need any more detail, kindly please tell me
image

@nmz787-intel
Copy link

@Rishabhgoyal07 please provide a minimal script testcase. We cannot use your image as a testcase, though it is thought provoking.

@Rishabhgoyal07
Copy link
Author

Sorry, I cant share more than this, you can recreate this at your end and check, this kind of issue is coming in while reading the paths only, if you need any help in recreating then I will help, as per my knowledge this is a kind of bug, and it will be very useful, when it is resolved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants