Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ProCoDA data smoothing #303

Open
annabel48lin opened this issue Apr 10, 2021 · 0 comments
Open

ProCoDA data smoothing #303

annabel48lin opened this issue Apr 10, 2021 · 0 comments
Assignees
Labels
feature Feature request/addition low Low priority

Comments

@annabel48lin
Copy link
Contributor

From Kevin S:

Is your feature request related to a problem?

  • there are ProCoDA read errors (either extremely large or small numbers)
  • data is too high resolution -- only need a few points

What kind of a solution would you like?

Want a method to smooth multiple columns with one call and the same parameter, and also remove faulty values before smoothing.

What alternatives have you considered?

The way I am smoothing it now is by grouping x number of data points into one by averaging. Before I do any data averaging I need to rid the data of those read errors because they would skew the data.

Is there anything else we should know?

Full messages:

Right now I am dealing with 40+ columns of data from ProCoDA. The way I am smoothing it now is by grouping x number of data points into one by averaging. I also have to deal with procoda errors which appear as extremely large or small numbers. I would like to smooth multiple columns with one call and the same parameter.

My raw data from ProCoDA usually spans days and is being logged every 5 seconds, so I have a lot of resolution. However, I don't need such fine resolution for outputting graphs or doing some of my analysis of that data so I need to turn 40,000 points to maybe 400. However, one of my instruments has given me some issues and produces a lot of read errors in ProCoDA. Those errors usually are logged as huge numbers or very very small numbers or a -9999 value. Before I do any data averaging I need to rid the data of those read errors because they would skew the data.

@annabel48lin annabel48lin added low Low priority feature Feature request/addition labels Apr 10, 2021
@annabel48lin annabel48lin self-assigned this Apr 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Feature request/addition low Low priority
Projects
None yet
Development

No branches or pull requests

1 participant