In the workshop day, a common problem in reprocessing is handling the pqc/mqc files. Although the UI allow cleanup of QC/replay, the session files are always re-loaded and create barriers in the workflow. Some people also need to delete these files to reprocess, and such some previous work can be lost.
The task here involves reviewing the usage and cases of these files and allow the user to ignore/pick a session file, or even ignore/pick a result save in these files and reuse/remove/edit the content completely.
Moreover, these files need to be reviewed in terms of storage/structure of the results. Maybe a centralized file per instrument would be best, instead of a multitude of them (ppp/mqc/pqc).
Some topics:
[ ] Pop-up window to acknowledge the use of the session files by the user. Allow buttons to Ignore pop-up for following files from sub-sequent instruments, Ignore session files altogether, or edit/cherry-pick results within them.
[ ] avoid dealing ith mqc/ppp file deletion for reprocessing. This will improve users re-processing workflow.
[ ] Allow cherry-picking the results within the session files. Help with "fearless" processing.
[ ] Store a "current" configuration, which is for the current session or the default loaded options when opening a session file.
[ ] Allow a menu to edit the session files "current" configuration.
[ ] Adapt structures accordingly.
Some possible improvements:
[ ] Be more certain in regards to the instrument file ownership of a ppp/mqc/pqc file. Currently, we use the filename, but if the filename content changes, it's likely the file content will be invalid.
[ ] store a hash inside the session file & match hash to file content.
[ ] Save ppp/mqc/etc results by datestamp. This would allow "fearless" processing - no need to be worried about losing your manualQC, everything is saved by timestamp in the session files.
In the workshop day, a common problem in reprocessing is handling the pqc/mqc files. Although the UI allow cleanup of QC/replay, the session files are always re-loaded and create barriers in the workflow. Some people also need to delete these files to reprocess, and such some previous work can be lost.
The task here involves reviewing the usage and cases of these files and allow the user to ignore/pick a session file, or even ignore/pick a result save in these files and reuse/remove/edit the content completely.
Moreover, these files need to be reviewed in terms of storage/structure of the results. Maybe a centralized file per instrument would be best, instead of a multitude of them (ppp/mqc/pqc).
Some topics:
[ ] Pop-up window to acknowledge the use of the session files by the user. Allow buttons to Ignore pop-up for following files from sub-sequent instruments, Ignore session files altogether, or edit/cherry-pick results within them.
[ ] avoid dealing ith mqc/ppp file deletion for reprocessing. This will improve users re-processing workflow.
Some possible improvements: