cloud-pipeline
cloud-pipeline copied to clipboard
[HCS images] Ability to lock ranges of the channels
Background
Once the #2489 is implemented, users can preview HCS images, selecting plate, well, field, etc. to view. Also, they can configure the contrast for any of the available channel of the image. Currently, value of the channel contrast range is being set automatically (autofluorescence regimen, for the best displaying). This happens every time when user select another field or another well, or something else. But in some cases, user may want to "lock" the selected contrast range for the channel - so that selecting another field will not change that range. We should add such ability.
Approach
Add a new checkbox to the Settings panel of the preview pop-up, e.g.:
By click this checkbox, current shown ranges for each channel and their extreme values should be fixed:
- if user will change the field, for example, then the contrast settings for channels shall not be changed and shall remain the same (this shall apply to both - channel boundary values (min and max) and the configured range). I.e. if for the
channel1
boundaries were from 100 to 2000 and selected range from 150 to 370 - all these values should be applied for thechannel1
for any other selected field - channel sliders should become disabled
And when the user changes the field, for example, then channels contrast settings shall remain:
If user unticks the "Lock" checkbox - for the current shown field:
- autofluorescence regimen shall be enabled again and channels contrast settings shall be autoconfigured
- channel sliders should become enabled
@sidoruka @NShaforostov Persist channels state option implemented (#2542)
@rodichenko Bug: Channels settings aren't kept at changing view from Well view to Field view or back.
Channels settings aren't kept at changing view from Well view to Field view or back.
40915c3841c40c05cf01e41c3b761295aa292ed7 should fix that
Channels settings aren't kept at changing view from Well view to Field view or back.
40915c3 should fix that
Verified as fixed
Test case was created by #2786 and located here.