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.
182
datasets available to search
ShareScore release 0.9.0
Dataset results
182 results for “real-time data”
Data from: Predicting habitat suitability and connectivity for management and conservation of urban wildlife: A real-time web application for grassland water voles
<ol> <li>Natural habitats in urban areas provide benefits for both humans and biodiversity. However, to achieve biodiversity gains we require new techniques to determine habitat suitability and ecological connectivity that will inform urban planning and development.</li> <li>Using an example of an urban population of water voles (<i>Arvicola amphibius</i>) we developed a habitat suitability model and a resistance-surface-based model of landscape connectivity to identify potential connectivity between areas of suitable habitat. We then updated the environmental variables according to new urban development plans and used our models to generate spatially explicit predictions of both habitat suitability and connectivity.</li> <li>To make models accessible to urban and conservation planners we developed an interactive mapping tool that provided users with a graphical user interface (GUI) to inform conservation planning for this species.</li> <li>The model found that habitat suitability for water voles was related to distance from key environmental variables, such as built-up areas and urban green spaces, while the connectivity model identified important corridors connecting areas of potential distribution for this species.</li> <li>Future development plans altered the potential spatial distribution of the water vole population, reducing the extent of suitable habitat in some core areas. The interactive mapping tool made available suitable habitat and connectivity maps for conservation managers to assess new planning applications and for the development of a conservation action plan for water voles.</li> <li>Synthesis and applications: We believe this approach provides a framework for future development of nature conservation tools that can be used by planners to inform ecological decision making, increase biodiversity and reduce human-wildlife conflict in urban environments.</li> </ol>
Data and Source codes for: Real-time Radial Tagging for Quantification of Left Ventricular Torsion
<p> </p> <p>Magnetic Resonance Imaging measurement raw data, simulation, and reconstruction codes used in our paper about ‘Real-time Radial Tagging for Quantification of Left Ventricular Torsion' (DOI:10.1002/mrm.29169).</p> <p> </p> <p> </p> <p> </p>
Code and Data for "Real-time dynamic single-molecule protein sequencing on an integrated semiconductor device"
<p><strong>Code and Data for "Real-time dynamic single-molecule protein sequencing on an integrated semiconductor device".</strong></p> <pre>Code to analyze data produced by the Quantum-Si benchtop device and semiconductor chip is provided in a Python library <strong>qsi_algo</strong> under several submodules: - <strong>rs_caller.py</strong>: Algorithm for calling RS segments (also called ROI segments throughout code). - <strong>rs_caller_controller.py</strong>: Code framework for executing RS calling and property computation in a distributed manner - <strong>rs_properties</strong>: Code for computing properties of identified RS - <strong>rs_classifier</strong>: Algorithms for identifying peptide states (i.e. residue calls) associated with an RS - <strong>utils.py</strong>: shared helper code - <strong>pulse_reader</strong>: reader for binary pulse file - <strong>filters</strong>: ROI and pulse filtering utilities - <strong>plotting</strong>: functions for visualization of data relevant to the analyses presented Jupyter notebooks (<strong>.ipynb</strong>) files are named according to the manuscript figure they are associated with. Analysis code inside uses provided RS (recognition segment) data to demonstrate filtering and residue-calling techniques required to replicate analyses shown in manuscript figures. Please note: several methods rely on randomization for model initialization and/or data sampling which can cause small deviations from equivalent analyses in published figures. The raw data produced from the Quantum-Si benchtop device and semiconductor chip for the assays presented in the accompanying study is presented in a pulse-called binary file format. Pulses can be used as input for RS identification and peptide state identification. Pre-segmented (RS-identified) files are included for convenience. The data contained in the files include: <strong>{run_id}.bin</strong>: Binary format for storing pulse info. The reader provided in <strong>qsi_algo.pulse_reader</strong> produces the following columns: - <strong>aperture_index</strong>: unique aperture index on chip - <strong>start_f</strong>: index of first frame in pulse, counted from the beginning of the run - <strong>end_f</strong>: index of last frame in pulse, counted from the beginning of the run - <strong>dur_f</strong>: duration of pulse in frames - <strong>dur_s</strong>: duration of pulse in seconds - <strong>ipd_f</strong>: interpulse duration in frames (number of frames since end of preceding pulse) - <strong>ipd_s</strong>: interpulse duration in seconds (time in seconds elapsed since end of preceding pulse) - <strong>snr</strong>: signal-to-noise ratio (bin1_intensity / bin1_bg_std) - <strong>intensity</strong>: intensity of pulse (counts above baseline in bin1) - <strong>bin0_intensity</strong>: counts above baseline in bin0 - <strong>intensity_display</strong>: bin1_intensity + bin1_bg_mean - <strong>binratio</strong>: bin0_intensity / bin1_intensity - <strong>bg_mean</strong>: bin1 background mean in region of pulse - <strong>bg_std</strong>: bin1 background standard deviation in region pulse - <strong>bin0_bg_mean</strong>: bin0 background mean in region of pulse - <strong>bin0_bg_std</strong>: bin0 background standard deviation in region pulse <strong>{run_id}.csv.gz</strong>: Compressed comma-separated value file containing RS/ROI properties computed from raw pulses.bin file by included RS caller (example in <strong>rs_caller.py</strong>). - <strong>ap</strong>: unique aperture index on chip - <strong>ROI</strong>: ordinal ROI number in the aperture, 0-indexed - <strong>start_p</strong>: index (.loc) of first pulse in the ROI (inclusive) in pulse dataframe - <strong>end_p</strong>: index (.loc) of last pulse in the ROI (inclusive) in pulse dataframe - <strong>start_f</strong>: first frame of the first pulse in the ROI (inclusive) - <strong>end_f</strong>: Last frame of the last pulse in the ROI (exclusive) - <strong>start_s</strong>: Time (in seconds elapsed from beginning of run) of the start of the ROI - <strong>end_s</strong>: Time (in seconds elapsed from beginning of run) of the end of the ROI - <strong>dur_f</strong>: Duration in frames of the ROI - <strong>dur_s</strong>: Duration in seconds of the ROI - <strong>num_pulses</strong>: Number of pulses in the ROI (that also passed filtering during ROI-calling) - <strong>pw_mean</strong>: Mean pulse duration (in seconds) of pulses in the ROI - <strong>ipd_mean</strong>: Mean inter-pulse duration (in seconds) of pulses in the ROI - <strong>snr_mean</strong>: Mean signal-to-noise ratio of pulses in the ROI - <strong>intensity_mean</strong>: Mean intensity above baseline of pulses in the ROI - <strong>binratio_norm</strong>: Estimated pulse bin ratio of pulses in the ROI, according to the following equation: sum(bin0_intensity*dur_f) / np.sum(bin1_intensity*dur_f) - <strong>ROI_score</strong>: ROI quality score (0-1 from least to most likely to contain recognizer-peptide recognition pulsing) - <strong>binratio_skew</strong>: bin ratio correction factor accounting for binning signal timing differences across the chip. This factor has already been applied to the binratio_norm column</pre>
Supplementary Data: Real-time optimal flood control decision making under uncertainty
<p>The files in this record contain data for real-time optimal flood control decision making and risk propagation under multiple uncertainties considered for publication in Water Resources Research.</p> <p>The files consist of:</p> <ul> <li>Pubugou Reservoir data;</li> <li>Source code and results of the Martingale Model of Forecast Evolution (MMFE);</li> <li>Source code and results of the SMAA-2 model;</li> <li>Source code and results of SMAA-TOPSIS model;</li> <li>Source code and results of the stochastic programming with recourse model.</li> </ul>
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.
Simulations dataset and pre-trained models of "Deep learning in real-time on the astrophysical data obtained from the Čerenkov CTA Observatory" Ph.D. project
<p>Ph.D. project datasets and models release, <br><em>Deep learning in real-time on the astrophysical data obtained from the Čerenkov CTA Observatory.</em></p>
Data supporting "A real-time, scalable, fast and resource-efficient decoder for a quantum computer"
<p>Data includes the circuits (stim_circuits.zip) used to create samples to benchmark CC decoder across different noise rates and code sizes. The resulting accuracy and cycle data is in fpga_accuracy_data.csv. The memory footprint (in KB) of the algorithm for different code sizes is in fpga_memory_data.csv.</p> <p>Weights of syndromes for different noise rates for both phenomenological and circuit-level noise at distance d=23 and d=21 are in noise_rate_sampling_full_d23.csv and noise_rate_sampling_full_d21.csv respectively.</p>
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. "Machine-learning-ready" means that all data-processing methods described in the journal paper have already been applied. 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. 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). However, since `example_io.read_file` is a lightweight wrapper for `xarray.open_dataset`, you can equivalently just use `xarray.open_dataset`. Variables in the table are listed below (the same printout produced by `print(xarray_table)`):</p> <p>Dimensions: (<br> satellite_valid_time_unix_sec: 289,<br> satellite_grid_row: 380,<br> satellite_grid_column: 540,<br> satellite_predictor_name_gridded: 1,<br> satellite_predictor_name_ungridded: 16,<br> ships_valid_time_unix_sec: 19,<br> ships_storm_object_index: 19,<br> ships_forecast_hour: 23,<br> ships_intensity_threshold_m_s01: 21,<br> ships_lag_time_hours: 5,<br> ships_predictor_name_lagged: 17,<br> ships_predictor_name_forecast: 129)<br>Coordinates:<br> * satellite_grid_row (satellite_grid_row) int32 2kB ...<br> * satellite_grid_column (satellite_grid_column) int32 2kB ...<br> * satellite_valid_time_unix_sec (satellite_valid_time_unix_sec) int32 1kB ...<br> * ships_lag_time_hours (ships_lag_time_hours) float64 40B ...<br> * ships_intensity_threshold_m_s01 (ships_intensity_threshold_m_s01) float64 168B ...<br> * ships_forecast_hour (ships_forecast_hour) int32 92B ...<br> * satellite_predictor_name_gridded (satellite_predictor_name_gridded) object 8B ...<br> * satellite_predictor_name_ungridded (satellite_predictor_name_ungridded) object 128B ...<br> * ships_valid_time_unix_sec (ships_valid_time_unix_sec) int32 76B ...<br> * ships_predictor_name_lagged (ships_predictor_name_lagged) object 136B ...<br> * ships_predictor_name_forecast (ships_predictor_name_forecast) object 1kB ...<br>Dimensions without coordinates: ships_storm_object_index<br>Data variables:<br> satellite_number (satellite_valid_time_unix_sec) int32 1kB ...<br> satellite_band_number (satellite_valid_time_unix_sec) int32 1kB ...<br> satellite_band_wavelength_micrometres (satellite_valid_time_unix_sec) float64 2kB ...<br> satellite_longitude_deg_e (satellite_valid_time_unix_sec) float64 2kB ...<br> satellite_cyclone_id_string (satellite_valid_time_unix_sec) |S8 2kB ...<br> satellite_storm_type_string (satellite_valid_time_unix_sec) |S2 578B ...<br> satellite_storm_name (satellite_valid_time_unix_sec) |S10 3kB ...<br> satellite_storm_latitude_deg_n (satellite_valid_time_unix_sec) float64 2kB ...<br> satellite_storm_longitude_deg_e (satellite_valid_time_unix_sec) float64 2kB ...<br> satellite_storm_intensity_number (satellite_valid_time_unix_sec) float64 2kB ...<br> satellite_storm_u_motion_m_s01 (satellite_valid_time_unix_sec) float64 2kB ...<br> satellite_storm_v_motion_m_s01 (satellite_valid_time_unix_sec) float64 2kB ...<br> satellite_predictors_gridded (satellite_valid_time_unix_sec, satellite_grid_row, satellite_grid_column, satellite_predictor_name_gridded) float64 474MB ...<br> satellite_grid_latitude_deg_n (satellite_valid_time_unix_sec, satellite_grid_row, satellite_grid_column) float64 474MB ...<br> satellite_grid_longitude_deg_e (satellite_valid_time_unix_sec, satellite_grid_row, satellite_grid_column) float64 474MB ...<br> satellite_predictors_ungridded (satellite_valid_time_unix_sec, satellite_predictor_name_ungridded) float64 37kB ...<br> ships_storm_intensity_m_s01 (ships_valid_time_unix_sec) float64 152B ...<br> ships_storm_type_enum (ships_storm_object_index, ships_forecast_hour) int32 2kB ...<br> ships_forecast_latitude_deg_n (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_forecast_longitude_deg_e (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_v_wind_200mb_0to500km_m_s01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_vorticity_850mb_0to1000km_s01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_vortex_latitude_deg_n (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_vortex_longitude_deg_e (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_mean_tangential_wind_850mb_0to600km_m_s01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_max_tangential_wind_850mb_m_s01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_mean_tangential_wind_1000mb_at500km_m_s01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_mean_tangential_wind_850mb_at500km_m_s01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_mean_tangential_wind_500mb_at500km_m_s01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_mean_tangential_wind_300mb_at500km_m_s01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_srh_1000to700mb_200to800km_j_kg01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_srh_1000to500mb_200to800km_j_kg01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_threshold_exceedance_num_6hour_periods (ships_storm_object_index, ships_intensity_threshold_m_s01) int32 2kB ...<br> ships_v_motion_observed_m_s01 (ships_storm_object_index) float64 152B ...<br> ships_v_motion_1000to100mb_flow_m_s01 (ships_storm_object_index) float64 152B ...<br> ships_v_motion_optimal_flow_m_s01 (ships_storm_object_index) float64 152B ...<br> ships_cyclone_id_string (ships_storm_object_index) object 152B ...<br> ships_storm_latitude_deg_n (ships_storm_object_index) float64 152B ...<br> ships_storm_longitude_deg_e (ships_storm_object_index) float64 152B ...<br> ships_predictors_lagged (ships_valid_time_unix_sec, ships_lag_time_hours, ships_predictor_name_lagged) float64 13kB ...<br> ships_predictors_forecast (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. 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. 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. The only lag time we use in machine learning is "NaN", which is a stand-in for the best available of all lag times. 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. 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). 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. For example, "m_s01" = metres per second; "deg_n" = degrees north; "deg_e" = degrees east; "j_kg01" = Joules per kilogram; ...; etc.</li> </ul>
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. "Machine-learning-ready" means that all data-processing methods described in the journal paper have already been applied. 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. 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). However, since `example_io.read_file` is a lightweight wrapper for `xarray.open_dataset`, you can equivalently just use `xarray.open_dataset`. Variables in the table are listed below (the same printout produced by `print(xarray_table)`):</p> <p>Dimensions: (<br> satellite_valid_time_unix_sec: 289,<br> satellite_grid_row: 380,<br> satellite_grid_column: 540,<br> satellite_predictor_name_gridded: 1,<br> satellite_predictor_name_ungridded: 16,<br> ships_valid_time_unix_sec: 19,<br> ships_storm_object_index: 19,<br> ships_forecast_hour: 23,<br> ships_intensity_threshold_m_s01: 21,<br> ships_lag_time_hours: 5,<br> ships_predictor_name_lagged: 17,<br> ships_predictor_name_forecast: 129)<br>Coordinates:<br> * satellite_grid_row (satellite_grid_row) int32 2kB ...<br> * satellite_grid_column (satellite_grid_column) int32 2kB ...<br> * satellite_valid_time_unix_sec (satellite_valid_time_unix_sec) int32 1kB ...<br> * ships_lag_time_hours (ships_lag_time_hours) float64 40B ...<br> * ships_intensity_threshold_m_s01 (ships_intensity_threshold_m_s01) float64 168B ...<br> * ships_forecast_hour (ships_forecast_hour) int32 92B ...<br> * satellite_predictor_name_gridded (satellite_predictor_name_gridded) object 8B ...<br> * satellite_predictor_name_ungridded (satellite_predictor_name_ungridded) object 128B ...<br> * ships_valid_time_unix_sec (ships_valid_time_unix_sec) int32 76B ...<br> * ships_predictor_name_lagged (ships_predictor_name_lagged) object 136B ...<br> * ships_predictor_name_forecast (ships_predictor_name_forecast) object 1kB ...<br>Dimensions without coordinates: ships_storm_object_index<br>Data variables:<br> satellite_number (satellite_valid_time_unix_sec) int32 1kB ...<br> satellite_band_number (satellite_valid_time_unix_sec) int32 1kB ...<br> satellite_band_wavelength_micrometres (satellite_valid_time_unix_sec) float64 2kB ...<br> satellite_longitude_deg_e (satellite_valid_time_unix_sec) float64 2kB ...<br> satellite_cyclone_id_string (satellite_valid_time_unix_sec) |S8 2kB ...<br> satellite_storm_type_string (satellite_valid_time_unix_sec) |S2 578B ...<br> satellite_storm_name (satellite_valid_time_unix_sec) |S10 3kB ...<br> satellite_storm_latitude_deg_n (satellite_valid_time_unix_sec) float64 2kB ...<br> satellite_storm_longitude_deg_e (satellite_valid_time_unix_sec) float64 2kB ...<br> satellite_storm_intensity_number (satellite_valid_time_unix_sec) float64 2kB ...<br> satellite_storm_u_motion_m_s01 (satellite_valid_time_unix_sec) float64 2kB ...<br> satellite_storm_v_motion_m_s01 (satellite_valid_time_unix_sec) float64 2kB ...<br> satellite_predictors_gridded (satellite_valid_time_unix_sec, satellite_grid_row, satellite_grid_column, satellite_predictor_name_gridded) float64 474MB ...<br> satellite_grid_latitude_deg_n (satellite_valid_time_unix_sec, satellite_grid_row, satellite_grid_column) float64 474MB ...<br> satellite_grid_longitude_deg_e (satellite_valid_time_unix_sec, satellite_grid_row, satellite_grid_column) float64 474MB ...<br> satellite_predictors_ungridded (satellite_valid_time_unix_sec, satellite_predictor_name_ungridded) float64 37kB ...<br> ships_storm_intensity_m_s01 (ships_valid_time_unix_sec) float64 152B ...<br> ships_storm_type_enum (ships_storm_object_index, ships_forecast_hour) int32 2kB ...<br> ships_forecast_latitude_deg_n (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_forecast_longitude_deg_e (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_v_wind_200mb_0to500km_m_s01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_vorticity_850mb_0to1000km_s01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_vortex_latitude_deg_n (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_vortex_longitude_deg_e (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_mean_tangential_wind_850mb_0to600km_m_s01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_max_tangential_wind_850mb_m_s01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_mean_tangential_wind_1000mb_at500km_m_s01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_mean_tangential_wind_850mb_at500km_m_s01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_mean_tangential_wind_500mb_at500km_m_s01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_mean_tangential_wind_300mb_at500km_m_s01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_srh_1000to700mb_200to800km_j_kg01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_srh_1000to500mb_200to800km_j_kg01 (ships_storm_object_index, ships_forecast_hour) float64 3kB ...<br> ships_threshold_exceedance_num_6hour_periods (ships_storm_object_index, ships_intensity_threshold_m_s01) int32 2kB ...<br> ships_v_motion_observed_m_s01 (ships_storm_object_index) float64 152B ...<br> ships_v_motion_1000to100mb_flow_m_s01 (ships_storm_object_index) float64 152B ...<br> ships_v_motion_optimal_flow_m_s01 (ships_storm_object_index) float64 152B ...<br> ships_cyclone_id_string (ships_storm_object_index) object 152B ...<br> ships_storm_latitude_deg_n (ships_storm_object_index) float64 152B ...<br> ships_storm_longitude_deg_e (ships_storm_object_index) float64 152B ...<br> ships_predictors_lagged (ships_valid_time_unix_sec, ships_lag_time_hours, ships_predictor_name_lagged) float64 13kB ...<br> ships_predictors_forecast (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. 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. 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. The only lag time we use in machine learning is "NaN", which is a stand-in for the best available of all lag times. 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. 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). 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. For example, "m_s01" = metres per second; "deg_n" = degrees north; "deg_e" = degrees east; "j_kg01" = Joules per kilogram; ...; etc.</li> </ul>
dhaw/fluCodeImperial: Using real-time data to guide decision-making during an influenza pandemic: a modelling analysis
<p><strong>All codes and data used for "Using real-time data to guide decision-making during an influenza pandemic: a modelling analysis" are included in this folder. The file "runExamples.m" contains a step-by-step method for reproducing figures and running model fits. Ensure that all data and code files are in the same directory, then a single execution of “runExamples” on the command line will generate all main and supplementary figures in the manuscript. There is one line of code per figure, clearly marked, that can be commented out as desired. In order to run the MCMC adaptive algorithm, a single line of code, also clearly marked, must be commented back in. Instructions to change the single-state example are given at the top of the file “runExamples.m”. The saved state selection of California (“state=1”) is consistent with all results presented in the manuscript. </strong></p> <p><strong> </strong></p> <p><strong>Plots make use of files from the following sources, with some modifications:</strong></p> <p><strong>Holger Hoffmann (2022). Violin Plot (https://www.mathworks.com/matlabcentral/fileexchange/45134-violin-plot);</strong></p> <p><strong>Evan (2022). Plot Groups of Stacked Bars (https://www.mathworks.com/matlabcentral/fileexchange/32884-plot-groups-of-stacked-bars);</strong></p> <p><strong>John Onofrey (2022). Shaded Plots and Statistical Distribution Visualizations (https://www.mathworks.com/matlabcentral/fileexchange/69203-shaded-plots-and-statistical-distribution-visualizations)</strong></p>
Incorporating real-time traffic data into air quality mapping uncovers more severe exposure disparities at the community level
<p>Data and codes for the XGBoost model training in our manuscript titled "Incorporating real-time traffic data into air quality mapping uncovers more severe exposure disparities at the community level"</p>
Real-Time Delphi data: How to identify and interpret weak signals of change in the forest bioeconomy
<p>Data from: Mauno, T., Catelo, F., Bengston, D.N., Pykäläinen, J. & Hujala, T. 2023. How to identify and interpret weak signals of change in the forest bioeconomy. Forest Policy and Economics. <a href="https://doi.org/10.1016/j.forpol.2023.103075?_gl=1*a2eeob*_ga*NDE0MDgzOTYwLjE2OTY0ODY2MTY.*_ga_NY8L5SJPMB*MTY5NjQ5NDIxNi4yLjEuMTY5NjUwMTI0Mi4wLjAuMA..">https://doi.org/10.1016/j.forpol.2023.103075</a></p> <p>This exploratory study sought to understand how to identify and interpret weak signals of change that may have an impact on the forest bioeconomy. An international panel of experts in the forest bioeconomy and in foresight provided their views through a two-stage Real-Time Delphi method which utilized the multiple rounds of traditional Delphi and the instantaneous feedback of the Real-Time Delphi method.</p> <p>The Real-Time Delphi exercise was conducted in two stages through the eDelphi software (edelphi.org); the first stage was focused on <em>Changes</em> and the second on <em>Weak Signals</em>. For the Real-Time Delphi exercise, two expert matrices (forest bioeconomy matrix and futures & foresight matrix) were prepared with the aim of obtaining diverse expertise to participate in the study.</p> <p>The first stage was conducted during a 10-day period in early September 2022 (Sep 5, 2022 – Sep 14, 2022). The second stage was also conducted during a 10-day period later in September 2022 (Sep 21, 2022 – Sep 30, 2022). A total of 11 (6 forest bioeconomy experts and 5 futures research and foresight specialists) participated in both eDelphi stages.</p> <p>This dataset includes: (i) completed Real-Time Delphi stages (including anonymized answers and discussions of 11 participants) (ii) questions for both Real-Time Delphi stages, and (iii) anonymized expert matrices (forest bioeconomy matrix and futures & foresight matrix)</p> <p>For more information, please contact the corresponding author (data controller): Tuomas Mauno (University of Eastern Finland), tuomas.mauno@uef.fi</p>
Data from: Predicting habitat suitability and connectivity for management and conservation of urban wildlife: A real-time web application for grassland water voles
Open the record for dataset details and reuse information.
Data from: Real-time imaging of rotation during synthesis by the replisome
Open the record for dataset details and reuse information.
Data from quantitative real-time PCR of corticotropin-releasing hormone and glucocorticoid receptor in the hippocampus and hypothalamus of rats subjected to midline fluid percussion injury or control sham surgery.
<p>These files contain all data from quantitative real-time PCR of corticotropin-releasing hormone (CRH) and glucocorticoid receptor (GR) measured in the hippocampus and hypothalamus of male and female rats. Rats were randomly assigned to a treatment group before the initiation of the study. Rats received a control sham surgery or were subjected to midline fluid percussion injury to induce a diffuse traumatic brain injury. Tissue biopsies were collected at 7 days post-injury and analyzed via quantitative real-time PCR. </p> <p> </p>
Data and Scripts for "Real-Time Time-Dependent Density Functional Theory Implementation of Electronic Circular Dichroism Applied to Nanoscale Metal-Organic Clusters"
<p>The xyz files were used for the ECD calculation in the paper :https://arxiv.org/abs/2007.08560<br> gsrun.py: ground-state calculation<br> td_calc.py: time -propagation for ECD<br> cdspecX.py: get rotatory strength for plotting</p>
Data from: Real-time quantification of damage in structural materials during mechanical testing
A novel methodology is introduced for quantifying the severity and morphology of damage created during testing in composite components. The method utilises digital image correlation combined with image processing techniques to monitor the rate at which the strain field changes during mechanical tests. The methodology is demonstrated using two distinct experimental datasets, a ceramic matrix composite specimen loaded in tension at high temperature and nine polymer matrix composite specimens containing fibre-waviness defects loaded in bending. The changes in the strain field due to damage creation are shown to be a more effective indicator that the specimen has reached its proportional limit than using load-extension diagrams. The technique also introduces a new approach to using experimental data for creating maps showing the spatio-temporal distribution of damage in a component. These maps indicate where damage occurs in a component, its morphology and the time of occurrence. This presentation format is both easier and faster to interpret than the raw data which, for some tests, can consist of tens of thousands of images. This methodology has the potential to reduce the time taken to interpret large material test datasets whilst increasing the amount of knowledge that can be extracted from each test.
Data from: Real-time assessment of hybridization between wolves and dogs: combining non-invasive samples with ancestry informative markers
Wolves and dogs provide a paradigmatic example of the ecological and conservation implications of hybridization events between wild and domesticated forms. However, our understanding of such implications has been traditionally hampered by both high genetic similarity and the difficulties in obtaining tissue samples (TS), which limit our ability to assess ongoing hybridization events. To assess the occurrence and extension of hybridization in a pack of wolf-dog hybrids in Northwestern Iberia, we compared the power of 52 nuclear markers implemented on TS with a subset of 13 ancestry informative markers (AIMs) typed in non-invasive samples (NIS). We demonstrate that the 13 AIMs are as accurate as the 52 markers that were chosen without regard to the power to differentiate between wolves and dogs, also having the advantage of being rapidly screened on NIS. The efficiency of AIMs significantly outperformed ten random sets of similar size and an additional commercial set of 18 markers. Bayesian clustering analysis implemented on AIMs and NIS identified nine hybrids, two wolves and two dogs. Four hybrids were unambiguously assigned to F1xWolf backcrosses. Our approach (AIMs + NIS) overcomes previous difficulties related to sample availability and informative power of markers, allowing a quick identification of wolf-dog hybrids in the first phases of hybridization episodes. This provides managers with a reliable tool to evaluate hybridization, and estimate the success of their actions. This approach may be easily adapted for other pairs of wild/domesticated species, thus improving our understanding of the introgression of domestication genes into natural populations.
Data from: Utility of real-time shear wave elastography in the assessment of testicular torsion
Real-time shear-wave elastography (SWE) is a newly developed method which can obtain the stiffness of tissues and organs based on tracking of shear wave propagation through a structure. Several studies have demonstrated its potential in the differentiation between diseased and normal tissue in clinical practices, however the applicability to testicular disease has not been well elucidated. We investigated the feasibility and reproducibility of SWE in the detection of testicular torsion. This prospective study comprised 15 patients with complete testicular torsion. Results obtained from SWE along with conventional gray-scale and color Doppler sonography and post-operative pathology were compared. The results revealed that (i) the size of injured testis was increased and the twisted testis parenchyma was heterogeneous. The blood flow signals in injured testis were barely visible or absent; (ii) The Young's modulus, including Emean, Emax, Emin and SD values in the border area of torsional testis were higher than those of normal testis (Emean, 78.07±9.01kPa vs 22.0±5.10kPa; Emax,94.07±6.53kPa vs 27.87±5.78kPa; Emin, 60.73±7.84 kPa vs 18.90±4.39kPa; SD, 7.67±0.60 kPa vs 2.30±0.36 kPa, [P<0.05]); The Emax and SD values in the central area of the torsional testis were higher than the corresponding area of the normal testis (Emax, 8.23±0.30 kPa vs 3.97±0.95kPa; SD, 1.5±0.26kPa vs 0.67±0.35kPa,[P<0.05]) and Emin values was lower than those of normal testicles(0.93±0.51kPa vs 1.6±0.36kPa; [P<0.05]); (iii) The Young's modulus measurement between two physicians showed good agreement. The pathological findings were accordance with SWE measurement. SWE is a non-invasive, convenient and high reproducible method and may serve as an important alternative tool in the diagnosis and monitoring the progression of the acute scrotums, in additional to conventional Doppler sonography.
Data from: Persistent near real-time passive acoustic monitoring for baleen whales from a moored buoy: system description and evaluation
1. Managing interactions between human activities and marine mammals often relies on an understanding of the real-time distribution or occurrence of animals. Visual surveys typically cannot provide persistent monitoring because of expense and weather limitations, and while passive acoustic recorders can monitor continuously, the data they collect are often not accessible until the recorder is recovered. 2. We have developed a moored passive acoustic monitoring system that provides near real-time occurrence estimates for humpback, sei, fin, and North Atlantic right whales from a single site for a year, and makes those occurrence estimates available via a publicly accessible website, email and text messages, a smartphone/tablet app, and the U.S. Coast Guard's maritime domain awareness software. We evaluated this system using a buoy deployed off the coast of Massachusetts during 2015-2016 and redeployed again during 2016-2017. Near real-time estimates of whale occurrence were compared to simultaneously collected archived audio as well as whale sightings collected near the buoy by aerial surveys. 3. False detection rates for right, humpback, and sei whales were 0% and nearly 0% for fin whales, while missed detection rates at daily time scales were modest (12-42%). Missed detections were significantly associated with low calling rates for all species. We observed strong associations between right whale visual sightings and near real-time acoustic detections over a monitoring range of 30-40 km and temporal scales of 24-48 hours, suggesting that silent animals were not especially problematic for estimating occurrence of right whales in the study area. There was no association between acoustic detections and visual sightings of humpback whales. 4. The moored buoy has been used to reduce the risk of ship strikes for right whales in a U.S. Coast Guard gunnery range, and can be applied to other mitigation applications.
ScienceDex guides
Understand access before you commit
These curated guides explain access requirements, typical timelines, costs, and reuse considerations for widely used research datasets.
Allen Brain Atlas
Allen Brain Atlas is an Allen Institute collection of brain map atlases, datasets, APIs, and analysis tools covering mouse, human, and non-human primate brain resources.
Annotated Behaviour and Observability Dataset (ABODe)
ABODe is a University of Edinburgh DataShare dataset for behavior classification in group-housed mice using home-cage video, identities, bounding boxes, ground-plate positions, and annotator labels.
DANDI Archive for NWB datasets
DANDI is a BRAIN Initiative archive for publishing and sharing neurophysiology data, including electrophysiology, optophysiology, and behavioral data packaged as NWB and related standards.
International Brain Laboratory public data
The International Brain Laboratory public data releases expose standardized mouse decision-making experiments, including Neuropixels recordings, widefield calcium imaging, behavior, and session metadata accessed through the ONE API.
OpenNeuro
OpenNeuro is a free, open platform for sharing neuroimaging datasets, with public search, dataset pages, and download paths for web, S3, DataLad, and the OpenNeuro CLI.