Where's my .cdsinit ???

Hi,

I have a confusing problem! I copied the $CDS_HOME/dfII/local/cdsinit
file to my home/<usr> and /root in order to run some SKILL codes i
wrote there when launching icfb from my home, the problem is it seems
that Cadence doen't see anything of what i wrote.
I renamed the /root/cdsinit intor .cdsinit and when i did, it gave me
huge number of warnings, and didn't do anything also!
I looked for other versions of .cdsinit on Cadence path, and found
many .. How can i know which one will be loaded during tools start up?
Which one to add SKILL scripts inside?
Can someone help?

Thanks in advance,
Kind Regards,
Ahmad,

 

I have a confusing problem! I copied the $CDS_HOME/dfII/local/cdsinit

/root ??

useless unless you're running cadence as root, which is not a very good idea in my opinion.

It's very clear in the documentation, the .cdsinit file is searched in this order :

1. <CDS_install_dir>/tools/dfII/local
2. the current directory "."
3. the home directory

But, once one .cdsinit file is found, the search stops. This means that if you have a
<CDS_install_dir>/tools/dfII/local/.cdsinit, it must EXPLICITELY load ~/.cdsinit and ./.cdsinit,
otherwise they won't be loaded at all.

Usually, a site .cdsinit would include something like

when( isFile("~/.cdsinit") load("~/.cdsinit") )
when( isFile("./.cdsinit") load("./.cdsinit") )



Stéphane

 

Thank you Stéphane for your valuable reply, but can i ask a little
more, you said it's clear in the manual that ... etc. , from which
manual can i find that and more regarding cadence structure and
organization?

Thanks again,
Kind Regards,
Ahmad,

 

Thank you Stéphane for your valuable reply, but can i ask a little

"Cadence Design Framework II Configuration Guide", page 33.


I admit there's a whole lot of documentation, and it's hard to find your way through.

These you might also find interesting :
"Cadence Design Framework II User Guide"
"Cadence Application Infrastructure User Guide"

This newsgroup is a valuable source of information, but don't forget to google search before you
post a question, since many have already been answered previously.

cheers,

Stéphane

 

Every now and then I think we would really need an FAQ for this
newsgroup. Problem is just where to put it and how to organize it.
Cadence themselves do have FAQ's on Sourcelink, but not all users of
Cadence tools have access to that page, and the FAQ that I think of is
for _this_ newsgroup. I would guess that collecting the most frequent
"Where is ..." and "How do I ..." or "I have this problem, where can
I ..." I would suggest that for a starter when we reply to something
that we think is a frequently asked question, then add a ##FAQ##
somewhere in the reply text. This will make it easier to google out
the FAQ when I get the time to collect them. I guess that this means
that I am stepping up to do this, but I need your help.

Kind regards,

 

Some time ago somebody, I don't know if it was you, suggest a WIKI.
Maybe be we can encourage the Cadence folks to create a WIKI on cdnusers.org

Bernd

 

Dear guys,

I agree with Svenn in fact, i'm mistaken, i should do some search
first, all of us should..
And i'm sorry for not doing so, as i was newbie to this newsgroup, and
didn't used to it yet..
When i made some search, i found that it was much helpful

Thank you for help, suggestion, and sorry again..
Regards
Ahmad,

 

Yes it was me. I still would like to have a wiki, but I am realistic
vs. the fact that Cadence is ignorant vs. good ideas coming from their
user base, so I step back a bit and think of collecting an FAQ
instead. Cadence change so little in their software that a FAQ written
10 years ago would still be very much up to date regarding where what
is. Bugs is a different case.

If I ever get to speak to a Cadence guy with a bit of decision power I
will surely bring up the topic. Talking to the guys doing training or
installation or customer support is like talking to the wall. Even
mentioning the wiki at the yearly web surveys is like shouting in the
woods.

Kind regards,

 

A FAQ posted regularly on a newsgroup has a lot of disadvantages compared to
a wiki, but there's one advantage which is exposure. I mean, anybody reading
the newsgroup will eventually find the FAQ.

Apart from that, it's a heavy burden for the maintainer and the lack of formatting
makes it quickly become unreadable. Not to mention the number of different versions
that get mixed up.

A wiki would definitely be a nice alternative, and, what does it cost ? Not much.
If it doesn't work out, well. But if it does, some really nice stuff could come
out of it. I may try to check if there's some decent hosting possibility here at
my university, if some talented guys from the community are willing to contribute.

Why wait for Cadence.. power to the users


Stéphane

 

Here is a free space for wiki pages:
http://www.wikispaces.com/

( What about legal stuffs in putting some kind of document about
Cadence's proprietary software into the public domain? )

-
Suresh

 

Well, this newsgroup is in the public domain too - so I don't see it's any
different than that.

Regards,

Andrew.

 

Thanks for the vote of confidence. Makes me feel the effort my colleagues and I
put in is really worthwhile ;-(

Andrew.

 

I think you've insulted Beckett and others like him, but knowing some
of his character by his posts, I expect that he will still be weighing
in on the newsgroup, which is very good.

I've been to multiple training sessions, and worked with AEs. I've
seen ideas that should've been implemented not implemented, but I also
have seen some that have been implemented. Also I've seen ideas that
should be implemented, and that will be implemented in the next
version (which usually takes, well, some time, but get's in there).
Typically they jot notes down, and pass that along.. However, if it is
pretty important, the AEs I've dealt with when I was at a large
corporation, stayed alert as to how it was being handled, and whether
it was going to make the next release, etc. and kept me posted.

It is a very large company, obviously some AEs and Trainers do better
follow-up than others, and it is a large company with the usual
associated bureaucracy. The majority of people from Cadence that I've
worked with are good. Some are "very" good, and some are okay.

Being a business, resources are limited, attention is put more to
where the money is, the things that will bring revenue.

 

Let's set a thing or two straight, I was talking about a Wiki, not
about the support abilities of Cadence AE or your/their commitment on
this newsgroup. Telling AE and Trainers about how fantastic a would
work in supporting the customers and let the customers support
themselves has so far not lead to any wiki or an equal system. The
ones I have met have all agreed that the concept sounds cool, but they
don't have the power to drive this idea inside the Cadence
organization for me.