Does the newly added f in the coordinates column of train_localizers.csv correspond to the z-axis coordinate in the 3D array?
\nIt might have been announced somewhere already, but it would be very helpful if the Dataset Description page could be updated to reflect this.
", "messages": [ { "id": 3285938, "postDate": "2025-09-08T23:25:58.983Z", "content": "Does the newly added f in the coordinates column of train_localizers.csv correspond to the z-axis coordinate in the 3D array?
\nIt might have been announced somewhere already, but it would be very helpful if the Dataset Description page could be updated to reflect this.
", "rawMarkdown": "Does the newly added f in the coordinates column of train_localizers.csv correspond to the z-axis coordinate in the 3D array?\n\nIt might have been announced somewhere already, but it would be very helpful if the Dataset Description page could be updated to reflect this.", "votes": 7 }, { "id": 3287118, "postDate": "2025-09-10T22:16:46.083Z", "content": "The f values correspond to the index of the DICOM frame where the aneurysm is located, which is effectively equivalent to the z coordinate. Note that this \"frame index\" starts at 0, while DICOM frame numbers start at 1. This only applies to the 3D DICOMS where multiple frames are present in a single DICOM file, which is a minority of the dataset.
", "rawMarkdown": "The f values correspond to the index of the DICOM frame where the aneurysm is located, which is effectively equivalent to the z coordinate. Note that this \"frame index\" starts at 0, while DICOM frame numbers start at 1. This only applies to the 3D DICOMS where multiple frames are present in a single DICOM file, which is a minority of the dataset.", "votes": 5 }, { "id": 3285948, "postDate": "2025-09-09T00:30:35.540Z", "content": "Thanks for the insigth. I think it should be more as the direct volume first index since is present in already stacked DICOM volumes. There is 0 values?
\nFrom here
\n\n\n\n
\n- Issue with aneurysm coordinates for multi-frame DICOMS
\n
\n https://www.kaggle.com/competitions/rsna-intracranial-aneurysm-detection/discussion/591546
\n Fixed with a new version train_localizer.csv with ‘f’ frame numbers for multi-frame DICOMS
Is the frame, so may be is the index + 1? So yes, like an instance number?
", "rawMarkdown": "Thanks for the insigth. I think it should be more as the direct volume first index since is present in already stacked DICOM volumes. There is 0 values?\n\nFrom [here](https://www.kaggle.com/competitions/rsna-intracranial-aneurysm-detection/discussion/600036)\n\n>1. Issue with aneurysm coordinates for multi-frame DICOMS\nhttps://www.kaggle.com/competitions/rsna-intracranial-aneurysm-detection/discussion/591546\nFixed with a new version train_localizer.csv with ‘f’ frame numbers for multi-frame DICOMS\n\nIs the frame, so may be is the index + 1? So yes, like an instance number?", "votes": 2, "replies": [ { "id": 3285955, "postDate": "2025-09-09T00:51:57.777Z", "content": "Thank you for the additional note.
\nI mentioned InstanceNumber, but since there are 3D arrays, the more appropriate question should have been whether it corresponds exactly to the z-axis coordinate or if it requires a +1 adjustment.
\nI will wait for the host’s response.
", "rawMarkdown": "Thank you for the additional note.\n\nI mentioned InstanceNumber, but since there are 3D arrays, the more appropriate question should have been whether it corresponds exactly to the z-axis coordinate or if it requires a +1 adjustment. \n\nI will wait for the host’s response.", "votes": 3, "replies": [ { "id": 3286570, "postDate": "2025-09-10T03:37:01.420Z", "content": "I just want to point out an additional host's response:
\nQ: Does 'f' start at 0 or 1?
\nA: Dicom standard is to start at 1
The f values correspond to the index of the DICOM frame where the aneurysm is located, which is effectively equivalent to the z coordinate. Note that this \"frame index\" starts at 0, while DICOM frame numbers start at 1. This only applies to the 3D DICOMS where multiple frames are present in a single DICOM file, which is a minority of the dataset.
", "votes": 5, "replies": [] }, { "id": 3285948, "author_name": "Ángel Jacinto Sánchez Ruiz", "author_url": "", "post_date": "2025-09-09T00:30:35.540000", "content": "Thanks for the insigth. I think it should be more as the direct volume first index since is present in already stacked DICOM volumes. There is 0 values?
\nFrom here
\n\n\n\n
\n- Issue with aneurysm coordinates for multi-frame DICOMS
\n
\n https://www.kaggle.com/competitions/rsna-intracranial-aneurysm-detection/discussion/591546
\n Fixed with a new version train_localizer.csv with ‘f’ frame numbers for multi-frame DICOMS
Is the frame, so may be is the index + 1? So yes, like an instance number?
", "votes": 2, "replies": [ { "id": 3285955, "author_name": "YYama", "author_url": "", "post_date": "2025-09-09T00:51:57.777000", "content": "Thank you for the additional note.
\nI mentioned InstanceNumber, but since there are 3D arrays, the more appropriate question should have been whether it corresponds exactly to the z-axis coordinate or if it requires a +1 adjustment.
\nI will wait for the host’s response.
", "votes": 3, "replies": [ { "id": 3286570, "author_name": "Đăng Nguyễn Hồng", "author_url": "", "post_date": "2025-09-10T03:37:01.420000", "content": "I just want to point out an additional host's response:
\nQ: Does 'f' start at 0 or 1?
\nA: Dicom standard is to start at 1