Skip to content

Added ExecuteChromDeconvolution Option to Control Chromatogram-Based Deconvolution#583

Merged
Bujee415 merged 2 commits intomasterfrom
feature/deactivate-ms2dec-button
Jun 13, 2025
Merged

Added ExecuteChromDeconvolution Option to Control Chromatogram-Based Deconvolution#583
Bujee415 merged 2 commits intomasterfrom
feature/deactivate-ms2dec-button

Conversation

@YukiMatsuzawa
Copy link
Copy Markdown
Contributor

PR Classification

New feature to enhance chromatogram deconvolution functionality.

PR Summary

This pull request introduces a new boolean property ExecuteChromDeconvolution to control the execution of chromatogram-based deconvolution. It includes updates to the model, view model, and UI to support this feature.

  • ParameterBase.cs: Added ExecuteChromDeconvolution property with a default value of true.
  • DeconvolutionSettingModel.cs: Integrated ExecuteChromDeconvolution into the model and updated the Commit method to save its state.
  • DeconvolutionSettingView.xaml: Added a checkbox in the UI for users to enable or disable ExecuteChromDeconvolution.
  • DeconvolutionSettingViewModel.cs: Created a reactive property for ExecuteChromDeconvolution to synchronize with the model and included it in error observation logic.

Changed `ExecuteChromDeconvolution` and `ExecuteQ1Deconvolution` from read-only to read-write properties, allowing modification after initialization. Default values remain unchanged.

# Conflicts:
#	src/MSDIAL5/MsdialCore/Parameter/ParameterBase.cs
Updated `DeconvolutionSettingModel.cs` to include new boolean properties `ExecuteChromDeconvolution` and `ExecuteQ1Deconvolution`, allowing users to control chromatogram-based and Q1 axis peak deconvolution. Modified the `Commit` method to save these settings.

Enhanced `DeconvolutionSettingView.xaml` with checkboxes for the new settings, including tooltips for user guidance.

Synchronized the new properties in `DeconvolutionSettingViewModel.cs` to ensure UI changes reflect in the model, maintaining validation consistency.
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR introduces a new boolean property, ExecuteChromDeconvolution, to enable or disable chromatogram-based deconvolution. Key changes include:

  • Adding the property to ParameterBase with a default value of true
  • Integrating the property in the model and view model with reactive binding
  • Updating the UI by introducing a checkbox to control the deconvolution execution

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File Description
src/MSDIAL5/MsdialGuiApp/ViewModel/Setting/DeconvolutionSettingViewModel.cs Added reactive binding for ExecuteChromDeconvolution
src/MSDIAL5/MsdialGuiApp/View/Setting/DeconvolutionSettingView.xaml Introduced a checkbox for ExecuteChromDeconvolution (label text may cause confusion)
src/MSDIAL5/MsdialGuiApp/Model/Setting/DeconvolutionSettingModel.cs Integrated ExecuteChromDeconvolution in Commit and LoadParameter methods
src/MSDIAL5/MsdialCore/Parameter/ParameterBase.cs Added ExecuteChromDeconvolution with a default value to the parameter definition
Comments suppressed due to low confidence (1)

src/MSDIAL5/MsdialGuiApp/View/Setting/DeconvolutionSettingView.xaml:85

  • The label 'Run RT deconvolution:' may be misleading given that the new property ExecuteChromDeconvolution controls chromatogram-based deconvolution. Consider updating the label to more clearly reflect the intended feature, such as 'Execute Chromatogram Deconvolution:'.
<ui:LabeledContent PrependLabel="Run RT deconvolution:"

@Bujee415 Bujee415 merged commit 38fc942 into master Jun 13, 2025
9 checks passed
@Bujee415 Bujee415 deleted the feature/deactivate-ms2dec-button branch June 13, 2025 10:46
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.

3 participants