BioRT-Flux-PIHM

BioRT-Flux-PIHM is the watershed-scale biogeochemical reactive transport model of the PIHM family code MM-PIHM for watershed processes.

watershed-scalebiogeochemicalwatershed processes
342

Authorship

Homepage:
View
Is authorship not correct? Feed back

Classification(s)

Application-focused categoriesNatural-perspectiveLand regions

Model Description

English {{currentDetailLanguage}} English

Quoted from: https://github.com/PSUmodeling/BioRT-Flux-PIHM

BioRT-Flux-PIHM is the watershed-scale biogeochemical reactive transport model of the PIHM family code MM-PIHM (https://github.com/PSUmodeling/MM-PIHM) for watershed processes. The model couples three modules: a multi-component bio-reactive transport module 'BioRT', the land-surface interaction module 'Flux' for processes such as solar radiation and evapotranspiration, and the surface hydrology module 'PIHM' for hydrological processes (e.g., precipitation, infiltration, recharge, surface runoff, subsurface interflow, and groundwater flow). The BioRT module takes in the calculated water fluxes and storages from Flux-PIHM and simulates processes including transport (advection, diffusion, and dispersion) and biogeochemical reactions. The reactions can be kinetics-controlled (e.g., mineral dissolution and precipitation and microbe-mediated reactions) and/or thermodynamically controlled (e.g., ion exchange, surface complexation (sorption), and aqueous complexation). The output is the aqueous and solid concentrations of interests.

The new version is developed based on the original RT-Flux-PIHM (Bao et al., 2017; Li et al., 2017), with expansions that include: 1) biotic processes including plant uptake, and microbe-mediated biogeochemical reactions that are relevant to the transformation of organic matter that involve carbon, nitrogen, and phosphorus; and 2) shallow and deep water partitioning to represent the surface and groundwater interactions, enabling the simulation of the “two water tables”. The model can be set up and run in two modes: the spatially explicit mode (i.e., a complex domain of hundreds of grids) vs. the spatially implicit mode (i.e., the two-grid model that has two land cells representing two hillslopes connected by one river cell). The spatially explicit mode includes details of topography, land cover, and soil/geology properties. It can be used to understand the impacts of spatial structure and identify hot spots of biogeochemical reactions. The spatially implicit mode focuses on processes and average behavior of a watershed. It requires less spatial data, is computationally inexpensive, and is relatively easy to set up.

The reactive transport part of the code has been verified against the widely used reactive transport benchmark code CrunchTope. The model BioRT-Flux-PIHM has recently been applied to understand reactive transport processes in multiple watersheds across different climate, vegetation, and geology conditions.

This page is in the development stage. Detailed instructions and example files will be added over time. For now, readers are referred to Bao et al. (2017) for details of code structure, governing equations, and example runs, and to Li et al. (2017) and Wen et al. (2020) for particular applications in the Susquehanna Shale Hills Critical Zone Observatory (SSHCZO), one of the 10 national CZOs in the United States, and to Zhi et al., (2019) for its application in Coal Creek, CO, a high-elevation mountaineous watershed in the central Rocky mountains.

For PIHM's diverse applications at other watersheds, see the page https://github.com/PSUmodeling/PIHM-Simulations

Model Domain
{{domain}}

Principles
{{principle}}
Incorporated Models
{{incorporatedModel}}
Model part of larger framework: {{metadata.design.framework}}
Incorporated Models
{{process}}

Inputs
{{input}}
Outputs
{{output}}

There is no usage info about this model. You can click to add overview.

How to Cite

Penn State Earth System Modeling Team (2019). BioRT-Flux-PIHM, Model Item, OpenGMS, https://geomodeling.njnu.edu.cn/modelItem/be114b1c-36bc-41a6-85e3-b020668203ff

Comment(s)

{{comment.date}}
{{comment.content}}
{{subComm.date}}
{{subComm.content}}

Authorship

Homepage:
View
Is authorship not correct? Feedback

QR Code

• {{curRelation.name}}
{{curRelation.name}}

{{curRelation.overview}}
{{curRelation.author.join('; ')}}
{{curRelation.journal}}

You can link related {{typeName}} from repository to this model item, or you can create a new {{typeName.toLowerCase()}}.

Related Items
{{ props.row.description }}
{{ props.row.description }}
Related Items
{{props.row.name}}

You can link resource from repository to this model item, or you can create a new {{typeName.toLowerCase()}}.

{{ props.row.description }}
{{ props.row.description }}
Drop the file here, orclick to upload.
File size should not exceed 10m.
Select From My Space

These authorship information will be submitted to the contributor to review.

Cancel Submit
Model Classifications
Cancel Submit
{{ item.label }} {{ item.value }}
{{props.row.localName}}
Model Name :
Cancel Submit
Name:
Version:
Model Type:
Model Domain:
Scale:
Purpose:
Principles:
Incorporated models:

Model part of

larger framework

Process:
Information:
Initialization:
Hardware Requirements:
Software Requirements:
Inputs:
Outputs:
Cancel Submit
Title Author Date Journal Volume(Issue) Pages Links Doi Operation
Cancel Submit

Yes, this is it Cancel

OK
Cancel Confirm
Model Classifications 1
Model Classifications 2
Title Author Date Journal Volume(Issue) Pages Links Doi Operation

NEW

Name:
Affiliation:
Email:
Homepage:

Yes, this is it Cancel

Confirm
path
:
/{{path.label}}
search results of '{{searchContentShown}}'

No content to show

{{item.label}}

.

{{item.suffix}}

.{{item.suffix}}

{{item.fileName}}.{{item.suffix}}

Copy
Delete
Rename
/{{path.label}}
Change
/{{path.label}}
Select File
Cancel Confirm
path
:
/{{path.label}}
/..
Cancel Confirm
{{ node.label }}
You have select  {{multipleSelection.length+multipleSelectionMyData.length}} data .
• My Uploaded Data
• Output Data
• {{item.computableName}}@{{formatDate(item.runTime)}}
{{scope.row.type}}
{{ scope.row.tag }}