@philculliton \nHi Phil,\ncan you please clarify the rule: \"Submission predictions must be based entirely on the pixel data in the provided datasets.\"
\n\nIt's a bit \"confusing\" - i.e. does it mean we cannot read the DICOM metadata - especially \"Window Center\", \"Window Width\", \"Rescale Intercept\" and \"Rescale Slope\" - for data pre-processing?
\n\nOr should we assume that all images have the same window information and hardcode it?
", "messages": [ { "id": 629930, "postDate": "2019-09-19T13:39:33.420Z", "content": "@philculliton \nHi Phil,\ncan you please clarify the rule: \"Submission predictions must be based entirely on the pixel data in the provided datasets.\"
\n\nIt's a bit \"confusing\" - i.e. does it mean we cannot read the DICOM metadata - especially \"Window Center\", \"Window Width\", \"Rescale Intercept\" and \"Rescale Slope\" - for data pre-processing?
\n\nOr should we assume that all images have the same window information and hardcode it?
", "rawMarkdown": "@philculliton \nHi Phil,\ncan you please clarify the rule: \"Submission predictions must be based **entirely on the pixel data** in the provided datasets.\"\n\nIt's a bit \"confusing\" - i.e. does it mean we **cannot read** the DICOM metadata - especially **\"Window Center\", \"Window Width\", \"Rescale Intercept\" and \"Rescale Slope\"** - for data pre-processing?\n\nOr should we assume that all images have the same window information and hardcode it?", "votes": 17 }, { "id": 630067, "postDate": "2019-09-19T17:16:03.583Z", "content": "According to the host: using the metadata for preprocessing, the way you're describing it, is fine.
", "rawMarkdown": "According to the host: using the metadata for preprocessing, the way you're describing it, is fine.", "votes": 8, "replies": [ { "id": 630068, "postDate": "2019-09-19T17:17:23.820Z", "content": "thanks
", "rawMarkdown": "thanks" }, { "id": 630263, "postDate": "2019-09-20T02:14:03.797Z", "content": "Thank you, this will be necessary.
", "rawMarkdown": "Thank you, this will be necessary." }, { "id": 631815, "postDate": "2019-09-22T18:21:35.770Z", "content": "@philculliton could you please clarify what is not allowed, or explain in some other way why was this remark added and what it means? E.g. which fields are allowed and which are not allowed?
", "rawMarkdown": "@philculliton could you please clarify what is not allowed, or explain in some other way why was this remark added and what it means? E.g. which fields are allowed and which are not allowed?", "votes": 4 }, { "id": 631888, "postDate": "2019-09-22T21:55:13.673Z", "content": "Is it against the rules to create a 3D construction or another section using series id etc.?
", "rawMarkdown": "Is it against the rules to create a 3D construction or another section using series id etc.?", "votes": 6 }, { "id": 632470, "postDate": "2019-09-23T16:21:24.100Z", "content": "Good questions!
\n\n@kambarakun - it is not against the rules to create a 3D construction using the series ID.
\n\n@lopuhin - sorry for the ambiguity. We're approaching this on a case-by-case basis. If you have a use for the metadata that falls outside of what has already been allowed, please ask, and the host will clarify. All of the provided fields were included so they could be used, but the exact use should be cleared to make sure you're falling within the guidelines of the rules.
", "rawMarkdown": "Good questions!\n\n@kambarakun - it is not against the rules to create a 3D construction using the series ID.\n\n@lopuhin - sorry for the ambiguity. We're approaching this on a case-by-case basis. If you have a use for the metadata that falls outside of what has already been allowed, please ask, and the host will clarify. All of the provided fields were included so they could be used, but the exact use should be cleared to make sure you're falling within the guidelines of the rules.", "votes": 3 }, { "id": 632490, "postDate": "2019-09-23T17:00:22.747Z", "content": "Ok that's fair, thanks for clarification!
", "rawMarkdown": "Ok that's fair, thanks for clarification!" }, { "id": 632503, "postDate": "2019-09-23T17:20:25.193Z", "content": "You're welcome - thanks for the question!
", "rawMarkdown": "You're welcome - thanks for the question!" }, { "id": 632585, "postDate": "2019-09-23T19:05:25.040Z", "content": "@philculliton Can we have a dedicated topic/thread for metadata usage Q&A, just like external data sharing? These are the information every participants want to know. We can also avoid duplicated questions.
", "rawMarkdown": "@philculliton Can we have a dedicated topic/thread for metadata usage Q&A, just like external data sharing? These are the information every participants want to know. We can also avoid duplicated questions.", "votes": 1 }, { "id": 632646, "postDate": "2019-09-23T20:51:42.200Z", "content": "@wowfattie - thanks! Great suggestion. Done!
", "rawMarkdown": "@wowfattie - thanks! Great suggestion. Done!", "votes": 2 } ] }, { "id": 630050, "postDate": "2019-09-19T16:34:02.220Z", "content": "yeah it's nearly impossible to do any thing useful with CT image without window and normalization info :)
", "rawMarkdown": "yeah it's nearly impossible to do any thing useful with CT image without window and normalization info :)", "votes": 1 } ], "comments": [ { "id": 630067, "author_name": "Phil Culliton", "author_url": "", "post_date": "2019-09-19T17:16:03.583000", "content": "According to the host: using the metadata for preprocessing, the way you're describing it, is fine.
", "votes": 8, "replies": [ { "id": 630068, "author_name": "steelrose", "author_url": "", "post_date": "2019-09-19T17:17:23.820000", "content": "thanks
", "votes": 0, "replies": [] }, { "id": 630263, "author_name": "ldawes", "author_url": "", "post_date": "2019-09-20T02:14:03.797000", "content": "Thank you, this will be necessary.
", "votes": 0, "replies": [] }, { "id": 631815, "author_name": "Konstantin Lopukhin", "author_url": "", "post_date": "2019-09-22T18:21:35.770000", "content": "@philculliton could you please clarify what is not allowed, or explain in some other way why was this remark added and what it means? E.g. which fields are allowed and which are not allowed?
", "votes": 4, "replies": [] }, { "id": 631888, "author_name": "kambarakun", "author_url": "", "post_date": "2019-09-22T21:55:13.673000", "content": "Is it against the rules to create a 3D construction or another section using series id etc.?
", "votes": 6, "replies": [] }, { "id": 632470, "author_name": "Phil Culliton", "author_url": "", "post_date": "2019-09-23T16:21:24.100000", "content": "Good questions!
\n\n@kambarakun - it is not against the rules to create a 3D construction using the series ID.
\n\n@lopuhin - sorry for the ambiguity. We're approaching this on a case-by-case basis. If you have a use for the metadata that falls outside of what has already been allowed, please ask, and the host will clarify. All of the provided fields were included so they could be used, but the exact use should be cleared to make sure you're falling within the guidelines of the rules.
", "votes": 3, "replies": [] }, { "id": 632490, "author_name": "Konstantin Lopukhin", "author_url": "", "post_date": "2019-09-23T17:00:22.747000", "content": "Ok that's fair, thanks for clarification!
", "votes": 0, "replies": [] }, { "id": 632503, "author_name": "Phil Culliton", "author_url": "", "post_date": "2019-09-23T17:20:25.193000", "content": "You're welcome - thanks for the question!
", "votes": 0, "replies": [] }, { "id": 632585, "author_name": "Guanshuo Xu", "author_url": "", "post_date": "2019-09-23T19:05:25.040000", "content": "@philculliton Can we have a dedicated topic/thread for metadata usage Q&A, just like external data sharing? These are the information every participants want to know. We can also avoid duplicated questions.
", "votes": 1, "replies": [] }, { "id": 632646, "author_name": "Phil Culliton", "author_url": "", "post_date": "2019-09-23T20:51:42.200000", "content": "@wowfattie - thanks! Great suggestion. Done!
", "votes": 2, "replies": [] } ] }, { "id": 630050, "author_name": "DatNT", "author_url": "", "post_date": "2019-09-19T16:34:02.220000", "content": "yeah it's nearly impossible to do any thing useful with CT image without window and normalization info :)
", "votes": 1, "replies": [] } ], "raw_markdown_by_id": { "629930": "@philculliton \nHi Phil,\ncan you please clarify the rule: \"Submission predictions must be based **entirely on the pixel data** in the provided datasets.\"\n\nIt's a bit \"confusing\" - i.e. does it mean we **cannot read** the DICOM metadata - especially **\"Window Center\", \"Window Width\", \"Rescale Intercept\" and \"Rescale Slope\"** - for data pre-processing?\n\nOr should we assume that all images have the same window information and hardcode it?", "630067": "According to the host: using the metadata for preprocessing, the way you're describing it, is fine.", "630050": "yeah it's nearly impossible to do any thing useful with CT image without window and normalization info :)" } }