你抓住了我们
为了加速SMC平均，我们只采用S22反向扫描的平均值的第一次扫描，然后对所有其他平均值使用if，这样我们就不必等待它。
Johan于10.25.02添加了此行为。
每当重新启动平均值时它都会更新。
所以，看它更新命中平均重启。
我们的想法是S22非常稳定，不需要进行平均，但Sc21阶段确实需要很多平均值，因此它不会更新S22的速度快1/3。
真正的驱动点是，如果客户正在测量下变频器并且下变频器输出处于频段的低端，而耦合器在该频段下滑，则IF需要很慢才能获得良好的结果，但扫描需要
永远，如果S22也有平均值。
告诉我你的想法;
这里有3种选择：1）保持原样。
现在工作，工作得更快，只需按平均重启重新扫描s22。
2）每次更新它，除非选中反向耦合器复选框（实际上这是原始意图，但我认为我谈到Johan即使在正常模式下也不更新它以获得更快的速度）。
修复需要几天时间。
请注意，如果反转耦合器，则不需要低IF BW，因为滚降不在路径中。
这就是我们要利用的东西。
3）添加一个单独的控件来说明是否更新它（更复杂，谁将找到它？需要几天时间才能修复）4）为Sc21测量添加一个单独的，可选择的前向平均计数，独立
S11和S21（通道）平均值。
我喜欢这一个。
修复需要花费几天时间。
欢迎大家加入新的Keysight“定义您最喜爱的模糊SMC功能”比赛。
以上来自于谷歌翻译
以下为原文
You caught us. In an attempt to speed up the SMC averaging, we only take the first sweep of the average for the S22 reverse sweep, and then use if for all the other averages so that we don't have to wait for it. Johan added this behavior in 10.25.02. It updates whenever the average is restarted. So, to see it update hit Average Restart.
Our thought is that the S22 is very stable, and doesn't need to be averaged, but the Sc21 phase does need lots of averages, and so it makes it 1/3 faster to not update S22. The real driving point for this was if a customer is measuring a down converter and the down converter output is in the low end of the band, where the coupler rolls off, the IF needs to be slow to get a good result but the sweep takes forever if the S22 has averages as well.
Tell me what do you think; here's 3 choices:
1) Leave it as it is. Works now, works faster, just hit average restart to resweep s22.
2) Update it every time, except when the reverse coupler checkbox is checked (in fact that is what the orginal intent was, but I think I talked Johan into not updating it even in normal mode for more speed). Fix takes a few days. Note if you reverse the coupler, you don't need a low IF BW because the rolloff isn't in the path. That's what we were going to take advantage of.
3) add a separate control to say to update it or not on ever sweep (more complicated, and who will ever find it? Takes several days to fix)
4) Add a separate, setable, forward average count for the Sc21 measurement, independent of the S11 and S21 (channel ) averaging. I like this one. Takes many more than a few days to fix.
Everyone welcome to join the new Keysight "define your favorite obscure SMC feature" contest.
你抓住了我们
为了加速SMC平均，我们只采用S22反向扫描的平均值的第一次扫描，然后对所有其他平均值使用if，这样我们就不必等待它。
Johan于10.25.02添加了此行为。
每当重新启动平均值时它都会更新。
所以，看它更新命中平均重启。
我们的想法是S22非常稳定，不需要进行平均，但Sc21阶段确实需要很多平均值，因此它不会更新S22的速度快1/3。
真正的驱动点是，如果客户正在测量下变频器并且下变频器输出处于频段的低端，而耦合器在该频段下滑，则IF需要很慢才能获得良好的结果，但扫描需要
永远，如果S22也有平均值。
告诉我你的想法;
这里有3种选择：1）保持原样。
现在工作，工作得更快，只需按平均重启重新扫描s22。
2）每次更新它，除非选中反向耦合器复选框（实际上这是原始意图，但我认为我谈到Johan即使在正常模式下也不更新它以获得更快的速度）。
修复需要几天时间。
请注意，如果反转耦合器，则不需要低IF BW，因为滚降不在路径中。
这就是我们要利用的东西。
3）添加一个单独的控件来说明是否更新它（更复杂，谁将找到它？需要几天时间才能修复）4）为Sc21测量添加一个单独的，可选择的前向平均计数，独立
S11和S21（通道）平均值。
我喜欢这一个。
修复需要花费几天时间。
欢迎大家加入新的Keysight“定义您最喜爱的模糊SMC功能”比赛。
以上来自于谷歌翻译
以下为原文
You caught us. In an attempt to speed up the SMC averaging, we only take the first sweep of the average for the S22 reverse sweep, and then use if for all the other averages so that we don't have to wait for it. Johan added this behavior in 10.25.02. It updates whenever the average is restarted. So, to see it update hit Average Restart.
Our thought is that the S22 is very stable, and doesn't need to be averaged, but the Sc21 phase does need lots of averages, and so it makes it 1/3 faster to not update S22. The real driving point for this was if a customer is measuring a down converter and the down converter output is in the low end of the band, where the coupler rolls off, the IF needs to be slow to get a good result but the sweep takes forever if the S22 has averages as well.
Tell me what do you think; here's 3 choices:
1) Leave it as it is. Works now, works faster, just hit average restart to resweep s22.
2) Update it every time, except when the reverse coupler checkbox is checked (in fact that is what the orginal intent was, but I think I talked Johan into not updating it even in normal mode for more speed). Fix takes a few days. Note if you reverse the coupler, you don't need a low IF BW because the rolloff isn't in the path. That's what we were going to take advantage of.
3) add a separate control to say to update it or not on ever sweep (more complicated, and who will ever find it? Takes several days to fix)
4) Add a separate, setable, forward average count for the Sc21 measurement, independent of the S11 and S21 (channel ) averaging. I like this one. Takes many more than a few days to fix.
Everyone welcome to join the new Keysight "define your favorite obscure SMC feature" contest.
举报
