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

Controlling the way a layout reader integrates cells into an existing layout #666

klayoutmatthias opened this issue Oct 27, 2020 · 1 comment


Copy link

klayoutmatthias commented Oct 27, 2020

The "poor man's layout merge" is implemented by reading two layout files into the same object.

By doing so, existing cells will be extended by the content of the new file.

However, this scheme may not be desirable always. Other schemes are possible.

In this context, I received a user request with the following options to control this feature:

  • The current behavior.
  • Always overwriting, in case of conflict, the cell already in the layout.
  • Never overwriting, in case of conflict, the cell already in the layout..
  • Automatically renaming, in case of conflict, the cell to be read.

If the existing cell is a ghost cell, the new cells should always be integrated (current behavior).

NOTE: For ghost cells in the new layout, the current behavior can't be implemented always as during sequential reading, the nature of a cell (ghost/normal cell) cannot be determined.

This applies to reading GDS and OASIS files mainly.

@klayoutmatthias klayoutmatthias added this to the 0.27 milestone Nov 23, 2020
Copy link
Collaborator Author

Issue has been addressed with the issue_666 branch. It has been merged to master with PR #677

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

No branches or pull requests

1 participant