-
Notifications
You must be signed in to change notification settings - Fork 43
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
update anomaly search backend #1295
update anomaly search backend #1295
Conversation
Does this mean we need to update this function as well? |
Nope! That looks great |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @BradleySappington this looks great.
@bhilbert4 I spoke with @BradleySappington about testing the code and he performed a couple of queries before and after merging his code in to verify the results were the same. Would you mind trying the same to verify since you are more familiar with the JWST data products. Once that is done, I can go ahead and merge it in! |
@BradleySappington @mfixstsci I just pulled this onto the dev server, restarted the service, and tried some queries. The results I'm getting back don't make any sense though. Is there something else I need to do to switch the dev server over to look at the correct database or something? |
Comment marking that this has been resolved |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Spot tests on the dev server gave the expected results.
Now that we have a postgres DB, use
union
andintersect
in standard backend query result filtering