bug in dbCreateLib / ddCreateLib ??
CADForums.net Forum Index CADForums.net
Discussion of AutoCAD and other CAD software.
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web cadforums.net
bug in dbCreateLib / ddCreateLib ??

 
Post new topic   Reply to topic    CADForums.net Forum Index -> Cadence
Author Message
Sylvio Triebel
Guest





Posted: Mon Oct 24, 2005 4:10 pm    Post subject: bug in dbCreateLib / ddCreateLib ?? Reply with quote

Hello,

i want to define for each start of icfb a temporary cdb library.

unless( ddGetObj("tmpLib")
dbCreateLib( "tmpLib" "/tmp/tmpLib" )
)

So far it works fine, but every start of icfb creates a
new line in the cds.lib file.

I could not find anything in SourceLink and just wanted to know,
if there is any good trick to avoid the explosion of cds.lib?

Thanks,
Sylvio

Back to top
Sylvio Triebel
Guest





Posted: Mon Oct 24, 2005 4:10 pm    Post subject: Re: bug in dbCreateLib / ddCreateLib ?? Reply with quote

....and I am using lsf (each run is on a different machine...)

Sylvio Triebel wrote:
Quote:
Hello,

i want to define for each start of icfb a temporary cdb library.

unless( ddGetObj("tmpLib")
dbCreateLib( "tmpLib" "/tmp/tmpLib" )
)

So far it works fine, but every start of icfb creates a
new line in the cds.lib file.

I could not find anything in SourceLink and just wanted to know,
if there is any good trick to avoid the explosion of cds.lib?

Thanks,
Sylvio
Back to top
Trevor Bowen
Guest





Posted: Tue Oct 25, 2005 4:10 pm    Post subject: Re: bug in dbCreateLib / ddCreateLib ?? Reply with quote

That's the problem - the library doesn't exist on that specific machine,
so the ddGetObj returns nil, triggering the creation of a new library,
which automatically adds the necessary line to the user's cds.lib.

The trick is to delete the library as one of the last steps on the
remote job. This will clean up the file space, but more importantly, it
will remove the newly added line from your cds.lib file. For example,
(plus other enhancements - makeTempFileName() for simple avoidance of
name space collision):

tempLibName = nil
unless(ddGetObj("tmpLib")
tempLibName = makeTempFileName("/tmp/tmpLib.")
ddCreateLib("tmpLib" tempLibName)
)

.....

< close all open cellViews in temp lib ... >

....

when(tempLibName
ddDeleteObj(ddGetObj(tempLibName))
)

No bug here - just the need to tidy up behind yourself. ;-)


Sylvio Triebel wrote:
Quote:
....and I am using lsf (each run is on a different machine...)

Sylvio Triebel wrote:

Hello,

i want to define for each start of icfb a temporary cdb library.

unless( ddGetObj("tmpLib")
dbCreateLib( "tmpLib" "/tmp/tmpLib" )
)

So far it works fine, but every start of icfb creates a
new line in the cds.lib file.

I could not find anything in SourceLink and just wanted to know,
if there is any good trick to avoid the explosion of cds.lib?

Thanks,
Sylvio


Back to top
Gerry Vandevalk
Guest





Posted: Tue Nov 01, 2005 1:10 am    Post subject: Re: bug in dbCreateLib / ddCreateLib ?? Reply with quote

What do you suggest I do when I am regenerating a Library from the pipo
command?

( This also generates new lines in the cds.lib! )


"Trevor Bowen" <m27315@gmail.com> wrote in message
news:Kys7f.6564$NJ.440@bignews7.bellsouth.net...
Quote:
That's the problem - the library doesn't exist on that specific machine,
so the ddGetObj returns nil, triggering the creation of a new library,
which automatically adds the necessary line to the user's cds.lib.

The trick is to delete the library as one of the last steps on the remote
job. This will clean up the file space, but more importantly, it will
remove the newly added line from your cds.lib file. For example, (plus
other enhancements - makeTempFileName() for simple avoidance of name space
collision):

tempLibName = nil
unless(ddGetObj("tmpLib")
tempLibName = makeTempFileName("/tmp/tmpLib.")
ddCreateLib("tmpLib" tempLibName)
)

....

close all open cellViews in temp lib ...

...

when(tempLibName
ddDeleteObj(ddGetObj(tempLibName))
)

No bug here - just the need to tidy up behind yourself. ;-)


Sylvio Triebel wrote:
....and I am using lsf (each run is on a different machine...)

Sylvio Triebel wrote:

Hello,

i want to define for each start of icfb a temporary cdb library.

unless( ddGetObj("tmpLib")
dbCreateLib( "tmpLib" "/tmp/tmpLib" )
)

So far it works fine, but every start of icfb creates a
new line in the cds.lib file.

I could not find anything in SourceLink and just wanted to know,
if there is any good trick to avoid the explosion of cds.lib?

Thanks,
Sylvio
Back to top
Trevor Bowen
Guest





Posted: Thu Nov 10, 2005 9:10 pm    Post subject: Re: bug in dbCreateLib / ddCreateLib ?? Reply with quote

what is the "pipo command"? That's a new one on me...

Gerry Vandevalk wrote:
Quote:
What do you suggest I do when I am regenerating a Library from the pipo
command?

( This also generates new lines in the cds.lib! )


"Trevor Bowen" <m27315@gmail.com> wrote in message
news:Kys7f.6564$NJ.440@bignews7.bellsouth.net...

That's the problem - the library doesn't exist on that specific machine,
so the ddGetObj returns nil, triggering the creation of a new library,
which automatically adds the necessary line to the user's cds.lib.

The trick is to delete the library as one of the last steps on the remote
job. This will clean up the file space, but more importantly, it will
remove the newly added line from your cds.lib file. For example, (plus
other enhancements - makeTempFileName() for simple avoidance of name space
collision):

tempLibName = nil
unless(ddGetObj("tmpLib")
tempLibName = makeTempFileName("/tmp/tmpLib.")
ddCreateLib("tmpLib" tempLibName)
)

....

close all open cellViews in temp lib ...

...

when(tempLibName
ddDeleteObj(ddGetObj(tempLibName))
)

No bug here - just the need to tidy up behind yourself. ;-)


Sylvio Triebel wrote:

....and I am using lsf (each run is on a different machine...)

Sylvio Triebel wrote:


Hello,

i want to define for each start of icfb a temporary cdb library.

unless( ddGetObj("tmpLib")
dbCreateLib( "tmpLib" "/tmp/tmpLib" )
)

So far it works fine, but every start of icfb creates a
new line in the cds.lib file.

I could not find anything in SourceLink and just wanted to know,
if there is any good trick to avoid the explosion of cds.lib?

Thanks,
Sylvio


Back to top
Andrew Beckett
Guest





Posted: Fri Nov 11, 2005 1:10 pm    Post subject: Re: bug in dbCreateLib / ddCreateLib ?? Reply with quote

Stream In/Stream Out (and other interfaces). It stands for "Physical In,
Physical Out".

To answer Gerry's question - create the library in DFII before you
start pipo. Actually I don't entirely understand what the issue is - presumably
if you just streamed it in, you don't want to delete it? Even if you do, not
sure why it can't be deleted in the same way...

Andrew.

On Thu, 10 Nov 2005 11:40:57 -0600, Trevor Bowen <m27315@gmail.com> wrote:

Quote:
what is the "pipo command"? That's a new one on me...

Gerry Vandevalk wrote:
What do you suggest I do when I am regenerating a Library from the pipo
command?

( This also generates new lines in the cds.lib! )


"Trevor Bowen" <m27315@gmail.com> wrote in message
news:Kys7f.6564$NJ.440@bignews7.bellsouth.net...

That's the problem - the library doesn't exist on that specific machine,
so the ddGetObj returns nil, triggering the creation of a new library,
which automatically adds the necessary line to the user's cds.lib.

The trick is to delete the library as one of the last steps on the remote
job. This will clean up the file space, but more importantly, it will
remove the newly added line from your cds.lib file. For example, (plus
other enhancements - makeTempFileName() for simple avoidance of name space
collision):

tempLibName = nil
unless(ddGetObj("tmpLib")
tempLibName = makeTempFileName("/tmp/tmpLib.")
ddCreateLib("tmpLib" tempLibName)
)

....

close all open cellViews in temp lib ...

...

when(tempLibName
ddDeleteObj(ddGetObj(tempLibName))
)

No bug here - just the need to tidy up behind yourself. ;-)


Sylvio Triebel wrote:

....and I am using lsf (each run is on a different machine...)

Sylvio Triebel wrote:


Hello,

i want to define for each start of icfb a temporary cdb library.

unless( ddGetObj("tmpLib")
dbCreateLib( "tmpLib" "/tmp/tmpLib" )
)

So far it works fine, but every start of icfb creates a
new line in the cds.lib file.

I could not find anything in SourceLink and just wanted to know,
if there is any good trick to avoid the explosion of cds.lib?

Thanks,
Sylvio


Back to top
Gerry Vandevalk
Guest





Posted: Mon Nov 14, 2005 1:10 am    Post subject: Re: bug in dbCreateLib / ddCreateLib ?? Reply with quote

Andrew:

After I stream in a cell multiple times into my library, I get a whole bunch
of lines in my
cds.lib that continue to add the library ... even though it is already
there.

This would not bother me, except that I now get constant warnings that the
library is defined more than once.
(even when the library is the same one!) I would like to be able to turn off
this complaint. ( and not others ... )

-- Gerry

"Andrew Beckett" <andrewb@DcEaLdEeTnEcTe.HcIoSm> wrote in message
news:hgu8n19ip0d18joue5sm6l6dh6uq138lfk@4ax.com...
Quote:
Stream In/Stream Out (and other interfaces). It stands for "Physical In,
Physical Out".

To answer Gerry's question - create the library in DFII before you
start pipo. Actually I don't entirely understand what the issue is -
presumably
if you just streamed it in, you don't want to delete it? Even if you do,
not
sure why it can't be deleted in the same way...

Andrew.

On Thu, 10 Nov 2005 11:40:57 -0600, Trevor Bowen <m27315@gmail.com> wrote:

what is the "pipo command"? That's a new one on me...

Gerry Vandevalk wrote:
What do you suggest I do when I am regenerating a Library from the pipo
command?

( This also generates new lines in the cds.lib! )


"Trevor Bowen" <m27315@gmail.com> wrote in message
news:Kys7f.6564$NJ.440@bignews7.bellsouth.net...

That's the problem - the library doesn't exist on that specific machine,
so the ddGetObj returns nil, triggering the creation of a new library,
which automatically adds the necessary line to the user's cds.lib.

The trick is to delete the library as one of the last steps on the
remote
job. This will clean up the file space, but more importantly, it will
remove the newly added line from your cds.lib file. For example, (plus
other enhancements - makeTempFileName() for simple avoidance of name
space
collision):

tempLibName = nil
unless(ddGetObj("tmpLib")
tempLibName = makeTempFileName("/tmp/tmpLib.")
ddCreateLib("tmpLib" tempLibName)
)

....

close all open cellViews in temp lib ...

...

when(tempLibName
ddDeleteObj(ddGetObj(tempLibName))
)

No bug here - just the need to tidy up behind yourself. ;-)


Sylvio Triebel wrote:

....and I am using lsf (each run is on a different machine...)

Sylvio Triebel wrote:


Hello,

i want to define for each start of icfb a temporary cdb library.

unless( ddGetObj("tmpLib")
dbCreateLib( "tmpLib" "/tmp/tmpLib" )
)

So far it works fine, but every start of icfb creates a
new line in the cds.lib file.

I could not find anything in SourceLink and just wanted to know,
if there is any good trick to avoid the explosion of cds.lib?

Thanks,
Sylvio


Back to top
Andrew Beckett
Guest





Posted: Tue Nov 15, 2005 9:10 am    Post subject: Re: bug in dbCreateLib / ddCreateLib ?? Reply with quote

Hi Gerry,

That should not happen. I've not seen it happen before - so report it to
customer support. Hopefully there's some explanation as to why it's happening -
perhaps something about your environment setup? Bit busy to think about this
enough at the moment ot figure out what might be going wrong.

Andrew.

On Sun, 13 Nov 2005 18:02:21 -0500, "Gerry Vandevalk" <g_vandevalk@yahoo.com>
wrote:

Quote:
Andrew:

After I stream in a cell multiple times into my library, I get a whole bunch
of lines in my
cds.lib that continue to add the library ... even though it is already
there.

This would not bother me, except that I now get constant warnings that the
library is defined more than once.
(even when the library is the same one!) I would like to be able to turn off
this complaint. ( and not others ... )

-- Gerry

"Andrew Beckett" <andrewb@DcEaLdEeTnEcTe.HcIoSm> wrote in message
news:hgu8n19ip0d18joue5sm6l6dh6uq138lfk@4ax.com...
Stream In/Stream Out (and other interfaces). It stands for "Physical In,
Physical Out".

To answer Gerry's question - create the library in DFII before you
start pipo. Actually I don't entirely understand what the issue is -
presumably
if you just streamed it in, you don't want to delete it? Even if you do,
not
sure why it can't be deleted in the same way...

Andrew.

On Thu, 10 Nov 2005 11:40:57 -0600, Trevor Bowen <m27315@gmail.com> wrote:

what is the "pipo command"? That's a new one on me...

Gerry Vandevalk wrote:
What do you suggest I do when I am regenerating a Library from the pipo
command?

( This also generates new lines in the cds.lib! )


"Trevor Bowen" <m27315@gmail.com> wrote in message
news:Kys7f.6564$NJ.440@bignews7.bellsouth.net...

That's the problem - the library doesn't exist on that specific machine,
so the ddGetObj returns nil, triggering the creation of a new library,
which automatically adds the necessary line to the user's cds.lib.

The trick is to delete the library as one of the last steps on the
remote
job. This will clean up the file space, but more importantly, it will
remove the newly added line from your cds.lib file. For example, (plus
other enhancements - makeTempFileName() for simple avoidance of name
space
collision):

tempLibName = nil
unless(ddGetObj("tmpLib")
tempLibName = makeTempFileName("/tmp/tmpLib.")
ddCreateLib("tmpLib" tempLibName)
)

....

close all open cellViews in temp lib ...

...

when(tempLibName
ddDeleteObj(ddGetObj(tempLibName))
)

No bug here - just the need to tidy up behind yourself. ;-)


Sylvio Triebel wrote:

....and I am using lsf (each run is on a different machine...)

Sylvio Triebel wrote:


Hello,

i want to define for each start of icfb a temporary cdb library.

unless( ddGetObj("tmpLib")
dbCreateLib( "tmpLib" "/tmp/tmpLib" )
)

So far it works fine, but every start of icfb creates a
new line in the cds.lib file.

I could not find anything in SourceLink and just wanted to know,
if there is any good trick to avoid the explosion of cds.lib?

Thanks,
Sylvio



Back to top
Andrew Beckett
Guest





Posted: Tue Nov 15, 2005 9:10 am    Post subject: Re: bug in dbCreateLib / ddCreateLib ?? Reply with quote

Hi Gerry,

I also meant to say that ddCreateLib() should only create a library if it's not
already there...

Andrew.

On Sun, 13 Nov 2005 18:02:21 -0500, "Gerry Vandevalk" <g_vandevalk@yahoo.com>
wrote:

Quote:
Andrew:

After I stream in a cell multiple times into my library, I get a whole bunch
of lines in my
cds.lib that continue to add the library ... even though it is already
there.

This would not bother me, except that I now get constant warnings that the
library is defined more than once.
(even when the library is the same one!) I would like to be able to turn off
this complaint. ( and not others ... )

-- Gerry

"Andrew Beckett" <andrewb@DcEaLdEeTnEcTe.HcIoSm> wrote in message
news:hgu8n19ip0d18joue5sm6l6dh6uq138lfk@4ax.com...
Stream In/Stream Out (and other interfaces). It stands for "Physical In,
Physical Out".

To answer Gerry's question - create the library in DFII before you
start pipo. Actually I don't entirely understand what the issue is -
presumably
if you just streamed it in, you don't want to delete it? Even if you do,
not
sure why it can't be deleted in the same way...

Andrew.

On Thu, 10 Nov 2005 11:40:57 -0600, Trevor Bowen <m27315@gmail.com> wrote:

what is the "pipo command"? That's a new one on me...

Gerry Vandevalk wrote:
What do you suggest I do when I am regenerating a Library from the pipo
command?

( This also generates new lines in the cds.lib! )


"Trevor Bowen" <m27315@gmail.com> wrote in message
news:Kys7f.6564$NJ.440@bignews7.bellsouth.net...

That's the problem - the library doesn't exist on that specific machine,
so the ddGetObj returns nil, triggering the creation of a new library,
which automatically adds the necessary line to the user's cds.lib.

The trick is to delete the library as one of the last steps on the
remote
job. This will clean up the file space, but more importantly, it will
remove the newly added line from your cds.lib file. For example, (plus
other enhancements - makeTempFileName() for simple avoidance of name
space
collision):

tempLibName = nil
unless(ddGetObj("tmpLib")
tempLibName = makeTempFileName("/tmp/tmpLib.")
ddCreateLib("tmpLib" tempLibName)
)

....

close all open cellViews in temp lib ...

...

when(tempLibName
ddDeleteObj(ddGetObj(tempLibName))
)

No bug here - just the need to tidy up behind yourself. ;-)


Sylvio Triebel wrote:

....and I am using lsf (each run is on a different machine...)

Sylvio Triebel wrote:


Hello,

i want to define for each start of icfb a temporary cdb library.

unless( ddGetObj("tmpLib")
dbCreateLib( "tmpLib" "/tmp/tmpLib" )
)

So far it works fine, but every start of icfb creates a
new line in the cds.lib file.

I could not find anything in SourceLink and just wanted to know,
if there is any good trick to avoid the explosion of cds.lib?

Thanks,
Sylvio



Back to top
 
Post new topic   Reply to topic    CADForums.net Forum Index -> Cadence All times are GMT
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




Windows Server DSP VoIP Electronics New Topics
Contact Us
Powered by phpBB