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

Library associated with multiple Technologies #560

Closed
lukasc-ubc opened this issue May 22, 2020 · 2 comments
Closed

Library associated with multiple Technologies #560

lukasc-ubc opened this issue May 22, 2020 · 2 comments
Assignees

Comments

@lukasc-ubc
Copy link

lukasc-ubc commented May 22, 2020

Presently, a Technology can have multiple libraries.

What about a Library that can function for multiple technologies?

I know there are obvious reasons not to do this.

But it is possible to make Library components that can be used in different technologies, especially when the differences between the processes are subtle.

Any chance we could have the following?

self.technology=[tech_name1, tech_name2, ...]

Then in our PCell code, the code can check which technology it is, and adjust accordingly.

An example of this would be an optical waveguide. Similar to the "Path" function, which applies to all technologies that have metal, we have a "Waveguide" in all integrated photonic technologies. Hence, it would be nice be able to make PCells that work for many technologies.

Thank you
Lukas

@klayoutmatthias
Copy link
Collaborator

klayoutmatthias commented May 23, 2020

Hi Lukas,

In general that should be possible.

I just wonder how to keep these files (macros, libraries ...). I was reasoning that they are conveniently kept inside a tech folder, but with common libs, they need to be stored outside in a common place.

Do you have a particular directory layout in mind?

Matthias

@lukasc-ubc
Copy link
Author

lukasc-ubc commented Jun 2, 2020

Hi Matthias,
I don't have a specific implementation / folder structure in mind.

klayoutmatthias added a commit that referenced this issue Jun 5, 2020
* First implementation.

* PORT BACK: fixed a few flaws (fixed-width side panel ..)

1. On "save as" the filename displayed in the cell view selection box
   was not updated
2. The width of the library and cellview panel could not be reduced
   below the width of the combo boxes in the headers. So the
   panels might have become pretty wide without being able to reduce
   them.

* Implemented #560 (multiple techs on libraries)
klayoutmatthias added a commit that referenced this issue Jun 5, 2020
* First implementation.

* PORT BACK: fixed a few flaws (fixed-width side panel ..)

1. On "save as" the filename displayed in the cell view selection box
   was not updated
2. The width of the library and cellview panel could not be reduced
   below the width of the combo boxes in the headers. So the
   panels might have become pretty wide without being able to reduce
   them.

* Implemented #560 (multiple techs on libraries)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants