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.
542
datasets available to search
ShareScore release 0.9.0
Dataset results
542 results for “model results”
Simulation Results Data for 'Modelling new insecticide-treated bed nets for malaria-vector control: How to strategically manage resistance?'
<p>GENERAL INFORMATION</p> <p>1. Title of Dataset: Simulation Results Data for 'Modelling new insecticide-treated bed-nets for malaria-vector control: How to strategically manage resistance?'</p> <p>2. Author Information<br> A. Investigator Contact Information<br> Name: Philip G. Madgwick<br> Institution: Syngenta <br> Address: Jealott’s Hill International Research Centre, Bracknell, RG42 6EY, UK<br> Email: philip.madgwick@syngenta.com</p> <p> B. Investigator Contact Information<br> Name: Ricardo Kanitz<br> Institution: Syngenta <br> Address: Syngenta Crop Protection, Rosentalstrasse 67, CH-4058 Basel, Switzerland<br> Email: ricardo.kanitz@syngenta.com</p> <p><br> 3. Date of data collection (single date, range, approximate date): 2021-01-13 to 2021-02-01 </p> <p>4. Geographic location of data collection: UK </p> <p>5. Information about funding sources that supported the collection of the data: </p> <p>This work was conducted during a postdoctoral research position for PGM funded by the Innovative Vector Control Consortium (IVCC).</p> <p><br> SHARING/ACCESS INFORMATION</p> <p>1. Licenses/restrictions placed on the data: NA</p> <p>2. Links to publications that cite or use the data: [UPDATE]</p> <p>3. Links to other publicly accessible locations of the data: NA</p> <p>4. Links/relationships to ancillary data sets: NA</p> <p>5. Was data derived from another source? No</p> <p>6. Recommended citation for this dataset: [UPDATE]</p> <p><br> DATA & FILE OVERVIEW</p> <p>1. File List: <br> PSData_random6.csv - 10^6 random samples of each of the 17 parameters in the model, where rows are samples and columns are parameters (with column names corresponding to the parameters identified in the rows of Table 1 of the manuscript; see also DATA-SPECIFIC INFORMATION)<br> Data_random6_maxpsMixture_Fixed_mm.csv - simulation dataset of 10^6 runs for each set of randomly sampled parameters; insecticide A and B are used in a mixture (at rate k=1; see manuscript) as a fixed strategy for the entire run; the resistance allele at locus 1 has mitochondrial inheritance and the resistance allele at locus 2 has mitochondrial inheritance <br> Data_random6_maxpsMixture_Fixed_mn.csv - simulation dataset of 10^6 runs for each set of randomly sampled parameters; insecticide A and B are used in a mixture (at rate k=1; see manuscript) as a fixed strategy for the entire run; the resistance allele at locus 1 has mitochondrial inheritance and the resistance allele at locus 2 has nuclear inheritance <br> Data_random6_maxpsMixture_Fixed_nn.csv - simulation dataset of 10^6 runs for each set of randomly sampled parameters; insecticide A and B are used in a mixture (at rate k=1; see manuscript) as a fixed strategy for the entire run; the resistance allele at locus 1 has nuclear inheritance and the resistance allele at locus 2 has nuclear inheritance <br> Data_random6_Mixture_Fixed_mm.csv - simulation dataset of 10^6 runs for each set of randomly sampled parameters; insecticide A and B are used in a mixture (at rate k; see manuscript) as a fixed strategy for the entire run; the resistance allele at locus 1 has mitochondrial inheritance and the resistance allele at locus 2 has mitochondrial inheritance <br> Data_random6_Mixture_Fixed_mn.csv - simulation dataset of 10^6 runs for each set of randomly sampled parameters; insecticide A and B are used in a mixture (at rate k; see manuscript) as a fixed strategy for the entire run; the resistance allele at locus 1 has mitochondrial inheritance and the resistance allele at locus 2 has nuclear inheritance <br> Data_random6_Mixture_Fixed_nn.csv - simulation dataset of 10^6 runs for each set of randomly sampled parameters; insecticide A and B are used in a mixture (at rate k; see manuscript) as a fixed strategy for the entire run; the resistance allele at locus 1 has nuclear inheritance and the resistance allele at locus 2 has nuclear inheritance <br> Data_random6_Mosaic_Fixed_mm.csv - simulation dataset of 10^6 runs for each set of randomly sampled parameters; insecticide A and B are used at 50% frequency each as a fixed strategy for the entire run; the resistance allele at locus 1 has mitochondrial inheritance and the resistance allele at locus 2 has mitochondrial inheritance <br> Data_random6_Mosaic_Fixed_mn.csv - simulation dataset of 10^6 runs for each set of randomly sampled parameters; insecticide A and B are used at 50% frequency each as a fixed strategy for the entire run; the resistance allele at locus 1 has mitochondrial inheritance and the resistance allele at locus 2 has nuclear inheritance <br> Data_random6_Mosaic_Fixed_nn.csv - simulation dataset of 10^6 runs for each set of randomly sampled parameters; insecticide A and B are used at 50% frequency each as a fixed strategy for the entire run; the resistance allele at locus 1 has nuclear inheritance and the resistance allele at locus 2 has nuclear inheritance <br> Data_random6_Rotation_Fixed_mm.csv - simulation dataset of 10^6 runs for each set of randomly sampled parameters; insecticide A is used first in a rotation that switch between insecticides every 36 generations as a fixed strategy for the entire run; the resistance allele at locus 1 has mitochondrial inheritance and the resistance allele at locus 2 has mitochondrial inheritance <br> Data_random6_Rotation_Fixed_mn.csv - simulation dataset of 10^6 runs for each set of randomly sampled parameters; insecticide A is used first in a rotation that switch between insecticides every 36 generations as a fixed strategy for the entire run; the resistance allele at locus 1 has mitochondrial inheritance and the resistance allele at locus 2 has nuclear inheritance <br> Data_random6_Rotation_Fixed_nn.csv - simulation dataset of 10^6 runs for each set of randomly sampled parameters; insecticide A is used first in a rotation that switch between insecticides every 36 generations as a fixed strategy for the entire run; the resistance allele at locus 1 has nuclear inheritance and the resistance allele at locus 2 has nuclear inheritance <br> Data_random6_Rotation_Fixed_revmm.csv - simulation dataset of 10^6 runs for each set of randomly sampled parameters; insecticide B is used first in a rotation that switch between insecticides every 36 generations as a fixed strategy for the entire run; the resistance allele at locus 1 has mitochondrial inheritance and the resistance allele at locus 2 has mitochondrial inheritance <br> Data_random6_Rotation_Fixed_revmn.csv - simulation dataset of 10^6 runs for each set of randomly sampled parameters; insecticide B is used first in a rotation that switch between insecticides every 36 generations as a fixed strategy for the entire run; the resistance allele at locus 1 has mitochondrial inheritance and the resistance allele at locus 2 has nuclear inheritance <br> Data_random6_Rotation_Fixed_revnn.csv - simulation dataset of 10^6 runs for each set of randomly sampled parameters; insecticide B is used first in a rotation that switch between insecticides every 36 generations as a fixed strategy for the entire run; the resistance allele at locus 1 has nuclear inheritance and the resistance allele at locus 2 has nuclear inheritance <br> Data_random6_SoloA_Fixed_mm.csv - simulation dataset of 10^6 runs for each set of randomly sampled parameters; insecticide A is used solo as a fixed strategy for the entire run; the resistance allele at locus 1 has mitochondrial inheritance and the resistance allele at locus 2 has mitochondrial inheritance <br> Data_random6_SoloA_Fixed_mn.csv - simulation dataset of 10^6 runs for each set of randomly sampled parameters; insecticide A is used solo as a fixed strategy for the entire run; the resistance allele at locus 1 has nuclear inheritance and the resistance allele at locus 2 has mitochondrial inheritance <br> Data_random6_SoloA_Fixed_nn.csv - simulation dataset of 10^6 runs for each set of randomly sampled parameters; insecticide A is used solo as a fixed strategy for the entire run; the resistance allele at locus 1 has nuclear inheritance and the resistance allele at locus 2 has nuclear inheritance <br> Data_random6_SoloB_Fixed_mm.csv - simulation dataset of 10^6 runs for each set of randomly sampled parameters; insecticide B is used solo as a fixed strategy for the entire run; the resistance allele at locus 1 has mitochondrial inheritance and the resistance allele at locus 2 has mitochondrial inheritance <br> Data_random6_SoloB_Fixed_mn.csv - simulation dataset of 10^6 runs for each set of randomly sampled parameters; insecticide B is used solo as a fixed strategy for the entire run; the resistance allele at locus 1 has nuclear inheritance and the resistance allele at locus 2 has mitochondrial inheritance <br> Data_random6_SoloB_Fixed_nn.csv - simulation dataset of 10^6 runs for each set of randomly sampled parameters; insecticide B is used solo as a fixed strategy for the entire run; the resistance allele at locus 1 has nuclear inheritance and the resistance allele at locus 2 has nuclear inheritance </p> <p>2. Relationship between files, if important: </p> <p>Files are named in accordance with the variables that describe each simulation setup, as described above. Each simulation dataset has 10^6 runs that correspond to the 10^6 random samples of each of the 17 parameters in the model in 'PSData_random6.csv'.</p> <p>3. Additional related data collected that was not included in the current data package: NA</p> <p>4. Are there multiple versions of the dataset? No</p> <p><br> METHODOLOGICAL INFORMATION</p> <p>1. Description of methods used for collection/generation of data: Data were collected using Simulator.R, which is in the vignettes of the 'detsims' R package that accompanies the manuscript. </p> <p>2. Methods for processing the data: Data were processed using Figures.R, which is in the vignettes of the 'detsims' R package that accompanies the manuscript. </p> <p>3. Instrument- or software-specific information needed to interpret the data: Analysis was conducted in R version 4.0.3 (2020-10-10), using R packages identified in Figures.R, which is in the vignettes of the 'detsims' R package that accompanies the manuscript. </p> <p>4. Standards and calibration information, if appropriate: NA</p> <p>5. Environmental/experimental conditions: NA</p> <p>6. Describe any quality-assurance procedures performed on the data: NA</p> <p>7. People involved with sample collection, processing, analysis and/or submission: NA </p> <p><br> DATA-SPECIFIC INFORMATION FOR: PSData_random6.csv</p> <p>1. Number of variables: </p> <p>17 variables with column names that have the following parameter meanings (see Table 1 in the manuscript): <br> Population Size = N = starting population size (and carrying capacity in logistic model); random sample range on log-scale: 10^2 - 10^9<br> Intrinsic Birth Rate = b = % population growth rate (in logistic model); random sample following a standard log-normal distribution with mean=0 and sd=1<br> Intrinsic Death Rate = d = % breeding mosquitoes that die into next generation; random sample range: 0 - 1<br> Female Exposure = x_[female-symbol] = % female mosquitoes that receive a dose; random sample range: 0 - 1<br> Male Exposure x_[male-symbol] = % male mosquitoes that receive a dose; random sample range: 0 - 1<br> Initial Frequency A = f_0,A = starting frequency of allele A; random sample range on log-scale: 10^-9 - 10^-2, limited to be within the range 1/N - N/100 where N is Population Size<br> Effectiveness 1 = m_1 = % dosed mosquitoes that die from insecticide 1; random sample range: 0 - 1<br> Resistance Restoration A = r_A = % return to baseline fitness with resistance allele A; random sample range: 0 - 1<br> Dominance of Resistance Restoration A = h^r_A = % resistance restoration in heterozygote with allele A; random sample range: 0 - 1<br> Resistance Cost A = c_A = % non-dosed mosquitoes that die from carrying allele A; random sample range on log-scale: 10^-3 - 10^-0.5<br> Dominance of Resistance Cost A = h^c_A = % resistance cost in heterozygote with allele A; random sample range: 0 - 1<br> Initial Frequency B = f_0,B = starting frequency of allele B; random sample range on log-scale: 10^-9 - 10^-2, limited to be within the range 1/N - N/100 where N is Population Size<br> Effectiveness 2 = m_2 = % dosed mosquitoes that die from insecticide 2; random sample range: 0 - 1<br> Resistance Restoration B = r_B = % return to baseline fitness with resistance allele B; random sample range: 0 - 1<br> Dominance of Resistance Restoration B = h^r_B = % resistance restoration in heterozygote with allele B; random sample range: 0 - 1<br> Resistance Cost B = c_B = % non-dosed mosquitoes that die from carrying allele B; random sample range on log-scale: 10^-3 - 10^-0.5<br> Dominance of Resistance Cost B = h^c_B = % resistance cost in heterozygote with allele B; random sample range: 0 - 1</p> <p>2. Number of cases/rows: </p> <p>10^6, corresponding to the number of random samples </p> <p>3. Variable List: NA </p> <p>4. Missing data codes: NA</p> <p>5. Specialized formats or other abbreviations used: NA</p> <p><br> DATA-SPECIFIC INFORMATION FOR: all other dataset files (e.g. Data_random6_maxpsMixture_Fixed_mm.csv) </p> <p>1. Number of variables: </p> <p>10 variables with column names that have the following meanings:<br> A_t_50% = the recorded number of generations that it takes for resistance allele A to reach >50% frequency; 0 means that resistance allele A never reaches >50% frequency <br> A_f_250 = the frequency of resistance allele A at the 250th generation <br> A_f_bar = the mean frequency of resistance allele A over the first 250 generations <br> B_t_50% = the recorded number of generations that it takes for resistance allele B to reach >50% frequency; 0 means that resistance allele B never reaches >50% frequency <br> B_f_250 = the frequency of resistance allele B at the 250th generation <br> B_f_bar = the mean frequency of resistance allele B over the first 250 generations <br> nf_80% = the recorded number of generations that it takes for the female population size to recover to >80% of its original size in the 0th generation; 0 means that the female population size never reaches >80% recovery; 1 means that the female population size never drops below 80% of its original size in the 1st generation<br> nf_250 = the female population size at the 250th generation<br> nf_bar = the mean female population size over the first 250 generations <br> nf_ext = the recorded number of generations that it takes for the female population size to drop below 1 (i.e. population extinction); 0 means that female population size never reaches <1</p> <p>2. Number of cases/rows: </p> <p>10^6, corresponding to the number of random samples </p> <p>3. Variable List: NA</p> <p>4. Missing data codes: all missing data is recorded as 0 </p> <p>5. Specialized formats or other abbreviations used: NA</p>
A new sampling capability for uncertainty quantification in the Ice-sheet and Sea-level System Model v4.19 using Gaussian Markov random fields -- Datasets and results
<p>Data archives for test experiments (Section 3) and Pine Island Glacier application (Section 4) from the manuscript "Kevin Bulthuis and Eric Larour, A new sampling capability for uncertainty quantification in the Ice-sheet and Sea-Level System Model v4.19 using Gaussian Markov random fields"</p> <p>Source code is available at https://doi.org/10.5281/zenodo.5532775.</p>
Competition between predicting mathematical models and laboratory results for covid 19 after vaccination in Iran
<p>All of us like to find a way to end Covid 19. Specially, economy confronts with many problems. In attached JPG, i bring two predictions for covid 19 pandemic in Iran. Mathematical model predicts that after a fall in figure we will have a peak. However, right now, most of people in Iran used of vaccines. In addition, government forced on all to get vaccine. Even, students with 12 to 18 years old get vaccine. It has been heard that soonly, kids with ages between 3-12 years old will receive vaccine. As a man or woman, all of us like that this program will response and vaccines work. However, predictions of math show reverse result. Although, maybe, we should enter the factor of vaccine in mathematical model. It is good opportunity for scientists to examine response of covid 19 to program of vaccine for all. Even if we have a peak, however its height be smaller, we can say that vaccines act. Hope for ending Covid 19 in all countries.</p>
Results from the FLEX Model for the paper "Impact of variable electricity price on heat pump operated buildings"
<p>The sqlite database contains the results of the Flex model for the Austrian single family house building stock ( insert GITHUB LINK). The building stock is represented by 36 different representative building archetypes (“OperationScenario_Component_Building”). Each building is simulated in twice. In the "reference" mode the energy demand is simply met and indoor comfort is kept constant. In the "optimization" mode the indoor temperature can be varied and thermal storages are charged and discharged minimizing the households energy cost based on a variable electricity price. The sqlite database “Variable_Price_Paper” contains the results for the building stock without any storage implemented. In “Variable_Price_Paper_TS” all buildings have a 750l hot water buffer storage and a 400l DHW storage implemented. The sqlite files SFH_23/25/27 contain the results for a single building where the maximum inside room temperature was changed to 23, 25 and 27 °C respectively.</p> <p>Following columns were used for generating the results for the Paper:</p> <p>In the hourly results relevant parameters used in the publication were:</p> <ul> <li>ID_Scenario: each building simulated under a different electricity price has a unique scenario number. “OperationScenario” gives an overview of the scenarios.</li> <li>Grid: describes the electricity demand from the grid by the household.</li> </ul> <p>In the yearly results relevant parameters used in the publication were:</p> <ul> <li>ID_Scenario</li> <li>TotalCost: represent the yearly operation cost</li> <li>Grid: electricity demand summed up for the whole year</li> </ul> <p>5 different electricity prices are used for scenario generation. The first price is constant, “electricity_2” is the real time price from 2021 plus a hypothetical grid fee of 20cents/kWh. “electricity_3, electricity_4, electricity_5” are prices generated for 2030 for Austria with the Balmorel model. Their profiles can be found under “OperationScenario_EnergyPrice”.</p> <p> </p>
Climate-ecosystem modelling made easy: the Land Sites Platform - simulation results
<p>Model data to reproduce the experiments and figures presented in "Climate-ecosystem modelling made easy: the Land Sites Platform" (Keetz & Lieungh et al., accepted; publication details to be added).</p> <p>The repository includes model input data for the BOR1 site, and model output for two cases (simulations) executed for that site. Case "bor1-1000y-allpfts" was run with default settings, whereas case "bor1-1000y-grasspfts" was run with C3 grass and Arctic C3 grass as the only plant functional types.<br> Concatenated versions of the model output (made by combining monthly history files) for each case are stored in the top folder as NetCDF files (.nc). The full case folders, including monthly output under /archive/lnd/hist, are stored under "cases/" as zipped directories.<br> The "data/" folder contains model input data for the site, and is identical for the two cases.</p> <p>Jupyter notebooks to analyse the data and create the plots in Figure 4 of the article are stored under "notebooks/technical_paper_results/" in the NorESM-LSP GitHub repository, which is accessible in the same version as the submitted manuscript here: 10.5281/zenodo.7310652</p> <p>Description: Model data to reproduce the experiments and figures presented in "Climate-ecosystem modelling made easy: the Land Sites Platform".<br> Coverage: Geographical coordinates 9.07876, 61.0355. Forcing data from the closest 0.5-degree model grid cell.<br> Format: NetCDF (.nc), zipped directories (.zip), shell scripts (.sh), XML files (.xml), text files (.txt), and others<br> Language: English<br> Relation: 10.5281/zenodo.7310652, <br> Source: GSWP3 for input data (Dirmeyer, P. A., Gao, X., Zhao, M., Guo, Z., Oki, T. and Hanasaki, N. (2006) GSWP-2: Multimodel Analysis and Implications for Our Perception of the Land Surface. Bulletin of the American Meteorological Society, 87(10), 1381–98.)</p>
Annotation-based Modeling of Non-functional Requirements and Analysis Results in Domain-driven Design
<p>This repo contains all supplementary data sets that we have created and used throughout this thesis. In particular, it contains<br> - expert interview material (elicitation): consent form and question catalogue for requirements elicitation<br> - expert interview material (evaluation): consent form and task description for expert evaluation<br> - Diagrams related to our modeling concept and Dqualizer<br> - Screenshots of the Domain Story Modeler with our Modeling Concept</p>
The computation results of coupled hydrological and hydrodynamic modelling application for the Nemunas River watershed – Curonian Lagoon – South-Eastern Baltic Sea continuum
<p>The datasets provided here were used to analyse the cumulative impacts of climate change in a Nemunas River watershed – Curonian Lagoon – South‑Eastern Baltic Sea continuum by applying a state-of-the-art coupled modelling system, which consists of hydrological and hydrodynamic models.</p> <p>Meteorological data used for running the models were acquired from CORDEX (Coordinated Regional Downscaling Experiment) scenarios for Europe from the Rossby Centre high-resolution regional atmospheric climate model (RCA4), which consisted of four sets of simulations (downscaling) driven by four global climate models:</p> <table> <tbody> <tr> <th>Abbreviation in datasets</th> <th>Model</th> <th><strong>Institution</strong></th> </tr> </tbody> <tbody> <tr> <td>ICHEC</td> <td>EC-Earth</td> <td>Irish Centre for High-End Computing</td> </tr> <tr> <td>IPSL</td> <td>IPSL-CM 5A-MR</td> <td>The Institut Pierre-Simon Laplace</td> </tr> <tr> <td>MOHC</td> <td>HadGEM2-ES</td> <td>Met Office Hadley Centre</td> </tr> <tr> <td>MPI</td> <td>MPI-ESM-LR</td> <td>Max Planck Institute for Meteorology</td> </tr> </tbody> </table> <p> </p> <p>Climate change scenarios and periods:</p> <ul> <li>Historical/reference (1970-2005);</li> <li>RCP4.5 (2005-2100);</li> <li>RCP8.5 (2005-2100).</li> </ul> <p>The datasets consist of time series for the parameters of:</p> <ul> <li><strong>Ice thickness</strong> - average ice thickness in the Curonian Lagoon;</li> <li><strong>Meteorological data</strong> - bias-corrected temperature and precipitation data for the marine and terrestrial areas;</li> <li><strong>Nemunas River discharge</strong> - simulated average daily values for the discharge and water temperature;</li> <li><strong>Salinity</strong> - selected points in the south-eastern Baltic Sea and one point next to Juodkrantė (in the Curonian Lagoon);</li> <li><strong>Water fluxes</strong> - through four predefined cross-sections in the Curonian Lagoon;</li> <li><strong>Water level</strong> - in 10 preselected points in the Curonian Lagoon and South-eastern Baltic Sea;</li> <li><strong>Water residence time</strong> - in the total Curonian Lagoon area, as well as its northern and southern parts;</li> <li><strong>Water temperature</strong> - in 10 preselected points in the Curonian Lagoon and South-eastern Baltic Sea.</li> </ul> <p>Some of the datasets (zip files) have additional information (coordinates, data column explanations, units, etc.) in READ_ME.txt files.</p>
200-years ice core bromine reconstruction at Dome C (Antarctica): observational and modelling results
<p>Bromine enrichment (Br<sub>enr</sub>) has been proposed as an ice core proxy for past sea-ice reconstruction. Understanding the processes that influence bromine preservation in the ice is crucial to achieve a reliable interpretation of ice core signals and to potentially relate them to past sea ice variability. Here, we present a 210 years bromine record that sheds light on the main processes controlling bromine preservation in the snow and ice at Dome C, East Antarctic plateau. Using observations alongside a modelling approach, we demonstrate that the bromine signal is preserved at Dome C and it is not affected by the strong variations in ultraviolet radiation reaching the Antarctic plateau due to the stratospheric ozone hole. Based on this, we investigate whether the Dome C Br<sub>enr</sub> record can be used as an effective tracer of past Antarctic sea ice. Due to the limited time window covered by satellite measurements and the low sea-ice variability observed during the last 30 years in East Antarctica, we cannot fully validate Br<sub>enr </sub>as an effective proxy for past sea-ice reconstructions at Dome C.</p> <p>In this database, annual averaged data for Br, Na and Br<sub>enr</sub> for the shallow ice core are provided.</p> <p> </p>
A habitat connectivity reality check for fish physical habitat model results and decision making for river restoration
<ol> <li>Fish physical habitat models are a tool for guiding restoration efforts in lotic ecosystems but often they overestimate restoration outcomes because currently they do not incorporate habitat connectivity. This persistent issue can, in extreme cases, result in little or no improvement to fish populations after the restoration, wasting valuable conservation resources.</li> <li>We present a case study where practitioners applied a fish habitat model for multiple life history stages of gravel spawning fishes to a 52 kilometer stretch of the Iller River but did so at a microscale implementation (every 200 meters). This approach provided an opportunity to assess the connectivity of gravel spawning fishes to find suitable habitats for all life history stages and seasonal movements.</li> <li>We used the assessed habitat estimates (availability of distinct habitat types within the 200 m reaches) to calculate the minimum distance a fish would need to go as it hypothetically “grew up” from egg to full spawning adult. We call this technique a reality check as it results in a decisive understanding of which areas were ultimately necessary to fulfill the life cycle of gravel spawning fishes, which standard assessments do not show.</li> <li>Our results show that complete connectivity still require long movement distances for vulnerable life stages to find suitable habitat. This contradicts standard practice, as restoration schemes and decision making often assume that connectivity inherently leads to more fish production without added habitat restoration.</li> <li>We recommend practitioners should perform this habitat connectivity approach when assessments implement fish habitat suitability models at similar scales. As a result, decision makers can evaluate proposed restoration sites and measures more realistically.</li> </ol>
Tables and Data for "Synthesis of Satellite and Surface Measurements, Model Results, and FRAPPÉ Study Findings to Assess the Impacts of Oil and Gas Emissions Reductions on Maximum Ozone in the Denver Metro and Northern Front Range Region in Colorado"
<p>These are data sets and tables used in the paper "Synthesis of Satellite and Surface Measurements, Model Results, and FRAPPÉ Study Findings to Assess the Impacts of Oil and Gas Emissions Reductions on Maximum Ozone in the Denver Metro and Northern Front Range Region in Colorado" to be submitted to Earth and Space Science. The monitor site 2016 and 2017 counts files have gridded HYSPLIT back trajectory counts for the 4 highest ozone concentration days at each site, as described in the manuscript.</p>
Results: Modeling the impact of the Omicron infection wave in Germany
<pre>Results: Modeling the impact of the Omicron infection wave in Germany This repository contains results of a modeling study regarding the spread of SARS-CoV-2 VOC "Omicron" in Germany. ## Columns and values | column name | type | description EN | description DE | | -- | -- | -- | -- | | `infectious_period_both` | int | Mean infectious period (in days) for both variants | Mittlere Infektiositaetsperiode fuer beide Varianten (in Tagen) | | `omicron_latent_period` | int | Mean latent period of VOC Omicron (in days) | Mittlere Latenzzeit der VOC Omikron (in Tagen) | | `booster_reach` | str | Reach of the booster campaign | Reichweite der Auffrischkampagne | | `booster_VE` | str | Vaccine efficacy of the booster vaccination | Impfeffektivitaet der Auffrischimpfung | | `contact_reduction_scenario_id` | int | ID of the contact reduction scenario | ID des Kontaktreduktionsszenarios | | `contact_reduction_strength` | float | prefactor with which the contact modulation f(t) is multiplied | Vorfaktor, mit der die Kontaktmodulation f(t) waehrend der Kontaktreduktionsperiode skaliert wird | | `contact_reduction_start` | date (ISO 8601) | Date when contact reduction begins | Beginn der Kontaktreduktion | | `contact_reduction_end` | date (ISO 8601) | Date when contact reduction ends | Ende der Kontaktreduktion | | `relative_risk_hospitalization` | float | Relative risk (RR) of hospitalization after infection with Omicron as compared to infection with Delta | Relatives Risiko (RR) der Hospitalisierung nach Infektion mit Omicron gegenueber Infektion mit Delta | | `relative_risk_icu` | float | Relative risk (RR) of ICU admission after infection with Omicron as compared to infection with Delta | Relatives Risiko (RR) der Intensivpflichtigkeit nach Infektion mit Omicron gegenueber Infektion mit Delta | | `value_type` | str | Wich value is shown in the `value` column | Art des Wertes in der Spalte `value` | | `date` | date (ISO 8601) | Date associated with the modeling result given in column `value` | Datum assoziiert mit dem Modellergebnis des Wertes in der Spalte `value` | | `value` | int | Model result (rounded to nearest integer) | Modellergebnis (gerundet auf ganze Zahl) | Additional columns regarding combinations of plausible scenarios (rounded to nearest integer) and 180 stochastic simulations per parameter combination: | column name | type | description EN | description DE | | -- | -- | -- | -- | | `95_PI_lower` | int | 95% PI lower bound (rounded to nearest integer) | Untere Schranke des 95% PIs (gerundet auf ganze Zahl) | | `50_PI_lower` | int | 50% PI lower bound (rounded to nearest integer) | Untere Schranke des 50% PIs (gerundet auf ganze Zahl) | | `median` | int | median (rounded to nearest integer) | Median (gerundet auf ganze Zahl) | | `50_PI_upper` | int | 50% PI upper bound (rounded to nearest integer) | Obere Schranke des 50% PIs (gerundet auf ganze Zahl) | | `95_PI_upper` | int | 95% PI upper bound (rounded to nearest integer) | Obere Schranke des 95% PIs (gerundet auf ganze Zahl) | ### Values: `booster_reach` | value | description EN | description DE | | -- | -- | -- | | `md` | medium booster campaign reach (80% of those that received full vaccination in 2021 receive booster vaccination) | Medium, 80% derjenigen, die in 2021 vollstaendig geimpft wurden, erhalten eine Auffrischimpfung | | `hi` | high booster campaign reach (100% of those that received full vaccination in 2021 receive booster vaccination) | Hoch, 100% derjenigen, die in 2021 vollstaendig geimpft wurden, erhalten eine Auffrischimpfung | | `hi-and-90perc-2dose` | 100% receive booster vaccination and vaccine uptake of first immunization suddenly increases to 90% in Jan 2022 | 100% erhalten Auffrischimpfung und Impfquote der Erstimmunisierung erreicht schnell 90% im Januar 2022 | ### Values: `booster_VE` | value | description EN | description DE | | -- | -- | -- | | `lo` | low booster vaccine efficacy (assumption: booster protects as well against infection as 2nd dose) | Niedrige Impfeffektivitaet (Auffr. schuetzt genauso gut vor Infektion wie 2 Dosen) | | `hi` | high booster vaccine efficacy (assumption: booster protects as well against infection as against symptomatic disease) | Hohe Impfeffektivitaet (Auffr. schuetzt genauso gut vor Infektion wie vor symptomatischer Erkrankung) | ### Values: `value_type` | value | description EN | description DE | | -- | -- | -- | | `inc` | incidence (absolute number of new reported cases per day) | Inzidenz (Zahl der gemeldeten Neuinfektion an diesem Tag, absolut) | | `hsp` | hospitalization incidence (absolute number of new hospital admissions per day) | Hospitalisierungsinzidenz (Zahl der gemeldeten Neuhospitalisierungen an diesem Tag, absolut) | | `icu` | total number of patients in ICUs | Gesamtzahl der intensivpflichtigen Patient:innen | ## License Licensed under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/).</pre>
Swiss Dwellings: A large dataset of apartment models including aggregated geolocation-based simulation results covering viewshed, natural light, traffic noise, centrality and geometric analysis
<p><strong>Introduction</strong></p> <p>This dataset contains detailed data on over 45,000 apartments (370,000 rooms) in ~3,100 buildings including their geometries, room typology as well as their visual, acoustical, topological, and daylight characteristics. Additionally, we have included location-specific characteristics for the buildings, including climatic data and points of interest within walking distance.</p> <p><strong>Changelog</strong></p> <ul> <li><strong>v3.0.0 (2023-03-31):</strong> <ul> <li>Updated the dataset increasing the total number of apartments to 45176 and incorporating fixes to some of the sites. The update includes re-digitized apartments and thus alters some ID values.</li> </ul> </li> <li><strong>v2.2.1 (2023-03-10):</strong> <ul> <li>A file, <code>location_ratings.csv</code>, has been included to provide ratings of the locations in which the buildings are situated. The ratings, provided by <a href="https://en.fpre.ch/">Fahrländer Partner AG</a>, give insights into the living situation at the buildings' addresses. Details for the different dimensions are provided below.</li> <li>The file <code>location.csv</code> has been updated to include the minimum and maximum temperatures for the locations in which the buildings are situated.</li> </ul> </li> <li><strong>v2.1.0 (2022-12-23)</strong>: <ul> <li>A file, <code>locations.csv</code>, has been included to provide information on the climatic and infrastructural characteristics of the locations in which each building is situated</li> </ul> </li> <li><strong>v2.0.0 (2022-10-17):</strong> <ul> <li>Additional to the residential units, we also include the commercial and public parts (such as staircases) of the models. The field <code>unit_usage</code> describes whether an area belongs to a commercial, residential, janitor or public part of the building</li> <li>Added the fields <code>elevation</code> and <code>height</code> to <em>geometries.csv</em> to describe the elevation above the terrain surface and the height of objects.</li> <li>Added the field <code>plan_id</code> which allows identifying which floors are based on the same floor plan (in some cases multiple floors of a building share the same floor plan</li> <li>Improved the ordering of fields in the CSV files (instead of alphabetic order)</li> <li>Minor changes to individual sites</li> </ul> </li> </ul> <p><strong>Procurement</strong></p> <p>The data is sourced from commercial clients of <a href="https://www.archilyse.com/">Archilyse AG</a> specializing on the digitization and analysis of buildings. The existing building plans of clients are converted into a geo-referenced, semantically annotated representation and undergo a manual Q/A process to ensure the accuracy of the data and to ensure a maximum 5%-deviation in the apartments' areas (validated with a median deviation of 1.2%).</p> <p><strong>Geometries</strong></p> <p>The dataset contains a file <code>geometries.csv</code> which contains the geometries of all areas, walls, railings, columns, windows, doors and features (sinks, bathtubs, etc.) of an apartment.</p> <p>In total, the datasets contain the 2D geometry of ~1.7 million separators (walls, railings), ~715,000 openings (windows, doors), ca. 520,000 areas (rooms, bathrooms, kitchens, etc.), and ~315,000 features (sinks, toilets, bathtubs, etc.).</p> <p>Each row contains:</p> <ul> <li><code>apartment_id</code>: The ID of the apartment (for features, areas), <em>note</em>: an apartment id is only unique per site</li> <li><code>site_id</code>: The ID of the site</li> <li><code>building_id</code>: The ID of the building</li> <li><code>floor_id</code>: The ID of the floor</li> <li><code>plan_id</code>: The ID of the plan on which the floor is based, multiple floors of a building might be based on the same plan</li> <li><code>unit_id</code>: The ID of the unit in which the element is spatially contained (for features, areas)</li> <li><code>area_id</code>: The ID of the area in which the element is spatially contained (for features)</li> <li><code>unit_usage</code>: The usage of the unit, possible values are: RESIDENTIAL, COMMERCIAL, PUBLIC, JANITOR</li> <li><code>entity_type</code>: The entity type (<em>area, separator, opening, feature</em>)</li> <li><code>entity_subtype</code>: The entity’s sub-type (e.g. <em>WALL</em>)</li> <li><code>geometry</code>: The element’s geometry as a <a href="https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry">WKT</a> geometry in meters. The geometry is given in the site’s local coordinate system. I.e. the position between elements of the same site are correct in respect to each other. The +y direction points northwards, the +x direction points eastwards.</li> <li><code>elevation</code>: The object's elevation above the terrain surface in meters. We assume one terrain baseline per building, thus all walls in a given floor share the same elevation value. However, windows in particular might start at different elevations and have differing heights.</li> <li><code>height</code>: The height of the entity in meters, <em>note</em>: In many cases, a default height is assumed</li> </ul> <p>An example:</p> <table> <thead> <tr> <th scope="col">column</th> <th scope="col"> </th> </tr> </thead> <tbody> <tr> <td>apartment_id</td> <td> <p>d4438f2129b30290845ce7eef98a5ba7</p> </td> </tr> <tr> <td>site_id</td> <td>127</td> </tr> <tr> <td>building_id</td> <td>164</td> </tr> <tr> <td>plan_id</td> <td>492</td> </tr> <tr> <td>floor_id</td> <td>861</td> </tr> <tr> <td>unit_id</td> <td>63777</td> </tr> <tr> <td>area_id</td> <td>767676</td> </tr> <tr> <td>unit_usage</td> <td>RESIDENTIAL</td> </tr> <tr> <td>entity_type</td> <td>area</td> </tr> <tr> <td>entity_subtype</td> <td>LIVING_ROOM</td> </tr> <tr> <td>geometry</td> <td> <p>POLYGON ((-6.1501158933490139 -4.8490786654693...</p> </td> </tr> <tr> <td>elevation</td> <td>0</td> </tr> <tr> <td>height</td> <td>2.6</td> </tr> </tbody> </table> <p><strong>Simulations</strong></p> <p>Besides the geometrical model, we also provide simulation data on the visual, acoustic, solar, layout, and connectivity-related characteristics of the apartments. The file <code>simulations.csv</code> contains the simulation data aggregated on a per-area basis. Each row contains the identifier columns <code>area_id</code>, <code>unit_id</code>, <code>apartment_id</code>, <code>floor_id</code>, <code>building_id</code>, <code>site_id</code> as defined above as well as 367 simulation columns. Each simulation column is formatted as:</p> <pre><code><simulation_category>_<simulation_dimensions>_<aggregation_function></code></pre> <p>For instance. the column <code>view_buildings_median</code> describes the amount of building surface that can be seen from any point in a given room. The aggregation methods vary per simulation category and are described in detail below.</p> <p><strong>Layout</strong></p> <p>The <em>layout</em> features represent simple features based on the geometry and composition of a room, the dataset provides the following information in an unaggregated form.</p> <p>Area Basics / Geometry</p> <table> <thead> <tr> <th>dimension</th> <th>description</th> </tr> </thead> <tbody> <tr> <td>layout_area_type</td> <td>The area’s area type</td> </tr> <tr> <td>layout_net_area</td> <td>The area’s share of the apartment’s net area (e.g. 0 for a balcony)</td> </tr> <tr> <td>layout_area</td> <td>The area’s actual area</td> </tr> <tr> <td>layout_perimeter</td> <td>The area’s perimeter</td> </tr> <tr> <td>layout_compactness</td> <td>The area’s compactness (the Polsby–Popper score)</td> </tr> <tr> <td>layout_room_count</td> <td>The area’s share to the apartment’s room count</td> </tr> <tr> <td>layout_is_navigable</td> <td>True if the area is navigable by a wheelchair</td> </tr> </tbody> </table> <p>Area Features</p> <table> <thead> <tr> <th>dimension</th> <th>description</th> </tr> </thead> <tbody> <tr> <td>layout_has_sink</td> <td>True if the area has a sink</td> </tr> <tr> <td>layout_has_shower</td> <td>True if the area has a shower</td> </tr> <tr> <td>layout_has_bathtub</td> <td>True if the area has a bathtub</td> </tr> <tr> <td>layout_has_toilet</td> <td>True if the area has a toilet</td> </tr> <tr> <td>layout_has_stairs</td> <td>True if the area has stairs</td> </tr> <tr> <td>layout_has_entrance_door</td> <td>True if the area is directly leading to an exit of the apartment</td> </tr> </tbody> </table> <p>Area Windows / Doors</p> <table> <thead> <tr> <th>dimension</th> <th>description</th> </tr> </thead> <tbody> <tr> <td>layout_number_of_doors</td> <td>The number of doors directly leading to the area</td> </tr> <tr> <td>layout_number_of_windows</td> <td>The number of windows of the area</td> </tr> <tr> <td>layout_door_perimeter</td> <td>The sum of all door lengths directly leading to the area</td> </tr> <tr> <td>layout_window_perimeter</td> <td>The sum of all window lengths of the area</td> </tr> </tbody> </table> <p>Area Walls / Railings</p> <table> <thead> <tr> <th>dimension</th> <th>description</th> </tr> </thead> <tbody> <tr> <td>layout_open_perimeter</td> <td>The sum of all of the boundaries of the area that are neither walls nor railings</td> </tr> <tr> <td>layout_railing_perimeter</td> <td>The sum of all of the boundaries of the area that are railings</td> </tr> <tr> <td>layout_mean_walllengths</td> <td>The mean length of the area’s sides</td> </tr> <tr> <td>layout_std_walllengths</td> <td>The standard deviation of the lengths of the area’s sides</td> </tr> </tbody> </table> <p>Area Adjacency</p> <table> <thead> <tr> <th>dimension</th> <th>description</th> </tr> </thead> <tbody> <tr> <td>layout_connects_to_bathroom</td> <td>True if the area connects to a bathroom</td> </tr> <tr> <td>layout_connects_to_private_outdoor</td> <td>True if the area connects to an outside area that is private to the apartment</td> </tr> </tbody> </table> <p><strong>View</strong></p> <p>The views from an object help to understand the impact of the surroundings on the object. The view simulation calculates the visible amount of buildings, greenery, water, etc. on each individual hexagon from the analyzed object. The values are expressed in steradians (sr) and represent the amount a particular object category occupies in the spherical field of view.</p> <p>Each of the following dimensions is provided using the room-wise aggregations' <em>min</em>, <em>max</em>, <em>mean</em>, <em>std</em>, <em>median</em>, <em>p20,</em> and <em>p80</em>. For instance, the column <code>view_greenery_p20</code> describes the amount of greenery that can be seen from at least 20% of the positions in the area.</p> <table> <thead> <tr> <th>dimension</th> <th>description</th> </tr> </thead> <tbody> <tr> <td>view_buildings</td> <td>The amount of visible buildings</td> </tr> <tr> <td>view_greenery</td> <td>The amount of visible greenery</td> </tr> <tr> <td>view_ground</td> <td>The amount of visible ground</td> </tr> <tr> <td>view_isovist</td> <td>The amount of visible isovist</td> </tr> <tr> <td>view_mountains_class_2</td> <td>The amount of visible mountains of UN mountain class 2</td> </tr> <tr> <td>view_mountains_class_3</td> <td>The amount of visible mountains of UN mountain class 3</td> </tr> <tr> <td>view_mountains_class_4</td> <td>The amount of visible mountains of UN mountain class 4</td> </tr> <tr> <td>view_mountains_class_5</td> <td>The amount of visible mountains of UN mountain class 5</td> </tr> <tr> <td>view_mountains_class_6</td> <td>The amount of visible mountains of UN mountain class 6</td> </tr> <tr> <td>view_railway_tracks</td> <td>The amount of visible railway_tracks</td> </tr> <tr> <td>view_site</td> <td>The amount of visible site</td> </tr> <tr> <td>view_sky</td> <td>The amount of visible sky</td> </tr> <tr> <td>view_tertiary_streets</td> <td>The amount of visible tertiary_streets</td> </tr> <tr> <td>view_secondary_streets</td> <td>The amount of visible secondary_streets</td> </tr> <tr> <td>view_primary_streets</td> <td>The amount of visible primary_streets</td> </tr> <tr> <td>view_pedestrians</td> <td>The amount of visible pedestrians</td> </tr> <tr> <td>view_highways</td> <td>The amount of visible highways</td> </tr> <tr> <td>view_water</td> <td>The amount of visible water</td> </tr> </tbody> </table> <p><strong>Sun</strong></p> <p>Sun simulations help to understand the impact of solar radiation on the object. The outcome of the sun simulations helps to identify surfaces that have great solar potential. Sun simulations are defined by the amount of solar radiation on each individual hexagon from the analyzed object. The sun simulation not only includes direct sun but also considers scattered light. The sun simulation values are given in Kilolux (klx). Simulations are performed for the days of the summer solstice, winter solstice, and the vernal equinox.</p> <p>Each of the following dimensions is provided using the room-wise aggregations' <em>min</em>, <em>max</em>, <em>mean</em>, <em>std</em>, <em>median</em>, <em>p20,</em> and <em>p80</em>. For instance, column <code>sun_201806211200_median</code> describes the median amount of direct daylight received on the positions in the area.</p> <p>Vernal Equinox</p> <table> <thead> <tr> <th>dimension</th> <th>description</th> </tr> </thead> <tbody> <tr> <td>sun_201803210800</td> <td>Daylight at 08:00 on 21st of March</td> </tr> <tr> <td>sun_201803211000</td> <td>Daylight at 10:00 on 21st of March</td> </tr> <tr> <td>sun_201803211200</td> <td>Daylight at 12:00 on 21st of March</td> </tr> <tr> <td>sun_201803211400</td> <td>Daylight at 14:00 on 21st of March</td> </tr> <tr> <td>sun_201803211600</td> <td>Daylight at 16:00 on 21st of March</td> </tr> <tr> <td>sun_201803211800</td> <td>Daylight at 18:00 on 21st of March</td> </tr> </tbody> </table> <p>Summer Solstice</p> <table> <thead> <tr> <th>dimension</th> <th>description</th> </tr> </thead> <tbody> <tr> <td>sun_201806210600</td> <td>Daylight at 06:00 on 21st of June</td> </tr> <tr> <td>sun_201806210800</td> <td>Daylight at 08:00 on 21st of June</td> </tr> <tr> <td>sun_201806211000</td> <td>Daylight at 10:00 on 21st of June</td> </tr> <tr> <td>sun_201806211200</td> <td>Daylight at 12:00 on 21st of June</td> </tr> <tr> <td>sun_201806211400</td> <td>Daylight at 14:00 on 21st of June</td> </tr> <tr> <td>sun_201806211600</td> <td>Daylight at 16:00 on 21st of June</td> </tr> <tr> <td>sun_201806211800</td> <td>Daylight at 18:00 on 21st of June</td> </tr> <tr> <td>sun_201806212000</td> <td>Daylight at 20:00 on 21st of June</td> </tr> </tbody> </table> <p>Winter Solstice</p> <table> <thead> <tr> <th>dimension</th> <th>description</th> </tr> </thead> <tbody> <tr> <td>sun_201812211000</td> <td>Daylight at 10:00 on 21st of December</td> </tr> <tr> <td>sun_201812211200</td> <td>Daylight at 12:00 on 21st of December</td> </tr> <tr> <td>sun_201812211400</td> <td>Daylight at 14:00 on 21st of December</td> </tr> <tr> <td>sun_201812211600</td> <td>Daylight at 16:00 on 21st of December</td> </tr> </tbody> </table> <p><strong>Noise / Window Noise</strong></p> <p>Noise level and the distribution of elements from an area help to understand how an object is exposed to the acoustics of this area. The acoustic simulation calculates the noise intensity on each individual hexagon from the analyzed object considering traffic and train noise datasets. Adjacent buildings are considered noise-blocking elements. The values are expressed in dBA (decibels).</p> <p>Window Noise</p> <p>The noise per window of a given area is aggregated via <code>min</code> and <code>max</code>. For instance, <code>window_noise_train_day_max</code> represents the maximum amount of noise received on any window of the area.</p> <table> <thead> <tr> <th>dimension</th> <th>description</th> </tr> </thead> <tbody> <tr> <td>window_noise_traffic_day</td> <td>The amount of noise received on the area’s windows from daytime car traffic</td> </tr> <tr> <td>window_noise_traffic_night</td> <td>The amount of noise received on the area’s windows from night-time car traffic</td> </tr> <tr> <td>window_noise_train_day</td> <td>The amount of noise received on the area’s windows from daytime train traffic</td> </tr> <tr> <td>window_noise_train_night</td> <td>The amount of noise received on the area’s windows from night-time train traffic</td> </tr> </tbody> </table> <p>Area-Wise Noise</p> <p>The area-wise noise describes the amount of noise received from a noise source aggregated over the whole area in an unaggregated form. For instance, <code>noise_traffic_night</code> describes the dBA of noise received in the area from car traffic at night when propagating noise from all windows.</p> <table> <thead> <tr> <th>dimension</th> <th>description</th> </tr> </thead> <tbody> <tr> <td>noise_traffic_day</td> <td>The amount of noise received in the area from daytime car traffic</td> </tr> <tr> <td>noise_traffic_night</td> <td>The amount of noise received in the area from night-time car traffic</td> </tr> <tr> <td>noise_train_day</td> <td>The amount of noise received in the area from daytime train traffic</td> </tr> <tr> <td>noise_train_night</td> <td>The amount of noise received in the area from night-time train traffic</td> </tr> </tbody> </table> <p><br> <strong>Connectivity</strong></p> <p>Centrality simulations help to analyze a floor plan, whether it’s a shopping mall and you want to identify prominent areas in order to select the most prominent spot or it’s an interior design circulation path and you want to determine open floor plan areas. Centrality simulations are done using topological measures that score grid cells by their importance as a part of a grid cell network.</p> <p>The distances and centralities are aggregated via <em>min</em>, <em>max</em>, <em>mean</em>, <em>std</em>, <em>median</em>, <em>p20,</em> and <em>p80</em>. For instance, <code>connectivity_balcony_distance_min</code> describes the shortest distance to the next balcony from the point closest to the balcony in the area.</p> <p>Distances</p> <table> <thead> <tr> <th>dimension</th> <th>description</th> </tr> </thead> <tbody> <tr> <td>connectivity_room_distance</td> <td>Distance to the next area of type ROOM</td> </tr> <tr> <td>connectivity_living_dining_distance</td> <td>Distance to the next area of type LIVING_DINING</td> </tr> <tr> <td>connectivity_bathroom_distance</td> <td>Distance to the next area of type BATHROOM</td> </tr> <tr> <td>connectivity_kitchen_distance</td> <td>Distance to the next area of type KITCHEN</td> </tr> <tr> <td>connectivity_balcony_distance</td> <td>Distance to the next area of type BALCONY</td> </tr> <tr> <td>connectivity_loggia_distance</td> <td>Distance to the next area of type LOGGIA</td> </tr> <tr> <td>connectivity_entrance_door_distance</td> <td>Distance to the next apartment exit</td> </tr> </tbody> </table> <p>Centralities</p> <table> <thead> <tr> <th>dimension</th> <th>description</th> </tr> </thead> <tbody> <tr> <td>connectivity_eigen_centrality</td> <td>The Eigen-Centrality value</td> </tr> <tr> <td>connectivity_betweenness_centrality</td> <td>The Betweenness-Centrality value</td> </tr> <tr> <td>connectivity_closeness_centrality</td> <td>The Closeness-Centrality value</td> </tr> </tbody> </table> <p><strong>Location Properties</strong></p> <p>In addition to the apartment-related data, we also provide simulation data on the climatic, and infrastructural characteristics of the locations. The file <code>locations.csv</code> contains the simulation data aggregated on a per-building basis. Each row contains the identifier <code>building_id</code> corresponding to the building ids referenced in <code>geometries.csv</code> and <code>simulations.csv</code>.</p> <p><strong>Climate</strong></p> <p>The climate features represent 39 simple features based on the spatial climate analysis of Meteo Swiss as derived from <a href="https://www.meteoswiss.admin.ch/climate/the-climate-of-switzerland/spatial-climate-analyses.html.">MeteoSwiss</a>. Each column is formatted as <code>climate_<category>_<period>. </code>For instance, the column <code>climate_tnorm_january</code> describes the monthly mean temperature in degrees Celsius (from the norm period of 1991-2020) at the location of the building. The aggregation methods vary per simulation category and are described in detail below.</p> <p>Temperature Normals</p> <table> <thead> <tr> <th>dimension</th> <th>description</th> </tr> </thead> <tbody> <tr> <td>climate_tnorm_year</td> <td>The yearly mean temperature in degrees Celsius of the current norm period from 1991 to 2020 (TnormY9120)</td> </tr> <tr> <td>climate_tnorm_january</td> <td>The monthly mean temperature in January in degrees Celsius of the current norm period from 1991 to 2020 (TnormM9120)</td> </tr> <tr> <td>climate_tnorm_februry</td> <td>The monthly mean temperature in February in degrees Celsius of the current norm period from 1991 to 2020 (TnormM9120)</td> </tr> <tr> <td>...</td> <td>...</td> </tr> <tr> <td>climate_tnorm_december</td> <td>The monthly mean temperature in December in degrees Celsius of the current norm period from 1991 to 2020 (TnormM9120)</td> </tr> <tr> <td>climate_tminnorm_january</td> <td>The monthly minimum temperature in January in degrees Celsius of the current norm period from 1991 to 2020 (TminnormM9120)</td> </tr> <tr> <td>...</td> <td> </td> </tr> <tr> <td>climate_tminnorm_december</td> <td>The monthly minimum temperature in December in degrees Celsius of the current norm period from 1991 to 2020 (TnormM9120)</td> </tr> <tr> <td>climate_tmaxnorm_january</td> <td>The monthly maximum temperature in January in degrees Celcius of the current norm period from 1991 to 2020 (TnormM9120)</td> </tr> <tr> <td>...</td> <td> </td> </tr> <tr> <td>climate_tmaxnorm_december</td> <td>The monthly maximum temperature in December in degrees Celcius of the current norm period from 1991 to 2020 (TnormM9120)</td> </tr> </tbody> </table> <p>Sunshine Duration Normals</p> <table> <thead> <tr> <th>dimension</th> <th>description</th> </tr> </thead> <tbody> <tr> <td>climate_snorm_year</td> <td>The yearly mean relative sunshine duration in percent of the current norm period from 1991 to 2020 (SnormY9120). Relative sunshine duration (RSD) is the ratio between the effective sunshine duration and the duration maximally possible if no clouds were covering the sun. A period with sunshine is defined as a period when the direct solar irradiance exceeds 200 W/m²</td> </tr> <tr> <td>climate_snorm_january</td> <td>The monthly mean relative sunshine duration for January in percent of the current norm period</td> </tr> <tr> <td>climate_snorm_februry</td> <td>The monthly mean relative sunshine duration for February in percent of the current norm period</td> </tr> <tr> <td>...</td> <td>...</td> </tr> <tr> <td>climate_snorm_december</td> <td>The monthly mean relative sunshine duration for December in percent of the current norm period</td> </tr> </tbody> </table> <p>Precipitation Normals</p> <table> <thead> <tr> <th>dimension</th> <th>description</th> </tr> </thead> <tbody> <tr> <td>climate_rnorm_year</td> <td>The yearly mean precipitation in mm of the current norm period (RnormY9120)</td> </tr> <tr> <td>climate_rnorm_january</td> <td>The monthly mean precipitation for January in mm of the current norm period (RnormM9120)</td> </tr> <tr> <td>climate_rnorm_februry</td> <td>The monthly mean precipitation for February in mm of the current norm period (RnormM9120)</td> </tr> <tr> <td>...</td> <td>...</td> </tr> <tr> <td>climate_rnorm_december</td> <td>The monthly mean precipitation for December mm of the current norm period (RnormM9120)</td> </tr> </tbody> </table> <p><strong>10-Minute Walkshed Infrastructure</strong></p> <p>Based on OpenStreetMap data and its tagging system we counted all 465 tags (key and value tuples as listed here: https://wiki.openstreetmap.org/wiki/Map_features) which can be reached within a 10-minute walk from the location of the building. Each column is formatted as <code>walkshed_<poi_category>_<poi_type>. </code>For instance, the column <code>walkshed_shop_coffee</code> describes the number of coffee shops located within 10 minutes of walking from the building.</p> <p>The following is an excerpt of support categories and their corresponding types.</p> <ul> <li><code>shop: antique, art, ...</code></li> <li><code>amenity: art, atm, ...</code></li> <li><code>tourism: alpine, attraction, ...</code></li> <li><code>leisure: amusement, beach, ...</code></li> <li><code>healthcare: clinic, dentist, ...</code></li> <li><code>historic: archaeological, battlefield, ...</code></li> <li><code>ariaelway: station</code></li> </ul> <p><strong>Location Ratings</strong></p> <p>The location ratings, provided by <a href="https://en.fpre.ch/">Fahrländer Partner AG</a>, give insights into the living situation at locations in which the buildings are situated. The file location_ratings.csv provides the following information:</p> <table> <thead> <tr> <th>dimension</th> <th>description</th> </tr> </thead> <tbody> <tr> <td>location_rating_MIKRAT_W</td> <td>Living situation - Overall (1.0=worst, 5.0=best)</td> </tr> <tr> <td>location_rating_IMAGE_W</td> <td>Living situation - Image (1.0=worst, 5.0=best)</td> </tr> <tr> <td>location_rating_DL_W</td> <td>Living situation - Service Quality (1.0=worst, 5.0=best)</td> </tr> <tr> <td>location_rating_FZ_W</td> <td> <p>Living situation - Leisure Quality (1.0=worst, 5.0=best)</p> </td> </tr> <tr> <td>location_rating_NASE_W_DOM</td> <td>The most dominant segment of demand:<br> <br> 1 Rural-traditional<br> 2 Modern worker<br> 3 Transitional-alternative<br> 4 Traditional middle class<br> 5 Liberal middle class<br> 6 Established alternative<br> 7 Upper middle class<br> 8 Professional elite<br> 9 Urban elite<br> 10 Unknown<br> <br> <a href="https://en.fpre.ch/marktdaten/nachfragersegmente/nachfragersegmente-im-wohnungsmarkt/">More Information</a></td> </tr> <tr> <td>location_rating_FGFRQZ</td> <td> <p>The mean number of pedestrians per hour throughout a day between 7 am and 8 pm of an average working day.<br> <br> 1 <50<br> 2 50-100<br> 3 100-200<br> 4 200-500<br> 5 >500</p> </td> </tr> </tbody> </table>
Interaction matters: Bottom-up driver interdependencies alter the projected response of phytoplankton communities to climate change, links to model results
<p>This dataset provides the output of ten model simulations with the global ocean biogeochemical model FESOM-REcoM necessary to reproduce the findings of Seifert et al. (2023). In addition to information on the mesh, the dataset contains 5-year means of global phytoplankton biomass, chlorophyll, net primary production, growth rates, limitations, carbonate system parameters (dissolved inorganic carbon, CO2 partial pressure, total alkalinity), temperature, photosynthetically active radiation, and mixed layer depths.</p> <p>File names refer to the figures in the paper where the respective data are used. See “readme” for detailed information on the dataset and separate files.</p>
Image dataset for cow identification, including code to train deep learning model, as well as analysis of results (SmARtview, 51088)
<p>This dataset and code was a result of the UKRI project "SmARtview: An AI-powered Augmented Reality Tool for Animal Health and Productivity", linked here: <a href="https://gtr.ukri.org/projects?ref=51088">https://gtr.ukri.org/projects?ref=51088</a></p> <p>These files are intended to be used for an accompanying publication in an academic journal.</p> <p>Anyone is free to use the contents for research and teaching purposes.</p>
model results from NHWAVE simulations of lobe-and-cleft instabilities at a river plume front
<p>The dataset contains the results from NHWAVE simulations of the lobe-and-cleft instabilities at a river plume front. The data format is .mat. The postprocessing scripts are included. </p>
Input and Output simulation data of the THOR GCM for the paper Dynamical and radiative effects resulting from the deep non-hydrostatic vs deep quasi-hydrostatic equations in the global circulation model THOR with an added non-grey radiative transfer scheme
<p>The input and ouput simulation data of the THOR GCM for Dynamical and radiative effects resulting from the deep non-hydrostatic vs deep quasi-hydrostatic equations in the global circulation model THOR with an added non-grey radiative transfer scheme</p> <p>Global circulation models (GCMs) play an important role in contemporary investigations of exoplanet atmospheres. Different GCMs evolve various sets of dynamical equations which can result in obtaining different atmospheric properties between models. In this study, we investigate the effect of different dynamical equation sets on the atmospheres of hot Jupiter exoplanets. We compare GCM simulations using the quasi-primitive dynamical equations (QHD) and the deep Navier-Stokes equations (NHD) in the GCM THOR. We utilise a two-stream non-grey "picket-fence" scheme to increase the realism of the radiative transfer scheme. We perform GCM simulations covering a wide parameter range grid of system parameters in the population of exoplanets. Our results show significant differences between simulations with the NHD and QHD equation sets at lower gravity, higher rotation rates or at higher irradiation temperatures. The parameter exploration shows the relevance of choosing dynamical equation sets dependent on system and planetary properties.Climate states of hot Jupiters seemed to be more diverse than previously thought. There are exceptions to prograde superrotation. Overall, our study shows the evolution of different climate states which arise just due to different selection of Navier-Stokes equations and approximations. We show the shortcomings of approximations in GCMs made for Earth, but used for non Earth-like planets.</p>
Model simulation data used in "The global impact of the transport sectors on the atmospheric aerosol and the resulting climate effects under the Shared Socioeconomic Pathways (SSPs)" (Righi et al., Earth Syst. Dynam., 2023)
<p>This dataset contains the output of the EMAC global model simulations analysed and discussed in Righi et al. (<i>Earth Syst. Dynam.</i>, 2023). For details see the README.md file.</p>
Experimental Results for "A Unified Perspective on Natural Gradient Variational Inference with Gaussian Mixture Models"
<p>This package contains the raw data / logs (fetched from WandB) for the experiments of the following publication:</p> <p>O. Arenz, P. Dahlinger, Z. Ye, M. Volpp, and G. Neumann. A unified perspective on natural gradient variational inference with gaussian mixture models. Transactions on Machine Learning Research, 2023. URL: <a href="https://openreview.net/forum?id=tLBjsX4tjs">https://openreview.net/forum?id=tLBjsX4tjs</a>.</p> <p> </p>
Results of a Survey on Obstacle Resolving Model Data
<p>This publication includes the results of the online survey "Obstacle resolving model data survey" which was available via https://www.uhh.de/orm-survey until June 2022. The data was collected between October 2019 and June 2022. The survey was created with the survey tool limesurvey (https://www.limesurvey.org/).</p> <p>The aim of the survey was to collect information on obstacle-resolving atmospheric models and their data, targeting the modeler community. As a part of the project AtMoDat (www.atmodat.de (https://www.atmodat.de/)) we invited the obstacle-resolving modeling community to contribute with their experience with obstacle-resolving models (ORM) and its model data, what models were used and how the user handles the data. We want to develop a data standard for obstacle-resolving model data, which shall be similar to existing standards. Therefore we need some information about the use and processing of model data. This survey asks about the usage of different obstacle-resolving models and/or outputs. </p> <p>The survey is divided into two parts, the first part contains questions about model properties and the second part contains questions about how the participants handle model data. </p>
Results and log of LLM-KG-Bench runs described in article "Developing a Scalable Benchmark for Assessing Large Language Models in Knowledge Graph Engineering", Meyer et al. 2023
<p>Results and logs of <a href="https://github.com/AKSW/LLM-KG-Bench">LLM-KG-Bench</a> runs described in article "Developing a Scalable Benchmark for Assessing Large Language Models in Knowledge Graph Engineering", Meyer et al., to appear in <a href="https://2023-eu.semantics.cc/page/accepted_posters">SEMANTICS 2023 poster track</a> proceedings.</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.