![\"\"](\"https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F2518187%2Fb7cef68e5cf63a812c22d0ebf42c0d80%2Fnotification.png?generation=1562317587516187&alt=media\")
With this topic, I would like to propose two simple upgrades in the submission process:
\n\nIn my opinion, it would be amazing being notified whenever our submissions end their processing.\nI think this would be a super helpful setting, especially in such kind of competition.
\n\nIt was already proposed at the end of Jigsaw Stage 1. A simple button that could save us to: commit - wait - submit - wait. If you are sure about your code and want to submit directly, then, click \"Commit and Submit\" :smile: .
\n\nDo you have other proposals to improve this process?
", "messages": [ { "id": "568625", "postDate": "07/05/2019 08:36:04", "content": "With this topic, I would like to propose two simple upgrades in the submission process:
\n\nIn my opinion, it would be amazing being notified whenever our submissions end their processing.\nI think this would be a super helpful setting, especially in such kind of competition.
\n\nIt was already proposed at the end of Jigsaw Stage 1. A simple button that could save us to: commit - wait - submit - wait. If you are sure about your code and want to submit directly, then, click \"Commit and Submit\" :smile: .
\n\nDo you have other proposals to improve this process?
", "rawMarkdown": "With this topic, I would like to propose two simple upgrades in the submission process:\n\n### 1. Submission Notification\nIn my opinion, it would be amazing being notified whenever our submissions end their processing.\nI think this would be a super helpful setting, especially in such kind of competition.\n\n### 2. \"Commit and Submit\" Button\nIt was already proposed at the end of [Jigsaw](https://www.kaggle.com/c/jigsaw-unintended-bias-in-toxicity-classification) Stage 1. A simple button that could save us to: commit - wait - submit - wait. If you are sure about your code and want to submit directly, then, click \"Commit and Submit\" :smile: .\n\n**Do you have other proposals to improve this process?**", "votes": null }, { "id": "568633", "postDate": "07/05/2019 08:45:52", "content": "@raimonds1993 Thank you for these suggestions! What do you mean by notification? Something like message in the Kaggle system or browser notifications in pop-up form?
", "rawMarkdown": "raimonds1993 Thank you for these suggestions! What do you mean by notification? Something like message in the Kaggle system or browser notifications in pop-up form?", "votes": null }, { "id": "568649", "postDate": "07/05/2019 09:07:00", "content": "Yes, like those you receive when you are mentioned in comments.\nThen, you could choose to receive emails or just on Kaggle.
\n\n
Thank you for nice thread.\nI wish I would be able to select when submitting whether or not to run kernel with private test set.\nI need not to check my ' maybe low scoerd' kernel would run with final data ;)
", "rawMarkdown": "raimonds1993 \n\nThank you for nice thread.\nI wish I would be able to select when submitting whether or not to run kernel with private test set.\nI need not to check my ' maybe low scoerd' kernel would run with final data ;)", "votes": null }, { "id": "589389", "postDate": "07/31/2019 20:19:52", "content": "Agree with your suggesstions @raimonds1993 @kaerunantoka.
\n\nI have another suggestion. This suggestion is related to the kernels and not specific to the submissions. Today, a kernel can have a single file. I would like to work on multiple files in the same kernel. So that I can split my single long python script into multiple python files. This allows me to organise my work in the same way as I would organise it in my personal computer.
", "rawMarkdown": "Agree with your suggesstions @raimonds1993 @kaerunantoka.\n\nI have another suggestion. This suggestion is related to the kernels and not specific to the submissions. Today, a kernel can have a single file. I would like to work on multiple files in the same kernel. So that I can split my single long python script into multiple python files. This allows me to organise my work in the same way as I would organise it in my personal computer.", "votes": null } ], "comments": [ { "id": 568633, "author_name": "morphism90", "author_url": "", "post_date": "07/05/2019 08:45:52", "content": "@raimonds1993 Thank you for these suggestions! What do you mean by notification? Something like message in the Kaggle system or browser notifications in pop-up form?
", "votes": null, "replies": [ { "id": 568649, "author_name": "raimonds1993", "author_url": "", "post_date": "07/05/2019 09:07:00", "content": "Yes, like those you receive when you are mentioned in comments.\nThen, you could choose to receive emails or just on Kaggle.
\n\n
Thank you for nice thread.\nI wish I would be able to select when submitting whether or not to run kernel with private test set.\nI need not to check my ' maybe low scoerd' kernel would run with final data ;)
", "votes": null, "replies": [] }, { "id": 589389, "author_name": "ravivadapalli", "author_url": "", "post_date": "07/31/2019 20:19:52", "content": "Agree with your suggesstions @raimonds1993 @kaerunantoka.
\n\nI have another suggestion. This suggestion is related to the kernels and not specific to the submissions. Today, a kernel can have a single file. I would like to work on multiple files in the same kernel. So that I can split my single long python script into multiple python files. This allows me to organise my work in the same way as I would organise it in my personal computer.
", "votes": null, "replies": [] } ], "raw_markdown_by_id": { "568625": "With this topic, I would like to propose two simple upgrades in the submission process:\n\n### 1. Submission Notification\nIn my opinion, it would be amazing being notified whenever our submissions end their processing.\nI think this would be a super helpful setting, especially in such kind of competition.\n\n### 2. \"Commit and Submit\" Button\nIt was already proposed at the end of [Jigsaw](https://www.kaggle.com/c/jigsaw-unintended-bias-in-toxicity-classification) Stage 1. A simple button that could save us to: commit - wait - submit - wait. If you are sure about your code and want to submit directly, then, click \"Commit and Submit\" :smile: .\n\n**Do you have other proposals to improve this process?**", "568633": "raimonds1993 Thank you for these suggestions! What do you mean by notification? Something like message in the Kaggle system or browser notifications in pop-up form?", "568649": "Yes, like those you receive when you are mentioned in comments.\nThen, you could choose to receive emails or just on Kaggle.\n\n\n", "568724": "raimonds1993 \n\nThank you for nice thread.\nI wish I would be able to select when submitting whether or not to run kernel with private test set.\nI need not to check my ' maybe low scoerd' kernel would run with final data ;)", "589389": "Agree with your suggesstions @raimonds1993 @kaerunantoka.\n\nI have another suggestion. This suggestion is related to the kernels and not specific to the submissions. Today, a kernel can have a single file. I would like to work on multiple files in the same kernel. So that I can split my single long python script into multiple python files. This allows me to organise my work in the same way as I would organise it in my personal computer." }, "source": "meta" }