History of XA60upgrade (No. 17)
- History
- View the diff.
- View the diff current.
- View the source.
- Go to XA60upgrade.
- 1 (2025-04-04 (Fri) 01:22:23)
- 2 (2025-04-04 (Fri) 02:43:17)
- 3 (2025-04-07 (Mon) 05:36:54)
- 4 (2025-04-07 (Mon) 09:36:45)
- 5 (2025-04-09 (Wed) 08:06:58)
- 6 (2025-04-14 (Mon) 23:00:23)
- 7 (2025-04-15 (Tue) 03:09:22)
- 8 (2025-04-16 (Wed) 04:00:27)
- 9 (2025-04-17 (Thu) 03:17:16)
- 10 (2025-04-17 (Thu) 07:07:52)
- 11 (2025-04-18 (Fri) 13:58:44)
- 12 (2025-04-22 (Tue) 03:28:46)
- 13 (2025-04-23 (Wed) 02:51:22)
- 14 (2025-04-23 (Wed) 07:05:59)
- 15 (2025-04-25 (Fri) 03:07:12)
- 16 (2025-04-25 (Fri) 05:48:57)
- 17 (2025-04-28 (Mon) 06:51:54)
Problems†
Patient table doesn't move when closing the experiment/restarting workplace/restarting system cases.†
Is this a problem? Or this is a new feature of XA60?
MRS data isn't shown in MR View&GO†
CMRR, Jn sequences
Starting program issue(Your organization used Windows Defender Application Control to block this app)†
Group Policy Editor(gpedit)>āConfigure Windows Defender SmartScreenā and select āEnabledā, with the setting āWarnā Fastmap and ShimCache started but Yarra still gives an error. Yarra:RDS.exe NG Fastmap OK ShimCache OK
Preparation of measurement system has failed.†
It seems the scanning is fine.
Turn on Windows Security Center service(The Windows Security Center service is turned off. Tap or click to turn on.†
The alert message has been shown as a floating window. We just closed it and didn't do anything.
JobView open icon(right lower corner) disappeared.†
Switching to medadmin could show it again but meduser didn't have it. After rebooting, meduser account has the icon.
Occasionally ND conversion takes so long time(MRS prep)†
After canceling, the conversion could be done immediately.
lSequenceID issue†
lSequenceID(in DICOM file) doesn't match with the MID00??? number in the corresponding dat file name.
Bootup issues†
Occasional fail during the boot process Connection to Image Reconstruction System has been lost. MRI_COS[s] Booting the Scanner has failed.
Sudden uncontrollable software during 3D shim on the adjustment window.†
Unwilled experimental termination made automatic table movement.
ideacmdtool IMA transfer†
MRS data cannot be transferred automatically.
System log file transfer†
Second decimal place cannot be entered.†
ćSlice thickness parameter
MREG†
Recon?
Trash button on MARS data viewer clears all of the data.†
Too Risky!
command line issue†
C:\ :P <RET> Cause error Error: the system cannot find the device specified.
Info†
/System/Adjustment/b0map has gradient shim types as protocols. Is raidtool useful for us?
Host†
Windows10 LoT Enterprise LTSC 128GB RAM 1TB SSD 12th Gen Intel(R) Core(TM) i9-12900 2.40GHz
16bit DICOM save(iceConfig.env)
Mars†
Debian GNU/Linux 11(bullseye) Linux mars 5.10.89-xenomai-l #1 SMP IRQPIPE Wed Jan 26 12:20:57 UTC 2022 x86_64 GNU/Linux /dev/nvme0nl: 1.75TiB SAMSUNG MZ1L21T9HCLS-00A07 Mem: 251Gi 32 processors? Intel(R) Xeon(R) Gold 6226R CPU @ 2.9GHz 16Cores I225-T1 10/100/1000/2.5GBASE-T (TX) 222.222.222.3 I219-LM 1000Base-T 192.168.2.1
In future†
- af command update
- lncarts command update
- dgs command update
- dcmall,ppall command check
- Yarra setup for K-space data transfer
Solved issues†
Protocol conversion has some problem.†
CMRR MB sequence conversion has some issues. (FatSat and others) Sinc exc. pulse BWTP setting BWTP=1.0 but BWTP=5.2 for default. 1.0->5.2 fixed the slice-intensity variation problem. Fat sat setting should be FA_fsat=110 (not 0)
ND data is saturated.†
T1MPRAGE_ND is saturated which is used for MRS. The ND calculation procedure handles data as 12bit integer. 16bit MPRAGE data turns to be saturated after the ND image calculation. dOverallImageScaleCorrectionFactor (DICOMout factor)
Some DICOM Tag data has been changed..†
Manual DICOM transfer†
Cannot transfer to the subfolder of SAMBA.
CMRR MB†
R017pre12 installation(2025Apr.25) FatSat FA/BWTP issues were solved. Segmented EPI ref is available for GRAPPA.
Freeze of adjustment window during 3D shim†
We reported the bug. Now we know what to do on this issue.