the Creative Commons Attribution 4.0 License.
the Creative Commons Attribution 4.0 License.
| 29 Dec 2025
Development of ACFIRE version 1.0: A mesoscale model with forest canopy and fire behavior submodels
Abstract. Numerical models are essential for advancing understanding of fire–atmosphere interactions, especially where field campaigns alone cannot provide sufficient insight. Existing wildland fire models vary greatly in complexity and scale, from computational fluid dynamics models with detailed combustion submodels, to mesoscale models with empirical or semi-empirical combustion representations, to global or regional models that omit combustion byproducts altogether. However, no current framework simultaneously resolves atmospheric responses to wildland fires across scales from hundreds of meters to hundreds of kilometers, incorporates a comprehensive suite of physical parameterizations, and explicitly resolves some scales of atmospheric turbulence within and above a forest canopy. To address this gap, we introduce ARPS-CANOPY/DEVS-FIRE (hereafter, ACFIRE), a mesoscale model that integrates a canopy resolving atmospheric model (ARPS-CANOPY) with a fire behavior model (DEVS-FIRE), and detail its development and preliminary evaluation. Unlike the original ARPS-CANOPY, which relied on a user-imposed fire heat source, ACFIRE employs two-way fire-atmosphere coupling to compute heat release dynamically. We demonstrate the coupled modeling system with a low-intensity prescribed fire conducted in the New Jersey Pine Barrens in March 2019, comparing simulated fire spread rates with measurements from an array of surface thermocouples deployed during the fire. The simulated spread rates compare favorably to observed spread rates, with differences mainly attributable to the use of uniform fuels in the ACFIRE simulation. The integration of the dynamically coupled fire heat source represents a significant advance in canopy-resolving mesoscale modeling, and beyond this case, highlights the potential of ACFIRE to extend the application of atmosphere-fire models to a broader range of wildland fire research questions as well as future operational use.
- Preprint
(9927 KB) - Metadata XML
-
Supplement
(22555 KB) - BibTeX
- EndNote
Status: open (until 23 Feb 2026)
-
CEC1: 'Comment on egusphere-2025-5863 - No compliance with the policy of the journal', Juan Antonio Añel, 07 Jan 2026
reply
-
AC1: 'Reply on CEC1', Shiyuan Zhong, 12 Jan 2026
reply
Dear Chief Editor,
Thank you for your detailed clarification regarding GMD’s Code and Data Policy. We would like to seek clarification on whether making an executable version of the ACFIRE model publicly available would be considered acceptable under the policy. The ACFIRE model is built on top of DEVS-FIRE, which in turn depends on DEVSJAVA, a framework copyrighted by the University of Arizona. Due to licensing restrictions associated with DEVSJAVA, we are not able to make the full source code of DEVS-FIRE publicly available. As a result, this limitation also affects the distribution of ACFIRE source code. Under these constraints, we can provide a publicly accessible executable version of the ACFIRE model, along with sufficient documentation to allow users to run the model and reproduce the results presented in the manuscript. We would appreciate your guidance on whether this level of access would satisfy GMD’s requirements for code availability during the discussion and review process, or whether full source-code publication is strictly required.
Thank you for your time and consideration. We look forward to your advice on how best to proceed.
Sincerely,
Sharon Zhong,
on behalf of the authors
Citation: https://doi.org/10.5194/egusphere-2025-5863-AC1 -
CEC2: 'Reply on AC1', Juan Antonio Añel, 12 Jan 2026
reply
Dear authors,
Executable packages that do not allow to see and check the code of a software do not comply with the requirements of the journal, as they do not allow to review the code, which is equivalent to reviewing the methods.
In your reply you state that "licensing restrictions associated with DEVSJAVA" prevent you of publishing the DEVS-FIRE AND AC-FIRE source code. To decide if we can accept them as an exception to our policy, we need to know which are the mentioned licensing issues, have access to the license, how they affect by inheritance of licensing properties to the DEVS-FIRE and AC-FIRE licenses, and to also who makes the decision on such license. For example, you need to demonstrate that none of the authors have the capability to influence on the decision of the license used and that does not allow sharing the code, and that such license has been imposed by an authority, law or regulation that forbids you (the authors of the paper) to publish the code. Otherwise, it is requested that you make public the code without restrictions or limitations to accept your manuscript for peer-review in GMD.
I hope this makes clearer the situation.
Juan A. Añel
Geosci. Model Dev. Executive Editor
Citation: https://doi.org/10.5194/egusphere-2025-5863-CEC2 -
AC2: 'Reply on CEC2', Shiyuan Zhong, 12 Jan 2026
reply
Dear Chief Editor,
Thank you again for your prompt response and for your detailed explanation the conditions under which exceptions to GMD’s Code and Data Policy may be considered. This is very helpful.
We would like to clarify the current situation regarding licensing and our ability to release the source code for DEVS-FIRE and AC-FIRE. DEVS-FIRE is built on top of DEVSJAVA, which is copyrighted by the University of Arizona. Our understanding is that the DEVSJAVA license does not currently permit redistribution of derivative source code without explicit permission from the copyright holder. Because DEVS-FIRE inherits core components and architectural elements from DEVSJAVA, this restriction propagates to DEVS-FIRE and, by extension, to AC-FIRE, which is a module developed on top of DEVS-FIRE. Importantly, the licensing terms for DEVSJAVA were not determined by the authors of this manuscript, and none of the authors have the authority to modify or override those terms. The decision regarding the DEVSJAVA license rests entirely with the University of Arizona as the copyright holder. As such, our current inability to publish the source code is not a matter of author preference, but rather a consequence of third-party copyright and licensing constraints.
Following your guidance, we have now initiated contact with the University of Arizona to formally request permission to release the relevant source code in a public repository. In parallel, we would appreciate clarification from GMD on the specific licensing requirements expected for code publication associated with a journal article (e.g., whether a particular open-source license is required or recommended). This information is necessary for us to assess the implications for DEVS-FIRE and to clearly communicate the journal’s requirements to the University of Arizona as part of our permission request. Once we receive clarification on the required license terms and a response from the University of Arizona, we will be in a better position to determine whether full compliance with GMD’s policy is feasible. We will, of course, report back promptly with any updates.
Thank you again for your time and for outlining the policy requirements clearly.
Sincerely,
Dr. Sharon Zhong, on behalf of all authors
Citation: https://doi.org/10.5194/egusphere-2025-5863-AC2 -
CEC3: 'Reply on AC2', Juan Antonio Añel, 13 Jan 2026
reply
Dear authors,
Thanks for your reply. I would like to insist on the fact that copyright and licensing are different issues. The University of Arizona could be the owner of the copyright of DEVSJAVA, and at the same time to be perfectly allowed to distribute the code. In this regard, please share the DEVSJAVA license, so we can judge better.
Also, the fact that DEVS-FIRE and AC-FIRE are build on top of DEVSJAVA does not necessarily affects them. This is exactly why we need the terms of the DEVSJAVA license, to check it. Actually, unless the DEVSJAVA license contains a "viral" clause, something quite uncommon, you can publish the DEVS-FIRE and AC-FIRE codes, as it seems clear that you have developed them.
The journal does not recommend a specific license to be used. However, the policy of the journal, which I have linked in my first comment, mentions as examples the GPL or MIT licenses.
Juan A. Añel
Geosci. Model Dev. Executive Editor
Citation: https://doi.org/10.5194/egusphere-2025-5863-CEC3 -
AC3: 'Reply on CEC3', Shiyuan Zhong, 14 Jan 2026
reply
Dear Chief Editor,
We have had extensive discussions with the Georgia State University tech transfer office and have reviewed the attached DEVSJAVA copyright form from the University of Arizona. The license we hold permits use of DEVSJAVA solely for educational and research purposes and explicitly prohibits further distribution.
Please review the attached license and let us know whether it would be sufficient to allow the DEVS-FIRE code to be made available for review, even though DEVSJAVA itself cannot be distributed. We truly wish to publish this article in your journal, which provides the ideal audience for our work.
We apologize for the length of this discussion and greatly appreciate your patience and guidance throughout the process.
-
CEC4: 'Reply on AC3', Juan Antonio Añel, 15 Jan 2026
reply
Dear authors,
From the license form you have attached, it is quite obvious that it does not impose any restriction on additional software or code developed on top of DEVSJAVA. Therefore, you must publish and share the DEVSFIRE and AC-FIRE codes following the policy of the journal. Please, read it for a list of acceptable repositories and requirements, and reply to this comment with their links and DOIs. Also, remember that you will have to modify your manuscript accordingly in the future (including the same information in the Code and Data Availability section of the manuscript) if the Topical Editor decides to move ahead in the review process or accept the manuscript for publication.
Juan A. Añel
Geosci. Model Dev. Executive Editor
Citation: https://doi.org/10.5194/egusphere-2025-5863-CEC4 -
EC1: 'Reply on CEC4', Chiel van Heerwaarden, 15 Jan 2026
reply
I would like to learn as soon as possible whether this is possible, to avoid letting people review a paper that won't be published. Thanks!
Citation: https://doi.org/10.5194/egusphere-2025-5863-EC1 -
AC5: 'Reply on EC1', Shiyuan Zhong, 15 Jan 2026
reply
Dear Dr. van Heerwaarden,
As noted in our response to the Chief Editor’s comment, the issue has now been resolved, and we have uploaded all related materials, including all source codes, to the same data archive under the same DOI.
We sincerely apologize for the delay and for any inconvenience this process may have caused. We look forward to receiving the reviewers’ comments in due course.
Thank you again for your time and consideration!
Dr. Sharon Zhong (on behalf of all co-authors)
Citation: https://doi.org/10.5194/egusphere-2025-5863-AC5
-
AC5: 'Reply on EC1', Shiyuan Zhong, 15 Jan 2026
reply
-
AC4: 'Reply on CEC4', Shiyuan Zhong, 15 Jan 2026
reply
Dear Chief Editor,
Thank you for pointing this out and for your careful review of the license language. We have been able to resolve the issue and have now uploaded all relevant materials, including the DEVS-FIRE and AC-FIRE codes, to the same data archive under the same DOI. The repository link and DOI are therefore unchanged. We understand that the manuscript will need to be updated accordingly, and we will revise the Code and Data Availability section in the future, should the Topical Editor decide to move the paper forward in the review process or toward acceptance.
Thank you very much again for your guidance and for helping us ensure compliance with the journal’s policy!
Dr. Sharon Zhong (on behalf of all authors)
Citation: https://doi.org/10.5194/egusphere-2025-5863-AC4 -
CEC5: 'Reply on AC4', Juan Antonio Añel, 16 Jan 2026
reply
Dear authors,
Many thanks for addressing this issue. We can consider now the current version of your manuscript in compliance with the code and data policy of the journal.
Juan A. Añel
Geosci. Model Dev. Executive Editor
Citation: https://doi.org/10.5194/egusphere-2025-5863-CEC5
-
CEC5: 'Reply on AC4', Juan Antonio Añel, 16 Jan 2026
reply
-
EC1: 'Reply on CEC4', Chiel van Heerwaarden, 15 Jan 2026
reply
-
CEC4: 'Reply on AC3', Juan Antonio Añel, 15 Jan 2026
reply
-
AC3: 'Reply on CEC3', Shiyuan Zhong, 14 Jan 2026
reply
-
CEC3: 'Reply on AC2', Juan Antonio Añel, 13 Jan 2026
reply
-
AC2: 'Reply on CEC2', Shiyuan Zhong, 12 Jan 2026
reply
-
CEC2: 'Reply on AC1', Juan Antonio Añel, 12 Jan 2026
reply
-
AC1: 'Reply on CEC1', Shiyuan Zhong, 12 Jan 2026
reply
Viewed
| HTML | XML | Total | Supplement | BibTeX | EndNote | |
|---|---|---|---|---|---|---|
| 214 | 63 | 21 | 298 | 35 | 62 | 58 |
- HTML: 214
- PDF: 63
- XML: 21
- Total: 298
- Supplement: 35
- BibTeX: 62
- EndNote: 58
Viewed (geographical distribution)
| Country | # | Views | % |
|---|
| Total: | 0 |
| HTML: | 0 |
| PDF: | 0 |
| XML: | 0 |
- 1
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
You do not provide in your manuscript a repository neither for the DEVS-FIRE nor the ACfire model, which we can not accept. You mention in the Code and Data Availability section of your manuscript that the fact that DEVS-FIRE is based on DEVSJAVA and copyrighted by the University of Arizona makes not possible to share it. This is not right. The fact that a software is based on other or ownership of copyright do not prevent publication of a software, but terms of licenses, and the potential share of code from one software used to develop another. In this way, it is perfectly possible that DEVS-FIRE can be published.
Something similar happens with ACfire. In this case, it seems even more clear that this is a kind of new module developed on top of DEVS-FIRE and presented in this work. Again, unless a licensing issue prevents it, which you should clarify, it is perfectly possible to publish the ACfire code.
You mention in your Code and Data Availability statement that "Furthermore, we are considering the option of commercializing the DEVS-FIRE software to better serve the community. " This statement is irrelevant for the purpose of the of the section, and therefore, you should remove it. Moreover, it is important to note that publishing a software under a free-libre open source software license does not prevent you from commercializing it, so such reasoning is wrong.
The GMD review process depends on reviewers and community commentators being able to access, during the discussion phase, the code and data on which a manuscript depends. Please, therefore, publish the DEVS-FIRE and ACfire software in one of the appropriate repositories and reply to this comment with the relevant information (link and a permanent identifier for it (e.g. DOI)) as soon as possible. We cannot have manuscripts under discussion that do not comply with our policy.
The 'Code and Data Availability’ section must also be modified to cite the new repository locations, and corresponding references added to the bibliography.
I must note that if you do not fix this problem, we cannot continue with the peer-review process or accept your manuscript for publication in GMD.
Juan A. Añel
Geosci. Model Dev. Executive Editor