An unexpected error occurred

An unexpected error occurred  

  By: Kobalt on Oct. 28, 2024, 4:21 p.m.

Dear Panorama Team,

We recently submitted our Docker container for sanity checking and encountered an unexpected issue. Our algorithm processed all cases successfully, except for one: 101480_00001_0000.nii(.mha), which resulted in an "An unexpected error occurred" message. Upon inspecting the output folder using the ls command, we found the expected files: 34667d08-2c8f-483d-994b-e23c11c1671f_detection_map.mha and pdac-likelihood.json. However, when we checked the "Algorithm Result", these files were not listed as part of the output. The error logs do not contain any clear indication of what went wrong, as everything seems to have been executed normally. Could you please provide guidance or suggestions on how to address this issue?

Best regards,

DKFZ Team

Re: An unexpected error occurred  

  By: NataliaAlves on Oct. 28, 2024, 5:46 p.m.

Dear participant,

I will contact the Grand Challenge team and request more information on the error. I will keep you posted.

Natalia Alves

Re: An unexpected error occurred  

  By: NataliaAlves on Oct. 29, 2024, 1:25 p.m.

Dear participant,

We have heard from the Grand Challenge team that the issue was the workers ran out of memory while processing your output. Specifically, the workers errored out with Exception thrown in SimpleITK ImageFileWriter_Execute: std::bad_alloc.

Since all tasks failed at this level, it seems to be a systematic error. Please make sure the output is the correct size and use single precision.

Regards,

Natalia Alves

Re: An unexpected error occurred  

  By: Kobalt on Oct. 29, 2024, 5:34 p.m.

Dear Panorama Team,

Thank you for your prompt response. Could you please confirm if the specific submission in question was thoroughly checked? Since that submission, we have experimented with various configurations in an attempt to resolve the issue, and new SITK errors emerged during this process. In our most recent submission, there are no SITK errors, yet we continue to receive the "An unexpected error occurred" message.

We would appreciate any additional insights or guidance to resolve this issue.

Best regards,

DKFZ Team

Re: An unexpected error occurred  

  By: Kobalt on Oct. 29, 2024, 5:38 p.m.

I am just sending the exact details of that particular submission:

Result ID: 7c36749b-4aff-4fcf-a074-a1a6a67b0376

Algorithm: Ridge

Algorithm Version: cb65e98a-68a0-4296-9c3f-b7ebfa812586

Model Version: None

Creator: Unknown

Created: Oct. 29, 2024, 3:01 p.m.

Status: Failed

Error Message: An unexpected error occurred

Duration: 11 minutes

Visibility: Result and images are private

Inputs:

Clinical Information Pancreatic CT

Venous phase CT scan: 101480_00001_0000.nii (.mha)

Re: An unexpected error occurred  

  By: Kobalt on Oct. 29, 2024, 5:41 p.m.

(The other cases are succeeded with warnings)

Re: An unexpected error occurred  

  By: NataliaAlves on Oct. 30, 2024, 6:32 p.m.

Dear participant,

We have once again reached out to the Grand Challenge team who has thoroughly reviewed the submissions in question and confirmed it is still the same out-of-memory issue. The output file you're producing is too large for the workers to handle.

Let me know if there are any other questions.

Regards, Natalia