Forum Replies Created
-
AuthorPosts
-
Keith
KeymasterIf you are running OpenGL, it is probable that your graphics card is running out of memory to support more than 10 pbuffers/FBOs. Only solution is (a) get a graphics card with more memory or (b) turn off OpenGL use via setting the env var GLADE_USE_OPENGL to NO.
I will look into the enhancement to move by a delta x/y.
What do you mean by 'dumb the log'?
Keith
KeymasterThe latest version, 4.1.14, has had work done on the extraction commands. In addition to 2 new extraction commands – extractDio() and extractBjt() – the extractMOS() command has been enhanced to support the use of pcells for the extracted MOS instances, such that the recognition region shapes can be passed to the pcell as a point list.
This has meant some extensive changes to the pcell code so that Python lists can be passed as arguments to pcells. Any pcell can now have an argument that is a python list; the current restriction is that this list is a list of points i.e. a variable length list of lists of length 2. This is probably not a big restriction as this is the most useful list format.
A new Python function, ui().loadPCell('libName', 'pcellName') has been added to make it easier to script automated pcell loading.
At some point the other extract… commands will be modified to handle pcells.
The extractMOS() command has also had some bugfixes related to handling of S/D area for multifingered transistors. If a S/D diffusion area is shared between 2 transistors, each transistor gets half the S/D area assigned to it.
The export CDL command has had various bugfixes and now supports pcell devices correctly. As ever, if you find a bug, let us know.
Keith
KeymasterI'll change it so it still reports the error but continues…
Keith
KeymasterDid you read in a technology LEF first? Layer definitions are required before macro definitions in LEF e.g.
LAYER METAL1
TYPE ROUTING ;
WIDTH 0.190 ;
SPACING 0.200 ;
…
END METAL1It is quite common for the technology LEF file to be supplied seperately from the LEF defining macros etc.
Keith
KeymasterReplied via email…
Keith
KeymasterAny details e.g. a logfile would help track this down:
– what data was imported
– what (if any) editing was carried out
– were new cells created
etc.Keith
KeymasterWindows build has the change to the drag box etc. done so it is now drawn in the 'select' colour.
Keith
KeymasterThe ruler and mouse cursor box colour is set by the 'cursor' layer, and the colour outline of selected objects by the 'selected' layer.
Having said that, the mouse selection drag box / zoom drag box is still drawn in white. I'll change it to the 'selected' layer coour.
Keith
KeymasterYes this is currently a known problem.
Keith
KeymasterLVS is on the 'to do' list, but its not there yet.
Keith
KeymasterMust be something in your design data that is causing a problem. Do you have an example GDS?
Keith
KeymasterWhat does your extract rules file look like? Do you have a small example?
Keith
KeymasterVersion 4.1.8 had a fix for a crash during boolean operations that would occur if colinear points were present. This was due to Import DXF not cleaning up colinear points.
Both import and export DXF have had various fixes; export DXF outputs paths as polygons now. Import DXF rounds to database units; previously it truncated, resulting in shapes with coordinates e.g. 3.999um.
Dynamic highlight and selection has been improved; if dynamic highlight is on then the last object/edge/vertex highlighted will be selected on LMB click. Dynamic highlight latency time has been reduced from 50mS to 10mS.
Deselecting objects using the ctrl key modifier now works correctly if gravity is enabled or not.
If gravity is enabled, clicking anywhere inside an object will select that object; previously you had to click within the gravity distance of the object's edges to select it.
January 25, 2010 at 9:28 am in reply to: Ctrl key deselection doesn't work for edge/vertex mode? #740Keith
KeymasterThis will be fixed in 4.1.8
Keith
Keymaster(1) still need to identify what is causing a problem with autocad, other dxf readers have no problem.
(2) will be fixed in 4.1.8.
-
AuthorPosts