You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue aims at developing a routine to randomly control the way that a studyList.json file is generating the Patient ID, respectively. We need to force the studyList.json file to generate only N patients, from a set of M patients. The set of M patients does not need any autonomous control. Since we can control it manually by only uploading those M images to the DICOM server.
The issue will be of great importance for #5 and #6 issues of prototype-heatmap repository. Thus, we will bring the issues together, as they are connected and dependent.
Explaining the issue in detail, when generating the studyList.json file information, i.e., following this behavior on the loadList.js file. For instance, we need to chance it triggering randomly the generation of the studyList.json file for just three patients. Therefore, the UI will only show the three patients, even if the studies/ folder has more patients. This is the naïve, yet easy and quick, solution for the problem. The random generation of the studyList.json file will just be updated each time the server runs. Therefore, we can control error occurrences and solve during user tests.
The text was updated successfully, but these errors were encountered:
From a high-level decision, we establish to not consider the presented issue. The reasons are simple, as it was better to create and generate a list of patients on several .txt files. The repository of those .txt files can be found on the named finders-datasets repository. By going through the results/users/uta7 folder, you will find what you need. Therefore, the issue will be Closed.
This issue aims at developing a routine to randomly control the way that a
studyList.json
file is generating the Patient ID, respectively. We need to force thestudyList.json
file to generate only N patients, from a set of M patients. The set of M patients does not need any autonomous control. Since we can control it manually by only uploading those M images to the DICOM server.The issue will be of great importance for #5 and #6 issues of
prototype-heatmap
repository. Thus, we will bring the issues together, as they are connected and dependent.Explaining the issue in detail, when generating the
studyList.json
file information, i.e., following this behavior on theloadList.js
file. For instance, we need to chance it triggering randomly the generation of thestudyList.json
file for just three patients. Therefore, the UI will only show the three patients, even if thestudies/
folder has more patients. This is the naïve, yet easy and quick, solution for the problem. The random generation of thestudyList.json
file will just be updated each time the server runs. Therefore, we can control error occurrences and solve during user tests.The text was updated successfully, but these errors were encountered: