Skip to content

Add the ability to disable post-processing for filterable modules#58

Merged
gabegma merged 8 commits intodevfrom
ggm/disabling-post-processing
May 5, 2022
Merged

Add the ability to disable post-processing for filterable modules#58
gabegma merged 8 commits intodevfrom
ggm/disabling-post-processing

Conversation

@gabegma
Copy link
Contributor

@gabegma gabegma commented Apr 29, 2022

Description:

Add a module option to disable post-processing for all filterable modules. This will allow a new toggle in the control panel to see metrics/top words/confusion matrix/histogram without post-processing.

Checklist:

You should check all boxes before the PR is ready. If a box does not apply, check it to acknowledge
it.

  • PRE-COMMIT. You ran pre-commit on all commits, or else, you
    ran pre-commit run --all-files at the end.
  • FRONTEND TYPES. Regenerate the front-ent types if you played with types and routes.
    Run cd webapp && yarn types while the back-end is running.
  • USER CHANGES. The changes are added to CHANGELOG.md and the documentation, if they impact
    our users.
  • DEV CHANGES.
    • Update the documentation if this PR changes how to develop/launch on the app.
    • Update the README files and our wiki for any big design decisions, if relevant.
    • Add unit tests, docstrings, typing and comments for complex sections.

@gabegma gabegma force-pushed the ggm/disabling-post-processing branch from c3ab905 to a14790d Compare April 29, 2022 02:18
@gabegma gabegma requested review from Dref360 and lindsaydbrin April 29, 2022 02:18
Copy link
Contributor

@lindsaydbrin lindsaydbrin left a comment

Choose a reason for hiding this comment

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

LGTM! This touches a lot of code that I'm not super familiar with, so if you have any uncertainty it might be worth validating with @Dref360, but otherwise I think it makes sense and it's great functionality!

@lindsaydbrin
Copy link
Contributor

Maybe we should add something to the changelog for this?

Copy link
Contributor

@Dref360 Dref360 left a comment

Choose a reason for hiding this comment

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

LGTM, some minor comments

@gabegma gabegma changed the base branch from main to dev May 5, 2022 15:06
@gabegma
Copy link
Contributor Author

gabegma commented May 5, 2022

@Dref360 can you review my latest commit (not the merge) since I made a few additional changes?

Copy link
Contributor

@Dref360 Dref360 left a comment

Choose a reason for hiding this comment

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

LGTM

@gabegma gabegma merged commit a029dbd into dev May 5, 2022
@gabegma gabegma deleted the ggm/disabling-post-processing branch May 5, 2022 18:58
dataset_split_manager: DatasetSplitManager = Depends(get_dataset_split_manager),
pipeline_index: Optional[int] = Depends(query_pipeline_index),
pagination: Optional[PaginationParams] = Depends(get_pagination),
without_postprocessing: bool = False,
Copy link
Contributor

@JosephMarinier JosephMarinier May 17, 2022

Choose a reason for hiding this comment

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

Sorry, I am late to the party, I didn't realize that was getting merged.
Everywhere this query parameter is defined, it should have an alias to make it camelCase, like the others, for example smartTags, dataActions, or confidenceMin/Max).
@nandhinibsn, could you add those in your PR?

Suggested change
without_postprocessing: bool = False,
without_postprocessing: bool = Query(
False, title="Without Postprocessing", alias="withoutPostprocessing"
),

Copy link
Contributor

Choose a reason for hiding this comment

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

I agree. I can add those alias on the UI.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oh so sorry, thanks! I should have tagged you in that PR.

Copy link
Contributor

Choose a reason for hiding this comment

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

No-no-no, no need to be sorry. One step at a time. 👍

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.

5 participants