In this discussion, it seems many people has applied specific post-processing for SJC collections(I'm one of them).
\nAnd in this discussion, the collection has been manually categorized into three areas(\"highway\"/\"tree\"/\"downtown\"), probably manually.
I am concerned that adding specific post-processing to a manual collection(or area) may be considered as \"hand labeling\". Is it not problem?
", "messages": [ { "id": "1382578", "postDate": "07/10/2021 03:50:54", "content": "In this discussion, it seems many people has applied specific post-processing for SJC collections(I'm one of them).
\nAnd in this discussion, the collection has been manually categorized into three areas(\"highway\"/\"tree\"/\"downtown\"), probably manually.
I am concerned that adding specific post-processing to a manual collection(or area) may be considered as \"hand labeling\". Is it not problem?
", "rawMarkdown": "In [this discussion](https://www.kaggle.com/c/google-smartphone-decimeter-challenge/discussion/250929), it seems many people has applied specific post-processing for SJC collections(I'm one of them).\nAnd in [this discussion](https://www.kaggle.com/c/google-smartphone-decimeter-challenge/discussion/245160), the collection has been manually categorized into three areas(\"highway\"/\"tree\"/\"downtown\"), probably manually.\n\n\nI am concerned that adding specific post-processing to a manual collection(or area) may be considered as \"hand labeling\". Is it not problem?", "votes": null }, { "id": "1382628", "postDate": "07/10/2021 04:39:33", "content": "Good discussion.
\nI don't think it's a problem because it's within the scope of normal strategy (like valid strat).
\nI'm sure that manually entering coordinates would be a problem, but
Thanks for your opinion!
\nI see, I feel like that.
\n\nI 'm sure that manually entering coordinates would be a problem, but
\n
Of course :)
", "rawMarkdown": "Thanks for your opinion!\nI see, I feel like that.\n\n\n>I 'm sure that manually entering coordinates would be a problem, but\n\nOf course :)", "votes": null }, { "id": "1382719", "postDate": "07/10/2021 07:22:35", "content": "So if we don't modify the coordinate manually, it's okay?
", "rawMarkdown": "So if we don't modify the coordinate manually, it's okay?", "votes": null }, { "id": "1382852", "postDate": "07/10/2021 09:14:17", "content": "Looks like it unless there is no further discussion.
", "rawMarkdown": "Looks like it unless there is no further discussion.", "votes": null }, { "id": "1382858", "postDate": "07/10/2021 09:23:20", "content": "Thanks for the reply.
", "rawMarkdown": "Thanks for the reply.", "votes": null }, { "id": "1383129", "postDate": "07/10/2021 14:51:15", "content": "Thank you for good discussion:)
\nI'm the one of them who apply post-processing to SJC collections.
\nI think it is OK to apply post-processing to automatically selecting collections.
\nHowever, it may be a problem to apply post-processing to manually selecting collections, because such a post processing method cannot be applied to new, unseen locations without hand-work.
\nPlease let me know if my understanding is wrong :)
", "rawMarkdown": "Thank you for good discussion:)\n\nI'm the one of them who apply post-processing to SJC collections.\n\nI think it is OK to apply post-processing to automatically selecting collections.\n\nHowever, it may be a problem to apply post-processing to manually selecting collections, because such a post processing method cannot be applied to new, unseen locations without hand-work.\n\nPlease let me know if my understanding is wrong :)", "votes": null }, { "id": "1383427", "postDate": "07/10/2021 20:20:50", "content": " it may be a problem to apply post-processing to manually selecting collections, because such a post processing method cannot be applied to new, unseen locations without hand-work.\nI agree with this opinion. I understand that we need a way to categorize routes automatically.
", "rawMarkdown": "```\n it may be a problem to apply post-processing to manually selecting collections, because such a post processing method cannot be applied to new, unseen locations without hand-work.\n\n```\nI agree with this opinion. I understand that we need a way to categorize routes automatically.", "votes": null }, { "id": "1383515", "postDate": "07/10/2021 23:44:39", "content": "\n\nit may be a problem to apply post-processing to manually selecting collections, because such a post processing method cannot be applied to new, unseen locations without hand-work.
\n
I agree, I also posted this discussion because of this concern.
\nCurrently our team categorized collections and roads automatically too.
Hi @sohier, How should we do?
", "rawMarkdown": ">it may be a problem to apply post-processing to manually selecting collections, because such a post processing method cannot be applied to new, unseen locations without hand-work.\n\nI agree, I also posted this discussion because of this concern.\nCurrently our team categorized collections and roads automatically too.\n\n\nHi @sohier, How should we do?", "votes": null }, { "id": "1383521", "postDate": "07/11/2021 00:37:45", "content": "I see, that's true.
\nOn the other hand, I think it is quite a delicate issue.
For example, it is easy to somehow reproduce categorizing with the same result as hand work.
\n (Ex. rule based on coordinate points)
\nAnd if we apply each parameter adjusted for each group,
\nwe can get the same result as hand work without hand work.
\nI feel this is not a problem in terms of rules because it is an automatic process,
\nbut essentially it is just mimicking handwork.
Anyway, let's wait for the host's answer.
", "rawMarkdown": "I see, that's true.\nOn the other hand, I think it is quite a delicate issue. \n\nFor example, it is easy to somehow reproduce categorizing with the same result as hand work. \n (Ex. rule based on coordinate points)\nAnd if we apply each parameter adjusted for each group, \nwe can get the same result as hand work without hand work. \nI feel this is not a problem in terms of rules because it is an automatic process, \nbut essentially it is just mimicking handwork.\n\nAnyway, let's wait for the host's answer.", "votes": null } ], "comments": [ { "id": 1382628, "author_name": "t88take", "author_url": "", "post_date": "07/10/2021 04:39:33", "content": "Good discussion.
\nI don't think it's a problem because it's within the scope of normal strategy (like valid strat).
\nI'm sure that manually entering coordinates would be a problem, but
Thanks for your opinion!
\nI see, I feel like that.
\n\nI 'm sure that manually entering coordinates would be a problem, but
\n
Of course :)
", "votes": null, "replies": [] }, { "id": 1382719, "author_name": "alvinai9603", "author_url": "", "post_date": "07/10/2021 07:22:35", "content": "So if we don't modify the coordinate manually, it's okay?
", "votes": null, "replies": [] }, { "id": 1382852, "author_name": "kuto0633", "author_url": "", "post_date": "07/10/2021 09:14:17", "content": "Looks like it unless there is no further discussion.
", "votes": null, "replies": [] }, { "id": 1382858, "author_name": "alvinai9603", "author_url": "", "post_date": "07/10/2021 09:23:20", "content": "Thanks for the reply.
", "votes": null, "replies": [] } ] }, { "id": 1383129, "author_name": "hashimotoryuichi", "author_url": "", "post_date": "07/10/2021 14:51:15", "content": "Thank you for good discussion:)
\nI'm the one of them who apply post-processing to SJC collections.
\nI think it is OK to apply post-processing to automatically selecting collections.
\nHowever, it may be a problem to apply post-processing to manually selecting collections, because such a post processing method cannot be applied to new, unseen locations without hand-work.
\nPlease let me know if my understanding is wrong :)
", "votes": null, "replies": [ { "id": 1383427, "author_name": "dehokanta", "author_url": "", "post_date": "07/10/2021 20:20:50", "content": " it may be a problem to apply post-processing to manually selecting collections, because such a post processing method cannot be applied to new, unseen locations without hand-work.\nI agree with this opinion. I understand that we need a way to categorize routes automatically.
", "votes": null, "replies": [] }, { "id": 1383515, "author_name": "kuto0633", "author_url": "", "post_date": "07/10/2021 23:44:39", "content": "\n\nit may be a problem to apply post-processing to manually selecting collections, because such a post processing method cannot be applied to new, unseen locations without hand-work.
\n
I agree, I also posted this discussion because of this concern.
\nCurrently our team categorized collections and roads automatically too.
Hi @sohier, How should we do?
", "votes": null, "replies": [] }, { "id": 1383521, "author_name": "t88take", "author_url": "", "post_date": "07/11/2021 00:37:45", "content": "I see, that's true.
\nOn the other hand, I think it is quite a delicate issue.
For example, it is easy to somehow reproduce categorizing with the same result as hand work.
\n (Ex. rule based on coordinate points)
\nAnd if we apply each parameter adjusted for each group,
\nwe can get the same result as hand work without hand work.
\nI feel this is not a problem in terms of rules because it is an automatic process,
\nbut essentially it is just mimicking handwork.
Anyway, let's wait for the host's answer.
", "votes": null, "replies": [] } ] } ], "raw_markdown_by_id": { "1382578": "In [this discussion](https://www.kaggle.com/c/google-smartphone-decimeter-challenge/discussion/250929), it seems many people has applied specific post-processing for SJC collections(I'm one of them).\nAnd in [this discussion](https://www.kaggle.com/c/google-smartphone-decimeter-challenge/discussion/245160), the collection has been manually categorized into three areas(\"highway\"/\"tree\"/\"downtown\"), probably manually.\n\n\nI am concerned that adding specific post-processing to a manual collection(or area) may be considered as \"hand labeling\". Is it not problem?", "1382628": "Good discussion.\nI don't think it's a problem because it's within the scope of normal strategy (like valid strat). \nI'm sure that manually entering coordinates would be a problem, but", "1382643": "Thanks for your opinion!\nI see, I feel like that.\n\n\n>I 'm sure that manually entering coordinates would be a problem, but\n\nOf course :)", "1382719": "So if we don't modify the coordinate manually, it's okay?", "1382852": "Looks like it unless there is no further discussion.", "1382858": "Thanks for the reply.", "1383129": "Thank you for good discussion:)\n\nI'm the one of them who apply post-processing to SJC collections.\n\nI think it is OK to apply post-processing to automatically selecting collections.\n\nHowever, it may be a problem to apply post-processing to manually selecting collections, because such a post processing method cannot be applied to new, unseen locations without hand-work.\n\nPlease let me know if my understanding is wrong :)", "1383427": "```\n it may be a problem to apply post-processing to manually selecting collections, because such a post processing method cannot be applied to new, unseen locations without hand-work.\n\n```\nI agree with this opinion. I understand that we need a way to categorize routes automatically.", "1383515": ">it may be a problem to apply post-processing to manually selecting collections, because such a post processing method cannot be applied to new, unseen locations without hand-work.\n\nI agree, I also posted this discussion because of this concern.\nCurrently our team categorized collections and roads automatically too.\n\n\nHi @sohier, How should we do?", "1383521": "I see, that's true.\nOn the other hand, I think it is quite a delicate issue. \n\nFor example, it is easy to somehow reproduce categorizing with the same result as hand work. \n (Ex. rule based on coordinate points)\nAnd if we apply each parameter adjusted for each group, \nwe can get the same result as hand work without hand work. \nI feel this is not a problem in terms of rules because it is an automatic process, \nbut essentially it is just mimicking handwork.\n\nAnyway, let's wait for the host's answer." }, "source": "meta" }