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

Processing #156

Open
lenn19 opened this issue Nov 24, 2021 · 3 comments
Open

Processing #156

lenn19 opened this issue Nov 24, 2021 · 3 comments

Comments

@lenn19
Copy link

lenn19 commented Nov 24, 2021

Hello,
I'm trying to use the suspect processing tools. At the moment only the water suppression works. When I try to run frequency correction I always get an error with **kwargs. What arguments are supposed to be written there? Do you have any example code for using the other processing tools provided by suspect?

Thank you for your help!

@bennyrowland
Copy link
Member

@lenn19 thanks for trying out suspect. I have just uploaded a new page on the documentation: https://suspect.readthedocs.io/en/latest/notebooks/consensus_playground.html. It covers all the standard parts of the processing pipeline, please check it out and then let me know if you still have any problems.

@lenn19
Copy link
Author

lenn19 commented Nov 30, 2021

@bennyrowland thanks for your reply.
In your demo notebook I struggle to use the channel combination. With data = data[:, 1] you reduce the dimension of the data to 2 and delete the 32. If I then try to execute noise = data[:,:, -noise_points:] I get the error, that data only has 2 dimensions but 3 are necessary. I think its my fault and I'm getting something wrong, but I would appreciate your help.

Cheers

@bennyrowland
Copy link
Member

@lenn19 what kind of data are you starting with (from which manufacturer and in which format)? That will make a difference to the kind of processing required. I realised that the demo notebook had somehow been run out of order and so some of the data was not correct - please check it again now as it is re-run and totally correct, so hopefully easier to follow.

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

2 participants