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

Max # Images in a Job #28

Open
demisjohn opened this issue Jun 10, 2021 · 5 comments
Open

Max # Images in a Job #28

demisjohn opened this issue Jun 10, 2021 · 5 comments
Labels
data-validation related to validating user data, to prevent conversion errors, or warn users about unexpected result

Comments

@demisjohn
Copy link
Owner

ASML's converter fails if more than 150 Images are defined.

Should pop a Warning during export() & add_Images() if this quantity is exceeded.


ASML's convert will produce the error:

Parsing error: section IMAGE_DEFINITION invalid section index near line 788.

On the 151'th Image that is defined.

Not sure if should limit to exactly 150 Images max (90% sure this is correct) or 149 to be safe.

@demisjohn
Copy link
Owner Author

demisjohn commented Jun 10, 2021

Acutal limit may actually be between 36 --> 108.
Maybe 99? Needs testing.

@demisjohn
Copy link
Owner Author

demisjohn commented Jun 10, 2021

Also could use Instance Images (only enabled if ASML s/w option "Compound Image Design/CID" is installed). Maybe not since this would require user to also verify this s/w option is licensed and enabled.

@demisjohn demisjohn changed the title Max # Images: 150 Max # Images in a Job Jun 13, 2021
@demisjohn
Copy link
Owner Author

Ran a job just now, and via GUI was able to expose up to ~900 of a single Image, but it failed for ~4000 Images. Still don't understand what the limit is, apparently not as simple as "max # Images" - might have something to do with internal Route creation.

@demisjohn
Copy link
Owner Author

demisjohn commented Feb 23, 2022

In the GUI, can't define more than exactly 50 separate Images in "Image Definition"

@demisjohn demisjohn added the data-validation related to validating user data, to prevent conversion errors, or warn users about unexpected result label Aug 15, 2022
@demisjohn
Copy link
Owner Author

MDaal noticed: need to also account for Alignment Mark images - so should pop this error in the Conversion script.

Make a new function Job._check_max_Images() or so, and call that at the beginning of conversion func.

Make sure those AlMk Images get added before the check!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data-validation related to validating user data, to prevent conversion errors, or warn users about unexpected result
Projects
None yet
Development

No branches or pull requests

1 participant