Skip to main content
Powered by ShareScore

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.

677

datasets available to search

ShareScore release 0.9.0

Reset

Dataset results

677 results for “time of use”

Learn how ShareScore rates datasets ↗
zenodo36/100

Replication package for "Pitfalls and Guidelines for Using Time-Based VCS Data"

<p>This dataset includes scripts, text files, and JSON files used to generate all analysis and results from the paper.&nbsp; A README.md file is included for details on using the scripts - though all of the data the scripts generate should already be cached as JSON or txt files and none of the scripts actually need run.</p> <p>It also includes a spreadsheet containing the paper survey results and manual judgements.</p> <p>The scripts are also on GitHub:&nbsp;<a href="https://github.com/psybers/emse21-timestudy">https://github.com/psybers/emse21-timestudy</a></p>

opencc-by-4.0Oct 2021View details →
dryad36/100

The time course of acclimation to the stress of triose phosphate use limitation

<p>Triose-phosphate utilization (TPU) limits the maximum rate at which plants can photosynthesize. However, TPU is almost never found to be limiting photosynthesis under ambient conditions for plants. This, along with previous results showing adaptability of TPU at low temperature, suggest that TPU capacity is regulated to be just above the photosynthetic rate achievable under the prevailing conditions. A set of experiments were performed to study the adaptability of TPU capacity when plants are acclimated to elevated CO<sub>2</sub> concentrations. Plants held at 1500 ppm CO<sub>2</sub> were initially TPU-limited. After 30 hours, they no longer exhibited TPU limitations, but they did not elevate their TPU capacity. Instead, the maximum rates of carboxylation and electron transport declined. A time course of regulatory responses was established. A step increase of CO<sub>2</sub> first caused PSI to be oxidized, but after 40 s, both PSI and PSII had excess electrons as a result of acceptor-side limitations. Electron flow to PSI slowed, and the proton motive force increased. Eventually, non-photochemical quenching reduced electron flow sufficiently to balance the TPU limitation. Over several minutes rubisco deactivated contributing to regulation of metabolism to overcome the TPU limitation.</p>

opencc-zeroOct 2022View details →
zenodo36/100

Data set for the figures in the manuscript "Real-Time Identification of Aerosol-Phase Carboxylic Acid Production Using Extractive Electrospray Ionization Mass Spectrometry"

Open the record for dataset details and reuse information.

opencc-by-4.0Apr 2024View details →
zenodo36/100

RepliChrom: Interpretable machine learning predicts cancer-associated enhancer-promoter interactions using DNA replication timing

<p>This dataset accompanies the study "RepliChrom: Interpretable machine learning predicts cancer-associated enhancer-promoter interactions using DNA replication timing". The study introduces RepliChrom, a computational framework designed to predict enhancer&ndash;promoter interactions (EPIs) by leveraging multi-scale replication timing (RT) signals. This approach addresses the fundamental challenge of distinguishing gene targets regulated by distal enhancers from those activated by proximal transcriptional activity-a key problem in understanding the causal basis of complex diseases.</p> <p>Despite recent advances in high-throughput technologies such as Hi-C, ChIA-PET, and Hi-TrAC that allow genome-wide reconstruction of 3D chromatin architecture, the role of DNA replication timing in mediating these spatial interactions remains underexplored. RepliChrom fills this gap by using cell-type-specific RT profiles as predictive features for chromatin interaction inference.</p> <p>To support model development, training, and evaluation, we provide a comprehensive multi-omics dataset covering six human cell lines (K562, GM12878, HeLaS3, IMR90, NHEK, and HUVEC ), encompassing:</p> <p>Hi-C datasets: Processed chromatin interaction loops used to define positive and negative enhancer&ndash;promoter interaction pairs.</p> <p>ChIA-PET datasets: Interaction data anchored around transcription factor binding, including POLR2A and CTCF, used for model validation across different interaction types.</p> <p>Hi-TrAC datasets: Targeted chromatin accessibility-derived interaction data, offering complementary validation of the model on alternate platforms.</p> <p>Replication Timing (RT) data: Processed RT signal profiles for each cell line, used to extract multi-scale temporal features as inputs for RepliChrom.</p> <p>These datasets enable reproducibility of the model training process and serve as benchmark resources for future research into DNA replication&ndash;mediated regulation of 3D genome architecture.</p> <p><strong>Included Files</strong></p> <p>Hi-C_datasets.zip (2.23 MB): Processed Hi-C interaction pairs for six cell types.</p> <p>ChIA-PET_datasets.zip (818.18 KB): CTCF and POLR2A ChIA-PET interactions across multiple lines.</p> <p>Hi-TrAC_datasets.zip (196 bytes): Hi-TrAC-based chromatin interaction training datasets across multiple lines.</p> <p>Cellline_RT_data.zip (86.17 MB): Replication timing signal data across multiple human cell types for multi-scale replication timing feature extraction.</p> <p><strong>Usage</strong><br>All datasets are intended for academic, non-commercial use. The provided files can be directly used to reproduce the training and evaluation of RepliChrom, and may also support broader applications in enhancer&ndash;promoter modeling, replication-timing analysis, and 3D genomics studies. For detailed usage instructions and code implementation, please refer to the GitHub repository: https://github.com/DaoFuying/RepliChrom</p>

opencc-by-4.0May 2024View details →
zenodo36/100

Landmine Detection Using Electromagnetic Time Reversal-Based Methods. Part 1: Classical TR, Iterative TR, DORT and TR-MUSIC

<p>In this repository, you can find the simulation files used to reproduce the results presented in the paper titled "Landmine Detection Using Electromagnetic Time Reversal-Based Methods." If you find these files useful, please cite the paper as it helps acknowledge the work and support future research.</p> <p>This repository is organized into three main folders, each serving a distinct purpose and containing specific types of files:</p> <p><strong>CST-MWS Files</strong>:&nbsp;This folder contains the necessary files to simulate the examples discussed in the paper using CST Microwave Studio (CST-MWS). These files are essential for setting up and running the simulations that replicate the experimental results.&nbsp;</p> <p><strong>TR-MUSIC</strong>:&nbsp;In this folder, you will find the MATLAB m-file required to implement the TR-MUSIC (Time Reversal-MUltiple SIgnal Classification) method proposed in the paper. This MATLAB script is designed to help users apply the TR-MUSIC algorithm to their data, enabling them to detect landmines effectively.&nbsp;</p> <p><strong>2D-GFB</strong>:&nbsp;The 2D-GFB folder contains the MATLAB m-file necessary to run the 2D TR-MUSIC and DORT (Decomposition of the Time Reversal Operator) methods. These advanced techniques are crucial for analyzing two-dimensional data and enhancing the accuracy of landmine detection.&nbsp;</p> <p><br>By organizing the repository in this manner, we aim to make it easier for researchers and practitioners to access and utilize the simulation files effectively. Whether you are replicating the study's results or applying these methods to new datasets, the files and instructions provided should serve as a valuable resource.</p> <p>If you encounter any issues or have questions regarding the use of these files, please do not hesitate to reach out for support. We hope this repository aids your research and contributes to advancements in landmine detection technologies.</p> <p>&nbsp;</p>

openmit-licenseJun 2024View details →
zenodo36/100

Research Compendium for Himes et al. (2024): "Using neural networks for near-real-time aerosol retrievals from OMPS Limb Profiler measurements"

<p>This archive is the Reproducible Research Compendium for</p> <p>Using neural networks for near-real-time aerosol retrievals from OMPS Limb Profiler measurements</p> <p>by Himes et al. (2024), submitted to Atmospheric Measurement Techniques.</p> <p>This compendium includes all files related to MARGE associated with the manuscript.</p> <p>NN model files are split into smaller files for convenience, given their sizes. &nbsp;To recombine the files, do, e.g.,&nbsp;<br>&nbsp; &nbsp; cat cnn_weights_NH-LW.h5* &gt; cnn_weights_NH-LW.h5</p> <p>User interested in running MARGE will need to clone the GitHub repo (https://github.com/exosports/MARGE), apply the patch file to checksum fc95b3c, organize the relevant files into directories as listed in the configuration files (Zenodo does not support organizing files into directory structures) and calculate the number of training, validation, and test cases to be stored in the relevant input file specified in the configuration file. &nbsp;MARGE is under the Reproducible Research Software License (https://planets.ucf.edu/resources/reproducible-research/software-license/). &nbsp;For more details on MARGE, see the User Manual on GitHub.</p>

openJun 2024View details →
zenodo36/100

Near real-time ultrahigh-resolution imaging from unmanned aerial vehicles for sustainable land use management and biodiversity conservation in semi-arid savanna under regional and global change (SAVMAP)

<p>To prevent aggravation of existing poverty in semi-arid savannas, a comprehensive concept for the sustainable adaptive management and use of these ecosystems under unprecedented conditions is needed. SAVMAP is an innovative, trans-, and inter-disciplinary initiative whose goal is to develop a valuable monitoring tool for both sustainable land-use management and rare species conservation (black rhinoceros) in semi-arid savanna in Namibia. SAVMAP uses near real-time ultrahigh-resolution photographic imaging (NURI) facilitated by unmanned aerial vehicles (UAVs) designed at EPFL.</p>

openafl-3.0Dec 2014View details →
zenodo36/100

Estimation of average diffuse aquifer recharge using time series modeling of groundwater heads

<p>This map contains the data used in the study &#39;Estimation of average diffuse aquifer recharge using time series modeling of groundwater heads&#39;. In this study a new method is presented to estimate average diffuse aquifer recharge of water table aquifers in temperate climates using time series analysis of water table level fluctuations. Recharge is estimated from time series models fitted to observed heads under the additional constraint that the seasonal harmonic of the observed head is reproduced as the sum of the transformed seasonal harmonics present in precipitation, evaporation, and pumping. The method is applied to measured heads obtained from piezometers situated on and around the ice-pushed sand ridge of Salland in the Netherlands. Results are compared with recharge estimates based on the saturated zone chloride mass balance.</p> <p>The data are ascii text files saved in the following compressed maps:<br> - Groundwater_chloride_concentration.zip<br> - Groundwater_head_time_series.zip<br> - Makkink_reference_evaporation_time_series.zip<br> - Measured_precipitation_time_series.zip<br> - Precipitation_chloride_concentrations.zip<br> - Pumping_time_series.zip</p> <p>For further details, please refer to the readme files contained in each submap.</p>

opencc-by-4.0Oct 2018View details →
zenodo36/100

A time-course analysis using Differential Static Light Scattering (DSLS) of purified HTT1-3144 Q23 - 2019/01/28

<p><strong>Project:&nbsp;</strong>Biophysical investigation of purified HTT protein samples</p> <p><strong>Experiment:&nbsp;</strong>A time-course analysis using Differential Static Light Scattering (DSLS) of purified HTT<sup>1-3144</sup>Q23&nbsp;</p> <p><strong>Date completed:&shy;&nbsp;</strong>2019/01/28</p> <p><strong>Rationale:&nbsp;</strong>Time and resources in the HD field have been primarily focussed on understanding HTT aggregation looking as caspase cleavage products spanning aa. 1-586 or exon 1 spanning aa. 1-90. However, we know that HTT protein purified in its apo form is able to self-associate into larger oligomeric species and that monomer, dimer and larger species are found following FLAG-affinity chromatography as determined by size-exclusion chromatography (SEC) and SEC-multi-angle light scattering (SEC-MALS). This experiment aimed to begin to investigate how HTT self-associates and aggregates over time in a range of different conditions.&nbsp;</p>

opencc-by-4.0Jan 2019View details →
zenodo36/100

Time-resolved single-cell RNA-seq using scSLAM-seq and GRAND-SLAM

<p>This is the example data for the protocol &quot;Time-resolved single-cell RNA-seq using scSLAM-seq and GRAND-SLAM&quot;.</p> <p>The test data comprises sequencing data from 12 different cells. Five of them in mock condition with 4sU, five infected with MCMV with 4sU and 2 uninfected cells without 4sU. For each sample, paired-end sequencing was conducted and therefore two files exist for each sample. The files can be found at data/fastq.</p> <p>The reads should be mapped against the mouse genome and the MCMV genome, which are located in data/genome. The sequence is in fasta-fomat and the features in gtf-format.The scripts conducting quality control, read mapping and GRAND-SLAM analysis can be found in the processing folder. For each computational step in this protocol there is a shell script for running the necessary steps. Executing all scripts will reproduce the analysis of our test data</p>

opencc-by-4.0Oct 2019View details →
zenodo36/100

An exploratory study (with and without time pressure) using mouse dynamics to detect faking-good behavior in the MMPI-2 and PPI-R validity scales

<p>Please find here&nbsp;the dataset&nbsp;generated and analyzed during the study entitled &quot;Can mouse dynamics detect faking-good behavior in personality questionnaires? An exploratory study (with and without time pressure) using the MMPI-2 and PPI-R validity scales&quot;.&nbsp;&nbsp;Moreover, here you can find the source code of the experiment to execute the task using MouseTracker software, the code of the statistical analysis and a file containing the instructions to replicate ML model results reported in the original paper.</p>

opencc-by-4.0Oct 2019View details →
zenodo36/100

Part 2 of real-time testing data for: "Identifying data sources and physical strategies used by neural networks to predict TC rapid intensification"

<p>Each file in the dataset contains machine-learning-ready data for one unique tropical cyclone (TC) from the real-time testing dataset. &nbsp;"Machine-learning-ready" means that all data-processing methods described in the journal paper have already been applied. &nbsp;This includes cropping satellite images to make them TC-centered; rotating satellite images to align them with TC motion (TC motion is always towards the +x-direction, or in the direction of increasing column number); flipping satellite images in the southern hemisphere upside-down; and normalizing data via the two-step procedure.</p> <p>The file name gives you the unique identifier of the TC -- e.g., "learning_examples_2010AL01.nc.gz" contains data for storm 2010AL01, or the first North Atlantic storm of the 2010 season. &nbsp;Each file can be read with the method `example_io.read_file` in the ml4tc Python library (https://zenodo.org/doi/10.5281/zenodo.10268620). &nbsp;However, since `example_io.read_file` is a lightweight wrapper for `xarray.open_dataset`, you can equivalently just use `xarray.open_dataset`. &nbsp;Variables in the table are listed below (the same printout produced by `print(xarray_table)`):</p> <p>Dimensions: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; satellite_valid_time_unix_sec: 289,<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; satellite_grid_row: 380,<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; satellite_grid_column: 540,<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; satellite_predictor_name_gridded: 1,<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; satellite_predictor_name_ungridded: 16,<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ships_valid_time_unix_sec: 19,<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ships_storm_object_index: 19,<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ships_forecast_hour: 23,<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ships_intensity_threshold_m_s01: 21,<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ships_lag_time_hours: 5,<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ships_predictor_name_lagged: 17,<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ships_predictor_name_forecast: 129)<br>Coordinates:<br>&nbsp; * satellite_grid_row &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (satellite_grid_row) int32 2kB ...<br>&nbsp; * satellite_grid_column &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(satellite_grid_column) int32 2kB ...<br>&nbsp; * satellite_valid_time_unix_sec &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(satellite_valid_time_unix_sec) int32 1kB ...<br>&nbsp; * ships_lag_time_hours &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (ships_lag_time_hours) float64 40B ...<br>&nbsp; * ships_intensity_threshold_m_s01 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_intensity_threshold_m_s01) float64 168B ...<br>&nbsp; * ships_forecast_hour &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_forecast_hour) int32 92B ...<br>&nbsp; * satellite_predictor_name_gridded &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (satellite_predictor_name_gridded) object 8B ...<br>&nbsp; * satellite_predictor_name_ungridded &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (satellite_predictor_name_ungridded) object 128B ...<br>&nbsp; * ships_valid_time_unix_sec &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_valid_time_unix_sec) int32 76B ...<br>&nbsp; * ships_predictor_name_lagged &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_predictor_name_lagged) object 136B ...<br>&nbsp; * ships_predictor_name_forecast &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_predictor_name_forecast) object 1kB ...<br>Dimensions without coordinates: ships_storm_object_index<br>Data variables:<br>&nbsp; &nbsp; satellite_number &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (satellite_valid_time_unix_sec) int32 1kB ...<br>&nbsp; &nbsp; satellite_band_number &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(satellite_valid_time_unix_sec) int32 1kB ...<br>&nbsp; &nbsp; satellite_band_wavelength_micrometres &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(satellite_valid_time_unix_sec) float64 2kB ...<br>&nbsp; &nbsp; satellite_longitude_deg_e &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(satellite_valid_time_unix_sec) float64 2kB ...<br>&nbsp; &nbsp; satellite_cyclone_id_string &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(satellite_valid_time_unix_sec) |S8 2kB ...<br>&nbsp; &nbsp; satellite_storm_type_string &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(satellite_valid_time_unix_sec) |S2 578B ...<br>&nbsp; &nbsp; satellite_storm_name &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (satellite_valid_time_unix_sec) |S10 3kB ...<br>&nbsp; &nbsp; satellite_storm_latitude_deg_n &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (satellite_valid_time_unix_sec) float64 2kB ...<br>&nbsp; &nbsp; satellite_storm_longitude_deg_e &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(satellite_valid_time_unix_sec) float64 2kB ...<br>&nbsp; &nbsp; satellite_storm_intensity_number &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (satellite_valid_time_unix_sec) float64 2kB ...<br>&nbsp; &nbsp; satellite_storm_u_motion_m_s01 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (satellite_valid_time_unix_sec) float64 2kB ...<br>&nbsp; &nbsp; satellite_storm_v_motion_m_s01 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (satellite_valid_time_unix_sec) float64 2kB ...<br>&nbsp; &nbsp; satellite_predictors_gridded &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (satellite_valid_time_unix_sec, satellite_grid_row, satellite_grid_column, satellite_predictor_name_gridded) float64 474MB ...<br>&nbsp; &nbsp; satellite_grid_latitude_deg_n &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(satellite_valid_time_unix_sec, satellite_grid_row, satellite_grid_column) float64 474MB ...<br>&nbsp; &nbsp; satellite_grid_longitude_deg_e &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (satellite_valid_time_unix_sec, satellite_grid_row, satellite_grid_column) float64 474MB ...<br>&nbsp; &nbsp; satellite_predictors_ungridded &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (satellite_valid_time_unix_sec, satellite_predictor_name_ungridded) float64 37kB ...<br>&nbsp; &nbsp; ships_storm_intensity_m_s01 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_valid_time_unix_sec) float64 152B ...<br>&nbsp; &nbsp; ships_storm_type_enum &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_storm_object_index, ships_forecast_hour) int32 2kB ...<br>&nbsp; &nbsp; ships_forecast_latitude_deg_n &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br>&nbsp; &nbsp; ships_forecast_longitude_deg_e &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br>&nbsp; &nbsp; ships_v_wind_200mb_0to500km_m_s01 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br>&nbsp; &nbsp; ships_vorticity_850mb_0to1000km_s01 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br>&nbsp; &nbsp; ships_vortex_latitude_deg_n &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br>&nbsp; &nbsp; ships_vortex_longitude_deg_e &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br>&nbsp; &nbsp; ships_mean_tangential_wind_850mb_0to600km_m_s01 &nbsp;(ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br>&nbsp; &nbsp; ships_max_tangential_wind_850mb_m_s01 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br>&nbsp; &nbsp; ships_mean_tangential_wind_1000mb_at500km_m_s01 &nbsp;(ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br>&nbsp; &nbsp; ships_mean_tangential_wind_850mb_at500km_m_s01 &nbsp; (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br>&nbsp; &nbsp; ships_mean_tangential_wind_500mb_at500km_m_s01 &nbsp; (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br>&nbsp; &nbsp; ships_mean_tangential_wind_300mb_at500km_m_s01 &nbsp; (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br>&nbsp; &nbsp; ships_srh_1000to700mb_200to800km_j_kg01 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br>&nbsp; &nbsp; ships_srh_1000to500mb_200to800km_j_kg01 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br>&nbsp; &nbsp; ships_threshold_exceedance_num_6hour_periods &nbsp; &nbsp; (ships_storm_object_index, ships_intensity_threshold_m_s01) int32 2kB ...<br>&nbsp; &nbsp; ships_v_motion_observed_m_s01 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_storm_object_index) float64 152B ...<br>&nbsp; &nbsp; ships_v_motion_1000to100mb_flow_m_s01 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_storm_object_index) float64 152B ...<br>&nbsp; &nbsp; ships_v_motion_optimal_flow_m_s01 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_storm_object_index) float64 152B ...<br>&nbsp; &nbsp; ships_cyclone_id_string &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_storm_object_index) object 152B ...<br>&nbsp; &nbsp; ships_storm_latitude_deg_n &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (ships_storm_object_index) float64 152B ...<br>&nbsp; &nbsp; ships_storm_longitude_deg_e &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_storm_object_index) float64 152B ...<br>&nbsp; &nbsp; ships_predictors_lagged &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_valid_time_unix_sec, ships_lag_time_hours, ships_predictor_name_lagged) float64 13kB ...<br>&nbsp; &nbsp; ships_predictors_forecast &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_valid_time_unix_sec, ships_forecast_hour, ships_predictor_name_forecast) float64 451kB ...</p> <p>Variable names are meant to be as self-explanatory as possible. &nbsp;Potentially confusing ones are listed below.</p> <ul> <li>The dimension ships_storm_object_index is redundant with the dimension ships_valid_time_unix_sec and can be ignored.</li> <li>ships_forecast_hour ranges up to values that we do not actually use in the paper. &nbsp;Keep in mind that our max forecast hour used in machine learning is 24.</li> <li>The dimension ships_intensity_threshold_m_s01 (and any variable including this dimension) can be ignored.</li> <li>ships_lag_time_hours corresponds to lag times for the SHIPS satellite-based predictors. &nbsp;The only lag time we use in machine learning is "NaN", which is a stand-in for the best available of all lag times. &nbsp;See the discussion of the "priority list" in the paper for more details.</li> <li>Most of the data variables can be ignored, unless you're doing a deep dive into storm properties. &nbsp;The important variables are satellite_predictors_gridded (full satellite images), ships_predictors_lagged (satellite-based SHIPS predictors), and ships_predictors_forecast (environmental and storm-history-based SHIPS predictors). &nbsp;These variables are all discussed in the paper.</li> <li>Every variable name (including elements of the coordinate lists ships_predictor_name_lagged and ships_predictor_name_forecast) includes units at the end. &nbsp;For example, "m_s01" = metres per second; "deg_n" = degrees north; "deg_e" = degrees east; "j_kg01" = Joules per kilogram; ...; etc.</li> </ul>

opencc-by-4.0Aug 2024View details →
zenodo36/100

Real-time testing data for: "Identifying data sources and physical strategies used by neural networks to predict TC rapid intensification"

<p>Each file in the dataset contains machine-learning-ready data for one unique tropical cyclone (TC) from the real-time testing dataset.&nbsp; "Machine-learning-ready" means that all data-processing methods described in the journal paper have already been applied.&nbsp; This includes cropping satellite images to make them TC-centered; rotating satellite images to align them with TC motion (TC motion is always towards the +x-direction, or in the direction of increasing column number); flipping satellite images in the southern hemisphere upside-down; and normalizing data via the two-step procedure.</p> <p>The file name gives you the unique identifier of the TC -- e.g., "learning_examples_2010AL01.nc.gz" contains data for storm 2010AL01, or the first North Atlantic storm of the 2010 season.&nbsp; Each file can be read with the method `example_io.read_file` in the ml4tc Python library (https://zenodo.org/doi/10.5281/zenodo.10268620).&nbsp; However, since `example_io.read_file` is a lightweight wrapper for `xarray.open_dataset`, you can equivalently just use `xarray.open_dataset`.&nbsp; Variables in the table are listed below (the same printout produced by `print(xarray_table)`):</p> <p>Dimensions: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; satellite_valid_time_unix_sec: 289,<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; satellite_grid_row: 380,<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; satellite_grid_column: 540,<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; satellite_predictor_name_gridded: 1,<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; satellite_predictor_name_ungridded: 16,<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ships_valid_time_unix_sec: 19,<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ships_storm_object_index: 19,<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ships_forecast_hour: 23,<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ships_intensity_threshold_m_s01: 21,<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ships_lag_time_hours: 5,<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ships_predictor_name_lagged: 17,<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ships_predictor_name_forecast: 129)<br>Coordinates:<br>&nbsp; * satellite_grid_row &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (satellite_grid_row) int32 2kB ...<br>&nbsp; * satellite_grid_column &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(satellite_grid_column) int32 2kB ...<br>&nbsp; * satellite_valid_time_unix_sec &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(satellite_valid_time_unix_sec) int32 1kB ...<br>&nbsp; * ships_lag_time_hours &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (ships_lag_time_hours) float64 40B ...<br>&nbsp; * ships_intensity_threshold_m_s01 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_intensity_threshold_m_s01) float64 168B ...<br>&nbsp; * ships_forecast_hour &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_forecast_hour) int32 92B ...<br>&nbsp; * satellite_predictor_name_gridded &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (satellite_predictor_name_gridded) object 8B ...<br>&nbsp; * satellite_predictor_name_ungridded &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (satellite_predictor_name_ungridded) object 128B ...<br>&nbsp; * ships_valid_time_unix_sec &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_valid_time_unix_sec) int32 76B ...<br>&nbsp; * ships_predictor_name_lagged &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_predictor_name_lagged) object 136B ...<br>&nbsp; * ships_predictor_name_forecast &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_predictor_name_forecast) object 1kB ...<br>Dimensions without coordinates: ships_storm_object_index<br>Data variables:<br>&nbsp; &nbsp; satellite_number &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (satellite_valid_time_unix_sec) int32 1kB ...<br>&nbsp; &nbsp; satellite_band_number &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(satellite_valid_time_unix_sec) int32 1kB ...<br>&nbsp; &nbsp; satellite_band_wavelength_micrometres &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(satellite_valid_time_unix_sec) float64 2kB ...<br>&nbsp; &nbsp; satellite_longitude_deg_e &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(satellite_valid_time_unix_sec) float64 2kB ...<br>&nbsp; &nbsp; satellite_cyclone_id_string &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(satellite_valid_time_unix_sec) |S8 2kB ...<br>&nbsp; &nbsp; satellite_storm_type_string &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(satellite_valid_time_unix_sec) |S2 578B ...<br>&nbsp; &nbsp; satellite_storm_name &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (satellite_valid_time_unix_sec) |S10 3kB ...<br>&nbsp; &nbsp; satellite_storm_latitude_deg_n &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (satellite_valid_time_unix_sec) float64 2kB ...<br>&nbsp; &nbsp; satellite_storm_longitude_deg_e &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(satellite_valid_time_unix_sec) float64 2kB ...<br>&nbsp; &nbsp; satellite_storm_intensity_number &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (satellite_valid_time_unix_sec) float64 2kB ...<br>&nbsp; &nbsp; satellite_storm_u_motion_m_s01 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (satellite_valid_time_unix_sec) float64 2kB ...<br>&nbsp; &nbsp; satellite_storm_v_motion_m_s01 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (satellite_valid_time_unix_sec) float64 2kB ...<br>&nbsp; &nbsp; satellite_predictors_gridded &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (satellite_valid_time_unix_sec, satellite_grid_row, satellite_grid_column, satellite_predictor_name_gridded) float64 474MB ...<br>&nbsp; &nbsp; satellite_grid_latitude_deg_n &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(satellite_valid_time_unix_sec, satellite_grid_row, satellite_grid_column) float64 474MB ...<br>&nbsp; &nbsp; satellite_grid_longitude_deg_e &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (satellite_valid_time_unix_sec, satellite_grid_row, satellite_grid_column) float64 474MB ...<br>&nbsp; &nbsp; satellite_predictors_ungridded &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (satellite_valid_time_unix_sec, satellite_predictor_name_ungridded) float64 37kB ...<br>&nbsp; &nbsp; ships_storm_intensity_m_s01 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_valid_time_unix_sec) float64 152B ...<br>&nbsp; &nbsp; ships_storm_type_enum &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_storm_object_index, ships_forecast_hour) int32 2kB ...<br>&nbsp; &nbsp; ships_forecast_latitude_deg_n &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br>&nbsp; &nbsp; ships_forecast_longitude_deg_e &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br>&nbsp; &nbsp; ships_v_wind_200mb_0to500km_m_s01 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br>&nbsp; &nbsp; ships_vorticity_850mb_0to1000km_s01 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br>&nbsp; &nbsp; ships_vortex_latitude_deg_n &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br>&nbsp; &nbsp; ships_vortex_longitude_deg_e &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br>&nbsp; &nbsp; ships_mean_tangential_wind_850mb_0to600km_m_s01 &nbsp;(ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br>&nbsp; &nbsp; ships_max_tangential_wind_850mb_m_s01 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br>&nbsp; &nbsp; ships_mean_tangential_wind_1000mb_at500km_m_s01 &nbsp;(ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br>&nbsp; &nbsp; ships_mean_tangential_wind_850mb_at500km_m_s01 &nbsp; (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br>&nbsp; &nbsp; ships_mean_tangential_wind_500mb_at500km_m_s01 &nbsp; (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br>&nbsp; &nbsp; ships_mean_tangential_wind_300mb_at500km_m_s01 &nbsp; (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br>&nbsp; &nbsp; ships_srh_1000to700mb_200to800km_j_kg01 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br>&nbsp; &nbsp; ships_srh_1000to500mb_200to800km_j_kg01 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br>&nbsp; &nbsp; ships_threshold_exceedance_num_6hour_periods &nbsp; &nbsp; (ships_storm_object_index, ships_intensity_threshold_m_s01) int32 2kB ...<br>&nbsp; &nbsp; ships_v_motion_observed_m_s01 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_storm_object_index) float64 152B ...<br>&nbsp; &nbsp; ships_v_motion_1000to100mb_flow_m_s01 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_storm_object_index) float64 152B ...<br>&nbsp; &nbsp; ships_v_motion_optimal_flow_m_s01 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_storm_object_index) float64 152B ...<br>&nbsp; &nbsp; ships_cyclone_id_string &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_storm_object_index) object 152B ...<br>&nbsp; &nbsp; ships_storm_latitude_deg_n &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (ships_storm_object_index) float64 152B ...<br>&nbsp; &nbsp; ships_storm_longitude_deg_e &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_storm_object_index) float64 152B ...<br>&nbsp; &nbsp; ships_predictors_lagged &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_valid_time_unix_sec, ships_lag_time_hours, ships_predictor_name_lagged) float64 13kB ...<br>&nbsp; &nbsp; ships_predictors_forecast &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(ships_valid_time_unix_sec, ships_forecast_hour, ships_predictor_name_forecast) float64 451kB ...</p> <p>Variable names are meant to be as self-explanatory as possible.&nbsp; Potentially confusing ones are listed below.</p> <ul> <li>The dimension ships_storm_object_index is redundant with the dimension ships_valid_time_unix_sec and can be ignored.</li> <li>ships_forecast_hour ranges up to values that we do not actually use in the paper.&nbsp; Keep in mind that our max forecast hour used in machine learning is 24.</li> <li>The dimension ships_intensity_threshold_m_s01 (and any variable including this dimension) can be ignored.</li> <li>ships_lag_time_hours corresponds to lag times for the SHIPS satellite-based predictors.&nbsp; The only lag time we use in machine learning is "NaN", which is a stand-in for the best available of all lag times.&nbsp; See the discussion of the "priority list" in the paper for more details.</li> <li>Most of the data variables can be ignored, unless you're doing a deep dive into storm properties.&nbsp; The important variables are satellite_predictors_gridded (full satellite images), ships_predictors_lagged (satellite-based SHIPS predictors), and ships_predictors_forecast (environmental and storm-history-based SHIPS predictors).&nbsp; These variables are all discussed in the paper.</li> <li>Every variable name (including elements of the coordinate lists ships_predictor_name_lagged and ships_predictor_name_forecast) includes units at the end.&nbsp; For example, "m_s01" = metres per second; "deg_n" = degrees north; "deg_e" = degrees east; "j_kg01" = Joules per kilogram; ...; etc.</li> </ul>

opencc-by-4.0Aug 2024View details →
zenodo36/100

Experiment and analysis data of Study on the Effect of Pore-Clogging Caused by Fenton's Reagent on the Hydraulic Conductivity Using Time-lapsed Hydraulic Tomography

<p>The Microsoft Office Excel data file ('HT data.xlsx') contains two sheets: the first sheet includes the raw data from the first and second HT experiments, labeled as '1st' and '2nd' respectively; the second sheet contains their processed data.</p> <p>The compressed file ('Models.rar') includes all the models, such as the forward and inverse models. Each model contains its own input files and an executable file.</p>

opencc-by-4.0Aug 2024View details →
zenodo36/100

Data used in "Revealing dominant patterns of aerosols regimes in the lower troposphere and their evolution from preindustrial times to the future in global climate model simulations" (Li et al., Atmos. Chem. Phys. 2024)

<p>This dataset contains the processed EMAC simulation used as input to the clustering algorithm and the resulting regimes discussed in Li et al. (<em>Atmos. Chem. Phys.</em>, 2024).</p>

opencc-by-4.0Sep 2024View details →
zenodo36/100

Supporting information for: The Time Requirements for Primary Care Consultations: Initial Sick Child Visits in Low- and Middle-income Countries Using the Integrated Management of Childhood Illness (IMCI) Clinical Algorithm

<p>Few studies have examined the time required for primary care consultations; none have focused on sick child visits in low- and middle-income countries (LMICs). This project begins to fill that gap by providing evidence-based estimates of the time needed for initial visits with under-five infants and children at public or not-for-profit facilities in countries using the Integrated Management of Childhood Illness (IMCI) clinical algorithm.</p> <p>Estimates of the mean expected duration of IMCI consultations require (a) classification profiles, i.e., tabulations of the gold standard health issues presented by patients less than 5 years old; (b) lists of the tasks included in applicable versions of the IMCI algorithm and the conditions that elicit them, and (c) an estimate of the time needed to perform tasks with no pre-defined minimum duration. The latter requires, in addition to classification profiles, information on rates of task performance and the mean observed duration of consultations.</p> <p>The IMCI clinical algorithm and the research surrounding it provide unusually rich sources of such information. Developed in the mid 1990s by the World Health Organization and the United Nations Children&rsquo;s Fund, the IMCI algorithm seeks to reduce child mortality in LMICs by improving the technical quality of primary care services. For infants less than 2 months old, the algorithm focuses on bacterial infections, feeding problems, low weight, and, in some versions, jaundice. For children 2-59 months old, the foci include acute respiratory infections, especially pneumonia; diarrhea; fevers, especially malaria and measles; malnutrition, and anemia. Immunization status is a concern for both age groups. The algorithm provides a scheme to classify the health issues with which infants and children present, an array of tasks providers may be expected perform, and criteria by which tasks are elicited. Research on the design and utility of the algorithm, its effects on provider performance, and related topics furnishes data on the prevalence of gold standard IMCI classifications in a variety of patient populations. In some cases, it also enables one to calculate the time required to perform tasks.</p> <p>I found such information by searching MEDLINE, the database of the International Network for Rational Use of Medicines, the websites of the WHO and its regional offices, GOOGLE, and GOOGLE SCHOLAR using search terms such as &lsquo;Integrated Management of Childhood Illness&rsquo;, &lsquo;observational&rsquo;, &lsquo;prospective&rsquo;, &lsquo;classification&rsquo;, &lsquo;clinical signs&rsquo;, &lsquo;health facility survey&rsquo;, and &lsquo;validity&rsquo;. I also reviewed studies that cited a qualified study and, conversely, material included in the bibliographies of qualified studies.</p> <p>The supplemental information files contain the following:</p> <p>WORKBOOK S1_STUDIES USED</p> <p>Lists features of, and sources for, the studies used to construct classification profiles and to estimate the time required to perform the average task with no predefined minimum duration. With 2 exceptions (see below, DATA S1 and DATA S2), all the studies have been published or are readily available on the internet. None of the data can be used to identify individuals.</p> <p>DATA S1_REPORT OF THE HEALTH FACILITY SURVEY IN BOTSWANA, 2007-08 and DATA S2_REPORT OF THE HEALTH FACILITY SURVEY IN TANZANIA, 2003</p> <p>PDF files of Health Facility Survey reports that were found on the internet but have since been taken down.</p> <p>DATA S3_BURKINA FASO CHART BOOKLET, 2015</p> <p>PDF provided <span>Drs. Sophie Sarrassat (London School of Hygiene and Tropical Medicine) and Serge M. A. Somda (Universit&eacute; Nazi BONI).</span></p> <p>WORKBOOK S2_CLASSIFICATION PROFILES: INFANTS; WORKBOOK S3_CLASSIFICATION PROFILES: CHILDREN IN UPPER MIDDLE-INCOME COUNTRIES; WORKBOOK S4_CLASSIFICATION PROFILES: CHILDREN IN LOWER MIDDLE-INCOME COUNTRIES (I); WORKBOOK S5_CLASSIFICATION PROFILES: CHILDREN IN LOWER MIDDLE-INCOME COUNTRIES (II), and WORKBOOK S6_CLASSIFICATION PROFILES: CHILDREN IN LOW INCOME COUNTRIES&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p> <p>The design of the worksheets in these workbooks is described in TEXT S1_NOTES OF THE CONSTRUCTION OF CLASSIFICATION PROFILES (see below).</p> <p>WORKBOOK S7_IMCI CLINICAL TASKS</p> <p>Lists the clinical tasks provided by relevant IMCI algorithms for the care of infants and children. Consists of 6 worksheets covering mandatory tasks, conditional assessments, and treatment and counseling tasks for infants and children.</p> <p>WORKBOOK S8_MINUTES PER TASK WITH NO MINIMUM DURATION</p> <p>Provides estimate of the mean time required to perform a task with no minimum duration for each of 7 populations for which the required data are available, corrected, where necessary, for the effect of an observer on the rate and pace of task performance. Also provides a geometric mean for all 7 populations.</p> <p>TEXT S1_NOTES ON METHODOLOGY</p> <p>WORD document describing the steps involved in estimating the expected durations of consultations.</p> <p>TEXT S2_NOTES OF THE CONSTRUCTION OF CLASSIFICATION PROFILES</p> <p>WORD document describing the steps involved in constructing each profile, problems encountered, and how they were solved.</p> <p>TEXT S3_NOTES ON THE IDENTIFICATION OF IMCI CLINICAL TASKS</p> <p>WORD document describing the standards used in identifying clinical tasks in IMCI algorithms.</p> <p>TEXT S4_NOTES ON THE ESTIMATION OF MINUTES PER TASK WITH NO MINIMUM DURATION</p> <p>WORD document describing the steps involved in estimating the mean time required to perform a task with no predefined minimum duration, problems encountered, and how they were solved.</p>

opencc-by-4.0Oct 2024View details →
dryad36/100

Data from: Evaluating consumptive and nonconsumptive predator effects on prey density using field times series data

Determining the degree to which predation affects prey abundance in natural communities constitutes a key goal of ecological research. Predators can affect prey through both consumptive effects (CEs) and nonconsumptive effects (NCEs), although the contributions of each mechanism to the density of prey populations remain largely hypothetical in most systems. Common statistical methods applied to time series data cannot elucidate the mechanisms responsible for hypothesized predator effects on prey density (e.g., differentiate CEs from NCEs), nor provide parameters for predictive models. State space models (SSMs) applied to time series data offer a way to meet these goals. Here, we employ SSMs to assess effects of an invasive predatory zooplankter, Bythotrephes longimanus, on an important prey species, Daphnia mendotae, in Lake Michigan. We fit mechanistic models in a SSM framework to seasonal time series (1994-2012) using a recently developed, maximum likelihood-based optimization method, iterated filtering, which can overcome challenges in ecological data (e.g. nonlinearities, measurement error, and irregular sampling intervals). Our results indicate that B. longimanus strongly influences D. mendotae dynamics, with mean annual peak densities of B. longimanus observed in Lake Michigan estimated to cause a 61% reduction in D. mendotae population growth rate and a 59% reduction in peak biomass density. Further, the mechanism underlying the B. longimanus effect is most consistent with an NCE via reduced birth rates. The SSM approach also provided estimates for key biological parameters (e.g., demographic rates) and the contribution of dynamic stochasticity and measurement error. Our study therefore highlights the utility of SSMs to enhance inference for species interactions from time series data. In particular, our findings provide evidence derived directly from survey data that the invasive zooplankter B. longimanus is affecting zooplankton demographics and offer parameter estimates needed to inform predictive models that explore the effect of B. longimanus under different scenarios such as climate change.

opencc-zeroDec 2017View details →
zenodo36/100

Time-Dependent Probabilistic Tsunami Inundation Assessment Using Mode Decomposition to Assess Uncertainty for an Earthquake Scenario

<p>This is the dataset of the manuscript submitted to JGR&nbsp;Ocean (Feb 2021).</p>

opencc-by-4.0May 2021View details →
dryad36/100

Data from: An inexpensive and open-source method to study large terrestrial animal diet and behavior using time-lapse video and GPS

1. The behavior of free-ranging animals is difficult to study, especially on the large spatial and temporal scales relevant to long-lived large species. Animal-borne video and environmental data collection systems (AVEDs) record behavior and other data in real time as animals conduct daily activities. However, few studies have combined systematically collected, long term AVED foraging data with environmental and movement data to test hypotheses on animal foraging. Additionally, AVEDs are often either prohibitively expensive, or require extensive fabrication and programming knowledge. 2. The video and coordinate animal-mounted system (VACAMS) is an animal-mounted data collection system based on a modified GoPro® action camera platform that records short, first "person" perspective videos of animal behavior on an automated time-lapse schedule. As most videos are georeferenced, researchers can return to the locations of specific behaviors and collect accurate, fine-grained data on non-woody vegetation and other habitat characteristics that may influence animal behavior. Moreover, VACAMS are inexpensive and easy to use. 3. This study describes VACAMS preliminary data on cattle foraging and a hypothesis exploring free-ranging cattle browsing habits throughout the rainy season in the tropical dry forest of Sonora, Mexico. I generated a database of vegetation types consumed by cows each month (Annual, Woody, and Leaf litter) and compared actual vegetation type frequencies to a priori assumptions based on seasonal patterns of forage availability. During the monsoons, when palatable vegetation was abundant, frequencies of annual and woody perennial vegetation in cattle diets did not differ from month to month. When the rains ceased and palatable vegetation became scarce, cows switched to leaf litter, dead annual vegetation, twigs, and dried leguminous fruits. 4. Open source software and commercially available hardware make VACAMS financially attainable for many researchers, land managers, students, and other user groups. VACAMS could be used on a range of domestic and semi-domestic free-ranging animals, particularly in dense forests where conventional observations are impossible. With improvements to GPS battery life and durability, the weakest points of the system, VACAMS could also potentially apply to studies of other large terrestrial animals.

opencc-zeroDec 2018View details →
zenodo36/100

A Non-destructive Method to Create a Time Series of Surface Area for Coral Using 3D Photogrammetry (Data)

<p>This is the underlying data for the publication &quot;A Non-destructive Method to Create a Time Series of Surface Area for Coral Using 3D Photogrammetry&quot; by Daniel D Conley and Erin N. R.&nbsp;Hollander published in 2021.</p>

opencc-by-4.0Jul 2021View details →

ScienceDex guides

Understand access before you commit

These curated guides explain access requirements, typical timelines, costs, and reuse considerations for widely used research datasets.

Compare curated 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.

allen-brain-atlas
neuroscienceopenDocumentation, web resources, and API references are available online.
Last verified 2026-04-30Open record

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.

abode-home-cage
behavioral-neuroscienceopenThe DataShare record exposes download links for annotations, documentation, license text, and the zipped per-snippet data directory.
Last verified 2026-04-30Open record

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.

dandi-nwb
electrophysiologyopenPublished Dandiset metadata and archive endpoints are available through the production DANDI API.
Last verified 2026-04-30Open record

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.

ibl
behavioral-neuroscienceopenPublic sessions can be searched and loaded from the IBL public data server through ONE.
Last verified 2026-04-29Open record

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.

openneuro
neuroscienceopenPublished datasets are available on demand over the internet.
Last verified 2026-04-29Open record

ScienceDex for faculty

Your academic CV and NIH biosketch

Make your CV in your school's format and your NIH biosketch from it, then download both as Word files.