ankitgarg0312 said:
some suggestions:
1. hspice has started using .option runlvl settings that automatically controls your reltol,delmax etc..
i would suggest you to use .option runlvl=5 and remove reltol,delmax etc...
2. i am bit confused on your comments on tstep , can you please eleborate in details
3. are u using .tran t1 t2 sweep a 1 2 (sweep in transient)??
please help me with above, i may be able to help you further.
hi ankitgarg0312,
1. i have set accurate=1, in hspice manual ,this means autoset runlvl=5,is this poor priority compare with reltol,delmax etc...?if yes ,i'll remve them,since accurate=1 don't set their value.
2.i'm sorry for it ,i didn't use sweep. just similar with your reply,since measure is not accurate ,i got data from .print ,since .print will print data per tstep.so for my data ,i need catch each period('1/fs'),thus set tstep directly 1/fs will got it easy,
but it seems will influence accurate.especially when use Exx,Gxx in netlist.
thanks for telling me about the difference between .measure and .print.
i feel powerless with hspice sometimes.for eg. i have a test.sp ,it contain 3 unrelated subckt.such a,b,c,when i do simulation and do psd for them.i got vout snr and sfdr etc for them
then,i change subckt a(in it , some part instead of veriloga model for ideal) ,do simulation again, the result of vout_a is different. and the result of vout_b is different also(about several db,not to big)! but absolutely unrelated subckts! it make me so helpless when try to find which part influence result, since same conditon for different result.
i only guess it come from when hspice do opration convergence frist, thus for convergence it will auto set some .option.is it the reason for difference?if yes,how we can control for the same result. if not ,what maybe the reason?