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.
328
datasets available to search
ShareScore release 0.9.0
Dataset results
328 results for “Simulation results”
Ocean model simulations in cold-water coral ecosystems off the coasts of Angola and Namibia in the Southeast Atlantic: Setup, boundary conditions and model results.
<p>The dataset contains all essential data for the setup of high-resolution local area model implementations using the ROMS-AGRIF model version 3.1 in two cold-water coral regions off the coasts of Angola and Namibia in the Southeast Atlantic. The data include computational grids, initialization fields (temperature, salinity), and boundary conditions (temperature, salinity, currents, and sea surface height) for each model area. It also includes model output, which has been used in different studies of the local oceanography of the region .</p> <p>Initialization, forcing and output data for each ROMS-AGRIF model implementation are provided in two compressed archive data files:</p> <ul> <li>Angola Margin: Angola_Model_Setup1.7z</li> <li>Namibia Margin: Namibia_Model_Setup1.7z</li> </ul> <p>The data set description is provided in the file:</p> <ul> <li>DataSet_Description_Angola_Namibia_Model.pdf</li> </ul> <div> <div> <div> <div> <div> <div> <div> <div> <div> <div> <div> <div> <div> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div>
Deliverable 1.1.1.1 BEL-Float project | Dataset containing the results of numerical simulations (motions, forces) of the operational performance analysis - Part 1: Operational scenario with 6.0 m significant wave height
<p>This dataset contains the results of OpenFAST simulations performed on the DeepCwind OC4 semi-submersible combined with the 5MW NREL turbine for various wind and wave conditions. The basis of the OpenFAST input files are taken from <a href="https://github.com/OpenFAST/r-test/tree/main/glue-codes/openfast/5MW_OC4Semi_WSt_WavesWN">OpenFAST r-test GitHub repository (5MW_OC4Semi_WSt_WavesWN)</a> and adapted to simulate various wind and wave conditions. The turbulent wind field as the input to the InflowWind module is generated using <a href="https://www.nrel.gov/wind/nwtc/turbsim.html">TurbSim</a>. The simulations are performed on a modified version of OpenFAST v3.5.3 to which adaptation to the code is made to extract additional Morison drag output up to 16 cylindrical members. This adapted code is <a href="https://github.com/abkpribadi/openfast/tree/Morison_additional_output">uploaded on GitHub as a branch from a forked OpenFAST repository</a>. In total there are 1152 simulation results consists of 768 irregular waves and 384 regular waves cases. The complete dataset is divided into 9 sub-datasets to which this is part number 1. A report describing this dataset is available on the BEL-Float project website: https://www.owi-lab.be/bel-float.</p> <p> </p> <p> </p> <p> </p>
Deliverable 1.1.1.1 BEL-Float project | Dataset containing the results of numerical simulations (motions, forces) of the operational performance analysis - Part 2: Operational scenario with 4.5 m significant wave height
<p>This dataset contains the results of OpenFAST simulations performed on the DeepCwind OC4 semi-submersible combined with the 5MW NREL turbine for various wind and wave conditions. The basis of the OpenFAST input files are taken from <a href="https://github.com/OpenFAST/r-test/tree/main/glue-codes/openfast/5MW_OC4Semi_WSt_WavesWN">OpenFAST r-test GitHub repository (5MW_OC4Semi_WSt_WavesWN)</a> and adapted to simulate various wind and wave conditions. The turbulent wind field as the input to the InflowWind module is generated using <a href="https://www.nrel.gov/wind/nwtc/turbsim.html">TurbSim</a>. The simulations are performed on a modified version of OpenFAST v3.5.3 to which adaptation to the code is made to extract additional Morison drag output up to 16 cylindrical members. This adapted code is <a href="https://github.com/abkpribadi/openfast/tree/Morison_additional_output">uploaded on GitHub as a branch from a forked OpenFAST repository</a>. In total there are 1152 simulation results consists of 768 irregular waves and 384 regular waves cases. The complete dataset is divided into 9 sub-datasets to which this is part number 2. A report describing this dataset is available on the BEL-Float project website: https://www.owi-lab.be/bel-float.</p>
Deliverable 1.1.1.1 BEL-Float project | Dataset containing the results of numerical simulations (motions, forces) of the operational performance analysis - Part 8: Damaged scenario with 1.5 m significant wave height
<p>This dataset contains the results of OpenFAST simulations performed on the DeepCwind OC4 semi-submersible combined with the 5MW NREL turbine for various wind and wave conditions. The basis of the OpenFAST input files are taken from <a href="https://github.com/OpenFAST/r-test/tree/main/glue-codes/openfast/5MW_OC4Semi_WSt_WavesWN">OpenFAST r-test GitHub repository (5MW_OC4Semi_WSt_WavesWN)</a> and adapted to simulate various wind and wave conditions. The turbulent wind field as the input to the InflowWind module is generated using <a href="https://www.nrel.gov/wind/nwtc/turbsim.html">TurbSim</a>. The simulations are performed on a modified version of OpenFAST v3.5.3 to which adaptation to the code is made to extract additional Morison drag output up to 16 cylindrical members. This adapted code is <a href="https://github.com/abkpribadi/openfast/tree/Morison_additional_output">uploaded on GitHub as a branch from a forked OpenFAST repository</a>. In total there are 1152 simulation results consists of 768 irregular waves and 384 regular waves cases. The complete dataset is divided into 9 sub-datasets to which this is part number 8. A report describing this dataset is available on the BEL-Float project website: https://www.owi-lab.be/bel-float.</p>
Deliverable 1.1.1.1 BEL-Float project | Dataset containing the results of numerical simulations (motions, forces) of the operational performance analysis - Part 7: Damaged scenario with 3.0 m significant wave height
<p>This dataset contains the results of OpenFAST simulations performed on the DeepCwind OC4 semi-submersible combined with the 5MW NREL turbine for various wind and wave conditions. The basis of the OpenFAST input files are taken from <a href="https://github.com/OpenFAST/r-test/tree/main/glue-codes/openfast/5MW_OC4Semi_WSt_WavesWN">OpenFAST r-test GitHub repository (5MW_OC4Semi_WSt_WavesWN)</a> and adapted to simulate various wind and wave conditions. The turbulent wind field as the input to the InflowWind module is generated using <a href="https://www.nrel.gov/wind/nwtc/turbsim.html">TurbSim</a>. The simulations are performed on a modified version of OpenFAST v3.5.3 to which adaptation to the code is made to extract additional Morison drag output up to 16 cylindrical members. This adapted code is <a href="https://github.com/abkpribadi/openfast/tree/Morison_additional_output">uploaded on GitHub as a branch from a forked OpenFAST repository</a>. In total there are 1152 simulation results consists of 768 irregular waves and 384 regular waves cases. The complete dataset is divided into 9 sub-datasets to which this is part number 7. A report describing this dataset is available on the BEL-Float project website: https://www.owi-lab.be/bel-float.</p>
Deliverable 1.1.1.1 BEL-Float project | Dataset containing the results of numerical simulations (motions, forces) of the operational performance analysis - Part 5: Damaged scenario with 6.0 m significant wave height
<p>This dataset contains the results of OpenFAST simulations performed on the DeepCwind OC4 semi-submersible combined with the 5MW NREL turbine for various wind and wave conditions. The basis of the OpenFAST input files are taken from <a href="https://github.com/OpenFAST/r-test/tree/main/glue-codes/openfast/5MW_OC4Semi_WSt_WavesWN">OpenFAST r-test GitHub repository (5MW_OC4Semi_WSt_WavesWN)</a> and adapted to simulate various wind and wave conditions. The turbulent wind field as the input to the InflowWind module is generated using <a href="https://www.nrel.gov/wind/nwtc/turbsim.html">TurbSim</a>. The simulations are performed on a modified version of OpenFAST v3.5.3 to which adaptation to the code is made to extract additional Morison drag output up to 16 cylindrical members. This adapted code is <a href="https://github.com/abkpribadi/openfast/tree/Morison_additional_output">uploaded on GitHub as a branch from a forked OpenFAST repository</a>. In total there are 1152 simulation results consists of 768 irregular waves and 384 regular waves cases. The complete dataset is divided into 9 sub-datasets to which this is part number 5. A report describing this dataset is available on the BEL-Float project website: https://www.owi-lab.be/bel-float.</p>
Deliverable 1.1.1.1 BEL-Float project | Dataset containing the results of numerical simulations (motions, forces) of the operational performance analysis - Part 6: Damaged scenario with 4.5 m significant wave height
<p>This dataset contains the results of OpenFAST simulations performed on the DeepCwind OC4 semi-submersible combined with the 5MW NREL turbine for various wind and wave conditions. The basis of the OpenFAST input files are taken from <a href="https://github.com/OpenFAST/r-test/tree/main/glue-codes/openfast/5MW_OC4Semi_WSt_WavesWN">OpenFAST r-test GitHub repository (5MW_OC4Semi_WSt_WavesWN)</a> and adapted to simulate various wind and wave conditions. The turbulent wind field as the input to the InflowWind module is generated using <a href="https://www.nrel.gov/wind/nwtc/turbsim.html">TurbSim</a>. The simulations are performed on a modified version of OpenFAST v3.5.3 to which adaptation to the code is made to extract additional Morison drag output up to 16 cylindrical members. This adapted code is <a href="https://github.com/abkpribadi/openfast/tree/Morison_additional_output">uploaded on GitHub as a branch from a forked OpenFAST repository</a>. In total there are 1152 simulation results consists of 768 irregular waves and 384 regular waves cases. The complete dataset is divided into 9 sub-datasets to which this is part number 6. A report describing this dataset is available on the BEL-Float project website: https://www.owi-lab.be/bel-float.</p>
Deliverable 1.1.1.1 BEL-Float project | Dataset containing the results of numerical simulations (motions, forces) of the operational performance analysis - Part 4: Operational scenario with 1.5 m significant wave height
<p>This dataset contains the results of OpenFAST simulations performed on the DeepCwind OC4 semi-submersible combined with the 5MW NREL turbine for various wind and wave conditions. The basis of the OpenFAST input files are taken from <a href="https://github.com/OpenFAST/r-test/tree/main/glue-codes/openfast/5MW_OC4Semi_WSt_WavesWN">OpenFAST r-test GitHub repository (5MW_OC4Semi_WSt_WavesWN)</a> and adapted to simulate various wind and wave conditions. The turbulent wind field as the input to the InflowWind module is generated using <a href="https://www.nrel.gov/wind/nwtc/turbsim.html">TurbSim</a>. The simulations are performed on a modified version of OpenFAST v3.5.3 to which adaptation to the code is made to extract additional Morison drag output up to 16 cylindrical members. This adapted code is <a href="https://github.com/abkpribadi/openfast/tree/Morison_additional_output">uploaded on GitHub as a branch from a forked OpenFAST repository</a>. In total there are 1152 simulation results consists of 768 irregular waves and 384 regular waves cases. The complete dataset is divided into 9 sub-datasets to which this is part number 4. A report describing this dataset is available on the BEL-Float project website: https://www.owi-lab.be/bel-float.</p>
Deliverable 1.1.1.1 BEL-Float project | Dataset containing the results of numerical simulations (motions, forces) of the operational performance analysis - Part 3: Operational scenario with 3.0 m significant wave height
<p>This dataset contains the results of OpenFAST simulations performed on the DeepCwind OC4 semi-submersible combined with the 5MW NREL turbine for various wind and wave conditions. The basis of the OpenFAST input files are taken from <a href="https://github.com/OpenFAST/r-test/tree/main/glue-codes/openfast/5MW_OC4Semi_WSt_WavesWN">OpenFAST r-test GitHub repository (5MW_OC4Semi_WSt_WavesWN)</a> and adapted to simulate various wind and wave conditions. The turbulent wind field as the input to the InflowWind module is generated using <a href="https://www.nrel.gov/wind/nwtc/turbsim.html">TurbSim</a>. The simulations are performed on a modified version of OpenFAST v3.5.3 to which adaptation to the code is made to extract additional Morison drag output up to 16 cylindrical members. This adapted code is <a href="https://github.com/abkpribadi/openfast/tree/Morison_additional_output">uploaded on GitHub as a branch from a forked OpenFAST repository</a>. In total there are 1152 simulation results consists of 768 irregular waves and 384 regular waves cases. The complete dataset is divided into 9 sub-datasets to which this is part number 3. A report describing this dataset is available on the BEL-Float project website: https://www.owi-lab.be/bel-float.</p>
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>
Time-averaged simulations results for bi-phasic blood flow simulations in realistic microvascular networks for various single- and multi-capillary occlusion scenarios.
<p><strong>DOCUMENTATION - Time-averaged simulations results for bi-phasic blood flow simulations in realistic microvascular networks for various single- and multi-capillary occlusion scenarios.</strong></p> <p>Correspondence: fschmid@ethz.ch (Franca Schmid, ORCID: <a href="https://orcid.org/0000-0002-0689-9366">0000-0002-0689-9366</a>)</p> <p><strong>1. Related references:</strong><br> The data set is published in context with the manuscript: <br> [1]<em> The severity of microstrokes depends on local vascular topology and baseline perfusion</em>. <br> F Schmid, G Conti, P Jenny and B Weber. eLife. 2021. Doi: 10.7554/eLife.60208</p> <p>The bi-phasic blood flow simulations have been performed in realistic microvascular networks (MVNs) from the mouse somatosensory cortex first published in:<br> [2]<em> The cortical angiome: an interconnected vascular network with noncolumnar patterns of blood flow</em>. P Blinder, PS Tsai, JP Kaufhold, PM Knutsen, H Suhl and D Kleinfeld. Nature Neuroscience. 2013. Doi: 10.1038/nn.3426</p> <p>The bi-phasic blood flow model for realistic MVNs has first been published in:<br> [3]<em> Depth-dependent flow and pressure characteristics in cortical microvascular networks</em>. F Schmid, PS Tsai, D Kleinfeld, P Jenny and B Weber. PLoS Computational Biology. 2017. Doi: 10.1371/journal.pcbi.1005392</p> <p><em>For further information on how to perform bi-phasic blood flow simulation, please contact the corresponding authors of [1] or [3].</em></p> <p><strong>2. Requirements (software):</strong><br> <em>All simulations and analyses have been performed in Python 2.7. To execute the analysis script the following python libraries need to be installed: cPickle, python-igraph, pandas, seaborn, scipy. The individual analyses script can then be executed by in Python (e.g. “python plot_Figure3.py”).</em></p> <p><strong>3. Content:</strong><br> <em>All folders are stored as compressed archives (*.tar.bz2). On unix-based system the folders can be unpacked by: "</em>tar –jxf ARCHIVE_NAME"<br> <br> <strong>3a. Time-averaged simulation results (python dictionaries stored as python 2.7 pickle files):</strong><br> <strong>SimulationResults_Baseline.tar.bz2:</strong><br> Folders: MVN1, MVN2<br> Content: verticesDict_baseline.pkl, edgesDict_baseline.pkl, pathsDict_allPaths_from_DA_to_AV_mainBranch.pkl (<em>generated from prepare_Figure4.py</em>), data_spatial_distribution_AVfactor.pkl (<em>generated from plot_Figure4.py</em>)</p> <p><strong>SimulationResults_SingleCapillaryOcclusions.tar.bz2:</strong><br> Folders: 1-in-1-out, 1-in-2-out, 2-in-1-out, 2-in-2-out, 2-in-2-out_high, 2-in-2-out_AL1, 2-in-2-out_AL2, 2-in-2-out_AL3, 2-in-2-out_AL4, 2-in-2-out_AL5, 2-in-2-out_closeToDA, 2-in-2-out_farFromDA<br> Content: verticesDict_baseline.pkl, edgesDict_baseline.pkl, pathsDict_allPaths_from_DA_to_AV_mainBranch_vertexBased.pkl (<em>only folders:</em> 1-in-1-out, 1-in-2-out, 2-in-1-out, 2-in-2-out)</p> <p><strong>SimulationResults_MultiCapillaryOcclusions.tar.bz2:</strong><br> Folders: vesselsOccluded_1, vesselsOccluded_3, vesselsOccluded_5, vesselsOccluded_7, vesselsOccluded_9<br> Content: verticesDict_baseline.pkl, edgesDict_baseline.pkl, pathsDict_allPaths_from_DA_to_AV_mainBranch_vertexBased.pkl</p> <p><strong>3b. Analysis scripts (python 2.7 scripts in folder Analyses_Scripts):</strong><br> <em>For details on the figure content see [1]. The verticesDict* and the edgesDict* are converted into graph structure (python-igraph) for all analyses. The functionality of python-igraph is used heavily throughout the various analyses.</em></p> <p><strong>helperFunctions.py</strong>: various functions used by the other analysis scripts</p> <p><strong>plot_Figure1_and_Figure1-supplement_1_a-d.py:</strong><br> <strong>Input:</strong> SimulationResults_Baseline/MVN1/edgesDict_baseline.pkl, SimulationResults_Baseline/MVN1/verticesDict_baseline.pkl, SimulationResults_SingleCapillaryOcclusion/2-in-2-out/edgesDict.pkl, SimulationResults_SingleCapillaryOcclusion/2-in-2-out/verticesDict.pkl, SimulationResults_SingleCapillaryOcclusion/2-in-1-out/edgesDict.pkl, SimulationResults_SingleCapillaryOcclusion/2-in-1-out/verticesDict.pkl, SimulationResults_SingleCapillaryOcclusion/1-in-2-out/edgesDict.pkl, SimulationResults_SingleCapillaryOcclusion/1-in-2-out/verticesDict.pkl, SimulationResults_SingleCapillaryOcclusion/1-in-1-out/edgesDict.pkl, SimulationResults_SingleCapillaryOcclusion/1-in-1-out/verticesDict.pkl<br> <strong>Output:</strong> Figures/Figure_1/*, Supplementary_Figures/Figure_1-supplement_1_a-d/*</p> <p><strong>plot_Figure2_and_Figure2_supplement_1_a-d.py:<br> Input:</strong> SimulationResults_Baseline/MVN1/edgesDict_baseline.pkl, SimulationResults_Baseline/MVN1/verticesDict_baseline.pkl, SimulationResults_SingleCapillaryOcclusion/2-in-2-out/edgesDict.pkl, SimulationResults_SingleCapillaryOcclusion/2-in-2-out/verticesDict.pkl, SimulationResults_SingleCapillaryOcclusion/2-in-1-out/edgesDict.pkl, SimulationResults_SingleCapillaryOcclusion/2-in-1-out/verticesDict.pkl, SimulationResults_SingleCapillaryOcclusion/1-in-2-out/edgesDict.pkl, SimulationResults_SingleCapillaryOcclusion/1-in-2-out/verticesDict.pkl, SimulationResults_SingleCapillaryOcclusion/1-in-1-out/edgesDict.pkl, SimulationResults_SingleCapillaryOcclusion/1-in-1-out/verticesDict.pkl<br> <strong>Output:</strong> Figures/Figure_2/*, Supplementary_Figures/Figure_2-supplement_1_a-d/*</p> <p><strong>plot_Figure3.py:<br> Input:</strong> SimulationResults_Baseline/MVN1/edgesDict_baseline.pkl, SimulationResults_Baseline/MVN1/verticesDict_baseline.pkl, SimulationResults_MultiCapillaryOcclusion/*/edgesDict.pkl, SimulationResults_MultiCapillaryOcclusion/*/verticesDict.pkl <br> <strong>Output</strong>: Figures/Figure_3/*</p> <p><strong>prepare_Figure4.py </strong>(<em>long execution time!):</em><br> <strong>Input:</strong> SimulationResults_Baseline/MVN*/edgesDict_baseline.pkl, SimulationResults_Baseline/MVN*/verticesDict_baseline.pkl,<br> <strong>Output:</strong> SimulationResults_Baseline/MVN*/pathsDict_allPaths_from_DA_to_AV_mainBranch.pkl</p> <p><strong>plot_Figure4.py </strong>(<em>long execution time!):</em><br> <strong>Input:</strong> SimulationResults_Baseline/MVN*/*<br> <strong>Output:</strong> SimulationResults_Baseline/MVN*/edgesDict_baseline.pkl (attribute Lfactor_median added), SimulationResults_Baseline/MVN*/data_spatial_distribution_AVfactor.pkl, Figures/Figure_4/*</p> <p><strong>plot_Figure5.py:</strong><br> <strong>Input:</strong> SimulationResults_Baseline/MVN*/* <br> <strong>Output:</strong> Figures/Figure_5/*</p> <p><strong>plot_Figure6.py:</strong><br> Input: SimulationResults_Baseline/MVN1/*, SimulationResults_SingleCapillaryOcclusion/2-in-2- out/pathsDict_allPaths_from_DA_to_AV_mainBranch_vertexBased.pkl, SimulationResults_SingleCapillaryOcclusion/2-in-1- out/pathsDict_allPaths_from_DA_to_AV_mainBranch_vertexBased.pkl, SimulationResults_SingleCapillaryOcclusion/1-in-2- out/pathsDict_allPaths_from_DA_to_AV_mainBranch_vertexBased.pkl, SimulationResults_SingleCapillaryOcclusion/1-in-1- out/pathsDict_allPaths_from_DA_to_AV_mainBranch_vertexBased.pkl Output: Figures/Figure_6/*</p> <p><strong>4. Attributes stored in python dictionaries:</strong><br> <br> <strong>4a. Baseline:</strong><br> <strong>verticesDict: </strong><em>contains all relevant information and data stored at vertices.</em></p> <ul> <li>index: index of vertex</li> <li>pressure: time averaged pressure at vertex [mmHg]</li> <li>inflowE: list of edges delivering blood to the vertex (inflows of the vertex)</li> <li>outflowE: list of edges removing blood from the vertex (outflows of the vertex)</li> <li>coords: coordinates of the vertex [µm]</li> <li>pBC: pressure boundary conditions [mmHg], None for internal vertices</li> <li>corticalDepth: depth from cortical surface [µm]</li> <li>nkind: identifier for the vessel type. 0: pial artery, 1: pial vein, 2: descending arteriole, 3: ascending vein, 4: capillary</li> </ul> <p><strong>edgesDict:</strong> <em>contains all relevant information and data stored at edges.</em></p> <ul> <li>diameter: effective vessel diameter [µm]. See [3] for details.</li> <li>htd: time averaged discharge hematocrit [-]. </li> <li>connectivity: tuple of vertex indices which are connected by the edge.</li> <li>mainAV: identifier for ascending venule (AV) main brain. 1: is AV main brain, 0: no AV main branch</li> <li>mainDA: identifier for descending arteriole (DA) main brain. 1: is DA main brain, 0: no DA main branch</li> <li>flow: time averaged flow rate [µm<sup>3</sup> ms<sup>-1</sup>]</li> <li>length: tortuous vessel length [µm] See [1] and [3] for details.</li> <li>tissueVolume: topological tissue volume supplied by vessel [µm<sup>3</sup>]. See [1] for details.</li> <li>nkind: identifier for the vessel type. 0: pial artery, 1: pial vein, 2: descending arteriole, 3: ascending vein, 4: capillary</li> <li>edgesFulfillingSelection: identifier if vessels fulfils selection criteria to qualify for analysis. 1: vessel included for analysis, 0: vessel not included for analysis. Details on the selection criteria are provided in [1].</li> <li>htt: time averaged tube hematocrit [-]</li> <li>RBCflux: time averaged RBC flux [RBC/s] computed from the discharge hematocrit and the flow rate.</li> <li>sign: sign describing the flow direction in the vessel. +: flow direction from source (vertex with lower index) to target (vertex with higher index), -: flow direction from target to source vertex. Based on time averaged pressure values.</li> <li>points: list of tortuous vessel coordinates of the edge [µm]. Starting at the source vertex. Ending at the target vertex.</li> <li>Lfactor_median: AV-factor of the vessel. None if no AV-factor can be assigned. See [1] for details. Attribute added by plot_Figure4.py</li> </ul> <p><strong>pathsDict_allPaths_from_DA_to_AV_mainBranch: </strong><em>contains all flow path from DA main brain to AV main branch. For details see [1]</em>.</p> <ul> <li>startPoint: list of vertex indices of the end point of the DA</li> <li>endPoint: list of vertex indices of the end point of the AV</li> <li>allPaths: list of lists of vertex indices describing all paths between a the associated startPoint and endPoint.</li> </ul> <p><strong>data_spatial_distribution_AVfactor:</strong> <em>contains information on the spatial distribution of venule-sided capillaries (AV-factor > 0.5). For details see [1].</em></p> <ul> <li>edges_L_mean_50um: list of all edges for which the average AV-factor in an analysis sphere of 50 µm has been computed.</li> <li>resulting_L_mean_50um: average AV-factor for an analysis sphere for 50 µm (see Figure4/AV_factor_delta_analysisSphere50_MVN*.pkl)</li> <li>shortest_distance_to_closest_vessel: list of shortest distances to any vessel for all discretization points along all venule sided capillaries.</li> <li>shortest_distance_to_Lfactor_lt_05: list of shortest distances to an arteriole-sided capillary (AV-factor < 0.5) for all discretization points along all venule sided capillaries.</li> </ul> <p><strong>4b. Occlusion scenarios (both single- and multi-capillary occlusions):</strong></p> <p><strong>verticesDict:</strong></p> <ul> <li>index: index of vertex</li> <li>coords: coordinates of the vertex [µm]</li> <li>pressure_strokeIndex_n: time averaged pressure at vertex [mmHg] for the simulation where edge n has been occluded. For details see [1].</li> </ul> <p><strong>edgesDict:</strong></p> <ul> <li>htd_strokeIndex_n: time averaged discharge hematocrit [-] for the simulation where edge n has been occluded. For details see [1]. </li> <li>flow: time averaged flow rate [µm<sup>3</sup> ms<sup>-1</sup>] for the simulation where edge n has been occluded. For details see [1].</li> <li>RBCflux: time averaged RBC flux [RBC/s] computed from the discharge hematocrit and the flow rate for the simulation where edge n has been occluded. For details see [1].</li> <li>htt: time averaged tube hematocrit [-] for the simulation where edge n has been occluded. For details see [1].</li> <li>connectivity: tuple of vertex indices which are connected by the edge.</li> <li>diameter_strokeIndex_n: effective vessel diameter [µm] for the simulation where edge n has been occluded (only given for multi-capillary occlusions).</li> </ul> <p><strong>pathsDict_allPaths_from_DA_to_AV_mainBranch_vertexBased:</strong> <em>contains all flow path from DA main brain to AV main branch (unique vertex sequences). For details see helperFunctions.py --></em><em> function convert_pathsDict_to_unique_vertexSequence.</em></p> <ul> <li>startPoint_strokeIndex_n: list of vertex indices of the end point of the DA for the simulation where edge n has been occluded.</li> <li>endpoint_strokeIndex_n: list of vertex indices of the end point of the AV for the simulation where edge n has been occluded.</li> <li>allPaths_strokeIndex_n: list of lists of vertex indices describing all paths between a the associated startPoint and endpoint for the simulation where edge n has been occluded.</li> </ul>
Text-fig. 1. Result of cumulative random counting of MN 5 localities in central Europe and the Iberian Peninsula. Ten simulations were run for each area. a. Results of the count including the average in bold, showing the clearly lower diversity in IB. b. The average lines standardized, showing similar patterns in the two areas. Note that in the simulation around thirty localities were needed to capture 80 % of the regional diversity. in Generically Speaking, A Survey On Neogene Rodent Diversity At The Genus Level In The Now Database
Text-fig. 1. Result of cumulative random counting of MN 5 localities in central Europe and the Iberian Peninsula. Ten simulations were run for each area. a. Results of the count including the average in bold, showing the clearly lower diversity in IB. b. The average lines standardized, showing similar patterns in the two areas. Note that in the simulation around thirty localities were needed to capture 80 % of the regional diversity.
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>
The results of SOCOLv4 simulations
<p>The results of SOCOLv4 simulations. Fin... - based on SSP2-4.5; s... - based on SSP5-8.5.</p>
Results set of GOTM-FABM-BFM 1D simulations at the BOUSSOLE site
<p>Output of model simulations of GOTM-FABM-BFM 1D at the BOUSSOLE site (RUNS_carbon) and time series of satellite data at the site (SAT_DATA). Both datasets can be integrated in https://github.com/ealvarez-s/results_BFM_CDOM.git, that contains all code scripts to reproduce results shown in Álvarez et al. (2023): Chromophoric dissolved organic matter dynamics revealed through the optimization of a spectrally and vertically resolved model in the NW Mediterranean Sea.</p>
Simulation results of advanced control for tri-generation heat pumps
<p>The data of this dataset comes from simulations performed in the software TRNSYS. The simulations were performed for the study case of a multi-family building situated in the climate of Tarragona, Spain, where the HVAC systems comprise a centralized dual source heat pump system. </p> <p>The simulations were done for 3 representative weeks selected for different seasons (winter, spring, summer). Each time, the simulation is performed twice: once with a standard reference control, and a second time with the advanced energy management system (AEMS) in control, programmed in GAMS and coupled with the TRNSYS simulation. Hence there are 6 tests in total, one per Excel sheet in the dataset file. The description of the columns is shown in the following table:</p> <table> <tbody> <tr> <td>Name</td> <td>Unit</td> <td>Description</td> </tr> <tr> <td>Tamb</td> <td>ºC</td> <td>Ambient outdoor temperature</td> </tr> <tr> <td>Irr</td> <td>kJ/h.m2</td> <td>Solar irradiation horizontal</td> </tr> <tr> <td>Troom</td> <td>ºC</td> <td>Room temperature</td> </tr> <tr> <td>Troom_set</td> <td>ºC</td> <td>Room set-point temperature</td> </tr> <tr> <td>Pel_FCU</td> <td>kW</td> <td>Electrical power consumption of the FCU</td> </tr> <tr> <td>Qth_cool_FCU</td> <td>kW</td> <td>Thermal cooling power of the FCU</td> </tr> <tr> <td>Qth_heat_RadFl</td> <td>kW</td> <td>Thermal heating power of the radiant floor</td> </tr> <tr> <td>TDHW_up</td> <td>ºC</td> <td>Temperature at the top of the DHW tank</td> </tr> <tr> <td>TDHW_lo</td> <td>ºC</td> <td>Temperature at the bottom of the DHW tank</td> </tr> <tr> <td>TSHC_up</td> <td>ºC</td> <td>Temperature at the top of the SHC tank</td> </tr> <tr> <td>TSHC_lo</td> <td>ºC</td> <td>Temperature at the bottom of the SHC tank</td> </tr> <tr> <td>Pel_HH_kW</td> <td>kW</td> <td>Electrical power consumption of the appliances</td> </tr> <tr> <td>Pel_PV_kW</td> <td>kW</td> <td>Electrical power generation of the PV</td> </tr> <tr> <td>Pel_HVAC_kW</td> <td>kW</td> <td>Electrical power consumption from the HVAC incl. HP</td> </tr> <tr> <td>Pel_Grid_kW</td> <td>kW</td> <td>Electrical exchange with the grid</td> </tr> <tr> <td>Pel_Bat_kW</td> <td>kW</td> <td>Charging/discharging power of the battery</td> </tr> <tr> <td>SOC_Bat</td> <td>%</td> <td>State of charge of the battery</td> </tr> <tr> <td>Qth_SH_kW</td> <td>kW</td> <td>Thermal heating power produced by the HP for space heating</td> </tr> <tr> <td>Qth_SC_kW</td> <td>kW</td> <td>Thermal cooling power produced by the HP for space cooling</td> </tr> <tr> <td>Qth_DHW_kW</td> <td>kW</td> <td>Thermal heating power produced by the HP for DHW</td> </tr> <tr> <td>Pel_HP_kW</td> <td>kW</td> <td>Electrical consumption of heat pump</td> </tr> </tbody> </table> <p>These results were extensively described in the deliverable D6.5 of the TRI-HP project. </p>
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>
The supplementary animations, results and the codes of the green-beard simulation study
<p>This dataset includes the Supplementary Animations, simulation codes and results of the article "The role of recognition error in the stability of green-beard genes" in <em>Evolution Letters</em>. <span>This dataset contains the MATLAB simulation code based on game-theoretic and green-beard aspects of the yeast interactions. The parameters of the simulation results (the relative fitness in each condition) are presented in the paper. The precise description is provided in the 'Simulation_code_and_dataset_guide.docx.' The visualizations of the simulation results are presented with Supplementary Animations. </span></p>
Global-mean results of short-term PPE simulations using GAMIL3
<p>Short-term perturbed-parameter-ensemble simulations are conducted using the Grid‐point Atmospheric Model of the Institute of Atmospheric Physics (IAP) of the Chinese Academy of Sciences (CAS) version 3, i.e., GAMIL3. A total of 256 parameter sets are generated using the quasi-Monte Carlo (QMC) sampling method. Each parameter set corresponds to a PPE member that consists of 12 two-month simulations initialized at 00UTC on the 1st day of each month of a model year. </p> <p>The uploaded dataset includes files related to parameter information and global-mean results of the PPE simulations.</p>
Deformation simulation results of Capriccio method coupled systems for conducting comparative one- and multidimensional studies on the coupling of the finite element method with particle-based techniques
<p>readme_3Dresults.txt</p> <p><br> <strong>Description</strong>:</p> <p>This readme explains the content and path structure of the results obtained from a<br> deformation test conducted on slightly different MD-FE coupled systems performing the<br> Capriccio method in a three-dimensional space within the associated project thesis [1],<br> published on the following dataset: <a href="https://doi.org/10.5281/zenodo.7924367">https://doi.org/10.5281/zenodo.7924367</a></p> <p>Furthermore, input files and parameters as well as potential tables required to reproduce<br> the obtained data are provided as well.</p> <p>The molecular dynamics (MD) part is executed in LAMMPS and the finite element (FE) method<br> part by a MATLAB script as described in Section 4.1 of [1]. The whole setup of the 3D<br> models is elaborated in Section 4.2 of [1]. A discussion of some results is given in<br> Chapter 6 of [1] in the context of assessing their comparability with the corresponding 1D<br> model.</p> <p><br> <strong>Context</strong>:</p> <p>[1] L. Laubert, "Establishing a framework for conducting comparative one- and<br> multidimensional studies on the coupling of the finite element method with<br> particle-based techniques", Project Thesis, Friedrich-Alexander-Universität<br> Erlangen-Nürnberg (FAU), 2023.</p> <p><br> <strong>Contact</strong>:</p> <p>Lukas Laubert<br> Institute of Applied Mechanics<br> Friedrich-Alexander-Universiät Erlangen-Nürnberg<br> Egerlandstraße 5<br> 91058 Erlangen</p> <p><br> <strong>License</strong>:</p> <p>Creative Commons Attribution Non Commercial 4.0 International</p> <p><br> <strong>Path structure and files</strong>:</p> <p>- The ZIP compressed files each contain a folder containing all simulation files as well as<br> postprocessing variables:<br> * /FE_data/ contains all output files after each FE simulation in each iteration step<br> * /MD_data/ contains all output files after each MD simulation in each iteration step<br> * /input_files/ contains the input FE model "cgps_dpd_c_1_2000.inp", the MD particle<br> configurations "cgps_dpd_c_1_2000.data", the AP particle coordinates <br> "cgps_dpd_c_1_2000.ac" as well as further Abaqus CAE FE files that<br> can be used to adapt the present FE model<br> * /input_parameters/ contains the parameter dataset; "Capriccio.prm" is the main parameter<br> dataset, whose adaptations lead to similar adjustments in the other parameter files<br> * "Capriccio_FEMD_main_meggie_WZ.sh" is a shell script for executing simulations<br> * "job.out" is an output protocol that documents the progress of the simulations<br> * "Job.err" is an error protocol that documents detected errors during the simulations<br> * "log.lammps" logs MD parameter sets<br> * "meta.info" provides version information of used softwares among few other information<br> * "next_job.info" documents the next load step and iteration step that is to be executed<br> when simulation jobs are restarted on the used computation cluser<br> * **_workspace_vars.mat comprises a set of postprocessing variables obtained by executing a<br> postprocessing script provided by Capriccio group</p> <p>- "md_dpd_main-CBpot-writeobs-sandw.in" is an input script that further defines and loads<br> MD simulation parameter</p> <p>- ***_table are potential tables applied during the MD simulations<br> * "Angle_table" lists the angle bending potential<br> * "Bond_table" lists the bond potentials<br> * "Nonbond_table" lists the non-bonded interaction potential</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.