MILabs U-CT

For ICT configuration, see https://sydneyuni.atlassian.net/wiki/spaces/RC/pages/960563231

For Upload Tool Config, see https://bitbucket.org/sydneyuni/sydney_upload_scripts/src/master/ which forks from https://bitbucket.org/radiologics/sydney_upload_scripts/src/master/

The microCT data needed to be transferred to the RDS before uploading from RDS to XNAT. Both XNAT and RDS will keep a copy of microCT data at the current stage. If RDS storage researches its maximum capacity or budget in the future, the microCT data on RDS will be removed periodically to save the space.

 The microCT data can be categorized into three types: raw data, temporary data and reconstructed data.

 The raw data is saved on the acquisition computer, and in the D drive of the reconstruction computer.

 The temporary data is generated in the reconstruction process including the “corr” and “prev” folder of each scan and saved in the “ct-data” folder. “corr“ folder contains all the projection correction files, while “prev“ folder contains the single slice preview image of reconstruction. “corr“ and “prev“ folder will not be uploaded to the RDS and XNAT.

 The reconstructed data contains the final images for CT reconstruction, and it is saved in the “Results” folder of each scan.

Data is uploaded from microCT to RDS daily at 7 p.m.

Open

The screenshot above is the acquisition control screen. The User field should always leave blank. The Study field should be filled with the XNAT Project ID and Subject Name in XNAT, e.g. 123_SubjectName.

Project name can’t contain _ , this symbol is used to seperate the Project ID and Subject Name. Subject Name can contain any numbers of _ .

The Scan name will become the Session name on XNAT.

Instrument data hierarchy is:

Z: (Aquisiton) D: (Reconstruction)

D:\Data\[Study]\[Scan]\*

                            [Study] is [XNAT Project ID]_[Subject]