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

dbu are sometimes incorrect. #181

Open
jevillegasd opened this issue Aug 22, 2022 · 1 comment
Open

dbu are sometimes incorrect. #181

jevillegasd opened this issue Aug 22, 2022 · 1 comment

Comments

@jevillegasd
Copy link
Contributor

The database units are always read from the technology definition, instead of the actual layout, and this often results in wrong behaviour whenever the layout units don't match the technology default db units.

I am guessing in general the db units are defined by the foundry and therefore you don't want to have your units to not match that of the fabrication process, but I guess it's still good if the shape generation works despite the units mismatch. Would it be reasonable to change the core to allow this? (I think this would need changes in the get_technology() function only).

Example: Here is a path, and the same path after transforming it into a waveguide while using the layout units as 0.002 um
image

Originally posted by @jevillegasd in #177

@jevillegasd jevillegasd changed the title The database units are always read from the technology definition, instead of the actual layout, and this often results in wrong behaviour whenever the layout units don't match the technology default db units. dbu are sometimes incorrect. Aug 22, 2022
@lukasc-ubc
Copy link
Member

This could be changed, but indeed the foundries usually only accept one dbu, so that should be defined in the technology.

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

2 participants