Find research datasets worth reusing
Search datasets from major research repositories and use ShareScore to quickly assess how well each record supports discovery, access, and reuse.
695
datasets available to search
ShareScore release 0.7.1
Dataset results
695 results for “Model output”
AgMIP's global gridded crop model intercomparison (GGCMI) phase II CTWN-A archive: priority 1 outputs from LPJmL soybean simulations
<p>This data set contains output data from simulations with the model LPJmL for soybean as part of AgMIP's Global Gridded Crop Model Intercomparison (GGCMI) phase II output data set. Output variables included are: crop yield, above-ground biomass, plant day, maturity day, potential irrigation water withdrawal, actual growing season evapotranspiration . Simulations are based on 31-year simulations using the AgMERRA data set with 4 atmospheric CO2 mixing ratios (C=360, 510, 660, 810 ppm) uniform offsets for temperature (T= -1, 0, 1, 2, 3, 4, 6 K), water (W= -50, -30, -20, -10, 0, 10, 20, 30 %, and infinite/irrigated), and 3 nitrogen input levels (N= 10, 60, 200 kgN/ha) using 2 assumptions on adaptation (A= 'none', 'regain original growing season').</p> <p>Version 2 of these files has been corrected with respect to the temporal sequence of results, which is not important if looking at 30-year averages as in Franke et al. 2020, but becomes relevant if looking at individual years.</p>
AgMIP's global gridded crop model intercomparison (GGCMI) phase II CTWN-A archive: priority 1 outputs from LPJmL rice simulations
<p>This data set contains output data from simulations with the model LPJmL for rice as part of AgMIP's Global Gridded Crop Model Intercomparison (GGCMI) phase II output data set. Output variables included are: crop yield, above-ground biomass, plant day, maturity day, potential irrigation water withdrawal, actual growing season evapotranspiration . Simulations are based on 31-year simulations using the AgMERRA data set with 4 atmospheric CO2 mixing ratios (C=360, 510, 660, 810 ppm) uniform offsets for temperature (T= -1, 0, 1, 2, 3, 4, 6 K), water (W= -50, -30, -20, -10, 0, 10, 20, 30 %, and infinite/irrigated), and 3 nitrogen input levels (N= 10, 60, 200 kgN/ha) using 2 assumptions on adaptation (A= 'none', 'regain original growing season').</p> <p>Version 2 of these files has been corrected with respect to the temporal sequence of results, which is not important if looking at 30-year averages as in Franke et al. 2020, but becomes relevant if looking at individual years.</p>
AgMIP's global gridded crop model intercomparison (GGCMI) phase II CTWN-A archive: priority 1 outputs from LPJmL maize simulations
<p>This data set contains output data from simulations with the model LPJmL for maize as part of AgMIP's Global Gridded Crop Model Intercomparison (GGCMI) phase II output data set. Output variables included are: crop yield, above-ground biomass, plant day, maturity day, potential irrigation water withdrawal, actual growing season evapotranspiration . Simulations are based on 31-year simulations using the AgMERRA data set with 4 atmospheric CO2 mixing ratios (C=360, 510, 660, 810 ppm) uniform offsets for temperature (T= -1, 0, 1, 2, 3, 4, 6 K), water (W= -50, -30, -20, -10, 0, 10, 20, 30 %, and infinite/irrigated), and 3 nitrogen input levels (N= 10, 60, 200 kgN/ha) using 2 assumptions on adaptation (A= 'none', 'regain original growing season').</p> <p>Version 2 of these files has been corrected with respect to the temporal sequence of results, which is not important if looking at 30-year averages as in Franke et al. 2020, but becomes relevant if looking at individual years.</p>
Model output from the Bern3D model of pre-industrial and Last Glacial Maximum
<p>The here presented datasets contain the model results of the Bern3D model to be published in Pöppelmeier et al. (2021) <em>Climate of the Past Discussions</em> (https://doi.org/10.5194/cp-2020-135).</p> <p>The datasets of the five performed simulations are presented: PI_CTRL, LGM_CTRL, LGM_BS, LGM_BS+wind, LGM_BS+wind+tidal. For detailed information on the model set ups please see section 2 and Table 1 of Pöppelmeier et al. (2021).</p>
RAPID input and output files corresponding to "RAPID Applied to the SIM-France Model"
<p><strong>Corresponding peer-reviewed publication</strong></p> <p>This dataset corresponds to all the RAPID input and output files that were used in the study reported in:</p> <ul> <li>David, Cédric H., Florence Habets, David R. Maidment and Zong-Liang Yang (2011), RAPID applied to the SIM-France model, Hydrological Processes, 25(22), 3412-3425. DOI: 10.1002/hyp.8070. </li> </ul> <p> </p> <p>When making use of any of the files in this dataset, please cite both the aforementioned article and the dataset herein. </p> <p> </p> <p><strong>Time format</strong></p> <p>The times reported in this description all follow the ISO 8601 format. For example 2000-01-01T16:00-06:00 represents 4:00 PM (16:00) on Jan 1<sup>st</sup> 2000 (2000-01-01), Central Standard Time (-06:00). Additionally, when time ranges with inner time steps are reported, the first time corresponds to the beginning of the first time step, and the second time corresponds to the end of the last time step. For example, the 3-hourly time range from 2000-01-01T03:00+00:00 to 2000-01-01T09:00+00:00 contains two 3-hourly time steps. The first one starts at 3:00 AM and finishes at 6:00AM on Jan 1<sup>st</sup> 2000, Universal Time; the second one starts at 6:00 AM and finishes at 9:00AM on Jan 1<sup>st</sup> 2000, Universal Time.</p> <p> </p> <p><strong>Data sources</strong></p> <p>The following sources were used to produce files in this dataset:</p> <ul> <li>The hydrographic network of SIM-France, as published in Habets, F., A. Boone, J. L. Champeaux, P. Etchevers, L. Franchistéguy, E. Leblois, E. Ledoux, P. Le Moigne, E. Martin, S. Morel, J. Noilhan, P. Quintana Seguí, F. Rousset-Regimbeau, and P. Viennot (2008), The SAFRAN-ISBA-MODCOU hydrometeorological model applied over France, Journal of Geophysical Research: Atmospheres, 113(D6), DOI: 10.1029/2007JD008548.</li> <li>The observed flows are from Banque HYDRO, Service Central d’Hydrométéorologie et d’Appui à la Prévision des Inondations. Available at http://www.hydro.eaufrance.fr/index.php.</li> <li>Outputs from a simulation using SIM-France (Habets et al. 2008). The simulation was run by Florence Habets, and produced 3-hourly time steps from 1995-08-01T00:00+02:00 to 2005-07-31T21:02+00:00. Further details on the inputs and options used for this simulation are provided in David et al. (2011).</li> </ul> <p> </p> <p><strong>Software</strong></p> <p>The following software were used to produce files in this dataset:</p> <ul> <li>The Routing Application for Parallel computation of Discharge (RAPID, David et al. 2011, http://rapid-hub.org), Version 1.1.0. Further details on the inputs and options used for this series of simulations are provided below and in David et al. (2011).</li> <li>ESRI ArcGIS (http://www.arcgis.com). </li> <li>Microsoft Excel (https://products.office.com/en-us/excel). </li> <li>The GNU Compiler Collection (https://gcc.gnu.org) and the Intel compilers (https://software.intel.com/en-us/intel-compilers). </li> </ul> <p> </p> <p><strong>Study domain</strong></p> <p>The files in this dataset correspond to one study domain:</p> <ul> <li>The river network of SIM-France is made of 24264 river reaches. The temporal range corresponding to this domain is from 1995-08-01T00:00+02:00 to 2005-07-31 T21:00+02:00.</li> </ul> <p> </p> <p><strong>Description of files </strong></p> <p>All files below were prepared by Cédric H. David, using the data sources and software mentioned above. </p> <ul> <li><em>rapid_connect_France.csv.</em> This CSV file contains the river network connectivity information and is based on the unique IDs of the SIM-France river reaches (the IDs). For each river reach, this file specifies: the ID of the reach, the ID of the unique downstream reach, the number of upstream reaches with a maximum of four reaches, and the IDs of all upstream reaches. A value of zero is used in place of NoData. The river reaches are sorted in increasing value of ID. The values were computed based on the SIM-France FICVID file. This file was prepared using a Fortran program.</li> <li><em>m3_riv_France_1995_2005_ksat_201101_c_zvol_ext.nc. </em>This netCDF file contains the 3-hourly accumulated inflows of water (in cubic meters) from surface and subsurface runoff into the upstream point of each river reach. The river reaches have the same IDs and are sorted similarly to <em>rapid_connect_France.csv</em>. The time range for this file is from 1995-08-01T00:00+02:00 to 2005/07/31T21:00+02:00. The values were computed using the outputs of SIM-France. This file was prepared using a Fortran program.</li> <li><em>kfac_modcou_1km_hour.csv.</em> This CSV file contains a first guess of Muskingum k values (in seconds) for all river reaches. The river reaches have the same IDs and are sorted similarly to <em>rapid_connect_France.csv</em>. The values were computed based on the following information: ID, size of the side of the grid cell, Equation (5) in David et al. (2011), and using a wave celerity of 1 km/h. This file was prepared using a Fortran program.</li> <li><em>kfac_modcou_ttra_length.csv. </em>This CSV file contains a second guess of Muskingum k values (in seconds) for all river reaches. The river reaches have the same IDs and are sorted similarly to <em>rapid_connect_France.csv</em>. The values were computed based on the following information: ID, size of the side of the grid cell, travel time, and Equation (9) in David et al. (2011).</li> </ul> <ul> <li><em>k_modcou_0.csv.</em> This CSV file contains Muskingum k values (in seconds) for all river reaches. The river reaches have the same COMIDs and are sorted similarly to <em>rapid_connect_San_Guad.csv</em>. The values were computed based on the following information: <em>kfac_modcou_1km_hour.csv </em>and using Table (2) in David et al. (2011). This file was prepared using a Fortran program.</li> </ul> <ul> <li><em>k_modcou_1.csv.</em> This CSV file contains Muskingum k values (in seconds) for all river reaches. The river reaches have the same COMIDs and are sorted similarly to <em>rapid_connect_San_Guad.csv</em>. The values were computed based on the following information: <em>kfac_modcou_1km_hour.csv </em>and using Table (2) in David et al. (2011). This file was prepared using a Fortran program.</li> <li><em>k_modcou_2.csv. </em>This CSV file contains Muskingum k values (in seconds) for all river reaches. The river reaches have the same COMIDs and are sorted similarly to <em>rapid_connect_San_Guad.csv</em>. The values were computed based on the following information: <em>kfac_modcou_1km_hour.csv </em>and using Table (2) in David et al. (2011). This file was prepared using a Fortran program.</li> <li><em>k_modcou_3.csv. </em>This CSV file contains Muskingum k values (in seconds) for all river reaches. The river reaches have the same COMIDs and are sorted similarly to <em>rapid_connect_San_Guad.csv</em>. The values were computed based on the following information: <em>kfac_modcou_1km_hour.csv </em>and using Table (2) in David et al. (2011). This file was prepared using a Fortran program.</li> <li><em>k_modcou_4.csv. </em>This CSV file contains Muskingum k values (in seconds) for all river reaches. The river reaches have the same COMIDs and are sorted similarly to <em>rapid_connect_San_Guad.csv</em>. The values were computed based on the following information: <em>kfac_modcou_1km_hour.csv </em>and using Table (2) in David et al. (2011). This file was prepared using a Fortran program.</li> <li><em>k_modcou_a.csv. </em>This CSV file contains Muskingum k values (in seconds) for all river reaches. The river reaches have the same COMIDs and are sorted similarly to <em>rapid_connect_San_Guad.csv</em>. The values were computed based on the following information: <em>kfac_modcou_1km_hour.csv </em>and using Table (2) in David et al. (2011). This file was prepared using a Fortran program.</li> <li><em>k_modcou_b.csv. </em>This CSV file contains Muskingum k values (in seconds) for all river reaches. The river reaches have the same COMIDs and are sorted similarly to <em>rapid_connect_San_Guad.csv</em>. The values were computed based on the following information: <em>kfac_modcou_1km_hour.csv </em>and using Table (2) in David et al. (2011). This file was prepared using a Fortran program.</li> <li><em>k_modcou_c.csv. </em>This CSV file contains Muskingum k values (in seconds) for all river reaches. The river reaches have the same COMIDs and are sorted similarly to <em>rapid_connect_San_Guad.csv</em>. The values were computed based on the following information: <em>kfac_modcou_1km_hour.csv </em>and using Table (2) in David et al. (2011). This file was prepared using a Fortran program.</li> <li><em>x_modcou_0.csv.</em> This CSV file contains Muskingum x values (dimensionless) for all river reaches. The river reaches have the same COMIDs and are sorted similarly to <em>rapid_connect_San_Guad.csv</em>. The values were computed based on Table (2) in David et al. (2011). This file was prepared using a Fortran program.</li> <li><em>x_modcou_1.csv.</em> This CSV file contains Muskingum x values (dimensionless) for all river reaches. The river reaches have the same COMIDs and are sorted similarly to <em>rapid_connect_San_Guad.csv</em>. The values were computed based on Table (2) in David et al. (2011). This file was prepared using a Fortran program.</li> <li><em>x_modcou_2.csv.</em> This CSV file contains Muskingum x values (dimensionless) for all river reaches. The river reaches have the same COMIDs and are sorted similarly to <em>rapid_connect_San_Guad.csv</em>. The values were computed based on Table (2) in David et al. (2011). This file was prepared using a Fortran program.</li> <li><em>x_modcou_3.csv.</em> This CSV file contains Muskingum x values (dimensionless) for all river reaches. The river reaches have the same COMIDs and are sorted similarly to <em>rapid_connect_San_Guad.csv</em>. The values were computed based on Table (2) in David et al. (2011). This file was prepared using a Fortran program.</li> <li><em>x_modcou_4.csv.</em> This CSV file contains Muskingum x values (dimensionless) for all river reaches. The river reaches have the same COMIDs and are sorted similarly to <em>rapid_connect_San_Guad.csv</em>. The values were computed based on Table (2) in David et al. (2011). This file was prepared using a Fortran program.</li> <li><em>x_modcou_a.csv.</em> This CSV file contains Muskingum x values (dimensionless) for all river reaches. The river reaches have the same COMIDs and are sorted similarly to <em>rapid_connect_San_Guad.csv</em>. The values were computed based on Table (2) in David et al. (2011). This file was prepared using a Fortran program.</li> <li><em>x_modcou_b.csv.</em> This CSV file contains Muskingum x values (dimensionless) for all river reaches. The river reaches have the same COMIDs and are sorted similarly to <em>rapid_connect_San_Guad.csv</em>. The values were computed based on Table (2) in David et al. (2011). This file was prepared using a Fortran program.</li> <li><em>x_modcou_c.csv.</em> This CSV file contains Muskingum x values (dimensionless) for all river reaches. The river reaches have the same COMIDs and are sorted similarly to <em>rapid_connect_San_Guad.csv</em>. The values were computed based on Table (2) in David et al. (2011). This file was prepared using a Fortran program.</li> <li><em>rivsurf_France.csv. </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the SIM-France domain. The river reaches are sorted from upstream to downstream. The values were computed using the ID field. This file was prepared using Excel.</li> <li><em>rivsurf_adour.csv. </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Adour River Basin. The river reaches are sorted from upstream to downstream. The values were computed using the ID field. This file was prepared using Excel.</li> <li><em>rivsurf_allier.csv. </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Allier River Basin. The river reaches are sorted from upstream to downstream. The values were computed using the ID field. This file was prepared using Excel.</li> <li><em>rivsurf_ardeche.csv. </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Ardeche River Basin. The river reaches are sorted from upstream to downstream. The values were computed using the ID field. This file was prepared using Excel.</li> <li><em>rivsurf_dordogne.csv. </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Dordogne River Basin. The river reaches are sorted from upstream to downstream. The values were computed using the ID field. This file was prepared using Excel.</li> <li><em>rivsurf_garonne.csv. </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Garonne River Basin. The river reaches are sorted from upstream to downstream. The values were computed using the ID field. This file was prepared using Excel.</li> <li><em>rivsurf_garonne_reste.csv. </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Garonne River Basin, downstream. The river reaches are sorted from upstream to downstream. The values were computed using the ID field. This file was prepared using Excel.</li> <li><em>rivsurf_garonneariege.csv. </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Garonne and Ariege River Basin. The river reaches are sorted from upstream to downstream. The values were computed using the ID field. This file was prepared using Excel.</li> <li><em>rivsurf_herault.csv. </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Herault River Basin. The river reaches are sorted from upstream to downstream. The values were computed using the ID field. This file was prepared using Excel.</li> <li><em>rivsurf_loir.csv. </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Loir River Basin. The river reaches are sorted from upstream to downstream. The values were computed using the ID field. This file was prepared using Excel.</li> <li><em>rivsurf_loire.csv. </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Loire River Basin. The river reaches are sorted from upstream to downstream. The values were computed using the ID field. This file was prepared using Excel.</li> <li><em>rivsurf_loire_amont_nevers.csv. </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Loire River Basin, upstream. The river reaches are sorted from upstream to downstream. The values were computed using the ID field. This file was prepared using Excel.</li> <li><em>rivsurf_loire_reste.csv. </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Loire River Basin, downstream. The river reaches are sorted from upstream to downstream. The values were computed using the ID field. This file was prepared using Excel.</li> <li><em>rivsurf_lot.csv. </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Lot River Basin. The river reaches are sorted from upstream to downstream. The values were computed using the ID field. This file was prepared using Excel.</li> <li><em>rivsurf_meuse.csv. </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Meuse River Basin. The river reaches are sorted from upstream to downstream. The values were computed using the ID field. This file was prepared using Excel.</li> <li><em>rivsurf_oise.csv. </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Oise River Basin. The river reaches are sorted from upstream to downstream. The values were computed using the ID field. This file was prepared using Excel.</li> <li><em>rivsurf_rhone.csv. </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Rhone River Basin. The river reaches are sorted from upstream to downstream. The values were computed using the ID field. This file was prepared using Excel.</li> <li><em>rivsurf_rhone_reste.csv. </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Rhone River Basin, downstream. The river reaches are sorted from upstream to downstream. The values were computed using the ID field. This file was prepared using Excel.</li> <li><em>rivsurf_rhone_suisse.csv. </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Rhone River Basin, upstream. The river reaches are sorted from upstream to downstream. The values were computed using the ID field. This file was prepared using Excel.</li> <li><em>rivsurf_saone.csv. </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Saone River Basin. The river reaches are sorted from upstream to downstream. The values were computed using the ID field. This file was prepared using Excel.</li> <li><em>rivsurf_seine.csv. </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Seine River Basin. The river reaches are sorted from upstream to downstream. The values were computed using the ID field. This file was prepared using Excel.</li> <li><em>rivsurf_seine_amont.csv. </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Seine River Basin, upstream. The river reaches are sorted from upstream to downstream. The values were computed using the ID field. This file was prepared using Excel.</li> <li><em>rivsurf_seine_reste.csv. </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Seine River Basin, downstream. The river reaches are sorted from upstream to downstream. The values were computed using the ID field. This file was prepared using Excel.</li> <li><em>rivsurf_tarn.csv. </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Tarn River Basin. The river reaches are sorted from upstream to downstream. The values were computed using the ID field. This file was prepared using Excel.</li> <li><em>rivsurf_vienne.csv. </em>This CSV file contains the list of unique IDs of SIM-France river reaches in the Vienne River Basin. The river reaches are sorted from upstream to downstream. The values were computed using the ID field. This file was prepared using Excel.</li> <li><em>Qout_France_201101_c_zvol_ext_3653days_p1_dtR1800s.nc. </em>This netCDF file contains the 3-hourly averaged outputs (in cubic meters per second) from RAPID corresponding to the downstream point of each reach. The river reaches have the same IDs and are sorted similarly to <em>rivsurf_France.csv</em>. The time range for this file is from 1995-08-01T00:00+02:00 to 2005-07-31-21:00+02:00. The values were computed using the Muskingum method with parameters of Table (2) in David et al. (2011). This file was prepared using RAPID v1.1.0 running with the preonly ILU solver on one core.</li> <li><em>Qout_France_201101_c_zvol_ext_3653days_p2_dtR1800s.nc. </em>This netCDF file contains the 3-hourly averaged outputs (in cubic meters per second) from RAPID corresponding to the downstream point of each reach. The river reaches have the same IDs and are sorted similarly to <em>rivsurf_France.csv</em>. The time range for this file is from 1995-08-01T00:00+02:00 to 2005-07-31-21:00+02:00. The values were computed using the Muskingum method with parameters of Table (2) in David et al. (2011). This file was prepared using RAPID v1.1.0 running with the preonly ILU solver on one core.</li> <li><em>Qout_France_201101_c_zvol_ext_3653days_p3_dtR1800s.nc. </em>This netCDF file contains the 3-hourly averaged outputs (in cubic meters per second) from RAPID corresponding to the downstream point of each reach. The river reaches have the same IDs and are sorted similarly to <em>rivsurf_France.csv</em>. The time range for this file is from 1995-08-01T00:00+02:00 to 2005-07-31-21:00+02:00. The values were computed using the Muskingum method with parameters of Table (2) in David et al. (2011). This file was prepared using RAPID v1.1.0 running with the preonly ILU solver on one core.</li> <li><em>Qout_France_201101_c_zvol_ext_3653days_p4_dtR1800s.nc. </em>This netCDF file contains the 3-hourly averaged outputs (in cubic meters per second) from RAPID corresponding to the downstream point of each reach. The river reaches have the same IDs and are sorted similarly to <em>rivsurf_France.csv</em>. The time range for this file is from 1995-08-01T00:00+02:00 to 2005-07-31-21:00+02:00. The values were computed using the Muskingum method with parameters of Table (2) in David et al. (2011). This file was prepared using RAPID v1.1.0 running with the preonly ILU solver on one core.</li> <li><em>Qout_France_201101_c_zvol_ext_3653days_pa_dtR1800s.nc. </em>This netCDF file contains the 3-hourly averaged outputs (in cubic meters per second) from RAPID corresponding to the downstream point of each reach. The river reaches have the same IDs and are sorted similarly to <em>rivsurf_France.csv</em>. The time range for this file is from 1995-08-01T00:00+02:00 to 2005-07-31-21:00+02:00. The values were computed using the Muskingum method with parameters of Table (2) in David et al. (2011). This file was prepared using RAPID v1.1.0 running with the preonly ILU solver on one core.</li> <li><em>Qout_France_201101_c_zvol_ext_3653days_pb_dtR1800s.nc. </em>This netCDF file contains the 3-hourly averaged outputs (in cubic meters per second) from RAPID corresponding to the downstream point of each reach. The river reaches have the same IDs and are sorted similarly to <em>rivsurf_France.csv</em>. The time range for this file is from 1995-08-01T00:00+02:00 to 2005-07-31-21:00+02:00. The values were computed using the Muskingum method with parameters of Table (2) in David et al. (2011). This file was prepared using RAPID v1.1.0 running with the preonly ILU solver on one core.</li> <li><em>Qout_France_201101_c_zvol_ext_3653days_pc_dtR1800s.nc. </em>This netCDF file contains the 3-hourly averaged outputs (in cubic meters per second) from RAPID corresponding to the downstream point of each reach. The river reaches have the same IDs and are sorted similarly to <em>rivsurf_France.csv</em>. The time range for this file is from 1995-08-01T00:00+02:00 to 2005-07-31-21:00+02:00. The values were computed using the Muskingum method with parameters of Table (2) in David et al. (2011). This file was prepared using RAPID v1.1.0 running with the preonly ILU solver on one core.</li> <li><em>Qout_France_201101_c_zvol_ext_366days_p0_dtR1800s.nc. </em>This netCDF file contains the 3-hourly averaged outputs (in cubic meters per second) from RAPID corresponding to the downstream point of each reach. The river reaches have the same IDs and are sorted similarly to <em>rivsurf_France.csv</em>. The time range for this file is from 1995-08-01T00:00+02:00 to 1996-07-31-21:00+02:00. The values were computed using the Muskingum method with parameters of Table (2) in David et al. (2011). This file was prepared using RAPID v1.1.0 running with the preonly ILU solver on one core.</li> <li><em>Qout_France_201101_c_zvol_ext_366days_pb_dtR1800s.nc. </em>This netCDF file contains the 3-hourly averaged outputs (in cubic meters per second) from RAPID corresponding to the downstream point of each reach. The river reaches have the same IDs and are sorted similarly to <em>rivsurf_France.csv</em>. The time range for this file is from 1995-08-01T00:00+02:00 to 1996-07-31-21:00+02:00. The values were computed using the Muskingum method with parameters of Table (2) in David et al. (2011). This file was prepared using RAPID v1.1.0 running with the preonly ILU solver on one core.</li> <li><em>Qout_France_201101_c_zvol_ext_366days_pb_dtR1800s_pougny.nc. </em>This netCDF file contains the 3-hourly averaged outputs (in cubic meters per second) from RAPID corresponding to the downstream point of each reach. The river reaches have the same IDs and are sorted similarly to <em>rivsurf_France.csv</em>. The time range for this file is from 1995-08-01T00:00+02:00 to 1996-07-31-21:00+02:00. The values were computed using the Muskingum method with parameters of Table (2) in David et al. (2011). This file was prepared using RAPID v1.1.0 running with the preonly ILU solver on one core.</li> <li><em>gage_id_1995_1996_full.csv. </em>This CSV file contains the list of IDs of rivers containing SCHAPI gauges and with full daily data record. The river reaches are sorted in increasing value of ID. The time range used for determining a full record is daily from 1995-08-01T00:00+02:00 to 1996-07-31T21:00+02:00. The values were computed using the following field: ID. This file was prepared using a Fortran program, and Excel.</li> <li><em>gage_id_1995_1996_full_nash.csv. </em>This CSV file contains the list of IDs of rivers containing SCHAPI gauges and with full daily data record and for which RAPID simulations led to a positive efficiency value. The river reaches are sorted in increasing value of ID. The time range used for determining a full record is daily from 1995-08-01T00:00+02:00 to 1996-07-31T21:00+02:00. The values were computed using the following field: ID. This file was prepared using a Fortran program, and Excel.</li> <li><em>gage_id_1995_2005_70.csv. </em>This CSV file contains the list of IDs of rivers containing SCHAPI gauges and with 70% daily data record. The river reaches are sorted in increasing value of ID. The time range used for determining a full record is daily from 1995-08-01T00:00+02:00 to 2005-07-31T21:00+02:00. The values were computed using the following field: ID. This file was prepared using a Fortran program, and Excel.</li> <li><em>Qobs_1995_1996_full.csv. </em>This CSV file contains daily averaged measured stream flow (in cubic meters per second). The river reaches have the same IDs and are sorted similarly to <em>gage_id_1995_1996_full.csv</em>. The time range for the daily values is from 1995-08-01T00:00+02:00 to 1996-07-31T21:00+02:00. The values were computed using the following field: ID, and the observations from SCHAPI. This file was prepared using a Fortran program and Excel.</li> <li><em>Qobs_1995_1996_full_nash.csv. </em>This CSV file contains daily averaged measured stream flow (in cubic meters per second). The river reaches have the same IDs and are sorted similarly to <em>gage_id_1995_1996_full_nash.csv</em>. The time range for the daily values is from 1995-08-01T00:00+02:00 to 1996-07-31T21:00+02:00. The values were computed using the following field: ID, and the observations from SCHAPI. This file was prepared using a Fortran program and Excel.</li> <li><em>Qobs_1995_1996_full_nash_93.csv. </em>This CSV file contains daily averaged measured stream flow (in cubic meters per second). The river reaches have the same IDs and are sorted similarly to <em>gage_id_1995_1996_full_nash.csv</em>. The time range for the daily values is from 1995-11-01T00:00+02:00 to 2005-07-31T21:00+02:00. The values were computed using the following field: ID, and the observations from SCHAPI. This file was prepared using a Fortran program and Excel.</li> <li><em>Qobs_1995_2005_70.csv. </em>This CSV file contains daily averaged measured stream flow (in cubic meters per second). The river reaches have the same IDs and are sorted similarly to <em>gage_id_1995_2005_70.csv</em>. The time range for the daily values is from 1995-08-01T00:00+02:00 to 2005-07-31T21:00+02:00. The values were computed using the following field: ID, and the observations from SCHAPI. This file was prepared using a Fortran program and Excel.</li> <li><em>Qobsbarrec_1995_1996_full_nash.csv. </em>This CSV file contains the reciprocal of the averaged measured stream flow (in cubic meters per second). The river reaches have the same IDs and are sorted similarly to <em>gage_id_1995_1996_full_nash.csv</em>. The time range for the computation of the average is from 1995-08-01T00:00+02:00 to 1996-07-31T21:00+02:00. The values were computed using the following field: ID, and the observations from SCHAPI. This file was prepared using a Fortran program and Excel.</li> <li><em>forcingtot_id_1995_1996_full.csv. </em>This CSV file contains the list of IDs of rivers containing SCHAPI gauges and used as forcing instead of RAPID simulations for the SIM-France domain. The river reaches are sorted in increasing value of ID. The time range used for determining a full record is daily from 1995-08-01T00:00+02:00 to 1996-07-31T21:00+02:00. The values were computed using the following field: ID. This file was prepared using a Fortran program, and Excel.</li> <li><em>forcinguse_id_garonne_reste.csv. </em>This CSV file contains the list of IDs of rivers containing SCHAPI gauges and used as forcing instead of RAPID simulations for the Garonne River Basin, downstream. The river reaches are sorted in increasing value of ID. The time range used for determining a full record is daily from 1995-08-01T00:00+02:00 to 1996-07-31T21:00+02:00. The values were computed using the following field: ID. This file was prepared using a Fortran program, and Excel.</li> <li><em>forcinguse_id_loire_reste.csv. </em>This CSV file contains the list of IDs of rivers containing SCHAPI gauges and used as forcing instead of RAPID simulations for the Loire River Basin, downstream. The river reaches are sorted in increasing value of ID. The time range used for determining a full record is daily from 1995-08-01T00:00+02:00 to 1996-07-31T21:00+02:00. The values were computed using the following field: ID. This file was prepared using a Fortran program, and Excel.</li> <li><em>forcinguse_id_rhone_pougny.csv. </em>This CSV file contains the list of IDs of rivers containing SCHAPI gauges and used as forcing instead of RAPID simulations for the Rhone River Basin, downstream of Lake Geneva. The river reaches are sorted in increasing value of ID. The time range used for determining a full record is daily from 1995-08-01T00:00+02:00 to 1996-07-31T21:00+02:00. The values were computed using the following field: ID. This file was prepared using a Fortran program, and Excel.</li> <li><em>forcinguse_id_rhone_reste.csv. </em>This CSV file contains the list of IDs of rivers containing SCHAPI gauges and used as forcing instead of RAPID simulations for the Rhone River Basin, downstream. The river reaches are sorted in increasing value of ID. The time range used for determining a full record is daily from 1995-08-01T00:00+02:00 to 1996-07-31T21:00+02:00. The values were computed using the following field: ID. This file was prepared using a Fortran program, and Excel.</li> <li><em>forcinguse_id_seine_reste.csv. </em>This CSV file contains the list of IDs of rivers containing SCHAPI gauges and used as forcing instead of RAPID simulations for the Seine River Basin, downstream. The river reaches are sorted in increasing value of ID. The time range used for determining a full record is daily from 1995-08-01T00:00+02:00 to 1996-07-31T21:00+02:00. The values were computed using the following field: ID. This file was prepared using a Fortran program, and Excel.</li> <li><em>Qfor_1995_1996_full.csv. </em>This CSV file is identical to <em>Qobs_1995_1996_full.csv.</em></li> <li><em>Qfor_1995_1996_full_93.csv. </em>This CSV file is identical to <em>Qobs_1995_1996_full_nash_93.csv.</em></li> <li><em>Qinit_93.csv. </em>This CSV file contains the final state of RAPID after a simulation ending on 1995-11-31T00:00+02:00</li> </ul> <p> </p> <p><strong>Known bugs and limitations in this dataset or the associated manuscript.</strong></p> <p>A small bug in RAPID v1.1.0 was discovered and fixed on 2011-07-16 that had an impact on the optimization of parameters when using forcing data to replace upstream simulations. This bug led to erroneous results for only two of the basins where upstream forcing was used: Garonne River Basin, downstream; and Rhone River Basin, downstream. The bug had no influence on: Loire River Basin, downstream, and Seine River Basin, downstream; or on any of the other simulations. This should not affect the conclusions of David et al. (2011) since only a few locations were impacted. </p> <p> </p> <p><strong>Funding</strong></p> <p>This work was partially supported by the French Mines Paristech, by the French Agence Nationale de la Recherche under the Vulnérabilité de la nappe du Rhin (VulNaR) project, by the French Programme Interdisciplinaire de Recherche sur l’Environnement de la Seine (PIREN-Seine) project, by the U.S. National Aeronautics and Space Administration under the Interdisciplinary Science Project NNX07AL79G, by the U.S. National Science Foundation under project EAR-0413265: CUAHSI Hydrologic Information Systems, and by the American Geophysical Union under a Horton (Hydrology) Research Grant.</p>
Model outputs from the study "A scalable framework for soil property mapping tested across a highly diverse tropical data-scarce region"
<p>Model outputs from the study "A scalable framework for soil property mapping tested across a highly diverse tropical data-scarce region". The study is published as open access and can be found at the following link: <a href="https://www.sciencedirect.com/science/article/pii/S2950289625000326">https://www.sciencedirect.com/science/article/pii/S2950289625000326</a></p> <p> </p> <p>The file "SWAT_USERSOIL.csv" was included to facilitate the assimilation of the soil mapping data into the Soil & Water Assessment Tool (SWAT, https://swat.tamu.edu/) for hydrological modeling. </p> <p> </p> <p>Regarding the raster files, please note:</p> <p>a) All values in these datasets have been multiplied by 10,000 to optimize file sizes.</p> <p>b) Files are named using the variable acronym, followed by the corresponding soil layer. For outputs derived from pedotransfer functions (PTFs), the PTF reference is appended after the variable acronym.</p> <p>c) Available data decrease with increasing soil layer number. This occurs because not all locations (grid cells) have the same soil depth or number of soil layers.</p> <p> </p> <p>If you have any questions about the dataset or its use, please don't hesitate to contact us.</p> <p> </p> <p> </p>
PISM model output data from Garbe et al. (Nature, 2020) publication
<p>This dataset contains the <a href="https://www.pism.io">PISM</a> model output data of the Antarctic Ice Sheet hysteresis simulations published and discussed in</p><p><a href="https://doi.org/10.1038/s41586-020-2727-5">Garbe, J., Albrecht, T., Levermann, A., Donges, J. F., and Winkelmann, R. The hysteresis of the Antarctic Ice Sheet. <i>Nature</i><strong> 585</strong>(7826), 2020.</a></p><p>A detailed description of the individual file contents is given in `README.txt` below. The corresponding PISM model code used for these simulations is archived <a href="https://doi.org/10.5281/zenodo.3956431">here</a>.</p><p>In case of questions, feel free to contact me at <a href="mailto:julius.garbe@pik-potsdam.de">julius.garbe@pik-potsdam.de</a>.</p>
Global Surface Ozone Concentration Dataset 1990-2017 Mapped at Fine Resolution through the Bayesian Maximum Entropy Data Fusion of Observations and Model Output
<p>This global surface ozone concentration dataset corresponds to the data developed in this paper:</p> <p>DeLang, M. N., J. S. Becker, K.-L. Chang, M. L. Serre, O. R. Cooper, M. G. Schultz, S. Schroder, X. Lu, L. Zhang, M. Deushi, B. Josse, C. A. Keller, J.-F. Lamarque, M. Lin, J. Liu, V. Marecal, S. A. Strode, K. Sudo, S. Tilmes, L. Zhang, S. Cleland, E. Collins, M. Brauer, and J. J. West (2021) Mapping yearly fine resolution global surface ozone through the Bayesian Maximum Entropy data fusion of observations and model output for 1990-2017, <em>Environmental Science & Technology</em>, 55, 4389-4398, doi: 10.1021/acs.est.0c07742.</p> <p>Ozone concentrations are estimated as described in the paper, with output shown for the Ozone Season Daily Maximum 8-hr metric (OSDMA8) for each year between 1990 and 2017, at 0.1 degree spatial resolution. Ozone is estimated through data fusion of output from several global models, with observations of ozone collected by TOAR. The data fusion involves application of the M3Fusion method to create a multi-model composite of several global models, followed by BME data fusion, as described in the paper. </p> <p>The *.nc file contains the latitude, longitude, ozone concentration estimate, and estimated variance for each 0.1 x 0.1 degree grid cell.</p> <p>Please contact Jason West (jasonwest@unc.edu) with questions about the dataset. We'd like to hear from you to know how you're using the data!</p> <p> </p> <p> </p>
Model Outputs for Characterizing the Atmospheric Mn Cycle and Its Impact on Terrestrial Biogeochemistry
<p>Includes the model output files used in calculations regarding the research article "Characterizing the Atmospheric Mn Cycle and Its Impact on Terrestrial Biogeochemistry". Output files contains: 1) surface Mn concentrations, annual; 2) Mn deposition, monthly; 3) soil Mn map; 4) soil Mn "pseudo" turnover time.</p>
ERDS alerts based on WRF model output
<p>Heavy rainfall alerts based on WRF model output at 7.5 km resolution produced by ERDS (<a href="https://erds.ithacaweb.org/">https://erds.ithacaweb.org/</a>).</p>
Output data of the models used in "Comparison of six approaches to predicting droplet activation of surface active aerosol. Part 1: moderately surface active organics" by Vepsäläinen et al. (2022)
<p>Output data of the different models used in "Comparison of six approaches to predicting droplet activation of surface active aerosol. Part 1: moderately surface active organics" by Vepsäläinen et al. (2022).</p> <p>Output data is included for 50 nm particles containing malonic acid (mna), succinic acid (sca) and glutaric acid (glutarica), mixed with ammonium sulphate (AS) in different organic mass fractions. </p> <p>A plotter that allows the user to plot the Köhler curves, surface tensions and organic<br> partitioning factors during droplet growth from the model output data provided is included. </p>
Supporting model output for article "Assessing the potential impact of river chemistry on Arctic coastal production"
<p>The following is a summary of processed model output data from a series of HiLAT model runs.<br> A description of the model runs and visualization of model output and analysis can be found in the<br> accompanying manuscript.</p> <p><br> Gibson G. A., Elliott, S., Piliouras, A. Clement Kinney, J., Jeffery, N. (2022) Assessing the potential<br> impact of river nitrate on coastal production in the Arctic. Frontiers in Marine Science: Coastal Ocean<br> Processes.</p> <p><br> This work was supported by the Regional and Global Model Analysis (RGMA) program of the US<br> Department of Energy’s Office of Science as a contribution to the HiLAT project. Additional support for<br> this project was provided by the National Science Foundation, under award #173886.<br> </p> <p><strong>River Nutrient Forcing</strong></p> <p>The experiments involved modifying the nutrient concentrations in the river nutrient forcing files.<br> The river nutrient files are specified during model setup. For use in the HiLAT model, GNEWS annual<br> river nutrient inputs were partitioned into twelve monthly forcing values. The nearest ocean grid point<br> to each of the GNEWS river mouth locations was identified and then, as with the runoff, the nutrient<br> inputs for each river basin were spatially mapped to surface ocean model grid cells, which are 10 meters<br> thick, such that the spatial pattern of river nutrient dispersion follows river water inputs to the oceans.</p> <p>The experiments were:<br> i) The baseline model simulation: The 12 monthly values for each grid cell were constant in time.<br> <strong>river_nutrients_GNEWS2000_gx1v6.nc</strong><br> ii) an experiment in which baseline Arctic River Nitrogen (NO 3 and NH 4 ) concentrations were doubled.<br> <strong>river_nutrients_GNEWS2000_gx1v6_x2Arctic.nc</strong><br> iii) an experiment in which baseline Arctic River Nitrogen (DON and DIN) concentrations were scaled to<br> the river volume discharge contained in <strong>runoff.daitren.iaf.20120419.nc</strong><br> <strong>river_nutrients_GNEWS2000_gx1v6_scaled_climatology.nc</strong><br> iv) an experiment in which the scaled river nutrient discharge (iii) was shifted earlier by two months.<br> <strong>river_nutrients_GNEWS2000_gx1v6_shifted2m_climatology.nc</strong><br> v) an experiment in which the scaled river nutrient discharge (iii) was shifted earlier by a month and<br> doubled in concentration.<br> <strong>river_nutrients_GNEWS2000_gx1v6_shifted_climatology_x2.nc</strong></p> <p>River nutrient fluxes are in units of nmol/cm2/s<br> Only concentrations within the domain TLONG>=60 &TLONG <=340 & TLAT >=60 were modified in<br> concentration/timing.</p> <p><br> Variables of interest:<br> din_riv_flux: dissolved inorganic nitrogen river flux<br> don_riv_flux: dissolved organic nitrogen river flux</p> <p>Each of the experiments is described in detail in Gibson et al (2022).</p> <p>---------------------------------------------<br> There are multiple versions of most output file types, corresponding to the river nutrient experiments that<br> were conducted.</p> <p><br> Many variables in the output files are <strong>regional averages</strong> where model regions are indicated by a number<br> *note - for aesthetics, the numbering used in the model output files differs slightly from the numbering<br> used in the accompanying manuscript. The numbers assigned in the analysis files aligns with the numbers<br> assigned to regions within the region mask provided in the grid file.</p> <p><strong>Grid File/region masks</strong><br> gx1v6_polar_mask_coast.5.22.20c.nc This file is an updated version of the standard grid file. It has been<br> updated to include the addition of a coastal Arctic region variable ‘Arctic_Coast_Mask’ which indicates<br> which grid cells are in the coastal regions used in the analysis and the Arctic_Region variable which<br> indicates which grid cells are in the broader regions.</p> <p><br> Variables contained in this file are:<br> Arctic_Coast_Mask: contains values 0-9 indicating which (if any) coastal region a grid cell is in<br> Arctic_Region Mask: contains values 0-11 indicating which (if any) region a grid cell is in</p> <p><br> TLAT: latitude of grid cell<br> TLONG: longitude of grid cell<br> TAREA: Area of grid cell<br> HT: Bathymetry of grid cell</p> <p> </p><table> <tbody> <tr> <td> </td> <td> <p><strong>Arctic_Region (seas)</strong></p> </td> <td> <p><strong>Arctic_Coast_Mask </strong><strong>(coast)</strong></p> </td> </tr> <tr> <td> <p><strong>Bering Sea</strong></p> </td> <td> <p>1</p> </td> <td> <p>1</p> </td> </tr> <tr> <td> <p><strong>Chukchi Sea</strong></p> </td> <td> <p>2</p> </td> <td> <p>2</p> </td> </tr> <tr> <td> <p><strong>East Siberian Sea</strong></p> </td> <td> <p>3</p> </td> <td> <p>3</p> </td> </tr> <tr> <td> <p><strong>Laptev Sea</strong></p> </td> <td> <p>4</p> </td> <td> <p>4</p> </td> </tr> <tr> <td> <p><strong>Beaufort Sea</strong></p> </td> <td> <p>5</p> </td> <td> <p>5</p> </td> </tr> <tr> <td> <p><strong>Barents Sea</strong></p> </td> <td> <p>6</p> </td> <td> <p>6</p> </td> </tr> <tr> <td> <p><strong>Canadian Basin</strong></p> </td> <td> <p>7</p> </td> <td> <p>-</p> </td> </tr> <tr> <td> <p><strong>Eurasian Basin</strong></p> </td> <td> <p>8</p> </td> <td> <p>-</p> </td> </tr> <tr> <td> <p><strong>Nordic Seas</strong></p> </td> <td> <p>9</p> </td> <td> <p>7</p> </td> </tr> <tr> <td> <p><strong>Labrador Sea</strong></p> </td> <td> <p>10</p> </td> <td> <p>8</p> </td> </tr> <tr> <td> <p><strong>Kara Sea</strong></p> </td> <td> <p>11</p> </td> <td> <p>9</p> </td> </tr> </tbody> </table> --------------<p></p> <p> </p><p>Model outputs that were analyzed in the manuscript are contained in three different kinds of output file.<br> For each file type a file exists for each river nutrient experiment.</p> <p></p> <p>The following series of files contains variables related to the particulate organic carbon flux to the<br> sediment, demineralization and remineralization rates.<br> bgc_T62_gx1GIF_nut-riv-BASELINE-coast_region-sed-137-157.nc<br> bgc_T62_gx1GIF_nut-riv-month-shiftx2-coast_region-sed-137-157.nc<br> bgc_T62_gx1GIF_nut-riv-2xArcticN-coast_region-sed-137-157.nc<br> bgc_T62_gx1GIF_nut-riv-mon-clim-coast_region-sed-137-157.nc<br> bgc_T62_gx1GIF_nut-riv-2mon-shift-coast_region-sed-137-157.nc<br> bgc_T62_gx1GIF_nut-riv_2XDC-coast_region-sed-137-157.nc<br> bgc_T62_gx1GIF_nut-riv-BASELINE-seas_region-sed-137-157.nc<br> bgc_T62_gx1GIF_nut-riv-month-shiftx2-seas_region-sed-137-157.nc<br> bgc_T62_gx1GIF_nut-riv-2xArcticN-seas_region-sed-137-157.nc<br> bgc_T62_gx1GIF_nut-riv-mon-clim-seas_region-sed-137-157.nc<br> bgc_T62_gx1GIF_nut-riv-2mon-shift-seas_region-sed-137-157.nc</p> <p><br> Variables contained in these are:<br> POCTOSED_AVG* : Particulate organic carbon flux to sediment<br> PONTOSED_AVG* : Particulate organic nitrogen flux to sediment<br> SEDDENITRIF_AVG* : Sediment denitrification rate<br> POC_PROD_AVG* : Production of Particulate organic carbon<br> POC_FLUX_AVG* : Particulate organic carbon flux into layer/cell<br> DON_REMIN_AVG* : Dissolved Organic Nitrogen remineralization rate<br> DOC_REMIN_AVG* : Dissolved Organic Carbon remineralization rate<br> DIAT_N_LIM_AVG* : Diatom nitrogen limitation<br> DIAT_N_LIM_AVG* : Diatom nitrogen limitation<br> DIAT_P_LIM_AVG* : Diatom phosphorous limitation<br> DIAT_FE_LIM_AVG* : Diatom iron limitation<br> DIAT_LIGHT_LIM_AVG*: Diatom light limitation<br> SP_N_LIM_AVG* : Small phytoplankton nitrogen limitation<br> SP_P_LIM_AVG* : Small phytoplankton phosphorous limitation<br> SP_FE_LIM_AVG* : Small phytoplankton iron limitation<br> SP_LIGHT_LIM_AVG* : Small phytoplankton light limitation<br> Where * represents the coastal region number.<br> ----------------------------------------</p> <p><br> The following series of files contains primary production for the small and large phytoplankton groups<br> and the zooplankton biomass.</p> <p>Coastal regional averages – based on regions marked in the Arctic_Coast_Mask variable<br> bgc_T62_gx1GIF_runoff-2xArcticN-region-prod-ACM-137-157.nc<br> bgc_T62_gx1GIF_nut-riv-mon-clim-region-prod-ACM-137-157.nc<br> bgc_T62_gx1GIF_nut-riv-month-shiftx2-region-prod-ACM-137-157.nc<br> bgc_T62_gx1GIF_riv-BASELINE-region-prod-ACM-137-157.nc<br> bgc_T62_gx1GIF_nut-riv-2mon-shift-region-prod-ACM-137-157.nc<br> bgc_T62_gx1GIF_nut-riv-2XDC-region-prod-ACM-137-157.nc</p> <p>Regional seas averages – based on regions marked in the Arctic_Region variable<br> bgc_T62_gx1GIF_runoff-2xArcticN-region-prod-seas-137-157.nc<br> bgc_T62_gx1GIF_nut-riv-mon-clim-region-prod-seas-137-157.nc<br> bgc_T62_gx1GIF_nut-riv-month-shiftx2-region-prod-seas-137-157.nc<br> bgc_T62_gx1GIF_riv-BASELINE-region-prod-seas-137-157.nc<br> bgc_T62_gx1GIF_nut-riv-2mon-shift-region-prod-seas-137-157.nc</p> <p>Variables contained in these files are:<br> TAREA_SUM* – total area of the region<br> PPSP_REGSUM* – sum of primary production by small phytoplankton in a region<br> PPDIAT_REGSUM*– sum of primary production by diatoms in a region<br> ZOOC_AVG*– sum of zooplankton biomass in a region</p> <p>----------------------------------------<br> The following series of files contains ice associated variables and mixed layer nutrients</p> <p>bgc_T62_gx1GIF_nut_riv-2xArcticN-ice_coastal-137-157.nc<br> bgc_T62_gx1GIF_nut-riv-mon-clim-ice_coastal -137-157.nc<br> bgc_T62_gx1GIF_nut-riv-month-shiftx2-ice_coastal -137-157.nc<br> bgc_T62_gx1GIF_nut-riv-BASELINE-ice_coastal -137-157.nc<br> bgc_T62_gx1GIF_nut-riv-2mon-shift-ice_coastal -137-157.nc<br> bgc_T62_gx1GIF_nut-riv-2XDC-ice_coastal -137-157.nc<br> bgc_T62_gx1GIF_nut-riv-2xArcticN-ice_seas-137-157.nc<br> bgc_T62_gx1GIF_nut-riv-mon-clim-ice_seas -137-157.nc<br> bgc_T62_gx1GIF_nut-riv-month-shiftx2-ice_seas -137-157.nc<br> bgc_T62_gx1GIF_nut-riv-BASELINE-ice_seas -137-157.nc<br> bgc_T62_gx1GIF_nut-riv-2mon-shift-ice_seas-137-157.nc</p> <p>HI_REGAVG* : Regional averaged ice depth<br> HS_REGAVG* : Regional averaged snow depth<br> ICEAREA_REGSUM* : Regional sum ice area<br> ICEVOL_REGSUM*: Regional sum volume area<br> MLAM_REGAVG* : Regional average ammonium concentration in mixed layer<br> MLNIT_REGAVG* : Regional average nitrate concentration in mixed layer<br> PP_REGAVG* : Regional average primary production (ice algae)<br> PP_REGSUM* : Regional total primary production (ice algae)<br> TAREA_SUM* : Total area of region<br> TIME : time</p>
Outputs of the Jupyter Notebook - Met Office UKV high-resolution atmosphere model data
<p>The dataset contains the outputs of the notebook "Met Office UKV high-resolution atmosphere model data" published in the urban sensors section of The Environmental Data Science Book.</p> <p><strong>Contributions</strong></p> <p><em>Notebook</em></p> <ul> <li> <p>Samantha V. Adams (author), Met Office Informatics Lab, <a href="https://github.com/svadams">@svadams</a></p> </li> <li> <p>Alejandro Coca-Castro (reviewer), The Alan Turing Institute, <a href="https://github.com/acocac">@acocac</a></p> </li> </ul> <p><em>Dataset originator/creator</em></p> <ul> <li> <p>Met Office Informatics Lab (creator)</p> </li> <li> <p>Microsoft (support)</p> </li> <li> <p>European Regional Development Fund (support)</p> </li> </ul> <p><em>Dataset authors</em></p> <ul> <li> <p>Met Office</p> </li> </ul> <p><em>Dataset documentation</em></p> <ul> <li> <p>Theo McCaie. Met office and partners offer data and compute platform for covid-19 researchers. URL: <a href="https://medium.com/informatics-lab/met-office-and-partners-offer-data-and-compute-platform-for-covid-19-researchers-83848ac55f5f">https://medium.com/informatics-lab/met-office-and-partners-offer-data-and-compute-platform-for-covid-19-researchers-83848ac55f5f</a>.</p> </li> </ul> <p> </p>
Effect of live cribwall on slope stability - modelling outputs
<p>These datasets contain outputs from a novel live cribwall model. The model assess the effect of a live cribwall on slope stability over time. The dataset contains Factor of Safety records under different plant cover and climate change scenarios. The model is still unpublished. For more detail, please get in touch aol3@gcu.ac.uk </p>
Archived Model Output for "Simulating Observations of Southern Ocean Clouds and Implications for Climate"
<p>This is an archive of CAM6 simulation output used in the paper Southern Ocean Aerosol and Ice Nucleating Particles in the Community Earth System Model Version 2, submitted to the Journal of Geophysical Research Atmospheres. </p>
Model output supporting MimiBRICK v1.1.0
<p>Model calibration output and model simulation output supporting the model calibration and analysis codes included in MimiBRICK v1.1.0.</p> <p>v1.1.0 edit: file naming simplified</p>
RRR/RAPID input and output files corresponding to "Underlying Fundamentals of Kalman Filtering for River Network Modeling"
<p><strong>Corresponding peer-reviewed publication</strong></p> <p>This dataset corresponds to all the RRR/RAPID input and output files that were used in the study reported in:</p> <ul> <li> <p>Emery, C. M., C. H. David, K. M. Andreadis, M. J. Turmon, J. T. Reager, and J. M. Hobbs (2020), Underlying Fundamentals of Kalman Filtering for River Network Modeling, Journal of Hydrometeorology, 21, 453-474, DOI: 10.1175/JHM-D-19-0084.1.</p> </li> </ul> <p>When making use of any of the files in this dataset, please cite both the aforementioned article and the dataset herein. </p> <p><strong>Known bugs and limitations in this dataset or the associated manuscript.</strong></p> <p>In the final version of the published manuscript, Figure 5a, Figure 5b, Figure 5c, and Figure SF1 are inaccurate. The issue in these figures is that they were all prepared with an incorrect indexing relating observed and simulated discharge, hence observations at any one location were consistently being compared to simulations at another different location. As a result, all values of "measured" discharge errors (i.e. Bias, STDE, and RMSE) are incorrect. This issue did not affect the values of "estimated" errors, nor did it affect all values of the Nash-Sutcliffe effeciency that are presented. The figures published in the manuscript can all be recreated using the files in which "BUG_DO_NOT_USE" was appended to the name. Correct figures can also be created using corresponding file names that were not so appended. </p> <p>Note that corrected versions of Figure 5a, Figure 5b, Figure 5c, and Figure SF1 all retain the same strong linear relationships that are discussed in the paper. The slope of the daily discharge STDE trend initially reported as <span class="math-tex">\(\alpha = 0.3876\)</span> in Figure 5c changes to <span class="math-tex">\(\alpha = 0.4507\)</span> after correction. The resulting value of the ideal inflation factor hence changes from <span class="math-tex">\(I = {1 \over 0.3876} \approx 2.58\)</span> to <span class="math-tex">\(I = {1 \over 0.4507} \approx 2.22\)</span>. This updated ideal inflation factor has no impact on the conclusions reached in the manuscript because it remains closer to <span class="math-tex">\(I = 2.58\)</span> than to <span class="math-tex">\(I = 1\)</span> or <span class="math-tex">\(I = 5\)</span>, <em>i.e.</em> the three values that were evaluated.</p> <p>Additionally, a faulty version 1.3.1 of the Python toolbox netCDF4 led to incorrect interpretation of _FillValue in which every data point of value greater than _FillValue was interpreted as masked. This created discrepancies in the following three files, which were updated between V1 and V2 of this dataset: "timeseries_rap_exp01.csv", "timeseries_rap_exp18.csv", and "stats_rap_exp18.csv". Faulty versions of the same files have "BUG_NETCDF4" appended to their names. Correct files have been recreated with file names that were not so appended. </p>
Model output and analysis scripts for "High-latitude precipitation as a driver of multicentennial variability of the AMOC in a climate model of intermediate complexity"
<p>Here, we provide annually averaged model output from a 3000-year control simulation of PlaSim–LSG, a climate model of intermediate complexity. Processed variables and a Jupyter notebook to reproduce all figures of the manuscript (Mehling et al.: "High-latitude precipitation as a driver of multicentennial variability of the AMOC in a climate model of intermediate complexity") can also be found in this repository.</p> <p>In addition, a Python implementation of the three-box model proposed in the manuscript can be found in the notebook <em>boxmodel.ipynb</em>.</p>
Data, scripts and model output to perform spatiotemporal analysis of plankton drivers in the Belgian part of the North Sea
<p>This archive contains the input data, R scripts and final results of a mechanistic model that uses near real-time data from the Belgian Part of the North Sea (2011-2017) to quantify the relative contributions of the bottom-up and top-down drivers in phytoplankton dynamics. Input data are zooplankton and phytoplankton abundances, nutrients, Sea Surface Temperature (SST), photosynthetically active radiation (PAR); from the LifeWatch data and infrastructure, funded by Research Foundation - Flanders (FWO). Water temperature data for one of the locations was obtained from Flemish Banks Monitoring Network at https://meetnetvlaamsebanken.be/. The R scripts are presented in a R Markdown file that can be executed in the Blue-Cloud Zoo and Phytoplankton EOV products Vlab at https://blue-cloud.d4science.org/web/zoo-phytoplankton_eov, operated by D4Science.org, www.d4science.org (Assante et al., 2019). </p>
Processed model output of the climate simulation in the study: The effects of diachronous surface uplift of the European Alps on regional climate and the isotopic composition of precipitation (δ18Op) [Boateng et al.]
<p><strong>The geodynamic evolution of the Alps suggests that the Alps did not rise monotonically due to the different post-collisional processes such as slab break-off. However, understanding such subsurface dynamics would require adequate knowledge about its surface uplift history. Stable isotope paleoaltimetry methods are widely used to infer past surface elevation using geologic archives. However, its accurate interpretation relies on attributing the extracted isotopic signal from proxies to surface uplift despite other influences such as climate. To resolve this issue, topographic sensitivity experiments across the Alps are used to investigate the impacts of the diachronous surface uplift on regional climate and δ18Op. The Atmospheric General Circulation Model ECHAM5 with water isotope tracking capabilities (ECHAM5-wiso) is used to simulate the climate with varied topographic scenarios. We present the processed (long-term means) model output of the relevant climate variables (i.e δ18Op, near-surface temperature, precipitation amount, near-surface meridional and zonal winds, mean sea level pressure, and elevation) in response to the changes in topography. The file names are representative of the topographic scenarios used for the simulations. For example, the file “W2E1.nc” is the model output produced by a topographic scenario in which the topography across the west-central Alps was set to 200% of its modern height, and the Eastern Alps were kept at 100%. The “CTL.nc” file contains model output from the control simulation that uses present-day topography. The datasets for instance can be used to select far-field sampling points for the δ-δ paleoaltimetry method that are not significantly affected by the topographic changes.</strong></p>
ScienceDex guides
Understand access before you commit
These curated guides explain access requirements, typical timelines, costs, and reuse considerations for widely used research datasets.
Allen Brain Atlas
Allen Brain Atlas is an Allen Institute collection of brain map atlases, datasets, APIs, and analysis tools covering mouse, human, and non-human primate brain resources.
Annotated Behaviour and Observability Dataset (ABODe)
ABODe is a University of Edinburgh DataShare dataset for behavior classification in group-housed mice using home-cage video, identities, bounding boxes, ground-plate positions, and annotator labels.
DANDI Archive for NWB datasets
DANDI is a BRAIN Initiative archive for publishing and sharing neurophysiology data, including electrophysiology, optophysiology, and behavioral data packaged as NWB and related standards.
International Brain Laboratory public data
The International Brain Laboratory public data releases expose standardized mouse decision-making experiments, including Neuropixels recordings, widefield calcium imaging, behavior, and session metadata accessed through the ONE API.
OpenNeuro
OpenNeuro is a free, open platform for sharing neuroimaging datasets, with public search, dataset pages, and download paths for web, S3, DataLad, and the OpenNeuro CLI.