\nNotice how when I mistakenly re-submitted the same version 1 twice it gives error on the 2nd run and onward versions.
\n
![\"\"](\"https://www.googleapis.com/download/storage/v1/b/kaggle-forum-message-attachments/o/inbox%2F3294467%2F389c91ed76c9d1dc388d52678a4c66be%2Ftempsnip.png?generation=1599318802309853&alt=media\")
Hello everyone,
\nI am trying to submit this notebook: https://www.kaggle.com/berniechou/clean-quantile-image?scriptVersionId=41779873.
\nBut I do not manage to do it, the problem seems to be \"Notebook Timeout\". But I have been investigating for hours and I do not find any possible error. Someone has already had this problem and solved it ?
Thank you
", "messages": [ { "id": "996922", "postDate": "09/03/2020 16:34:34", "content": "Hello everyone,
\nI am trying to submit this notebook: https://www.kaggle.com/berniechou/clean-quantile-image?scriptVersionId=41779873.
\nBut I do not manage to do it, the problem seems to be \"Notebook Timeout\". But I have been investigating for hours and I do not find any possible error. Someone has already had this problem and solved it ?
Thank you
", "rawMarkdown": "Hello everyone, \nI am trying to submit this notebook: https://www.kaggle.com/berniechou/clean-quantile-image?scriptVersionId=41779873.\nBut I do not manage to do it, the problem seems to be \"Notebook Timeout\". But I have been investigating for hours and I do not find any possible error. Someone has already had this problem and solved it ? \n\nThank you", "votes": null }, { "id": "998400", "postDate": "09/04/2020 17:49:21", "content": "Hello! Your notebook is unavailable, chance are it was hidden.
", "rawMarkdown": "Hello! Your notebook is unavailable, chance are it was hidden.", "votes": null }, { "id": "999342", "postDate": "09/05/2020 15:17:20", "content": "It is not limited to this notebook, I've had many of my other notebooks getting infected like this. For reasons unknown once infected randomly the further versions of the notebook behave similarly on submission (Timeout) regardless of changes done
\nLuckily enough I cloned the aforementioned notebook before getting deleted and yes I've faced the same issues on it too.
\nNotice how when I mistakenly re-submitted the same version 1 twice it gives error on the 2nd run and onward versions.
\n
Perhaps someone from Kaggle team could come with a reason for this. I've lost many notebooks and submissions to this infection issue
", "rawMarkdown": "It is not limited to this notebook, I've had many of my other notebooks getting *infected* like this. For reasons unknown once infected randomly the further versions of the notebook behave similarly on submission (Timeout) regardless of changes done\n\nLuckily enough I cloned the aforementioned notebook before getting deleted and yes I've faced the same issues on it too.\nNotice how when I mistakenly re-submitted the same version 1 twice it gives error on the 2nd run and onward versions.\n\n\nPerhaps someone from Kaggle team could come with a reason for this. I've lost many notebooks and submissions to this *infection* issue", "votes": null }, { "id": "1003043", "postDate": "09/08/2020 16:15:59", "content": "If you are receiving a timeout error, it's because your notebook runtime is exceeding the allowable time limit, per the Code Requirements specified for this competition. Note that this runtime applies to both the smaller public run and the longer private run. In this thread the host shares the difference in sizes of these test sets.
", "rawMarkdown": "If you are receiving a timeout error, it's because your notebook runtime is exceeding the allowable time limit, per the [Code Requirements](https://www.kaggle.com/c/osic-pulmonary-fibrosis-progression/overview/code-requirements) specified for this competition. Note that this runtime applies to both the smaller public run **and** the longer private run. [In this thread](https://www.kaggle.com/c/osic-pulmonary-fibrosis-progression/discussion/165723#948287) the host shares the difference in sizes of these test sets.", "votes": null }, { "id": "1003189", "postDate": "09/08/2020 18:08:30", "content": "Although I haven't yet encountered a timeout error with my submissions, I would like to clarify the time limits. The Code Requirements say \"CPU Notebook <= 9 hours run-time\". Does this mean total elapsed time of the run, or is it the total CPU time across all 4 CPUs? The \"Execution Info\" of my last submission said \"Run Time 2618.1 seconds\". Is that what was compared to the 9 hour limit? Also, is that based on the time to predict only for the 15% of data in the Public LB, in which case it could increase considerably when scoring the 85% for the Private LB?
", "rawMarkdown": "Although I haven't yet encountered a timeout error with my submissions, I would like to clarify the time limits. The Code Requirements say \"CPU Notebook <= 9 hours run-time\". Does this mean total elapsed time of the run, or is it the total CPU time across all 4 CPUs? The \"Execution Info\" of my last submission said \"Run Time 2618.1 seconds\". Is that what was compared to the 9 hour limit? Also, is that based on the time to predict only for the 15% of data in the Public LB, in which case it could increase considerably when scoring the 85% for the Private LB?", "votes": null } ], "comments": [ { "id": 998400, "author_name": "koza4ukdmitrij", "author_url": "", "post_date": "09/04/2020 17:49:21", "content": "Hello! Your notebook is unavailable, chance are it was hidden.
", "votes": null, "replies": [] }, { "id": 999342, "author_name": "ii5m0k3ii", "author_url": "", "post_date": "09/05/2020 15:17:20", "content": "It is not limited to this notebook, I've had many of my other notebooks getting infected like this. For reasons unknown once infected randomly the further versions of the notebook behave similarly on submission (Timeout) regardless of changes done
\nLuckily enough I cloned the aforementioned notebook before getting deleted and yes I've faced the same issues on it too.
\nNotice how when I mistakenly re-submitted the same version 1 twice it gives error on the 2nd run and onward versions.
\n
Perhaps someone from Kaggle team could come with a reason for this. I've lost many notebooks and submissions to this infection issue
", "votes": null, "replies": [] }, { "id": 1003043, "author_name": "juliaelliott", "author_url": "", "post_date": "09/08/2020 16:15:59", "content": "If you are receiving a timeout error, it's because your notebook runtime is exceeding the allowable time limit, per the Code Requirements specified for this competition. Note that this runtime applies to both the smaller public run and the longer private run. In this thread the host shares the difference in sizes of these test sets.
", "votes": null, "replies": [] }, { "id": 1003189, "author_name": "dslate", "author_url": "", "post_date": "09/08/2020 18:08:30", "content": "Although I haven't yet encountered a timeout error with my submissions, I would like to clarify the time limits. The Code Requirements say \"CPU Notebook <= 9 hours run-time\". Does this mean total elapsed time of the run, or is it the total CPU time across all 4 CPUs? The \"Execution Info\" of my last submission said \"Run Time 2618.1 seconds\". Is that what was compared to the 9 hour limit? Also, is that based on the time to predict only for the 15% of data in the Public LB, in which case it could increase considerably when scoring the 85% for the Private LB?
", "votes": null, "replies": [] } ], "raw_markdown_by_id": { "996922": "Hello everyone, \nI am trying to submit this notebook: https://www.kaggle.com/berniechou/clean-quantile-image?scriptVersionId=41779873.\nBut I do not manage to do it, the problem seems to be \"Notebook Timeout\". But I have been investigating for hours and I do not find any possible error. Someone has already had this problem and solved it ? \n\nThank you", "998400": "Hello! Your notebook is unavailable, chance are it was hidden.", "999342": "It is not limited to this notebook, I've had many of my other notebooks getting *infected* like this. For reasons unknown once infected randomly the further versions of the notebook behave similarly on submission (Timeout) regardless of changes done\n\nLuckily enough I cloned the aforementioned notebook before getting deleted and yes I've faced the same issues on it too.\nNotice how when I mistakenly re-submitted the same version 1 twice it gives error on the 2nd run and onward versions.\n\n\nPerhaps someone from Kaggle team could come with a reason for this. I've lost many notebooks and submissions to this *infection* issue", "1003043": "If you are receiving a timeout error, it's because your notebook runtime is exceeding the allowable time limit, per the [Code Requirements](https://www.kaggle.com/c/osic-pulmonary-fibrosis-progression/overview/code-requirements) specified for this competition. Note that this runtime applies to both the smaller public run **and** the longer private run. [In this thread](https://www.kaggle.com/c/osic-pulmonary-fibrosis-progression/discussion/165723#948287) the host shares the difference in sizes of these test sets.", "1003189": "Although I haven't yet encountered a timeout error with my submissions, I would like to clarify the time limits. The Code Requirements say \"CPU Notebook <= 9 hours run-time\". Does this mean total elapsed time of the run, or is it the total CPU time across all 4 CPUs? The \"Execution Info\" of my last submission said \"Run Time 2618.1 seconds\". Is that what was compared to the 9 hour limit? Also, is that based on the time to predict only for the 15% of data in the Public LB, in which case it could increase considerably when scoring the 85% for the Private LB?" }, "source": "meta" }