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

Update GUI #80

Merged
merged 24 commits into from
Oct 10, 2024
Merged

Update GUI #80

merged 24 commits into from
Oct 10, 2024

Conversation

rnmitchell
Copy link
Contributor

Reformatting GUI and exploring interactive plots.

@rnmitchell rnmitchell marked this pull request as ready for review October 10, 2024 13:59
@rnmitchell
Copy link
Contributor Author

rnmitchell commented Oct 10, 2024

This is ready for review @standage. I want to address the warning that lusSTR is throwing in the filter step, but it's proving to be a little bit more challenging than I thought, so figured this could be merged first since it's unrelated to the warning message.

Copy link
Member

@standage standage left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Functional review was great. Thanks for the walkthrough the other day.

A lot of code changes appear to be related to autoformatting.

I have a couple questions and requests: see below.

The GUI code is a bit unwieldy in its current state, as we discussed. I'll take a crack at refactoring soon.

Comment on lines -149 to +151
profile = profile[profile.allele_type == "real_allele"]
profile = profile.query("allele_type == 'Typed'")
else:
profile = profile[profile.allele_type != "BelowAT"]
profile = profile.query("allele_type != ['BelowAT', 'Deleted']")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you make these changes to get rid of the pandas warnings? Because functionally, they look very similar.

I will say though, I was unaware that you could use list syntax in a query string! TIL

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, I changed it to use a list since it needs to remove both BelowAT and Deleted sequences. I did it in line 149 just to be consistent in the code.

Comment on lines 259 to 260
filtered_df = profile[profile.allele_type != "BelowAT"]
# filtered_df = profile.loc[([profile.allele_type != "BelowAT"]) & ([profile.allele_type != "Deleted"])]
filtered_df = profile.query("allele_type != ['BelowAT', 'Deleted']")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please delete commented out code or fix.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

gah yup.

@standage standage merged commit 32554e1 into master Oct 10, 2024
2 checks passed
@standage standage deleted the update_gui branch October 10, 2024 17:57
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

Successfully merging this pull request may close these issues.

2 participants