Search the web
Sign In
New User? Sign Up
InterceptUsers
? Already a member? Sign in to Yahoo!

Yahoo! Groups Tips

Did you know...
Show off your group to the world. Share a photo of your group with us.

Best of Y! Groups

   Check them out and nominate your group.
Having problems with message search? Fill out this form to ensure your group is one of the first to be migrated to the new message search system.

Messages

  Messages Help
Advanced
5.1 issues   Message List  
Reply | Forward Message #41 of 71 |
RE: [PantheonUsers] 5.1 issues

I have the same problem with all of the special tools I created for Agilent. We are still using 5.0 because of the specific library naming convention that was created in 5.1.

 

Chuck

 


From: PantheonUsers@yahoogroups.com [mailto:PantheonUsers@yahoogroups.com] On Behalf Of greg_dance
Sent: Tuesday, January 30, 2007 12:21 PM
To: PantheonUsers@yahoogroups.com
Subject: [PantheonUsers] 5.1 issues

 

Anyone else in the group actively using the 5.1 release for
production work?

I'm curious as to others thoughts on some of the 5.1 changes. In
particular the way that the name of the library a geom came from is
now incorporated into the geometry name.

comp("L1002", "1005_8p_CHIP_ARRAY", @placed, 5.625, 6.0,
0, @top)

in the pdb now becomes:

comp("L1002", "<internal>:1005_8p_CHIP_ARRAY", @placed,
5.625, 6.0, 0, @top)

Instead of adding an attribute to the design they put the name of the
library in the geom name, just like when the height property was
augmented with the gap height information to become:

prop("COMPONENT_HEIGHT", "0.6,0.0")
when it should have been done like this:
prop("COMPONENT_HEIGHT", "0.6")
prop("GAP_HEIGHT", "0.0")

Here's my basic beef (beyond the fact that a augmenting other data
onto a property or field violates database integrity) is that the
impact affects most everything everything:

1) the library name appears before the geoms name in the GUI so it
makes it difficult to read the real meaningful name of your geom as
it is usually to long to fit in the display now.
2) Perl commands that used to return the component geometry name now
include the library in the name which screws up any and all perl
scripts you may have dealing with opening and closing geometries or
reporting geoms information to a file.
3) Schematics driving pantheon from a non-mozaic/Indx path are now
royally messed up because the schematic that says "SOIC_8P" needs to
say "<internal>:SOIC_8P" instead.

Anyone else finding this a pain in the backside?

Greg



Tue Jan 30, 2007 8:29 pm

chuckhurst
Offline Offline
Send Email Send Email

Forward
Message #41 of 71 |
Expand Messages Author Sort by Date

Anyone else in the group actively using the 5.1 release for production work? I'm curious as to others thoughts on some of the 5.1 changes. In particular the...
greg_dance
Offline Send Email
Jan 30, 2007
8:22 pm

I have the same problem with all of the special tools I created for Agilent. We are still using 5.0 because of the specific library naming convention that was...
chuck_hurst@...
chuckhurst
Offline Send Email
Jan 30, 2007
8:29 pm

Same here. Crying shame... From: <chuck_hurst@...> Reply-To: PantheonUsers@yahoogroups.com To: <PantheonUsers@yahoogroups.com> Subject: RE:...
Greg Dance
greg_dance
Offline Send Email
Jan 31, 2007
12:09 am
Advanced

Copyright © 2009 Yahoo! Inc. All rights reserved.
Privacy Policy - Terms of Service - Guidelines - Help