Scheduled Downtime
On Tuesday 24 October 2023 @ 5pm MT the forums will be in read only mode in preparation for the downtime. On Wednesday 25 October 2023 @ 5am MT, this website will be down for maintenance and expected to return online later in the morning.
Normal Operations
The forums are back online with normal operations. If you notice any issues or errors related to the forums, please reach out to help@ucar.edu

CLM-FATES fire emission?

xiulingao

Xiulin Gao
New Member
Please fill in all relevant information below, deleting the red text after you have read it.

No post is relevant or provide solutions.


What version of the code are you using?

I am using ctsm5.1.dev153
FATES version sci.1.68.2_api.31.0.0-42, with local changes to the code



Have you made any changes to files in the source tree?
No for CTSM but yes for FATES.


Describe every step you took leading up to the problem:



If this is a port to a new machine: Please attach any files you added or changed for the machine port (e.g., config_compilers.xml, config_machines.xml, and config_batch.xml) and tell us the compiler version you are using on this machine.
Please attach any log files showing error messages or other useful information.

- Not at all.


Describe your problem or question:

I am running CLM-FATES to try get fire emission output from CESM (such as "FireComp_BC", "FireComp_OC"). Nothing wrong during case build and submit (all usual steps one would take to run the model). But after case submit, the model failed and the error indicate that history variables "FireComp_BC" (the first named emission variable) is not found. I then searched online to see what history variables CESM output, found there are two versions of it. The version without FATES has all the emission variables while the version with FATES does not. Does this mean that fire emission outputs are only available for CLM run but not for CLM-FATES run? Is it possible to pass them to FATES too???

Thank you!
 
Top