Sequence missing from a scan

32 views
Skip to first unread message

Tuomas Tolvanen

unread,
Oct 14, 2021, 3:18:22 AM10/14/21
to xnat_discussion
Hi,

We have noticed an issue that once in a while one sequence from a scan is missing from XNAT. This seems to be a random issue and has happened for multiple projects. The missing sequence is always the last sequence in the protocol and so far it has been the anatomical T1-weighted sequence. Has anyone experienced similar issue? Luckily we store the images also to another server so nothing has been lost but we are planning to use only XNAT. Obviously we can't until this issue is solved.  

XNAT version 1.8.0, build: 1974

br,

Tuomas

elijah....@gmail.com

unread,
Oct 14, 2021, 12:06:00 PM10/14/21
to xnat_discussion
Actually, yes. We are using XNAT 1.6.5 in production and I had a user that described this exact issue. I checked XNAT logs at the time but didn't see anything out of the ordinary. He said the last sequence was missing from some of his PET images, and that he had the technologist re-send the images from the scanner - the second time all the sequences were there. I chalked it up to user error at the time, but looks like we may need to revisit this issue, as it is quite serious.

Herrick, Rick

unread,
Oct 14, 2021, 1:03:09 PM10/14/21
to xnat_di...@googlegroups.com

Hi Tuomas,

 

Do you know if the data makes it to the server at all? All incoming DICOM data gets logged in the received.log file. Entries there look something like this:

 

2021-10-14 11:04:00,153 - admin:/data/xnat/prearchive/Test_01/20211014_110350413/Test_01_01_MR_02/SCANS/7/DICOM/1.2.276.0.7230010.3.1.2.0.31909.1624637609.925-7-46-2z8kcp.dcm

 

That’s for a file uploaded using the XNAT desktop client. It’s a little different for data sent via C-STORE:

 

2021-10-14 11:07:08,931 - TERM@/10.1.1.1:58687:/data/xnat/prearchive/Test_01/20211014_110650893/Test_01_01_MR_03/SCANS/5/DICOM/1.2.276.0.7230010.3.1.2.0.31909.1624637609.925-5-60-2ynj6a.dcm

 

The only difference is that data uploaded through the REST API (e.g. with the desktop client) has the name of the user who uploaded the data, while data via C-STORE has the title, IP address, and port of the AE that sent the data (the port is kind of useless because it’s an ephemeral port on the client side).

 

The main point is that you can tell which scans were received based on the path:

 

/data/xnat/prearchive/Test_01/20211014_110650893/Test_01_01_MR_03/SCANS/5/DICOM/1.2.276.0.7230010.3.1.2.0.31909.1624637609.925-5-60-2ynj6a.dcm

 

The highlighted parts of that path are:

 

  • The root prearchive folder
  • The project where the data is to be archived
  • The label for the new session
  • The scan (i.e. series) number
  • The study instance UID

 

Between those bits of info, you should be able to verify whether the data arrived in the first place.

 

If the data did arrive, check to see if it happens to be lying around somewhere, maybe in the prearchive or cache folders. Something like:

 

find /data/xnat/prearchive -name 1.2.276.0.7230010.3.1.2.0.31909.1624637609.925-5-60-2ynj6a.dcm

 

You can also check if there are any entries in other log files around the time that the data arrived that might indicate what happened during the archive operation.

 

-- 

Rick Herrick

XNAT Architect/Developer

Computational Imaging Laboratory

Washington University School of Medicine

 

 

From: xnat_di...@googlegroups.com <xnat_di...@googlegroups.com> on behalf of Tuomas Tolvanen <tuomas.j...@aalto.fi>
Date: Thursday, October 14, 2021 at 2:18 AM
To: xnat_discussion <xnat_di...@googlegroups.com>
Subject: [XNAT Discussion] Sequence missing from a scan

* External Email - Caution *

--
You received this message because you are subscribed to the Google Groups "xnat_discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to xnat_discussi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/xnat_discussion/243da5b5-352c-4dec-b21c-cd65755bb281n%40googlegroups.com.

 


The materials in this message are private and may contain Protected Healthcare Information or other information of a sensitive nature. If you are not the intended recipient, be advised that any unauthorized use, disclosure, copying or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via telephone or return mail.

Tuomas Tolvanen

unread,
Feb 1, 2023, 8:25:09 AM2/1/23
to xnat_discussion
Hi,

Sorry for the really late reply on this issue. I had some issues with the permissions to access log files and this transfer problem stopped happening after a while. Now it has begun again and I had a chance to check the log files. Previously the missing scan was always the last one but now we have missing scans from different part of the protocol. This is what I found (for one measurement, 10 scans, scan #8 missing):

1. Every scan is received by XNAT (from received.log) 
2. I found some of the data for scan #8 (107 files out of 392 in this case) from folders archive/PROJECTID and cache/PROJECTID/
3. I found an error logged in prearchive.log and jms.log

prearchive.log:
2023-01-30 12:20:52,117 [DefaultMessageListenerContainer-15] ERROR org.nrg.xnat.helpers.prearchive.PrearcDatabase -
org.nrg.xnat.helpers.prearchive.SessionException: A record with session 23_01_30-12_55_48-STD-1_3_12_2_1107_5_2_19_45177, timestamp 20230130_121409437 and project DCE123 could not be found.


jmg.log
2023-01-30 12:20:52,144 [DefaultMessageListenerContainer-15] ERROR org.nrg.xnat.services.messaging.prearchive.PrearchiveOperationRequestListener - An error occurred processing a request from user admin to perform Archive operation on prearchive session at: /prearchive/projects/DCE123/20230130_121409437/23_01_30-12_55_48-STD-1_3_12_2_1107_5_2_19_45177
org.nrg.xnat.helpers.prearchive.PrearcDatabase$SyncFailedException: Operation Failed: A record with session 23_01_30-12_55_48-STD-1_3_12_2_1107_5_2_19_45177, timestamp 20230130_121409437 and project DCE123 could not be found.

So it seems to me that there is something happening when XNAT is archiving data from prearchive and only part of data gets archived. However users don't see that partly archived scan at all when browsing their data in XNAT. Any idea what could cause this? I can share the log files if necessary.

br,

Tuomas Tolvanen

The materials in this message are private and may contain Protected Healthcare Information or other information of a sensitive nature. If you are not the intended recipient, be advised that any unauthorized use, disclosure, copying or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via telephone or return mail.

Reply all
Reply to author
Forward
0 new messages