While optimizing designs in M/Filter...I've encountered numerous issues. The strangest of which is while optimizing - occasionally all dimensions will change to "1.#QO". I've not found a way to recover from this. I'll have to stop then start the design over again.
Also - I'm not sure if this a bug or if I'm doing something wrong... If I change the units of the program to GHz (Tools, Options, Units)...then start an M/Filter synthesis it still asks me for the cutoff frequencies in MHz. So say I enter cutoffs of 4500 and 5000 MHz.
Now - the optimization fails because the rest of the program is set to GHz. If I open the optimization propers that M/Filter created (MFilter1_Goal) the frequencies in the Min and Max columns are shown in MHz (ie 4500 to 5000), however the program treats these as GHz (4500-5000 GHz). The optimization won't work because the frequencies are way outside the range of the analysis.
Thoughts on this?
Justin
Also - I'm not sure if this a bug or if I'm doing something wrong... If I change the units of the program to GHz (Tools, Options, Units)...then start an M/Filter synthesis it still asks me for the cutoff frequencies in MHz. So say I enter cutoffs of 4500 and 5000 MHz.
Now - the optimization fails because the rest of the program is set to GHz. If I open the optimization propers that M/Filter created (MFilter1_Goal) the frequencies in the Min and Max columns are shown in MHz (ie 4500 to 5000), however the program treats these as GHz (4500-5000 GHz). The optimization won't work because the frequencies are way outside the range of the analysis.
Thoughts on this?
Justin
The #qo bug was fixed in 2006.10. It is caused in 2006.07 by optimizing a variable at zero and you can workaround by setting min values for your variables.
Synthesis modules really are designed to run in MHz because this was all that GENESYS knew when they were written and they haven't all been updated to variable units. You may be right about the min/max values in the optimization not synching to units right. We will look into that; obviously you can work around this by setting the min/max manually. Note that once the optimization is built that GENESYS will avoid resetting it unless you change frequencies.
Mark