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

Adding datatype to the Qgeometry #983

Draft
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

maxhant
Copy link

@maxhant maxhant commented Jan 17, 2024

What are the issues this pull addresses (issue numbers / links)?

It is based on Issue #982.

Did you add tests to cover your changes (yes/no)?

No.

Did you update the documentation accordingly (yes/no)?

No, only doctstrings.

Did you read the CONTRIBUTING document (yes/no)?

Yes, but I am not an experienced programmer.

Summary

I am adding the sublayer parameter to the qgeometry default parameters. It corresponds to the datatype kwarg that is being passed to the gdspy. This will allow experimentalists to have different sublayers in the GDS file. This is useful if one wants to expose areas with greater doses in lithography. This works better than creating a new layer because the cheesing is ignoring higher layers, thus it would overlap with the added feature because they correspond physically to the same layer.

Details and comments

It is not working for now, and I am getting some help in the issue #982 from @zlatko-minev. It is only giving my datatypes of value 0 since I have made those changes.

@@ -2343,13 +2343,13 @@ class to a series of GDSII format on the input pd.Series.
use_width,
layer=qgeometry_element.layer,
max_points=max_points,
datatype=11)
datatype=qgeometry_element.sublayer+1)
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is temporary. I need to properly check here whether it is None or not, and make it 11 as a default.
Otherwise, I am losing the ability to have Flexpaths and Polygon on the same datatype

@zlatko-minev
Copy link
Collaborator

Did you get it sorted out?

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

Successfully merging this pull request may close these issues.

2 participants