ocean's warnings/error

[AG]

I have found ocean to behave unfairly , if not strangely, when I
have a large number of expressions calculated or large number of
values printed to a file.
I have a script which calculates around 30 expressions, ocean crashes
without giving any error.
(The script which runs in the background and dumps the output into a
file)
I, after lot of head-banging, found out that when I reduce the number
of expressions being calculated, the same scripts runs perfectly fine.
(Not that ANY of the expressions had error in calculation. I checked
that)
Does ocean have any option which can flag such errors/warnings?

 

[Andrew Beckett]

AG wrote, on 09/16/08 18:22:

I have found ocean to behave unfairly , if not strangely, when I
have a large number of expressions calculated or large number of
values printed to a file.
I have a script which calculates around 30 expressions, ocean crashes
without giving any error.
(The script which runs in the background and dumps the output into a
file)
I, after lot of head-banging, found out that when I reduce the number
of expressions being calculated, the same scripts runs perfectly fine.
(Not that ANY of the expressions had error in calculation. I checked
that)
Does ocean have any option which can flag such errors/warnings?

Sounds very odd. Try running in "icms" or "icfb" rather than in "ocean" and see
if that gives any more info.

You should report this to customer support, with your testcase to illustrate it.

I've not seen anything like this happening before.

Regards,

Andrew.

--
Andrew Beckett
Senior Solution Architect - Cadence Design Systems Ltd (UK)

 

[AG]

On Sep 16, 10:25 pm, Andrew Beckett <andr...@DcEaLdEeTnEcTe.HcIoSm>
wrote:

AG wrote, on 09/16/08 18:22:

I have found ocean to behave unfairly , if not strangely, when I
have a large number of expressions calculated or large number of
values printed to a file.
I have a script which calculates around 30 expressions, ocean crashes
without giving any error.
(The script which runs in the background and dumps the output into a
file)
I, after lot of head-banging, found out that when I reduce the number
of expressions being calculated, the same scripts runs perfectly fine.
(Not that ANY of the expressions had error in calculation. I checked
that)
Does ocean have any option which can flag such errors/warnings?

Sounds very odd. Try running in "icms" or "icfb" rather than in "ocean" and see
if that gives any more info.

You should report this to customer support, with your testcase to illustrate it.

I've not seen anything like this happening before.

Regards,

Andrew.

--
Andrew Beckett
Senior Solution Architect - Cadence Design Systems Ltd (UK)

Hi Andrew,
I don't know the reason though, but on using local variables in my
script, instead of gloabl variables, it solves my problem. Thanks to
my local cadence support.
Do you have any idea why that can create such a strange behavior?

Regards,
Anand

 

[Andrew Beckett]

AG wrote, on 10/01/08 08:57:

On Sep 16, 10:25 pm, Andrew Beckett <andr...@DcEaLdEeTnEcTe.HcIoSm
wrote:
AG wrote, on 09/16/08 18:22:

I have found ocean to behave unfairly , if not strangely, when I
have a large number of expressions calculated or large number of
values printed to a file.
I have a script which calculates around 30 expressions, ocean crashes
without giving any error.
(The script which runs in the background and dumps the output into a
file)
I, after lot of head-banging, found out that when I reduce the number
of expressions being calculated, the same scripts runs perfectly fine.
(Not that ANY of the expressions had error in calculation. I checked
that)
Does ocean have any option which can flag such errors/warnings?
Sounds very odd. Try running in "icms" or "icfb" rather than in "ocean" and see
if that gives any more info.

You should report this to customer support, with your testcase to illustrate it.

I've not seen anything like this happening before.

Regards,

Andrew.

--
Andrew Beckett
Senior Solution Architect - Cadence Design Systems Ltd (UK)



Hi Andrew,
I don't know the reason though, but on using local variables in my
script, instead of gloabl variables, it solves my problem. Thanks to
my local cadence support.
Do you have any idea why that can create such a strange behavior?

Regards,
Anand

That sounds rather unlikely. Without seeing it, I can't explain - I'm sure there
is some perfectly reasonable explanation, but from the info above, I can't give
one. Do you have a service request number that I can take a look at (I work for
Cadence)?

Andrew.