单独保存Sij数据还是.s***件？为什么会有所不同？

请举例说明它们的不同之处。
它们是彼此不同还是与显示值不同或两者不同？
您使用平滑或端口扩展或其他处理（数据/内存，公式编辑器）吗？
您使用什么方式保存（远程或前面板），当您单独保存时，文件类型是什么？
SnP有一种自动化，它将从校正的数据阵列中提取所有S参数，我认为没有增加处理（PNA代码和8753代码在这方面有点不同）。
如果从单个跟踪中保存Sij，则可以包含上述处理的效果。



     以下为原文

  Please give an example of how they are different.  Are they different from each other or different from the displayed value or different from both?

Are you using smoothing or port extensions or other processing (data/memory, equation editor)?  What means are you using to save (remote or front panel) and when you save individually, what is the file type?

SnP has a kind of automation that will pull all the S-parameters from corrected data-arrays, and I think without added processing (PNA code and 8753 code is a little different in that way).  If you save Sij from a single trace, it can have the effects of the processing above included.

嗨lham和Dr_joel，我在这里有同样的问题。
我想对测量数据进行一些数学运算，所以我决定将修正后的数据保存到touchstone文件中。
对于我的测试设置，我使用带有四个端口的E5071C NWA，并通过固件中的“Save to SnP”按钮将数据直接保存到S4P文件中。
它工作正常，但上次我将跟踪数据单独保存到单个CSV文件中，并且惊讶于有比S4P文件更多的小数。
例如，这里是我的S4P文件中有关单个参数的报价（S11）和单个频率，格式为LOG / Phase两种情况（仅LOG，未显示相位）：300000-1.408585e + 001引用的相同参数
CSV：300000-14.0858484053迹线上没有额外处理（仅完整的4端口OSLT校准）。
似乎S4P输出四舍五入到小于CSV的小数，可能为指数提供空间。
有没有办法在S4P输出中更改小数或禁用指数？
试金石格式本身不限于单一或双精度的单一格式以及指数的使用。
非常感谢任何提示或建议，最好的问候，蒂姆



     以下为原文

  Hi lham and Dr_joel,

I have the same issue here. I want to do some math operation on the measured data, so I decided to save the corrected data into touchstone files. For my test setup I use a E5071C NWA with four ports and save the data into S4P file direct through the "Save to SnP" button in firmware. It works fine, but last time I saved the trace data seperate into single CSV files and was surprised that there are more decimals than in the S4P file.

For example here is a quote from my S4P file for a single parameter (S11) and a single frequency, format is LOG/Phase in both cases (only LOG, no phase shown):

300000     -1.408585e+001     

The same parameter quoted from CSV:

300000     -14.0858484053

There has been no extra processing on the traces (only full 4 port OSLT calibration). It seems that the S4P output is rounded to fewer decimals than the CSV, maybe to give space for the exponent. Is there a way to change the decimals or disable the use of exponent in S4P output? The touchstone format itself is not limited to a single format like single or double precision and the use of exponent.

Thanks a lot for any hint or advise,
best regards,
Tim

由于差值在.000002 dB的范围内，我猜它对你实际做的任何事情都没什么影响。
迹线上的噪声可能是0.0001 dB的最佳情况，实际上2微伏是一个相当小的差异。
我可以问你真的在乎吗？
或只是好奇心。
我猜这段代码会做类似“如果它是以dB为单位只给小数点后的6位数”。



     以下为原文

  Since the difference is in the order of .000002 dB, I would guess that it is of very little consequence to anything you are actually doing.  The noise on the trace is probably on the order of 0.0001 dB best case, and really 2 microdB is a pretty small difference.  May I ask do you really care? or just curiosity.  I would guess that the code does something like "if it is in dB only give 6 digits after the decimal".

嗨Dr_joel，谢谢你的回复。
我同意你的看法，尽管数据格式不同，但差别很小。
不仅受dB影响的数据受到影响，而且线性和复杂数据也受影响。
我编写了一个转换工具，用于使用Octave和Bash计算混合模式s参数（四个端口，两个虚拟平衡 - 不平衡变换器）。
因此我使用NWA的四端口touchstone文件（* .S4P）作为输入。
我想知道为什么转换后的s参数与NWA中直接转换的值略有不同。
我想这是数据格式的差别。
我的方法是验证我的转换工具的输出与NWA中实现的转换。
为了确保我使用与NWA相同的输入数据，最好有一个包含所有小数的touchstone文件存储在NWA中。
可以将分离数据保存为16个CSV（S11，S12，S13，...，S44）并将它们组合成带有完整小数的touchstone文件。
但这是一种非常复杂的方式。



     以下为原文

  Hi Dr_joel,

thanks for your reply.

I agree with you that there is a very little difference though the different data format. Not only data in dB is affected, also linear and complex data.

I have written a conversion tool for calculating mixed-mode s-parameter (four ports, two virtual baluns) using Octave and Bash. Therefor I use the four port touchstone file (*.S4P) from NWA as input. I was wondering why the converted s-parameter differ a bit from the values converted directly in NWA. I guess it is the little difference though the data format.

My approach is to verify the output of my conversion tool against the conversion implemented in NWA. To be sure that I use the same input data as the NWA it would be nice to have a touchstone file with all decimals stored in NWA. There would be the way to save trace data seperate into 16 CSVs (S11, S12, S13,...,S44) and combine them to a touchstone file with full decimals. But this is a very complicated way.