Bug in Export measurement as text with custom smoothing

[archiez]

I have 1M Sweep measurement and want to export it for further manipulation. If I export it with no smoothing, I will get 1.6MB data (54627 lines), if I export it with 1/3 smoothing, I will only get 45KB data (1526 lines). If I use API /measurements/{id}/eq/frequency-response, it will give me the same results. This is tested on version V5.40 beta 77 and V5.31.3.

V5.20.13 has no such issue, but it doesn't support API so I didn't try the API.

Any workaround?

 

[archiez]

V5.30.9 has the issue.

 

[John Mulcahy]

I have 1M Sweep measurement and want to export it for further manipulation. If I export it with no smoothing, I will get 1.6MB data (54627 lines), if I export it with 1/3 smoothing, I will only get 45KB data (1526 lines).

That's not a bug. All smoothed data in recent builds is log spaced.

 

[archiez]

That's not a bug. All smoothed data in recent builds is log spaced.

Is there any way to get full smoothed data like V5.20.13? My calculation is based on full data set.

 

[John Mulcahy]

No, but you could carry out your own smoothing on unsmoothed data.

 

[archiez]

No, but you could carry out your own smoothing on unsmoothed data.

Even a pro version couldn't support that?

 

[John Mulcahy]

I don't understand why anyone would want that, the data would be massively oversampled. The response is the same either way.

 

[archiez]

I feel adding a checkbox(or a flag in API) to enable/disable log space is just a piece of work. Hope the Pro version can support that.

 

[John Mulcahy]

V5.40 and later V5.3 builds use log spaced data internally for any smoothed response, there is no linear spaced smoothed data.