Stats

  • Locked Locked
  • Replies 6
  • Subscribers 125
  • Views 15122
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Problem to initialize Quantum after update

manudupouy

HI,

I just updated ASSURA and EXT to the newer versions (ASSURA41 and EXT191).

I succeeded in running LVS but when I try to run Assura - Quantus to make a parasitic extraction, it generates an error:

*Error* putprop: first arg must be either symbol, list, defstruct or user type - nil

<<< Stack Trace >>>

(... in _quiAddDefaultsToVuiQueueing ...)

(... in _quiGetQueuePreferences ...)

(... in _quiCheckForQueuing ...)

(... in _quiInitRunLocation ...)

(... in _quiInitRunDetailsTable ...)

(... in _quiInitRunForm ...)

(... in _vuiMakeRcxRunForm ...)

(... in _vuiRcxInit ...)

(... in vuiQrcInit ...)

(... in _qrcuiOpenAssuraRunForm ...)

_qrcuiOpenAssuraRunForm()

Any help please ?

Thanks

Emmanuel

Parents
  • Andrew Beckett

    Hi Emmanuel,

    Please contact customer support.  I saw a report of something similar with PVS - Quantus in a pre-release version of EXT191, but it appeared to be fixed by the production build.

    Perhaps you can try deleting the .qrc.Last.state file from the working directory and then try bringing up the form (in a fresh Virtuoso, to be sure)? I'm wondering if the Run Details tab have been set to "queue"? Is the UNIX environment variable QRCUI_LSF_RESOURCE set? Anyway, these questions are better dealt with by customer support as we may just need to look at your environment and setup.

    Andrew.

Reply
  • Andrew Beckett

    Hi Emmanuel,

    Please contact customer support.  I saw a report of something similar with PVS - Quantus in a pre-release version of EXT191, but it appeared to be fixed by the production build.

    Perhaps you can try deleting the .qrc.Last.state file from the working directory and then try bringing up the form (in a fresh Virtuoso, to be sure)? I'm wondering if the Run Details tab have been set to "queue"? Is the UNIX environment variable QRCUI_LSF_RESOURCE set? Anyway, these questions are better dealt with by customer support as we may just need to look at your environment and setup.

    Andrew.

Children
  • manudupouy
    in reply to Andrew Beckett

    Hi Andrew,

    First, I cannot contact the support because I am using CentOS instead of RedHat. And support just doesn't help in this case.

    I tried to delete .qrc.Last.state. It didn't help.

    Then, I setted environment variable QRCUI_LSF_RESOURCE with no value, as I have no idea how to set correctly and didn't find in the documentation. And it worked just fine !

    Thanks a lot again for your help Andrew

    Emmanuel

  • Andrew Beckett
    in reply to manudupouy

    Hi Emmanuel,

    The fact that you are using CentOS should not prevent us from providing you with tool usage support, unless the issue is clearly related to CentOS itself and is not reproducible on another platform. In this case it would have nothing to do with CentOS and I would hope we would not turn you away for simply running the tools on an unsupported OS. "Support" merely means that we do not test on that platform, nor can provide a fix if it solely appears on that platform. It doesn't mean that you're prevented from accessing customer support, as far as I'm concerned.

    I filed CCR 2067792 to get the documentation fixed to describe how to use this variable, as right now it just mentions it without giving any information on how it should be set.

    Regards,

    Andrew.

  • manudupouy
    in reply to Andrew Beckett

    Hi Andrew,

    I agree with you for the support. But it just happened in the past. So I stick to this forum when I am in trouble.

    I will update my QRCUI_LSF_RESOURCE value when it will be available through documentation. I just checked now but I didn't find.

    Thanks again.

    Emmanuel

  • Andrew Beckett
    in reply to manudupouy

    Hi Emmanuel,

    If you have a case number where this happened, I can follow up with the support team to try to ensure this doesn't happen in future. I did a bit of searching but in the cases that I think are from you (I can't really identify users from the forums though, so I may have had the wrong contact) I couldn't see any mention of CentOS as being a problem for support.

    You should note that these forums are not intended as an alternative for full customer support. Those of us from Cadence who respond here (including me) do so in our spare time and it's not part of our job at Cadence to respond here. So you may not get an answer or it may not happen very quickly...

    For the documentation issue, hopefully that can be resolved soon to clarify how to use this variable correctly.

    Regards,

    Andrew.

  • manudupouy
    in reply to Andrew Beckett

    Actually, I am working on Cadence at UFPB, with prof. Antonio Souza.

    You can check on antonio.souza@cear.ufpb.br account.

    The last time, you helped me when QRC menu was greyed. I had to set environment variable W3264_NOWARN_UNSUPPORTED_CENTOS.

    But it is true that the problem was linked to CentOS.

    After that, I integrated the fact that I could not use support.

    Regards,

    Emmanuel

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.