Skip to main content
ConductScienceScienceDex
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.

120

datasets available to search

ShareScore release 0.9.0

Reset

Dataset results

120 results for “testing strategy”

Learn how ShareScore rates datasets ↗
zenodo40/100

Simulated Solar Spectra for Testing Stellar Activity Mitigation Strategies

<p>Recent and upcoming stabilized spectrographs are pushing the frontier for &nbsp;Doppler spectroscopy to detect and characterize low-mass planets. &nbsp;Specifications for these instruments are so impressive that intrinsic stellar variability is&nbsp;expected to&nbsp;limit&nbsp;their Doppler precision for most target&nbsp;stars &nbsp;(Fischer et&nbsp;al. &nbsp;2016). &nbsp; In order to realize&nbsp;their full&nbsp;potential, astronomers must develop&nbsp;new&nbsp;strategies for distinguishing true &nbsp;Doppler&nbsp;shifts from&nbsp;intrinsic&nbsp;stellar variability. &nbsp; Stellar&nbsp;variability due to&nbsp;starspots, &nbsp;faculae, and other rotationally-linked variability is particularly concerning, as the stellar rotation period is often included in the range of potential planet orbital periods. &nbsp;In order to robustly detect and accurately characterize low-mass planets via Doppler planet surveys, the exoplanet community must develop statistical models capable of jointly modeling planetary perturbations and intrinsic stellar variability. Towards this effort, we present simulations of extremely high-resolution solar-like spectra created with SOAP 2.0(Dumusque et al. 2014) that includes multiple evolving starspots to aid in developing and testing future statistical methods.</p>

opencc-by-4.0Apr 2020View details →
zenodo40/100

Tensile tests results on artificially aged aluminum-magnesium-silicon alloy blanks subjected to different localized heat treatment strategies

<p>Tensile tests results on artificially aged aluminum-magnesium-silicon alloy blanks subjected to different localized heat treatment strategies&nbsp;</p>

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

Data and Code for the paper "GUI Testing of Android Applications: Investigating the Impact of the Number of Testers on Different Exploratory Testing Strategies"

<p>This package contains data and code to replicate the findings presented in our paper titled &quot;<em>GUI Testing of Android Applications: Investigating the Impact of the Number of Testers on Different Exploratory Testing Strategies</em>&quot;.</p> <p><strong>Abstract</strong></p> <p>Graphical User Interface (GUI) testing plays a pivotal role in ensuring the quality and functionality of mobile apps. In this context, Exploratory Testing (ET), a distinctive methodology in which individual testers pursue a creative, and experience-based approach to test design, is often used as an alternative or in addition to traditional scripted testing. Managing the exploratory testing process is a challenging task, that can easily result either in wasteful spending or in inadequate software quality, due to the relative unpredictability of exploratory testing activities, which depend on the skills and abilities of individual testers. A number of works have investigated the<br> diversity of testers&rsquo; performance when using ET strategies, often in a crowdtesting setting. These works, however, investigated ET effectiveness in detecting bugs, and not in scenarios in which the goal is to generate a re-executable test suite, as well. Moreover, less work has been conducted on evaluating the impact of adopting different exploratory testing strategies. As a first step towards filling this gap in the literature, in this work we conduct an empirical evaluation involving four open-source Android apps and twenty masters students, that we believe can be representative of practitioners partaking in exploratory testing activities. The students were asked to generate test suites for the apps using a Capture and Replay tool and different exploratory testing strategies. We then compare the effectiveness, in terms of aggregate code coverage, that different-sized groups of students using different exploratory testing strategies may achieve. Results provide deeper insights into code coverage dynamics to project managers interested in using exploratory&nbsp; approaches to test simple Android apps, on which they can make more informed decisions.</p> <p>&nbsp;</p> <p><strong>Contents and Instructions</strong></p> <p>This package contains:</p> <ul> <li><strong>apps-under-test.zip</strong> A zip archive containing the source code of the four Android applications we considered in our study, namely MunchLife, TippyTipper, Trolly, and SimplyDo.</li> <li><strong>apps-under-test-instrumented.zip</strong> A zip archive containing the instrumented source code of the four Android applications we used to compute branch coverage.</li> <li><strong>students-test-suites.zip</strong> A zip archive containing the test suites developed by the students using Uninformed Exploratory Testing (referred to as &quot;Black Box&quot; in the subdirectories) and Informed Exploratory Testing (referred to as &quot;White Box&quot; in the subdirectories). This also includes coverage reports.</li> <li><strong>compute-coverage-unions.zip </strong>A zip archive containing Python scripts we developed to compute the aggregate LOC coverage of all possible subsets of students. The scripts have been tested on MS Windows. To compute the LOC coverage achieved by any possible subsets of testers using IET and UET strategies, run the <em>analysisAndReport.py</em> script. To compute the LOC coverage achieved by mixed crowds in which some testers use a U+IET approach and others use a UET approach, run the&nbsp;<em>analysisAndReport_UET_IET_combinations_emma.py</em> script.</li> <li><strong>branch-coverage-computation.zip </strong>A zip archive containing Python scripts we developed to compute the aggregate branch coverage of all considered subsets of students. The scripts have been tested on MS Windows. To compute the branch coverage achieved by any possible subsets of testers using UET and I+UET strategies, run the <em>branch_coverage_analysis.py</em> script. To compute the code coverage achieved by mixed crowds in which some testers use a U+IET approach and others use a UET approach, run the <em>mixed_branch_coverage_analysis.py</em> script.</li> <li><strong>data-analysis-scripts.zip</strong> A zip archive containing R scripts to merge and manipulate coverage data, to carry out statistical analysis and draw plots. All data concerning RQ1 and RQ2 is available as a ready-to-use R data frame in the <em>./data/all_coverage_data.rds</em> file. All data concerning RQ3 is available in the <em>./data/all_mixed_coverage_data.rds </em>file.</li> </ul>

opencc-by-4.0Jun 2023View details →
ClinicalTrials.gov40/100

Combination Partner HIV Testing Strategies for HIV-positive and HIV-negative Pregnant Women

ClinicalTrials.gov study NCT04124536. IPD Sharing: YES. Countries: 1. Publications: 1.

controlledIPD-YESFeb 2026View details →
ClinicalTrials.gov40/100

Testing a Novel Data-to-Suppression (D2S) Intervention Strategy in the Ryan White HIV/AIDS Program

ClinicalTrials.gov study NCT05140421. IPD Sharing: NO. Countries: 1. Publications: 1.

closedIPD-NOFeb 2026View details →
dryad40/100

Data from: Comparing alternative harvest strategies to address robustness to recruitment variability and uncertainty: Implications for Alaska Sablefish tested with management strategy evaluation

Open the record for dataset details and reuse information.

publicOct 2025View details →
zenodo36/100

Search Strategies for Gene Expression Profiling Tests

<p>The dataset includes the complete, reproducible search strategies for all literature databases searched during this project. The Endnote file contain all citations considered for inclusion in the review.</p>

opencc-by-4.0Jul 2022View details →
zenodo36/100

Data for: "Different dry-wet pulses favor different functional strategies: a test using tropical dry forest tree species" by Vega-Ramos, Flor, Cifuentes Gómez, Lucas, Pineda-García, Fernando, Dawson, Todd, Paz, Horacio

<p>These data represent those published in "Different dry-wet pulses favor different functional strategies: a test using tropical dry forest tree species" by Vega-Ramos, Flor, Cifuentes G&oacute;mez, Lucas, Pineda-Garc&iacute;a, Fernando, Dawson, Todd, Paz, Horacio</p>

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

Pilot 1 Model-based decision support for testing drought-related adaptation strategies in the Aa of Weerijs river basin, the Netherlands: Hydrological model description, input data sources and model results

<p>This dataset contains:&nbsp; the report with the description of the model structure, the input data sources and the spatial locations within the catchment for which surface&nbsp; and groundwater results data are provided.</p>

opencc-by-4.0Apr 2024View 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

Testing the Skill-based Approach: Consolidation strategy impacts Attentional Blink performance

<p>Data accompanying the journal article Testing the Skill-based Approach: Consolidation strategy impacts Attentional Blink performance published in PLOS ONE. It contains the datasets (without personal information) for both experiments and a small R file that can be used to read in the data.</p>

opencc-by-4.0Jul 2021View details →
zenodo36/100

Understanding practitioners' strategies to handle test smells: a multi-method study [DATA]

<p>Test smells are poor design and implementation choices that can affect the test code&#39;s understanding and maintainability. Recent studies show the industry is not aware of the test smells concept, while software engineers commonly encounter obstacles to maintain test code. This study investigated test creation and maintenance strategies through developers&#39; perception of eight test smells types. We surveyed 87 software testers and interviewed eight to understand their view on test smells in practice. Our results show that most participants use manual strategies for creating and maintaining test cases. Based on data captured from software testers&#39; perspectives, this study contributes with possible directions and treatments to analyze test smells, seeking to understand how the test affects and potential solutions for test smells.</p>

opencc-by-4.0Jul 2021View details →
ClinicalTrials.gov36/100

Secondary Distribution of HIV Self-tests: an Innovative Strategy for Promoting Partner Testing and Reducing HIV Risk

ClinicalTrials.gov study NCT03135067. IPD Sharing: NO. Countries: 1. Publications: 37.

closedIPD-NOFeb 2026View details →
ClinicalTrials.gov36/100

Developing and Testing an Implementation Strategy for Active Learning to Promote Physical Activity in Children

ClinicalTrials.gov study NCT05048433. IPD Sharing: NO. Countries: 1. Publications: 2.

closedIPD-NOFeb 2026View details →
ClinicalTrials.gov36/100

Developing and Testing Implementation Strategies for Evidence-Based Obesity Prevention in Childcare

ClinicalTrials.gov study NCT03075085. IPD Sharing: NO. Countries: 1. Publications: 31.

closedIPD-NOFeb 2026View details →
ClinicalTrials.gov36/100

Assessing Testing Strategies for Safe Return to K-12 Schools in an Underserved Population

ClinicalTrials.gov study NCT04875520. IPD Sharing: Not stated. Countries: 1. Publications: 10.

restrictedIPD-UNDECIDEDFeb 2026View details →
ClinicalTrials.gov36/100

Self-Test Strategies and Linkage Incentives to Improve ART and PrEP Uptake in Men

ClinicalTrials.gov study NCT04772469. IPD Sharing: NO. Countries: 1. Publications: 101.

closedIPD-NOFeb 2026View details →
ClinicalTrials.gov36/100

Tel-Me-Box: Testing a New, Real-time Strategies for Monitoring HIV Medication Adherence in India

ClinicalTrials.gov study NCT03086655. IPD Sharing: NO. Countries: 1. Publications: 23.

closedIPD-NOFeb 2026View details →
ClinicalTrials.gov36/100

HIV Testing Strategies in the Perinatal Setting

ClinicalTrials.gov study NCT00503308. IPD Sharing: Not stated. Countries: 1. Publications: 16.

restrictedIPD-UNDECIDEDFeb 2026View 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