To calculate the average noise temperature over simulated frequency one can use
mean(te(2))
function.
To only use the desired band, but still see behavior outside the band I used
mean(te(2)[XX::YY]))
for example.
To be able to change simulation frequency without the need to manually calculate the indexes one can use:
IndexStart=find(freq==1GHz)
IndexStop=find(freq==2GHz)
mean(te(2)[IndexStart::IndexStop]))
which works fine for usual simulation, and tuning.
But for optimization the mean() function seems broken when using variables like "IndexStart". If I instead use numbers, like
mean(te(2)[9::19]))
the equation is ok, except that one has to adjust the values in case of changed frequency or stepsize.
I also used
sum(te(2)[XX::YY]/(YY-XX)
to avoid mean() but without any luck.
Is this a bug or a feature? and is there any nice solution.
mean(te(2))
function.
To only use the desired band, but still see behavior outside the band I used
mean(te(2)[XX::YY]))
for example.
To be able to change simulation frequency without the need to manually calculate the indexes one can use:
IndexStart=find(freq==1GHz)
IndexStop=find(freq==2GHz)
mean(te(2)[IndexStart::IndexStop]))
which works fine for usual simulation, and tuning.
But for optimization the mean() function seems broken when using variables like "IndexStart". If I instead use numbers, like
mean(te(2)[9::19]))
the equation is ok, except that one has to adjust the values in case of changed frequency or stepsize.
I also used
sum(te(2)[XX::YY]/(YY-XX)
to avoid mean() but without any luck.
Is this a bug or a feature? and is there any nice solution.
Apr 26, 2007 2:42 AM