-
Notifications
You must be signed in to change notification settings - Fork 1
User Tests
Home | Installation Guide | User Guide | Admin Guide | User Tests
FOR RTTQA AND ARTNET TESTERS:
Before starting the User Tests, please read carefully the Overview and Requirements and technical details. The XNAT Overview is useful for navigating XNAT
Here you can find an extensive list of User Tests that demonstrate the functionality of DASHER, and will test that it is working correctly on your system. We have provided data for performing these tests see this page for instructions how to download this.
We suggest you first complete the tests using the provided data, which we know should work correctly with DASHER. However, we would also like you to repeat the tests using 'dummy datasets' created using your own Treatment Planning Systems (TPS), e.g. from phantom scans. It is important that the header information in the dummy data resembles real data as much as possible, e.g. by including dummy information for all of the patient details that are usually present (name, DOB, etc.). The dummy datasets should not be anonymised/pseudonymised before being imported to DASHER. If you have suitable phantom scans from a variety of modalities (e.g. CT, MRI, PET) it would be very useful if you could test DASHER with these data as well. Testing DASHER with a wide variety of data from different scanners and TPS is the only way to ensure DASHER will work with data from different systems (and in particular those used in your hospital).
Please work through these tests and report any issues or comments via DASHER gitlab repo Issues page.
When reporting an issue, please include your xnat.cfg file, your system setup (OS, memory, cpu etc) and the output to:
docker image ls
docker ps
Details of the different User Tests can be found via the links below. It is suggested to perform the tests in order, but it is not necessary to perform all the tests in a single session. The initial installation is part of the tests (tests no. 2-3) and may require a person with background knowledge of the local IT system. This may also be the case for test 17 "restarting docker". Those tests are marked in the table below with "IT support required". The other tests are aimed for users who will interact with the system on a day-to-day basis (including trial/user administration etc.).
No. | Name of test | IT support required |
---|---|---|
1. | Download Test Data | |
2. | Installing DASHER | X |
3. | Installing Plugins | X |
4. | Adding Clinical Trial | |
5. | Creating a New User | |
6. | Importing Data into DASHER | |
7. | Pseudonymising Data 1 | |
8. | Export Pseudonymised Data Locally | |
9. | Upload Data (XSync) | |
10. | Import - DICOM push | |
11. | Import - Duplicate | |
12. | Import - Single RTSTRUCT | |
13. | Import - Quarantine | X |
14. | Pseudonymise - Edits | |
15. | Pseudonymise - Missing structure | |
16. | Pseudonymise - Local research | |
17. | Restart docker | X |
Navigate: Home | Installation Guide | User Guide | Admin Guide | User Tests
New Pages:
- Test Release Version 4 Notes
- First time install on Windows
- First time install on Linux
- Updating DASHER on Windows
- Updating DASHER on Linux
- Editing xnat.cfg
- Building DASHER on Windows
- Building DASHER on Linux
- Installing the Processing Pipelines
- Setting up XSync
- Troubleshooting
- Logging in to the Servers
- Overview of DASHER
- Importing Data into DASHER
- Pseudonymising Data
- Uploading Data to a Remote Server
- Exporting Data from DASHER
- The QUARANTINE Project
- Create and Edit Users
- Adding Clinical Trials
- Managing the QUARANTINE Project
- Setting Quarantine Protocol
- Adding a Project for Local Research
- Adding a Project for a Remote Server
- Changing the Pseudonymisation
- Installing SSL Certificates
- Maintenance
- Download Test Data
- Installing DASHER
- Installing Plugins
- Adding Clinical Trial
- Creating a New User
- Importing Data into DASHER
- Pseudonymising Data 1
- Export Pseudonymised Data Locally
- Upload Data (XSync)
- Import - DICOM push
- Import - Duplicate
- Import - Single RTSTRUCT
- Import - Quarantine
- Pseudonymise - Edits
- Pseudonymise - Missing structure
- Pseudonymise - Local research
- Restarting Docker