[#793] feat: update feasible value quantile from 90th to 80th#794
Merged
wayangalihpratama merged 1 commit intostagingfrom May 1, 2026
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Updated the "feasible value" calculation logic across the stack to use the 80th quantile instead of the 90th. This change ensures that the targets displayed in Step 2 are more realistically achievable for farmer segments based on the uploaded data.
Key Changes
case_import_process_confirmed_segmentation.pyto calculatefeasible_valueusingvalues.quantile(0.8).EnterIncomeData.jsto inform users that feasibility is now calculated as the 80th quantile.CASE_MANAGEMENT_UX.mdand updatedGEMINI.md.Verification
quantile(0.8)passed.yarn lint) passed../check.sh) passed.