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.
105
datasets available to search
ShareScore release 0.9.0
Dataset results
105 results for “AIS data”
Synthetic Datasets for "Binary Classification Optimisation with AI-Generated Data"
<p>Images of melanomas and Basal Cell Carcinoma generated with a stylegan2. Dataset corresponding to the article "Binary Classification Optimisation with AI-Generated Data"</p>
JuniperMapper: AI for Shrub Delineation (DATA)
<p>JuniperMapper is a dataset created to individually delineate <em>Juniperus</em> shrubs from satellite images using deep learning models. This data contains two types of datasets collected from the national park of Sierra Nevada, Spain:</p> <ol> <li>Photo Interpreted (PI) data: manually created by experts using a visual inspection of satellite images.</li> <li>Field Work (FW) data: manually created by experts using an in-situ inspection.</li> </ol> <p>Both datasets contain a set of RGB input images (.tif) at 13 cm resolution downloaded from Google Earth satellites, and their corresponding annotations (shapefiles) delineating each shrub. In addition, a .json file following the COCO dataset structure is also provided to train deep learning models.</p> <p>The PI dataset can be used to develop the deep learning model. It is already partitioned into Train, Validation, and Test sets. While the FW dataset can be used to perform the external validation of the model.</p>
Datasets and scripts related to the paper: "*Can Generative AI Help us in Open Coding of Software Engineering Data?*"
<p>This replication package contains datasets and scripts related to the paper: "<em>Can Generative AI Help us in Open Coding of Software Engineering Data?</em>"</p> <p>The replication package is organized into two directories:</p> <ul> <li> <p><code>manual_analysis</code>: This directory contains all sheets used to perform the manual analysis for RQ1, RQ2, and RQ3.</p> </li> <li> <p><code>stats</code>: This directory contains all datasets, scripts, and results metrics used for the quantitative analyses of RQ1 and RQ2.</p> </li> </ul> <p>In the following, we describe the content of each directory:</p> <h2>manual_analysis</h2> <ul> <li> <p><code>manual_analysis_rq1</code>: This directory contains all sheets used to perform manual analysis for RQ1 (independent and incremental coding).</p> <ul> <li> <p>The sub-directory <code>incremental_coding</code> contains .csv files for all datasets (<code>DL_Faults_COMMIT_incremental.csv</code>, <code>DL_Faults_ISSUE_incremental.csv</code>, <code>DL_Fault_SO_incremental.csv</code>, <code>DRL_Challenges_incremental.csv</code> and <code>Functional_incremental.csv</code>). All these .csv files contain the following columns:</p> <ul> <li><em>Link</em>: The link to the instances</li> <li><em>Prompt</em>: Prompt used as input to GPT-4-Turbo</li> <li><em>ID</em>: Instance ID</li> <li><em>FinalTag</em>: Tag assigned by the human in the original paper</li> <li><em>Chatgpt_output_memory</em>: Output of GPT-4-Turbo with incremental coding</li> <li><em>Chatgpt_output_memory_clean</em>: (only for the DL Faults datasets) output of GPT-4-Turbo considering only the label assigned, excluding the text</li> <li><em>Author1</em>: Label assigned by the first author</li> <li><em>Author2</em>: Label assigned by the second author</li> <li><em>FinalOutput</em>: Label assigned after the resolution of the conflicts</li> </ul> </li> <li> <p>The sub-directory <code>independent_coding</code> contains .csv files for all datasets (<code>DL_Faults_COMMIT_independent.csv</code>, <code>DL_Faults_ISSUE_ independent.csv</code>, <code>DL_Fault_SO_ independent.csv</code>, <code>DRL_Challenges_ independent.csv</code> and <code>Functional_ independent.csv</code>), containing the following columns:</p> <ul> <li><em>Link</em>: The link to the instances</li> <li><em>Prompt</em>: Prompt used as input to GPT-4-Turbo</li> <li><em>ID</em>: Specific ID for the instance</li> <li><em>FinalTag</em>: Tag assigned by the human in the original paper</li> <li><em>Chatgpt_output</em>: Output of GPT-4-Turbo with independent coding</li> <li><em>Chatgpt_output_clean</em>: (only for DL Faults datasets) output of GPT-4-Turbo considering only the label assigned, excluding the text</li> <li><em>Author1</em>: Label assigned by the first author</li> <li><em>Author2</em>: Label assigned by the second author</li> <li><em>FinalOutput</em>: Label assigned after the resolution of the conflicts.</li> </ul> </li> <li> <p>Also, the sub-directory contains sheets with inconsistencies after resolving conflicts. The directory <code>inconsistency_incremental_coding</code> contains .csv files with the following columns:</p> <ul> <li><em>Dataset</em>: The dataset considered</li> <li><em>Human</em>: The label assigned by the human in the original paper</li> <li><em>Machine</em>: The label assigned by GPT-4-Turbo</li> <li><em>Classification</em>: The final label assigned by the authors after resolving the conflicts. Multiple classifications for a single instance are separated by a comma “,”</li> <li><em>Final</em>: final label assigned after the resolution of the incompatibilities</li> </ul> </li> <li> <p>Similarly, the sub-directory <code>inconsistency_independent_coding</code> contains a .csv file with the same columns as before, but this is for the case of independent coding.</p> </li> </ul> </li> <li> <p><code>manual_analysis_rq2</code>: This directory contains .csv files for all datasets (<code>DL_Faults_redundant_tag.csv</code>, <code>DRL_Challenges_redundant_tag.csv</code>, <code>Functional_redundant_tag.csv</code>) to perform manual analysis for RQ2.</p> <ul> <li> <p>The <code>DL_Faults_redundant_tag.csv</code> file contains the following columns:</p> <ul> <li><em>Tags Redundant</em>: tags identified as redundant by GPT-4-Turbo</li> <li><em>Matched</em>: inspection by the authors to see if the tags are redundant matching or not</li> <li><em>FinalTag</em>: final tag assigned by the authors after the resolution of the conflict</li> </ul> </li> <li> <p>The <code>Functional_redundant_tag.csv</code> file contains the same columns as before</p> </li> <li> <p>The <code>DRL_Challenges_redundant_tag.csv</code> file is organized as follows:</p> <ul> <li><em>Tags Suggested</em>: The final tag suggested by GPT-4-Turbo</li> <li><em>Tags Redundant</em>: tags identified as redundant by GPT-4-Turbo</li> <li><em>Matched</em>: inspection by the authors to see if the tags redundant matching or not with the tags suggested</li> <li><em>FinalTag</em>: final tag assigned by the authors after the resolution of the conflict</li> </ul> </li> <li> <p>The sub-directory <code>code_consolidation_mapping_overview</code> contains .csv files (<code>DL_Faults_rq2_overview.csv</code>, <code>DRL_Challenges_rq2_overview.csv</code>, <code>Functional_rq2_overview.csv</code>) organized as follows:</p> <ul> <li><em>Initial_Tags</em>: list of the unique initial tags assigned by GPT-4-Turbo for each dataset</li> <li><em>Mapped_tags</em>: list of tags mapped by GPT-4-Turbo</li> <li><em>Unmatched_tags</em>: list of unmatched tags by GPT-4-Turbo</li> <li><em>Aggregating_tags</em>: list of consolidated tags</li> <li><em>Final_tags</em>: list of final tags after the consolidation task</li> </ul> </li> </ul> </li> <li> <p><code>prompt_for_each_rq</code>: This directory contains: - (i) the history of prompts used in each dataset (<code>prompts_history.txt</code>) -(ii) all final prompt used for the analysis of each dataset, prompt used for incremental coding, prompt used in rq2 to consolidate redundant codes, prompt used in rq3 to create taxonomy (<code>generic_prompt.txt</code>) -(iii) all .csv files in which there are indicate, for each dataset, the link and the prompt used (<code>prompt_DL_Faults_COMMIT.csv</code>, <code>prompt_DL_Faults_ISSUE.csv</code>, <code>prompt_DL_Faults_SO.csv</code>, <code>prompt_DRL_Challenges.csv</code>). For the Functional Dataset .csv file contains, instead, Question, Answer and Prompt used (<code>prompt_Functional.csv</code>)</p> </li> <li> <p><code>rq3</code>: This directory contains the taxonomies obtained from GPT-4-Turbo for the DL Faults and for the DRL Challenges (<code>taxonomy_DL_Faults.txt</code>,<code>taxonomy_DRL_Challenges.txt</code>)</p> </li> </ul> <h2>stats</h2> <ul> <li> <p><code>RQ1</code>: contains script and datasets used to perform metrics for RQ1. The analysis calculates all possible combinations between Matched, More Abstract, More Specific, and Unmatched.</p> <ul> <li><code>RQ1_Stats.ipynb</code> is a Python Jupyter nooteook to compute the RQ1 metrics. To use it, as explained in the notebook, it is necessary to change the values of variables contained in the first code block.</li> <li><code>independent-prompting</code>: Contains the datasets related to the independent prompting. Each line contains the following fields: <ul> <li><em>Link</em>: Link to the artifact being tagged</li> <li><em>Prompt</em>: Prompt sent to GPT-4-Turbo</li> <li><em>FinalTag</em>: Artifact coding from the replicated study</li> <li><em>chatgpt_output_text</em>: GPT-4-Turbo output</li> <li><em>chatgpt_output</em>: Codes parsed from the GPT-4-Turbo output</li> <li><em>Author1</em>: Annotator 1 evaluation of the coding</li> <li><em>Author2</em>: Annotator 2 evaluation of the coding</li> <li><em>FinalOutput</em>: Consolidated evaluation</li> </ul> </li> <li><code>incremental-prompting</code>: Contains the datasets related to the incremental prompting (same format as independent prompting)</li> <li><code>results</code>: contains files for the RQ1 quantitative results. The files are named <code>RQ1\_<<Dataset>>\_<<Prompt method>>\_<<ExcludingNegative>>\_<<MetricAggregation>>.csv</code>, where <em>Dataset</em> is the dataset name, <em>Prompt method</em> indicates whether results are for independent or incremental prompting, <em>Excluding Negatives</em> (for datasets where this applies) whether results have been obtained by excluding negative instances, and <em>MetricAggregation</em> (where it applies) how metrics have been aggregated (macro or weighted average). The files report columns indicating the <em>Dataset</em>, the <em>Matching type</em>, the <em>Accuracy</em>, <em>Precision</em>, <em>Recall</em>, <em>F1 Score</em>, and <em>Cohen's Kappa</em>.</li> </ul> </li> <li> <p><code>RQ2</code>: contains the script used to perform metrics for RQ2, the datasets it uses, and its output.</p> <ul> <li><code>RQ2_SetStats.ipynb</code> is the Python Jupyter notebook to perform the analyses. The scripts takes as input the following types of files, contained in the directory contains the script used to perform the metrics for RQ2. The script takes in input:</li> <li>RQ1 Data Files (<code>RQ1_DLFaults_Issues.csv</code>, <code>RQ1_DLFaults_Commits.csv</code>, and <code>RQ1_DLFaults_SO.csv</code>, joined in a single .csv <code>RQ1_DLFaults.csv</code>). These are the same files used in RQ1.</li> <li>Mapping Files (<code>RQ2_Mappings_DRL.csv</code>, <code>RQ2_Mappings_Functional.csv</code>, <code>RQ2_Mappings_DLFaults.csv</code>). These contain the mappings between human tags (<em>HumanTags</em>), GPT-4-Turbo tags (<em>Final Tags</em>), with indicated the type of matching (<em>MatchType</em>).</li> <li>Additional codes creating during the consolidation (<code>RQ2_newCodes_DRL.csv</code>, <code>RQ2_newCodes_Functional.csv</code>, <code>RQ2_newCodes_DLFaults.csv</code>), annotated with the matching: <em>new code</em>,<em>old code</em>,<em>human code</em>,<em>match type</em></li> <li>Set files (<code>RQ2_Sets_DRL.csv</code>, <code>RQ2_Sets_Functional.csv</code>, <code>RQ2_Sets_DLFaults.csv</code>). Each file contains the following columns: <ul> <li><em>HumanTags</em>: List of tags from the original dataset</li> <li><em>InitialTags</em>: Set of tags from RQ1,</li> <li><em>ConsolidatedTags</em>: Tags that have been consolidated,</li> <li><em>FinalTags</em>: Final set of tags (results of RQ2, used in RQ3)</li> <li><em>NewTags</em>: New tags created during consolidation</li> </ul> </li> <li><code>RQ2_Set_Metrics.csv</code>: Reports the RQ2 output metrics (Precision, Recall, F1-Score, Jaccard).</li> </ul> </li> </ul>
Data for study "AI-Driven Facial Emotion Analysis for Customer Emotion Recognition - an explanatory study".
<p>This study aims to determine whether it is possible to use a commercial tool like Morphcast SDK AI to identify images that evoke more positive emotions, and thus contribute to a better perception of the hotel facility by customers, and whether it is possible to identify common elements of these photographs. The dataset was collected using Morphcast SDK AI with users.</p>
[Supplementary Data] PowerModel-AI: A First On-the-fly Machine-Learning Predictor for AC Power Flow Solutions.
<h1><strong>Abstract</strong></h1> <p>The real-time creation of machine-learning models via active or on-the-fly learning has attracted considerable interest across various scientific and engineering disciplines. These algorithms enable machines to autonomously build models while remaining operational. Through a series of query strategies, the machine can evaluate whether newly encountered data fall outside the scope of the existing training set. In this study, we introduce <em>PowerModel-AI</em>, an end-to-end machine learning software designed to accurately predict AC power flow solutions. We present detailed justifications for our model design choices and demonstrate that selecting the right input features effectively captures the load flow decoupling inherent in power flow equations. Our approach incorporates on-the-fly learning, where power flow calculations are initiated only when the machine detects a need to improve the dataset in regions where the model's performance is sub-optimal, based on specific criteria. Otherwise, the existing model is used for power flow predictions. This study includes analyses of five Texas A&M synthetic power grid cases, encompassing the 14-, 30-, 37-, 200-, and 500-bus systems. The training and test datasets were generated using <em>PowerModel.jl</em>, an open-source power flow solver/optimizer developed at Los Alamos National Laboratory, NM, USA.</p> <div> <h1><strong>Overview</strong></h1> <p>This dataset, provided as supplementary material for the above-referenced study, includes a comprehensive collection of images (plots) from the study’s analyses, along with Jupyter notebooks containing Python scripts used for the training, validation, and testing phases of PowerModel-AI. Additionally, it includes all training and external test data used in this work, generated via LANL-based open-source power flow solver, PowerModels.jl.</p> <p>The primary objective of this dataset is to ensure full reproducibility of the study’s analyses and facilitate critical examination by the scientific community, thereby maximizing the overall impact of the work.</p> <h1>Directory Structure</h1> <p>The hierarchy of folders and file organization of the dataset is illustrated in the chart below. The directory contains a README.md file which contains the information provided here and a requirements.txt that contains all libraries necessary to run the python scripts or Jupyter notebooks in this directory. A brief description of the folders and what they contain are provided below: </p> </div> <div> <strong>.</strong></div> <div>├── <strong>Models/</strong></div> <div>│ ├── _PM_AI_Models/</div> <div>│ │ ├── Type1/</div> <div>│ │ ├── Type2/</div> <div>│ │ └── Type3/</div> <div>│ │</div> <div>│ ├── _PM_AI_Module/</div> <div>│ │ ├── __init__.py</div> <div>│ │ └── PM_Methods.py</div> <div>│ │</div> <div>│ ├── _PM_JL_Data/</div> <div>│ ├── C1_Model/</div> <div>│ ├── C2_Model/</div> <div>│ ├── C3_Model/</div> <div>│ ├── M1_Model/</div> <div>│ ├── M2_Model/ </div> <div>│ └── M3_Model/</div> <div>│</div> <div>├── <strong>NodeSensitivityAnalysis/</strong></div> <div>│ ├── Sensitivity_Plots/</div> <div>│ ├── Sensitivity_PM_JL_Data/</div> <div>│ ├── get_sensitivity_PMJL_data.py</div> <div>│ └── NodeSensitivityAnalysis.ipynb</div> <div>│</div> <div>├── <strong>PlotsForOnTheFlyAnalysis/</strong></div> <div>│ ├── BaseModel_A/</div> <div>│ ├── BaseModel_B/ </div> <div>│ └── BaseModel_C/</div> <div>│ </div> <div>├── <strong>README.md</strong></div> <div>└── <strong>requirements.txt</strong></div> <p> </p> <h2>Files Description </h2> <h3><strong>1. </strong><strong>Models/</strong></h3> <p><strong><em>_PM_AI_Models/</em></strong> contains the ML models discussed in the manuscript. Type1, Type2, and Type3 refers to the C and M models with numbers "1", "2," and "3". Each Type folder contains individual subfolders for the synthetic grids discussed.</p> <p><strong> <em>_PM_AI_Module/</em></strong> contains a python script that has all the functions used in model training and analysis. It is imported in the Jupyter notebooks in the C and M subfolders in this directory.</p> <p><strong><em>_PM_JL_Data/</em> </strong>contains the following subfolders:</p> <p>a) <strong> </strong><em>_</em><strong><em><strong>G</strong>eneratePowerModelData/</em></strong> has a python script (<u>get_PowerModelJLData.py)</u> that is used to parse <u>PowerModels.jl</u> to compute AC power flow solutions for different power demand configurations. It also contains a subfolder, <strong><em>BusData_MATLAB/</em></strong>, that has all the synthetic grids used in the study and in MATLAB format.</p> <p>b) It also contains other subfolders (not shown in the chart above) that contains AC power flow solutions generated using LANL’s PowerModels.jl, for each synthetic grids and other grid-related data.</p> <p>The folders starting with C and M are the control and candidate models (more details in manuscript). Each folder contains Jupyter notebooks (for each power grid) that has python algorithms used in model training and testing, as well as functions to analyze and plot the prediction performance of the models. It accesses (if already trained) or stores (if newly trained) the models in the <strong><em>_PM_AI_Models/</em></strong> directory. Additionally, they contain 2 subfolders (not shown in the chart above): <strong>AbsoluteErrorPlots/</strong> and <strong>PredictionPlots/</strong> were the results (plots) from the analyses are stored. Some of these results are shown in the manuscript (<em>Figures 4</em>,<em> 5</em>, <em>6</em>, and <em>7</em>).</p> <h3><strong>2. </strong><strong>NodeSensitivityAnalysis/</strong></h3> <p>This folder contains the tools used for the node dependency analysis in Section 3.1.1 of the manuscript.</p> <p>It contains a python script called get_sensitivity_PMJL_data.py, which has similar operation like the <u>get_PowerModelJLData.py</u> script but only compute changes for one bus at a time (see details in manuscript). There is also a Jupyter notebook called <u>NodeSensitivityAnalysis.ipynb </u>that analyzes the bus node dependencies and produces the plots that are shown in Figure 3 in the manuscript. It contains 2 additional sub-folders:</p> <p>a) <strong> <em>Sensitivity_PM_JL_Data/</em></strong> where PowerModels.jl generated AC power flow solution data are stored, and</p> <p>b) <em><strong>Sensitivity_Plots/</strong> </em>where the results from <u>NodeSensitivityAnalysis.ipynb</u> are stored.</p> <h3><strong>3. </strong><strong>PlotsForOnTheFlyAnalysis/</strong></h3> <p>This directory contains only the results for the discussion in Section 3.2 in the manuscript, which is the on-the-fly implementation of PowerModel-AI. The on-the-fly algorithm will be provided and distributed separately in the PowerModel-AI package, which will be publicly available through LANL’s <a href="https://github.com/lanl-ansi" target="_blank" rel="noopener">The Advanced Network Science Initiative</a> (Github). It contains 3 subfolders with similar names but ends with "A", "B," and "C" which correspond to the designations shown and discussed in <em>Figure 8</em> of the manuscript.</p> <h1>Summary</h1> <h3><strong> </strong><strong>Models/</strong></h3> <p><strong>1. _PM_AI_Models/: </strong></p> <p>Contains the machine learning models discussed in the manuscript. The Type1, Type2, and Type3 folders refer to C and M models labeled "1", "2," and "3". Each type folder includes subfolders for the corresponding synthetic grids analyzed.</p> <div><strong>2. _PM_AI_Module/: </strong> </div> <div>Contains Python scripts for model training and analysis. PM_Methods.py is the script that defines functions for model training and analysis, which are imported in the Jupyter notebooks in the C and M subfolders. </div> <div> </div> <div><strong>3. _PM_JL_Data/: </strong></div> <div>-_GeneratePowerModelData/: Contains a Python script (get_PowerModelJLData.py) used to parse PowerModels.jl and compute AC power flow solutions for various power demand configurations. This folder also includes BusData_MATLAB/, which holds the synthetic grid data in MATLAB format. </div> <div>- Other Subfolders: Contain PowerModels.jl AC power flow solutions for each synthetic grid, as well as related data.</div> <div> </div> <div><strong>4. C1_Model/, C2_Model/, C3_Model/, M1_Model/, M2_Model/, M3_Model/: </strong></div> <div>These folders contain the control and candidate models (refer to manuscript details). Each folder includes pre-run Jupyter notebooks for model training and analysis, as well as two subfolders: </div> <div> - <em>AbsoluteErrorPlots/</em>: Contains saved analysis results for each grid.</div> <div> <strong> </strong>- <em>PredictionPlots/</em>: Stores model prediction results. </div> <div>Some results are shown in <em>Figures 4, 5, 6,</em> and <em>7</em> of the manuscript and can be reproduced using the notebooks.</div> <h3>NodeSensitivityAnalysis/</h3> <div><strong>1. Node Dependency Analysis Tools: </strong> </div> <div> This folder contains scripts and data used for the node dependency analysis in Section 3.1.1 of the manuscript.</div> <div> </div> <div><strong>2. Scripts: </strong></div> <div> - get_sensitivity_PMJL_data.py: Computes power flow changes for individual buses (refer to the manuscript for details). </div> <div> - NodeSensitivityAnalysis.ipynb: Analyzes dependencies and generates plots for Figure 3 in the manuscript. </div> <div> </div> <div><strong>3. Subfolders:</strong> </div> <div> - Sensitivity_PM_JL_Data/: Stores PowerModels.jl data for sensitivity analysis. </div> <div> - Sensitivity_Plots/: Contains the generated results from the Jupyter notebook.</div> <h3>PlotsForOnTheFlyAnalysis/</h3> <div><strong>On-the-Fly Learning Results: </strong>Contains the results for the on-the-fly learning analysis discussed in Section 3.2 of the manuscript. The subfolders BaseModel_A/, BaseModel_B/, and BaseModel_C/ correspond to the designations in <em>Figure 8</em> of the manuscript. These subfolders contain plots generated during analysis.</div> <h3>Additional Files</h3> <div>- README.md: This file.</div> <div>- requirements.txt: Contains a list of necessary Python libraries required to run the scripts and Jupyter notebooks.</div> <h3>Notes:</h3> <div>- The PowerModel-AI code is publicly available on GitHub.</div> <div>- The supplementary materials include additional Jupyter notebooks and results for each power grid analysis. </div> <div>- The generated results and predictions in this repository are consistent with those discussed in the manuscript.</div>
Supplementary data: "Revealing drivers and risks for power grid frequency stability with explainable AI"
<p>This repository contains processed data and result files for the paper <a href="https://arxiv.org/abs/2106.04341">Revealing drivers and risks for power grid frequency stability with explainable AI</a>. The code for producing the processed data and the results is <a href="https://github.com/johkruse/XAI-for-grid-frequency-stability">available at github</a>.</p> <p><strong>Data</strong></p> <p>For each area, the data folder contains the feature and target data used to train the ML model.</p> <ul> <li><em>raw_input_data.h5</em><strong> </strong>:<strong> </strong>The aggregated external features without additional engineered features.</li> <li><em>input_forecast.h5 </em>and<em> input_actual.h5: </em>The day-ahead available (forecast) and ex-post available (actual) data of external features including the engineered features.</li> <li><em>outputs.h5 </em>: The grid frequency stability indicators.</li> <li><em>version_2021-07-01</em>: Folder containing the training and test sets used for the results.</li> <li><em>documentation_of_data_download</em><strong>: </strong>Plots and information files concerning the ENTSO-E raw data and its aggregation.</li> </ul> <p><strong>Data sources</strong></p> <p>The data for input features (<em>raw_input_data.h5, input_forecast.h5 </em>and<em> input_actual.h5</em>) is derived from ENTSO-E Transparency Platform data [1]. The target data (<em>outputs.h5</em>) is based on power grid frequency recordings from the German Transmission System Operator TransnetBW [2].</p> <p><strong>Results</strong></p> <p>For each area and each target, the result folder comprises the results of hyper-parameter optimization, model prediction and interpretation via SHAP. The results refer to the full model and the restricted model (containing only day-ahead features).</p> <ul> <li><em>cv_results_gtb_full.csv</em> and <em>cv_results_gtb_day_ahead.csv</em> : Performance results for each combination in the hyper-parameter grid search.</li> <li><em>cv_best_params_gtb_full.csv</em> and <em>cv_best_params_gtb_day_ahead.csv</em> : Hyper-parameters used in the final (optimized) model.</li> <li><em>shap_values_gtb_full.npy</em> and <em>shap_interaction_values_gtb_full.npy </em>: First-order SHAP values and second-order SHAP interaction values for the full model.</li> <li><em>y_pred.h5</em> : Predictions of daily profile predictor, full model and day-ahead model.</li> </ul> <p><strong>Disclaimer</strong></p> <p>The data might be subject to copyright or related rights. Please consult the primary data owner.</p>
Supplementary data: "Secondary control activation analysed and predicted with explainable AI"
<p>This repository contains processed data and result files for the paper <a href="https://arxiv.org/abs/2109.04802">Secondary control activation analysed and predicted with explainable AI</a> . The code for producing the processed data and the results is <a href="https://github.com/johkruse/XAI-for-aFRR-activation">available at github</a>.</p> <p><strong>Data</strong></p> <p>The data folder contains the feature and target data used to train the ML model. The data for Germany comprises the following folders and files:</p> <ul> <li><em>raw_input_data.h5</em><strong> </strong>:<strong> </strong>The aggregated external features without additional engineered features.</li> <li><em>inputs_<model_type>.h5 </em><em>:</em> The input features for the different model types used in the paper including the engineered features. Depending on the model type, the input files also contain the IGCC features.</li> <li><em>outputs.h5 </em>: The activated aFRR volumes in Germany.</li> <li><em>version_2021-08-20</em>: Folder containing the training and test sets used for the results.</li> <li><em>documentation_of_data_download</em>: Information files concerning the ENTSO-E raw data and its aggregation.</li> </ul> <p>In addition to the German time series, the data folder contains the raw input data for the remaining IGCC states. Note that the results contain more model types as actually discussed in the paper.</p> <p><strong>Data sources</strong></p> <p>The data for input features (<em>raw_input_data.h5</em> and <em>input_<model_type>.h5</em>) is derived from ENTSO-E Transparency Platform data [1]. The target data (<em>outputs.h5</em>) is based on publicly available data from the German Transmission System Operators (TSOs) [2].</p> <p><strong>Results</strong></p> <p>The result folder comprises the results of hyper-parameter optimization, model prediction and interpretation via SHAP. The model type, the loss function to train the model and the data set for prediction/interpretation were varied.</p> <ul> <li><em>cv_results_<model_type>_<loss_function>.csv</em> : Performance results for each combination in the hyper-parameter grid search.</li> <li><em>cv_best_params_<model_type>_<loss_function>.csv</em> : Hyper-parameters used in the final (optimized) model.</li> <li><em>shap_values_<data_set>_<model_type>_<loss_function>.npy</em> : First-order SHAP values calculated on different data sets: The train set, the randomized test set and the continuous test set.</li> <li><em>y_pred_<data_set>.h5</em> : Predictions of daily profile predictor and Machine Learning models.</li> </ul> <p><strong>Disclaimer</strong></p> <p>The data might be subject to copyright or related rights. Please consult the primary data owner.</p>
High-quality Image (NIR and RGB) Dataset Synchronized With Contact Vital Sings Recordings and Clinical Data of Stratified Healthy Population. Algorithms and AI Models to Obtain a Set of Vital Signs Im
ClinicalTrials.gov study NCT05947721. IPD Sharing: NO. Countries: 1. Publications: 2.
Artificial Intelligence for Automated Clinical Data Exploration From Electronic Medical Records (CardioMining-AI)
ClinicalTrials.gov study NCT05176769. IPD Sharing: YES. Countries: 1. Publications: 7.
AI-Based Medical Data Analysis for Differentiating Inflammatory vs Degenerative Joint Diseases in Elderly Patients
ClinicalTrials.gov study NCT07153315. IPD Sharing: Not stated. Countries: 1. Publications: 3.
AI to Improve Data From Danish Cardiac Arrest Registry
ClinicalTrials.gov study NCT05308303. IPD Sharing: Not stated. Countries: 1. Publications: 7.
Prediction of Targeted Therapy Efficacy in EGFR-mutant Lung Cancer Patients Using AI-based Multimodal Data
ClinicalTrials.gov study NCT07287904. IPD Sharing: UNDECIDED. Countries: 1. Publications: 3.
Data from: Using satellite AIS to improve our understanding of shipping and fill gaps in ocean observation data to support marine spatial planning
Open the record for dataset details and reuse information.
Data from: A community-based approach to ethical decision-making in AI for health care
Open the record for dataset details and reuse information.
Raw data for analysis in AI-NERD: Elucidation of Relaxation Dynamics Beyond Equilibrium Through AI-informed X-ray Photon Correlation Spectroscopy
Open the record for dataset details and reuse information.
Exploring Ethical Implications: Unraveling Factors Influencing Data Governance Awareness Behavior in Generative AI Chatbot
<p>Data set</p>
Additional data for "AI-driven Integrated Online Layout Planning and Scheduling in Flexible Assembly Systems"
<p>Additional data for the thesis on "Integrated online layout planning and scheduling in flexible<br>assembly systems".</p>
Some data for phage protein annotation AI pipeline
Open the record for dataset details and reuse information.
Data set for AI in health PR
<p>Dataset for a study of AI on health PR in Indonesia</p>
Data set for AI Chatbot in banking
<p>Data set for AI Chatbot in banking for Indonesia case.</p>
ScienceDex guides
Understand access before you commit
These curated guides explain access requirements, typical timelines, costs, and reuse considerations for widely used research datasets.
Allen Brain Atlas
Allen Brain Atlas is an Allen Institute collection of brain map atlases, datasets, APIs, and analysis tools covering mouse, human, and non-human primate brain resources.
Annotated Behaviour and Observability Dataset (ABODe)
ABODe is a University of Edinburgh DataShare dataset for behavior classification in group-housed mice using home-cage video, identities, bounding boxes, ground-plate positions, and annotator labels.
DANDI Archive for NWB datasets
DANDI is a BRAIN Initiative archive for publishing and sharing neurophysiology data, including electrophysiology, optophysiology, and behavioral data packaged as NWB and related standards.
International Brain Laboratory public data
The International Brain Laboratory public data releases expose standardized mouse decision-making experiments, including Neuropixels recordings, widefield calcium imaging, behavior, and session metadata accessed through the ONE API.
OpenNeuro
OpenNeuro is a free, open platform for sharing neuroimaging datasets, with public search, dataset pages, and download paths for web, S3, DataLad, and the OpenNeuro CLI.