-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[No.129]Function with the ability to select cells (Data filter B… #536
base: develop-main
Are you sure you want to change the base?
Conversation
- make workflow/node's run status constant. - rename some symbols
- refactor node pickle data operation - clarification of processing, improvement of error handling, etc.
- refactor SmkStatusLogger operation - improved node status updates on errors throughout workflow
- refactor ConfigWriter modules - clarification of processing and simplification of code
- refactor workflow pid file processing - refactor cancel workflow processing
frontend/src/components/Workspace/FlowChart/FlowChartNode/AlgorithmNode.tsx
Show resolved
Hide resolved
frontend/src/components/Workspace/FlowChart/FlowChartNode/AlgorithmNode.tsx
Show resolved
Hide resolved
…w' into feature/516
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Currently the filter box has bugs in the input
- Cannot delete "0"
- Cannot input commas into ROI
- Actual data dims should be used for placeholders
- Filter box parameters are not passed to the subsequent analysis. This is the whole point of the filter box. If dim 1:500 is selected, only that data should be used for the next step of analysis. This will allow users to save time by only performing analysis on certain important sections of the data. For PCA it will also change the results. This is a top priority.
- Fluorescence and ROI windows should be shown simultaneously and side-by-side (this is lower priority as user could still manage to use the filter box without this. However, it was still in the request)
<InputDim | ||
title="ROI" | ||
name="roi" | ||
placeholder="1:23,50:52" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The input does not allow this input style "1:23,50:52"
Comma is not possible
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@milesAraya I have fixed it.
<InputDim | ||
title="Dim 2" | ||
name="dim2" | ||
placeholder="1:128" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you input "1:0", you cannot delete the 0 using backspace. You need to highlight the whole text and delete, or add some more numbers and then delete those
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This conversation will be unresolved because the reviewer has not yet checked it.
*The reviewer should resolve the conversation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@milesAraya I have fixed it.
return ( | ||
<Box> | ||
<Box mb={1}>{title}</Box> | ||
<Input inputProps={{ style: { textAlign: "center" } }} {...p} /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think in the powerpoint request, there were 2 side-by-side windows, with ROI and fluorescence both visible.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think in the powerpoint request, there were 2 side-by-side windows, with ROI and fluorescence both visible.
@milesAraya
Currently, I see that the description in the PowerPoint about the UI is similar to the output UI, so I am reusing this UI for now. If we follow the PowerPoint layout, the UI will only display two side-by-side panels, right? Because the output UI has quite a few tabs.
|
||
const { dim1, dim2, dim3, roi } = useMemo(() => { | ||
return { | ||
dim1: getData(dataFilterParams?.dim1), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be good if these dimensions, from the real data, are used in the placeholders
placeholder="1:1000" -> placeholder="1:dim3"
@@ -48,6 +49,19 @@ export const algorithmNodeSlice = createSlice({ | |||
} | |||
} | |||
}, | |||
updateFilterParams: ( | |||
state, | |||
action: PayloadAction<{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When i choose filter settings, these do not seem to be passed on to the next nodes.
Here i select ROI 1:30
But in the ETA visualise window all the ROI are present (e.g. 121). Only ROI 1:30 should be present
And the fluorescence dim was selected to be 1:500, but in the flourescence window 1:2000 are still visible
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@milesAraya
When you change the filter parameters, please run it again to update the data. The changes will not be reflected until you run it again.
) | ||
|
||
return ( | ||
<Box display="flex" gap={2} textAlign="center" pt={2}> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you place the following buttons
- APPLY
- CANCEL
- RESET
Design documents are being updated
status !== NODE_RESULT_STATUS.SUCCESS || isParentParamsUpdated | ||
} | ||
> | ||
Filter |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If I apply a Filter, can I have the Node's Hilight applied only to the Filter button? (Node itself will remain white)
The design document has been updated.
If the implementation is going to be complicated, please contact us.
|
||
return ( | ||
<Box display="flex" gap={2} textAlign="center" pt={2}> | ||
<InputDim |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Validate must be applied to input values
- Numeric values start from 1
- Compare the value to a larger or smaller value
- Check the upper limit of the numerical value
- This requires obtaining the upper limit of the actual data. If this is difficult to handle, please contact us.
[No.129]Function with the ability to select cells (Data filter Button) #516