Dear authors,

Unfortunately, after checking your manuscript, it has come to our attention that it does not comply with our "Code and Data Policy".

https://www.geoscientific-model-development.net/policies/code_and_data_policy.html

After checking your manuscript and its "Code and data availability" statement several outstanding issues arise.

First, the section states "The MIT data on tropical cyclone tracks with wind and precipitation fields data shall be used for non‐commercial research or academic purposes only. Data can be made available by the ISIMIP team upon written consent by Kerry Emanuel (MIT, email: emanuel@mit.edu)".  Dr. Emanuel is a co-author of this submitted manuscript, therefore, it does not make any sense to point out to readers to contact somebody that is co-author to get access to the mentioned data. Therefore, you must publish the mentioned data in one of the repositories acceptable according to our policy, and reply to this comment with its link and permanent identifier. If some kind of law or regulation prevents you of sharing such data, then you need to provide us with evidence of it, and we will study the possibility of granting you an exception to it.

Second, you state "All other input data described are available for participating modelers with a respective account from the DKRZ server." This information is not enough. We can accept the DKRZ servers as hosting service for the repositories containing the mentioned data, but you must provide specific information (links and permanent identifiers) for all of them. I am aware that you communicated internally before that "The described data includes >1000 data sets that are comprised in quite a number of DOIs. Should we cite all these DOIs here again?". If with your question you were referring to these datasets, the answer to your question if you have used them to produce your manuscript, is "yes". A potential solution for this is that you deposit a document containing such information in a permanent repository and you link in the manuscript such repository (with its link and permanent identifier).

Also, you state that "Data will be made publicly available... at the ISIMIP data repository at https://data.isimip.org/". First, we can not accept expressions of future compliance with our policy. The policy of the journal is very clear that compliance with code and data availability must be assured before submitting a manuscript to the journal. Therefore, you must publish all the datasets, as they should have been published before submission, and your manuscript desk rejected instead of accepted for Discussions because of such lack of compliance.

A major problem is that you host your data in the ISIMIP data portal, managed by the PIK. You state that it complies with the policy of the journal, but it does not comply. I have checked the ISIMIP webpage and terms of use. First, we do not have any kind of guarantee that the PIK servers comply with our requirements for long-term archival, usually requested in at least 15-20 years of secured funding to operate. The ISIMIP portal is simply a subdomain of pik-postdam.de, operating under the same IP address than the PIK webpage. Second, you state that data removal has to be approved by the ISIMIP steering committee, but my understanding is that this is basically the list of authors contributing to this manuscript, which actually means that the authors can decide to remove the data, and this is not acceptable according to the policy of the journal. Also, the "ISIMIP data team" is mentioned, but it is not clear at all who are the persons in such committee or how it operates. From the structure published in the ISIMIP web page, it looks like if only one person is involved on it, identified as the "ISIMIP data manager".

In summary, there are many outstanding issues regarding your manuscript and its compliance with the policy of the journal, and the fact that it is under review and Discussions without having properly addressed all of them is irregular. Therefore, please, publish the necessary data in one of the repositories listed in our policy and reply to this comment as soon as possible with a modified 'Code and Data Availability' section for your manuscript, which must include the relevant information (link and handle or DOI) of the new repositories, and which you should include in a potentially reviewed manuscript.

I must note that if you do not fix this problem, we will have to reject your manuscript for publication in our journal.

Juan A. Añel

Geosci. Model Dev. Executive Editor