Steps needed to enable BLAZE within CABLE/ACCESS independently of POP

[har917]

This is a placeholder/umbrella issue for (likely) several issues that will be spread across the various repos

At the risk of getting ahead of ourselves (6/2026) - BLAZE has been partially reconfigured so that the science code can operate without POP (note that operate /= equivalent). This opens up the possibility of enabling BLAZE within ACCESS ahead of the more difficult task of merging the CABLE and CABLE-POP lines of development.

However there are some tasks that require additional effort (within CABLE and/or ACCESS) before this is possible.

From a technical perspective:

1. all additional state variables need to be identified and (for ACCESS at least) included in the restart. This includes elements of the climate% TYPE and (at least) sumBLAZE%annBA (since we need to cover monthly chunking in AM3).
2. rewriting the climate% MODULE so that only the necessary calculations/variables are required.
3. a better method of passing information about which patches/tiles belong in which grid cell needs to be designed and implemented across all applications. Currently this relies on USEing the land_pts% construct which is specific to offline simulations.
4. testing with non-zero grid cell fractions for lake, bare soil, urban and ice needs to be undertaken.
5. testing with phosphorus cycle active (noting that we shouldn't lose P with fire, instead convert it between pools - this is unlike C and N).
6. general i/o considerations - e.g. parallelisation, namelist read/distribution, adding additional outputs to standard CABLE offline output, default values, frequency of read etc. and (in ACCESS) where different bits of the memory sit.

I expect 3. and 6. to be the most problematic

From a science perspective:

• consideration of fire season start and how to reset variables accordingly.
• encapsulating the dependence between fire events and biophysical parameters such as surface reflectences (i.e. albedo) and possibly canopy height.