-
Notifications
You must be signed in to change notification settings - Fork 37
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
Adding in new function #845
Conversation
ajsockol
commented
Jul 17, 2024
•
edited
Loading
edited
- Closes #xxxx
- Tests added
- Documentation reflects changes
- PEP8 Standards or use of linter
- Xarray Dataset or DataArray variable naming follows 'ds' or 'da' naming
pull request
pull request
making my branch updated to current act branch
@ajsockol Thanks for the PR! I added some review comments. Also could we add unit tests to this PR as well for the new code? |
I added all the changes you mentioned except the testing. I'll add that next! |
Okay, I've added the tests. Now to just figure out why the linting keeps failing |
@ajsockol Can you try installing pre-commit? It should help with the linting issues. I'm also trying to find out why the test_arm_qc tests are failing |
It should be in your within your main ACT directory you can run pre-commit install Then, when you commit, it will auto-lint and fix where needed. |
@kenkehoe I'm still trying to familiarize with QC code of ACT, but do you possibly know why this PR might be failing the ARM QC tests? |
@mgrover1 when i try to run |
@ajsockol Maybe try pre-commit install from within the act directory no . |
@zssherman I know why the QC test is failing. We use a production DQR to test the functionality of the ARM DQR web-service. The DQR used was reprocessed so it is now not returned in the API call. I have a fix for this in my current PR. It's a simple fix if we want to include it in this PR to allow it to pass the tests. In act.tests.qc.test_arm_qc.py change line 15 to: ds = add_dqr_to_qc(ds, assessment='Reprocessed,Suspect,Incorrect') |
@kenkehoe Ah makes sense! Thanks for the info! We could always wait to have your PR merge in and then can rerun the tests here. |
Okay I got things figured out and was able to push changes through SSH. It looks like what's failing now are the arm_qc tests |
@ajsockol Cool, yeah looks like the linter etc are passing. Ken's PR fixes that QC issue so we can wait for that one to get approved then once its merge rerun the tests here. |
Okay, I copied and pasted a fix from Ken for one of the tests that was failing, but there is still one test failing from tests/discovery/test_asos.py::test_get_region that seems to be something out of my hands. @zssherman do you know what might be going wrong there? |
@ajsockol It is a connection error, i'll rerun the tests which will fix it. |