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

Add curation keyboard shortcuts #366

Merged
merged 6 commits into from
Feb 7, 2024
Merged

Add curation keyboard shortcuts #366

merged 6 commits into from
Feb 7, 2024

Conversation

adamltyson
Copy link
Member

@adamltyson adamltyson commented Jan 16, 2024

Requires #365 to be merged first

Closes #364

@adamltyson adamltyson requested a review from a team January 16, 2024 17:46
Copy link
Member

@alessandrofelder alessandrofelder left a comment

Choose a reason for hiding this comment

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

Looks good!

Just making a note here for our future selves and other interested people, that this PR mainly

  • adds keyboard shortcuts
    but also
  • replaces local functions with brainglobe-utils equivalents
  • removes tests for those functions
  • makes tiny improvements to explicitness of code
  • adds a "overwrite existing data?" warning.


self.__delete_existing_saved_training_data()

def __delete_existing_saved_training_data(self):
Copy link
Member

Choose a reason for hiding this comment

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

For my understanding, why do functions in the file start with two underscores?? Worth an issue if it's not intended.

Copy link
Member Author

Choose a reason for hiding this comment

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

Double underscores are as close to private as you can get in Python. Not sure why they're used here and not anywhere else in BrainGlobe though.

Copy link
Member

Choose a reason for hiding this comment

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

Ah cool! Didn't know. From reading that it sounds like the use case is mainly to make it impossible to override this in subclasses. We currently don't have any subclasses of CurationWidget, and for consistency it would be good to not use it here, but then again not sure it's enough of a priority right now 🤔

TLDR I suggest leaving for now?

Copy link
Member Author

Choose a reason for hiding this comment

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

Fine by me.

@adamltyson
Copy link
Member Author

The tests are failing now, but is this due to #368?

@alessandrofelder
Copy link
Member

alessandrofelder commented Feb 6, 2024

The tests are failing now, but is this due to #368?

Yup, presumably. Just to be sure, shall we wait with merging until we resolve that?

@adamltyson
Copy link
Member Author

Yeah there's no rush for this

@willGraham01 willGraham01 merged commit 25b39a8 into main Feb 7, 2024
14 checks passed
@willGraham01 willGraham01 deleted the curation-shortcuts branch February 7, 2024 14:27
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.

[Feature] Add keyboard shortcuts to the curation interface
3 participants