Repository navigation
Clarify likelihood implementation labels and menu priority - #37
Merged
Merged
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.
Make likelihood choices explicit and easier to scan: parenthesized JAX/Numba labels, hidden unspecified variants, and priority Delaunay, Rectangular, MGE, KNN, MGE Mass, Sersic. Keep one plain Sersic fallback for its unclassified latent tools, as requested; stored evidence and direct links retain their backend classification.
Scripts Changed
pulse/setup_browser.js: implementation labels, menu filtering and priority.Validation checklist
release validation incomplete: no rehearsal for current source; no development-blocking reason.Refs PyAutoLabs/PyAutoInsight#19. User authorized autonomous completion and merge on green; no library dependency.