-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
phydro issues #218
Comments
Points resolved (not yet all) as per PR #219 |
Build of > morrisOut.df <- data.frame(
+ parameter = names(par_cal_best),
+ mu.star = apply(abs(morrisOut$ee), 2, mean, na.rm = T),
+ sigma = apply(morrisOut$ee, 2, sd, na.rm = T)
+ ) %>%
+ arrange( mu.star )
Error in data.frame(parameter = names(par_cal_best), mu.star = apply(abs(morrisOut$ee), :
arguments imply differing number of rows: 11, 10 Should run this again but if fails, too: > morrisOut <- sensitivity::morris(
+ model = morris_setup$posterior$density,
+ factors = names(par_cal_best),
+ r = 1000,
+ design = list(type = "oat", levels = 20, grid.jump = 3),
+ binf = par_cal_min,
+ bsup = par_cal_max,
+ scale = TRUE)
Warning in dunif(x, min = lower, max = upper, log = T) : NaNs produced
Error in if (out == Inf) stop("Inf encountered in prior") :
missing value where TRUE/FALSE needed
|
Can PM be used in combination with P-model-Gs? There is code that is now commented but may have to be un-commented and completed? if (use_pml) then
! We plug Pmodel/Phydro-derived gs into the PM equation to calculate T (note this is uncoupled PM-transpiration)
! use PFT-specific gs for this calculation: tile_fluxes(lu)%plant(pft)%gs_accl
! TODO: Fill this in
! tile_fluxes(lu)%plant(pft)%dtransp = PM_EQUATION(tile_fluxes(lu)%plant(pft)%gs_accl) The argument |
Yes, as mentioned in the comment, this is just a placeholder where the PM equation should go. It's not coded in yet. Just uncommenting won't do, because PM_EQUATION doesn't exist. It'll have to be coded. All the PM equation calculations should be done at the PFT level, hence they are in gpp_pmodel rather than waterbal_splash |
I think the PM should be applied at the LU-level (land unit-level), not PFT-level. I suggest to use the fractional plant coverage-weighted average Gs and calculate PML-ET in the waterbal module (it's fine to duplicate code that is already in |
Isn't the whole point of PM to distinguish surface properties of different vegetation types? If you want to do this only for inter-cell differences, then yes, the entire code chunk with the T calculation can be moved to waterbal_splash |
The gridcell-average (or land unit-average) surface properties can be used. The model structure is adopted from LPX (and other similar models) where all PFTs have access to the same soil water and the soil water balance is done at the gridcell-level (or land-unit level). The idea is that PFTs occur tightly interspersed and are not separated into disjunct tiles. The canopy exchanges with the atmosphere and represents a mix of PFTs. |
@jaideep777
I suspect this error arises because you have
contains
statements inside functions and further function definitions below that. Could you move allcontains
statements inside functions (only allowed at top level in module) and specify the functions outside?drivers$params_siml
.devtools::check()
and resolve all issues..Rmd
files. Scripts go intoanalysis/
. Function definitions go intoR/
. Shell scripts go intosrc/
pkgdown::build_site()
) and clean it up - All.Rmd
files invignettes/
will appear as 'Articles'. This will be public-facing. Make it nice.data-raw/
.md_photosynth_phydro
are duplicated as they are already in modulemd_waterbal
. Please remove them frommd_photosynth_phydro
.md_waterbal_pml
, see here? (maybe no so important)stop
,print
, andwrite
statements in Fortran code (except for testing, but comment out upon commit).md_photosynth_phydro
.I suspect that a clear separation between the model and the analysis done for your research @jaideep777 is needed. Keep only the very minimum in the {rsofun} repo such that you achieve a documentation of a very simplified example. Best is to use the data already contained in the repo (flux data for FR-Pue). All that goes beyond that and which is specific to what you did for the model calibration and evaluation on a larger set of sites should go in a separate (personal analysis) repository. Remember that our plan is to have {rsofun} on CRAN...
The text was updated successfully, but these errors were encountered: