We now have phenological activity values, biomass, litter, and %live contained within input csvs and passed into rSFSTEP2. We populated these tables with the default values that were being used in sxw_phen.in and sxw_prodv2.in. These same values are being used for every site (but then ultimately scaled based on mean monthly temp).
Potential future functionality related to this issue is to also allow the user to specify differ phenological activity values, biomass, litter, and %live values for sxw_phen.in and sxw_prod.v2.in for different sites (i.e. site-specific inputs). This would be consistent with the functionality available for species, rgroup, and soil inputs (the user can currently provide the same input values for all sites or site-specific inputs).
I document this issue for now and we can re-address its utility in the future.
We now have phenological activity values, biomass, litter, and %live contained within input csvs and passed into rSFSTEP2. We populated these tables with the default values that were being used in sxw_phen.in and sxw_prodv2.in. These same values are being used for every site (but then ultimately scaled based on mean monthly temp).
Potential future functionality related to this issue is to also allow the user to specify differ phenological activity values, biomass, litter, and %live values for sxw_phen.in and sxw_prod.v2.in for different sites (i.e. site-specific inputs). This would be consistent with the functionality available for species, rgroup, and soil inputs (the user can currently provide the same input values for all sites or site-specific inputs).
I document this issue for now and we can re-address its utility in the future.