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

Add option to keep data in PSD Data Structure #26

Open
jdpigeon opened this issue May 16, 2018 · 4 comments
Open

Add option to keep data in PSD Data Structure #26

jdpigeon opened this issue May 16, 2018 · 4 comments

Comments

@jdpigeon
Copy link
Contributor

currently, when going from Epoch to PSD we leave behind the data array that contains the raw EEG data. Some people may want to keep this around in their processing pipeline, but for sake of efficiency, maybe we should just make this an option?

@ruut12
Copy link

ruut12 commented Jul 30, 2019

yes please :)
Any workaround atm?

@kylemath
Copy link

kylemath commented Dec 5, 2019

yes @jdpigeon same problem we are just hitting, want to plot raw data and spectra side by side for example, how do we pull out data from the intermediate pipe steps

@beebus
Copy link

beebus commented Oct 23, 2020

Would the tap() operator (formerly the do() operator) work for this?

I just finished a tutorial on RxJS and I used the following code which pulled data from an intermediate pipe step, using the tap() operator. Now, it just console.logged it, but I assume that you could do other things with that data using the tap() operator.

this.results$ = this.searchSubject$
.pipe(debounceTime(200))
.pipe(distinctUntilChanged())
.pipe(tap(x => console.log('tap', x)))
.pipe(switchMap(searchString => this.queryAPI(searchString)));

You can see the results of this in the console, each time it logs "tap ... ".
Picture1

@beebus
Copy link

beebus commented Oct 23, 2020

And if the question is "How do we go back to that data that was in those intermediate steps?", then I would think either logging the data to a database that can be retrieved later or (if possible) some sort of repeating of those same pipe steps to get the same data again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants