-
Notifications
You must be signed in to change notification settings - Fork 17
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
Window/Unwindow #44
base: main
Are you sure you want to change the base?
Window/Unwindow #44
Conversation
added window and unwindowing functionality
@ubsuny/cp1-24 Who wants to review this? This should be reviewed and merged asap |
@laserlab I can review this |
Here are some suggestions:
Let me know if, @abruns123 , you run into any issue. |
Adjusted my code to make it run correctly and fix pylint errors
Added test function for window/unwindow
Alright, I updated the pylint stuff and made sure to add unit test functions. Also included a few fixes where the code wasn't running as intended. |
@Cosmos491 Please finish your review so this can get merged |
@abruns123 Please resolve merge conflicts |
merge conflicts should be resolved now |
There seems to be a syntax issue with the line starting with """test the powerspectrums length and type of export""". This could happen if the line is misplaced or if it is intended as a docstring but is not properly formatted. However, I also think that Instead of passing data as a parameter, define it within each test or use a pytest fixture to initialize shared data across tests. |
@SchrodingersStruggle @abruns123 pytest issues have to be fixed before this can be merged |
trying to fix pytest
Okay, all the pytest errors should be fixed now |
While the pytest is running now we gained a lot of inting error due to all the unnecessary triple quotes that were inserted. This has to be fixed. |
@Cosmos491 you still didn’t approve or reject the PR … |
I fixed the triple quotes. Some have to be there to make sure certain parts of the code that are in there which I didn't write aren't running as they produce pytest errors. |
The pytest seems to run fine, however there are some issues with pylint:
@abruns123 Let me know if you need any clarification regarding the suggestions. |
You actually still have most tests commented out that were in there before that run without issues. That is not adding to files this is removing functionality and cannot be merged |
But it was those sections of code that were causing the pytest errors. What am I supposed to do with them? |
causing errors was commented out.
the current test_preparation.py does not generate any pytest errors, so either you changed something that lead to failing or you are not using the most current version. |
Alright, I copy and pasted in the most up to date pytest file. pytest check works. There are some pylint errors, but it should be mergeable now |
Linting
Have not tested linting yet. Will update
Contents
functions which describe the windowing functions
Anyone may review this.