Try   HackMD

Ecosystems of the Southeast US

The transect that Kristina sampled contains:

Southern Coastal Plain: https://bplant.org/region/134

  • longleaf pine flatwoods and savannas
  • richer forests with slash pine, pond pine, pond cypres, american sweetgum, southern magnolia, laurel oak, white oak, american beech (i.e. mix of evergreen, evergreen hardwood, and deciduous hardwood PFTs)
  • Floodplains with bald cypres, pond cypres, water tupelo, sweetgum, green ash, water hickory ("temperate.Hydric" PFT??)
  • Florida scrub
  • monoculture pine plantations

Southeastern plains: https://bplant.org/region/123

  • more hardwoods and more closed-canopy than southern coastal plain
  • pine forests with longleaf pine and loblolly pine
  • Mixed oak-hickory-pine forests
  • southeastern mixed forest with mix of braodleaf evergreens, deciduous evergreens (SIC), and pines
  • Floodplains had deciduous forests
  • Cypress swamps

Piedmont: https://bplant.org/region/102

  • Different bedrock / soil than other regions
  • oak-pine-hickory forest with various Carya species, shortleaf pine, loblolly pine, white oak, post oak
  • Agriculture, old-field, and early successional forest

Can probably summarize this as:

  1. pine forest
  2. oak-hickory-pine forest (deciduous hardwood and pine)
  3. mixed forest (pine, deciduous hardwood, evergreen hardwood)
  4. prairie (c4 and c3 grass, maybe forb)
  5. old field (like above but with more forbs?) or early successional forest (like prairie but with small trees)

Pine Forest

Notes:
Longleaf pine and loblolly pine DBH by age:
https://www.ncforestservice.gov/publications/techBulletins/TRB009.pdf
https://www.srs.fs.usda.gov/pubs/ja/2014/ja_2014_benecke_001.pdf

For longleaf pine, age range 4-73 years, DBH range is 3.6 to 61cm (mean 24.6, SD 10.3, n = 199) (Gonzalez-Benecke et al. 2014)

data in spatstat.data::longleaf dataset:

584 longleaf pine trees in 200m x 200m plot in southern Georgia. Platt, Evans and Rathbun 1988.

Image Not Showing Possible Reasons
  • The image file may be corrupted
  • The server hosting the image is unavailable
  • The image path is incorrect
  • The image format is not supported
Learn More →

PFTs:

  • temperate.Southern_Pine (7)

Cohorts:

PFT Cohort DBH Density
7 saplings 7.2 0.006125
7 mature 36.9 0.006675
7 old 54.9 0.0018
Last changed by 
 
Eric R Scott
0
58

Read more

Questions for Personal Trainers

Hi ____,

Sep 20, 2024
AZmet QA/QC

Matt "plugged in" rounding to correct precision--only applied to new data (since the last month or so) Part of azmetr could be checking for correct precision Matt has a place online where we can edit the measured variables and it will propogate to derived variables (we think). Split tasks: modeling and workflow automation Phase one is alert Jeremy of extreme values and imputed values (a daily report table published with Quarto, for example) Could fit multivariate model as additional step (can't be raining all day and have high solar radiation) Could detect things in derived variables that we don't see in measured variables beause of transformations? Report refinements Report currently uses all data for rule-based validations and just one day for forecast-based validations. This doesn't make sense. Need some flexibility in terms of what days are being viewed in the report and consistency between types of validations.

Jan 30, 2023
"Manually" updating PEcAn.ED / ED2 singularity container on HPC

NOTE: I never got this to work. The docker containers don't run for reasons I don't understand. There are only 2 possibilities currently for ED versions because there is only one release tag---v.2.2.0. So its either that or the development version "git". If you want a specific commit, you'll have to edit the code in the Dockerfile to git checkout a specific SHA. Why would you want to do this? When running ED2 models on the HPC, you might want to: use the development version of ED2 when the container on docker hub isn't updated use a version of PEcAn.ED2 other than the develop branch or the latest release (e.g. a PR you're working on) use some custom combination of PEcAn and ED2 versions

Nov 1, 2022
Mismatch between priors and data

What's the deal with the posteriors.pdf plots for setariaWT? Vcmax: Prior in BETY says dist = lnorm, a = 3.75, b = 0.3, n = 12 query.trait.data() also shows 3.75, 0.3, 12 Prior in Vcmax.model.bug says beta.o ~ dlnorm (3.75, 11.1111111111111)#BBB. This is just because BUGS paramaterizes distributions differentlly None of those are truncated at ~20 like in the plot above Output of query.trait.data():

Sep 27, 2022
Read more from Eric R Scott
Published on HackMD