Save peak detection inputs - #55
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
This pull request updates how user inputs for automatic peak detection are handled and persisted in the
AutoGrowth/2_turbiostat.pyfile. The main improvements ensure that user-edited values for minimum peak height and minimum distance between peaks are properly saved and restored when navigating between pages, but only after an analysis has actually been run.Persistence and restoration of peak detection parameters:
minimum_peak_heightandminimum_distanceare now loaded fromst.session_stateif available, ensuring that previously entered values are restored when returning to the page.minimum_peak_heightandminimum_distanceare explicitly saved back tost.session_state, so they persist across page switches.User input handling improvements:
minimum_peak_heightandminimum_distance) now use the restored session state values, rather than always defaulting toNoneor300.These changes improve the user experience by ensuring that edits to peak detection parameters are not lost when navigating away and returning, but only after an analysis has been run.