You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Along the lines of my other issue (#13), I cannot seem to set the position of components. According to the documentation, you set the position via:
However, this did not work when testing it out. Here is the example I tried:
DEVICE mint_test
LAYER FLOW
PORT p1,p2,p3 portRadius=700;
NODE n1;
p1 SET X 10 Y 10;
CHANNEL c1 from p1 3 to n1 1 channelWidth=800;
CHANNEL c2 from p2 2 to n1 4 channelWidth=800;
CHANNEL c3 from n1 2 to p3 1 channelWidth=800;
END LAYER
Please note: I set the X and Y position to be (10,10) since 3dUf has the position specification in mm. However, I did also try this with p1 SET X 2000 Y 2000 (in case it was actually specified in micrometers), but still ran into an error.
This generated the following error:
output dir: /var/www/fluigicad.org/jobs/tmp__6082fbf3c4667500180b75e8/output
Running File: /var/www/fluigicad.org/jobs/tmp__6082fbf3c4667500180b75e8/MINT_example.uf
Creating the output directory:
Computing Constraints
Traceback (most recent call last):
File "//.pyenv/versions/3.8.0/bin/fluigi", line 8, in <module>
sys.exit(main())
File "//.pyenv/versions/3.8.0/lib/python3.8/site-packages/fluigi/cmdline.py", line 136, in main
current_device = generate_device_from_mint(args.input, args.unconstrained)
File "//.pyenv/versions/3.8.0/lib/python3.8/site-packages/fluigi/cmdline.py", line 57, in generate_device_from_mint
current_device = MINTDevice.from_mint_file(file_path, skip_constraints)
File "/pybin/pymint/pymint/mintdevice.py", line 259, in from_mint_file
walker.walk(constraint_listener, tree)
File "//.pyenv/versions/3.8.0/lib/python3.8/site-packages/antlr4/tree/Tree.py", line 160, in walk
self.walk(listener, child)
File "//.pyenv/versions/3.8.0/lib/python3.8/site-packages/antlr4/tree/Tree.py", line 160, in walk
self.walk(listener, child)
File "//.pyenv/versions/3.8.0/lib/python3.8/site-packages/antlr4/tree/Tree.py", line 160, in walk
self.walk(listener, child)
[Previous line repeated 3 more times]
File "//.pyenv/versions/3.8.0/lib/python3.8/site-packages/antlr4/tree/Tree.py", line 158, in walk
self.enterRule(listener, t)
File "//.pyenv/versions/3.8.0/lib/python3.8/site-packages/antlr4/tree/Tree.py", line 178, in enterRule
ctx.enterRule(listener)
File "/pybin/pymint/pymint/antlrgen/mintParser.py", line 6108, in enterRule
listener.enterSetCoordinate(self)
File "/pybin/pymint/pymint/constraints/constraintlistener.py", line 62, in enterSetCoordinate
raise Exception("Invalid coordinate label !")
Exception: Invalid coordinate label !
The error seems to suggest that the coordinates are not being parsed from the statement correctly, or maybe are not being casted from string to int. I also tried various things like putting an equals sign between x/y and their corresponding value, making X/Y lower case, and omitting X Y and just specifying the values, but they all generated syntax errors suggesting the SET syntax shown above is correct, but cannot be interpreted.
The text was updated successfully, but these errors were encountered:
Along the lines of my other issue (#13), I cannot seem to set the position of components. According to the documentation, you set the position via:
However, this did not work when testing it out. Here is the example I tried:
Please note: I set the X and Y position to be (10,10) since 3dUf has the position specification in mm. However, I did also try this with
p1 SET X 2000 Y 2000
(in case it was actually specified in micrometers), but still ran into an error.This generated the following error:
The error seems to suggest that the coordinates are not being parsed from the statement correctly, or maybe are not being casted from string to int. I also tried various things like putting an equals sign between x/y and their corresponding value, making X/Y lower case, and omitting X Y and just specifying the values, but they all generated syntax errors suggesting the
SET
syntax shown above is correct, but cannot be interpreted.The text was updated successfully, but these errors were encountered: