{
  "id": 609809,
  "title": "SharedFunctionalGroupsSequence for multiframe DICOMs in test set",
  "url": "/competitions/rsna-intracranial-aneurysm-detection/discussion/609809",
  "author_name": "Ian Pan",
  "post_date": "2025-09-29T19:30:51.825000",
  "votes": 10,
  "comment_count": 4,
  "views": 0,
  "content": "<p>I am making a separate topic on this for visibility.</p>\n<p>There has already been discussing regarding <code>PerFrameFunctionalGroupsSequence</code>, which the test set has been updated to include. This is for extracting <code>ImagePositionPatient</code> information. </p>\n<p>Multiframe DICOMs also contain <code>SharedFunctionalGroupsSequence</code> which contains <code>ImageOrientationPatient</code> and <code>PixelSpacing</code> information. However, this is not present in the test set based on my submissions. All multiframe DICOMs in the training set contain this attribute. It would be helpful if this attribute was also available in the test set.</p>",
  "messages": [
    {
      "id": 3295924,
      "postDate": "2025-09-29T19:30:51.827Z",
      "content": "<p>I am making a separate topic on this for visibility.</p>\n<p>There has already been discussing regarding <code>PerFrameFunctionalGroupsSequence</code>, which the test set has been updated to include. This is for extracting <code>ImagePositionPatient</code> information. </p>\n<p>Multiframe DICOMs also contain <code>SharedFunctionalGroupsSequence</code> which contains <code>ImageOrientationPatient</code> and <code>PixelSpacing</code> information. However, this is not present in the test set based on my submissions. All multiframe DICOMs in the training set contain this attribute. It would be helpful if this attribute was also available in the test set.</p>",
      "rawMarkdown": "I am making a separate topic on this for visibility.\n\nThere has already been discussing regarding `PerFrameFunctionalGroupsSequence`, which the test set has been updated to include. This is for extracting `ImagePositionPatient` information. \n\nMultiframe DICOMs also contain `SharedFunctionalGroupsSequence` which contains `ImageOrientationPatient` and `PixelSpacing` information. However, this is not present in the test set based on my submissions. All multiframe DICOMs in the training set contain this attribute. It would be helpful if this attribute was also available in the test set.\n\n",
      "votes": 10
    },
    {
      "id": 3297154,
      "postDate": "2025-10-02T14:03:50.090Z",
      "content": "<p>The metadata for multiframe files might still be in there but then organized in the same way for singleframe files, meaning it might just be under their 'normal' names. We reasoned that they took all the metadata out of each file and then only put back the allowed tags without keeping the original structure of dicom metadata. We dont know for sure, but would seem logical to us. Hope this helps!</p>",
      "rawMarkdown": "The metadata for multiframe files might still be in there but then organized in the same way for singleframe files, meaning it might just be under their 'normal' names. We reasoned that they took all the metadata out of each file and then only put back the allowed tags without keeping the original structure of dicom metadata. We dont know for sure, but would seem logical to us. Hope this helps!",
      "votes": 1
    },
    {
      "id": 3296096,
      "postDate": "2025-09-30T06:59:41.180Z",
      "content": "<p>To be honest, I've already trained an orientation classifier.<br>\nSeemed easier to me than looking for potentially missing dicom fields :) </p>",
      "rawMarkdown": "To be honest, I've already trained an orientation classifier.\nSeemed easier to me than looking for potentially missing dicom fields :) ",
      "votes": 1,
      "replies": [
        {
          "id": 3296797,
          "postDate": "2025-10-01T16:17:05.287Z",
          "content": "<p>If you are willing to share, that would be extremely helpful!</p>",
          "rawMarkdown": "If you are willing to share, that would be extremely helpful!"
        }
      ]
    },
    {
      "id": 3296796,
      "postDate": "2025-10-01T16:16:44.463Z",
      "content": "<p>Unfortunately its too late for any additional changes. I will make a separate post about this.</p>",
      "rawMarkdown": "Unfortunately its too late for any additional changes. I will make a separate post about this."
    }
  ],
  "comments": [
    {
      "id": 3297154,
      "author_name": "Willem Dieleman",
      "author_url": "",
      "post_date": "2025-10-02T14:03:50.090000",
      "content": "<p>The metadata for multiframe files might still be in there but then organized in the same way for singleframe files, meaning it might just be under their 'normal' names. We reasoned that they took all the metadata out of each file and then only put back the allowed tags without keeping the original structure of dicom metadata. We dont know for sure, but would seem logical to us. Hope this helps!</p>",
      "votes": 1,
      "replies": []
    },
    {
      "id": 3296096,
      "author_name": "Theo Viel",
      "author_url": "",
      "post_date": "2025-09-30T06:59:41.180000",
      "content": "<p>To be honest, I've already trained an orientation classifier.<br>\nSeemed easier to me than looking for potentially missing dicom fields :) </p>",
      "votes": 1,
      "replies": [
        {
          "id": 3296797,
          "author_name": "Evan Calabrese",
          "author_url": "",
          "post_date": "2025-10-01T16:17:05.287000",
          "content": "<p>If you are willing to share, that would be extremely helpful!</p>",
          "votes": 0,
          "replies": []
        }
      ]
    },
    {
      "id": 3296796,
      "author_name": "Evan Calabrese",
      "author_url": "",
      "post_date": "2025-10-01T16:16:44.463000",
      "content": "<p>Unfortunately its too late for any additional changes. I will make a separate post about this.</p>",
      "votes": 0,
      "replies": []
    }
  ],
  "raw_markdown_by_id": {
    "3295924": "I am making a separate topic on this for visibility.\n\nThere has already been discussing regarding `PerFrameFunctionalGroupsSequence`, which the test set has been updated to include. This is for extracting `ImagePositionPatient` information. \n\nMultiframe DICOMs also contain `SharedFunctionalGroupsSequence` which contains `ImageOrientationPatient` and `PixelSpacing` information. However, this is not present in the test set based on my submissions. All multiframe DICOMs in the training set contain this attribute. It would be helpful if this attribute was also available in the test set.\n\n",
    "3297154": "The metadata for multiframe files might still be in there but then organized in the same way for singleframe files, meaning it might just be under their 'normal' names. We reasoned that they took all the metadata out of each file and then only put back the allowed tags without keeping the original structure of dicom metadata. We dont know for sure, but would seem logical to us. Hope this helps!",
    "3296096": "To be honest, I've already trained an orientation classifier.\nSeemed easier to me than looking for potentially missing dicom fields :) ",
    "3296796": "Unfortunately its too late for any additional changes. I will make a separate post about this."
  }
}