how to count the number of iteration and check time

The Spectre Diagnose Mode might help you (see https://support.cadence.com/apex/ArticleAttachmentPortal?id=a1Od0000000u8vxEAA).

it's really helpful thank u so much

You might also find https://www.cadence.com/content/dam/cadence-www/global/en_US/documents/company/Events/CDNLive/Secured/Proceedings/SV/2018/MIX207.pdf and https://www.cadence.com/content/dam/cadence-www/global/en_US/documents/company/Events/CDNLive/Secured/Proceedings/EU/2019/cus/CUS08.pdf useful.

really thank u for your kind and fruitful reply

i think i understand the diagnostic function on transient simulation attributed to u

and here's one more question, is there any way to check dc solution (initial solution) like diagnostic

what my problem is that bad initial condition for transient simulation keep making bad pivot 

so i want to dig into initial solution information more in detail

any tips for this?

and really thank u again

The Spectre Diagnose Mode also gives detailed convergence information for the dc analysis.

you're right. we can also check diagnose result from dc analysis

but what I meant is that I want to check pre-simulation information in which initial condition is calculated before the transient simulation

for instance, there are bad pivot information like fig 1.

what I want to do is to compare the CPU times. I think the time difference is originating from the number of bad pivots

However, I am unable to find the time that spectre takes to solve one bad pivot point (and/or iterations to solve one bad pivot) 

Additionally,

2. I have 1 LTE problem. Although I can find which nodes have LTE error, can I also know the time information about time taken to process the LTE

3. time to fix newton iteration

4. also, I would like to check the CPU time per transient step. there is no information about the CPU time as you can see in fig 2 

if my pre-assumption is wrong, please let me know the guide
thank u so much
 

fig 1.

fig 2.

For the tran analysis, you can access some additional information with the Results Browser, see pages 18-19 of https://www.cadence.com/content/dam/cadence-www/global/en_US/documents/company/Events/CDNLive/Secured/Proceedings/EU/2019/cus/CUS08.pdf 

I rather doubt that knowing the CPU time taken or numbers of iterations is going to help you very much in solving what appears to be a circuit or modelling issue.

The best way forward here is probably to talk to customer support so that we can help you diagnose the real problem.

Andrew

thank u for your guide

where do i forward this?

in cadence support site?

On that page, go to Cases->Submit Case.

Andrew