Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Hi Gabriel,
could you provide an example (vi!) showing this behaviour - this way we should be able to reproduce your problem...
could you provide an example (vi!) showing this behaviour - this way we should be able to reproduce your problem...
Hi Gabriel,
the problem is: you're using express vis...
I changed your vi to show the behaviour: the filter is now called in a loop. In the first iteration the result looks fine, but in the second you see the starting glitch! This is due to the buffering behaviour of the express vi! The express vi is buffering values to allow the running mean - when the next iteration starts you still have values from last iteration in this buffer resulting in this peak at start of signal...
To solve this:
- easiest: make your own running mean (see attachment) (and avoid express vis
)
- prepend dummy data on your input array (twice the size of the running average...)
the problem is: you're using express vis...
I changed your vi to show the behaviour: the filter is now called in a loop. In the first iteration the result looks fine, but in the second you see the starting glitch! This is due to the buffering behaviour of the express vi! The express vi is buffering values to allow the running mean - when the next iteration starts you still have values from last iteration in this buffer resulting in this peak at start of signal...
To solve this:
- easiest: make your own running mean (see attachment) (and avoid express vis
)- prepend dummy data on your input array (twice the size of the running average...)
Hi Gerardo,
here's a snippet of that VI:
The lower for loop was my suggestion for a running average. The upper while loop is for demonstration of the OPs problem...
