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.
118
datasets available to search
ShareScore release 0.9.0
Dataset results
118 results for “Software Modelling”
On the Effect of Semantically Enriched Context Models on Software Modularization
<p>The dataset used for evaluating the approaches outlined in this paper, comprising of 10 open source Java projects. The algorithms employed can be found at https://github.com/amirms/GeLaToLab, </p>
Data, software, and Figures used in a manuscript submitted to Geoscientific Model Development
<p>Data, software, and Figures used in 'A General Comprehensive Evaluation Method for Cross-Scale Precipitation Forecast' submitted to Geoscientific Model Development.</p>
Code generation for classical-quantum software systems modelled in UML - Dataset and EGL Transformation
<p>This dataset contains all the elements necessary for carry out the EGL transformation from UML models to Hybrid and Quantum code, as well as to carry its validation. </p> <blockquote> <p><em>Quantum computing is gaining an increasing interest since it can solve certain problems exponentially faster than classical computing. Thus, many organizations are researching and launching investments for integrating quantum software into their existing systems. Software modernization (as based on Model-Driven Engineering) has been proposed to migrate from/to the so-called hybrid software systems, which integrate classical and quantum software. In that process, both, reverse engineering and restructuring phases, have already been investigated. However, forward engineering phase for generating hybrid source code from high-level design models has not yet been addressed. Thus, this research proposes a quantum code generation technique from extended UML design models. It consists of a set of Model-to-Text transformations (defined through Epsilon Generation Language) to generate both Python and Qiskit code, which respectively integrate classical and quantum code. The transformation has been validated through a multi-case study with 7 hybrid software systems modelled in UML, which demonstrated that the transformation is effective and efficient. The implication of this work is that the software modernization process for hybrid software systems can be completed by tackling forward engineering phase, and that Model-Driven Engineering can therefore globally facilitate industry adoption of quantum software.</em></p> </blockquote>
Data and Software of "Development of a Geometric Modeling Strategy for the Generation of Representative Unit Cells in 2D Braids"
<h1><strong>Id: Data of following publication</strong></h1> <p>title = "Development of a Geometric Modeling Strategy for the Generation of Representative Unit Cells in 2D Braids",<br>journal = "<span>Composite Structures</span>",<br>volume =" 348",<br>pages = "118503",<br>year = "2025",<br>doi = "<a href="https://doi.org/10.1016/j.compstruct.2024.118503" target="_blank" rel="noopener">10.1016/j.compstruct.2024.118503</a>",<br>author = "José Rothkegel, Benjamin Renson, Michael Bruyneel, Ludovic Noels"</p> <p>Data doi on 10.5281/zenodo.10829042</p> <h1>pyRVE</h1> <h2><em>Python Code for Geometrical Generator for Braided Composites RVE</em></h2> <p>pyRVE is a code written in <em>Python</em> using the <em>GMSH API</em> that generates the Representative Unit Cell (RUC) of braided composites. It allows the generation of the RUC of triaxial braided for <em>Diamond</em> and <em>Regular</em> patterns.</p> <h2>Requirements</h2> <p>To run, it requires:</p> <ul> <li>The GMSH Python API, which must be built with OpenCascade support. <ul> <li>Choose a local installation directory; <code>CMAKE_INSTALL_PREFIX=$HOME/local/gmsh</code>, and <code>GMSHPY_INSTALL_DIRECTORY=$HOME/local/gmsh</code> e.g.;</li> <li>Make that directory part of your <code>export PYTHONPATH=$HOME/local/gmsh/lib:$PYTHONPATH</code>.</li> <li>After compiling use <code>make install</code>.</li> </ul> </li> <li>The CM3 app dG3D if the final RVE homogenized solution is needed (<a href="https://gitlab.onelab.info/cm3/cm3Libraries">https://gitlab.onelab.info/cm3/cm3Libraries</a>).</li> <li>Make sure that the latest version of OpenCascade (OCCT) is used. Current used version in occt-V7.8.0.</li> </ul> <h2>Usage</h2> <h3>File Structure</h3> <p>A typical run case must have a file structure, where:</p> <ul> <li><code>brd</code>: the files <code>.brd</code> and <code>.brep</code> are located here. The <code>.brd</code> is a backup of the <code>braidClass</code> instance used in the model saved using <code>pickle</code>, the <code>.brep</code> is the Boundary Representation file that can be opened with <em>GMSH</em>.</li> <li><code>csv</code>: the <code>.csv</code> file saved here is the initial output of the code. It contains the actually used dimensions and the final cover factor of the braid.</li> <li><code>data</code>: It contains <code>.csv</code> files with the material properties and the dimensions of the tows. The original model dimensions are read from here.</li> <li><code>dir</code>: In the case of running the RVE homogenization, the directions of the tow fibers are stored here. They are saved for post processing.</li> <li><code>msh</code>: the mesh file <code>.msh</code> obtained after the geometry geneartion is stores here.</li> <li><code>png</code>: in the case of automatic post processing, png files are stored here.</li> <li><code>res</code>: this folder is used to store the homogenization results. They have to be moved here.</li> <li><code>stp</code>: if acitvated, a <code>.stp</code> file of the geometry is stored here</li> <li><code>svg</code>: the projection of the geometry on the <em>x-y</em> plane is stored here.</li> <li><code>vtk</code>: A copy of the mesh file without the matrix mesh is sotred here as a `.vtk`` file.</li> </ul> <h3>How to Run</h3> <p>We will consider the current file structure to run the example in 000_Base. To run the code, it can be called from the command prompt as</p> <div> <pre><code>python3 ../../source/mainRVE.py --name <i> --pattern <pattern></code></pre> </div> <p>In this case, the <code>--name</code> refers to the index that will be given to the model, where <code><i></code> must be changed to an integer and <code>--pattern</code> refers to the wanted pattern to be used, where <code><pattern></code> must be changed to either <code>dia</code> or <code>reg</code>.</p> <blockquote> <p>Note: <code><code>--name</code>cat</code> can also be used to reproduce the regular pattern benchmark of the paper. In that case, the volume fraction of fiber in the tows is hard coded as the provided value in the reference (i.e. 0.86). For other cases, the volume fraction is evaluated from the tow cross-sections.</p> <p>Note: <code>mainRVE.py</code> must be accesible from the directory where the case is being run. This example shows the usage of the current file structure.</p> </blockquote> <h3>All Command Line Options</h3> <p>The code can be run using further options that serve different purpouses, some serving pre processing needs and other serving run administration. The different command line options are:</p> <ul> <li>Required: <ul> <li><code>--name</code> : it gives a suffix to the run model. It is usually an integer.</li> <li><code>--pattern</code> : indicates the type of pattern to be used to build the geometry. The two current options are <code>dia</code> for diamond and <code>reg</code> for regular.</li> </ul> </li> <li>Optional <ul> <li><code>-dG3D</code>: it indicates that the homogenization of the generated RUC is to be perfomed.</li> <li><code>-GMSH</code> : it indicates that GMSH must be open upon competion of the generation of the mesh.</li> <li><code>-loadModel</code> : it will try to load a premade model. It will ignore <code>--pattern</code>.</li> <li><code>--rndPrm</code> : it will generate randomized geometrical parameters. It can be used to generate batches of results. It takes an argument that can be <code>2</code>, <code>4</code> or <code>6</code>. Currently, <code>2</code> gives a random value for <code>s_axial</code> and <code>theta</code>, <code>4</code> randomizes the same as <code>2</code> and adds <code>h_axial</code> and <code>h_bias</code>, and <code>6</code> randomizes the same as <code>4</code> and adds <code>w_axial</code> and <code>w_bias</code>.</li> </ul> </li> <li>Pre-Processing <ul> <li><code>-refCF</code>: it tells the code to generate a grid of values for <code>s_axial</code> and <code>theta</code> where only the cover factor is obtained. It is meant for posterior graphing purposes.</li> </ul> </li> </ul> <h3>Examples</h3> <p>Following the run options, a few examples are indicated</p> <ul> <li>A basic mesh generation run for the basic data, considering a <strong>regular pattern</strong>, for a model named <strong>2</strong>:</li> </ul> <div> <pre><code>python3 ../../source/mainRVE.py --name 2 --pattern reg</code></pre> </div> <ul> <li>The generation of the cover factor data and export, considering a <strong>regular pattern</strong>:</li> </ul> <div> <pre><code>python3 ../../source/mainRVE.py --pattern reg -refCF</code></pre> </div> <ul> <li>A run for the modified basic data, where the <strong>2</strong> parameters are modified <em>randomly</em>, considering a <strong>regular pattern</strong>, for a model named <strong>2</strong>:</li> </ul> <div> <pre><code>python3 ../../source/mainRVE.py --name 2 --pattern reg --rndPrm 2</code></pre> </div> <ul> <li>A run, where model <strong>2</strong> already exists in <code>brd</code> folder but not the <code>.msh</code> and <code>.vtk</code> files:</li> </ul> <div> <pre><code>python3 ../../source/mainRVE.py --name 2 -loadModel </code></pre> </div> <h2>Code Structure</h2> <p>The code is implemented into Python files, where <code>mainRVE.py</code> runs the whole code. The files are:</p> <ul> <li>Braid: <ul> <li><code>braidClass.py</code> :</li> <li><code>bzrPairClass.py</code> :</li> </ul> </li> <li>Geometry <ul> <li><code>bezrClass.py</code> :</li> <li><code>bilnClass.py</code> :</li> <li><code>patchClass.py</code> :</li> <li><code>pntSetClass.py</code> :</li> <li><code>pointClass.py</code> :</li> <li><code>sctnClass.py</code> :</li> <li><code>stripeClass.py</code> :</li> <li><code>surfClass.py</code> :</li> <li><code>surfOffClass.py</code> :</li> </ul> </li> <li>Material: <ul> <li><code>chamis.py</code> :</li> </ul> </li> <li>Tools: <ul> <li><code>dataIO.py</code> :</li> <li><code>postDirection.py</code> :</li> <li><code>tool.py</code> :</li> <li><code>toolData.py</code> :</li> </ul> </li> <li><code>curveClass.py</code> :*</li> </ul> <p> </p> <p> </p>
Ancestral allele estimates for cattle using est-sfs software with the K2 model
<h1>Overview</h1> <p>The assignment of bovine ancestral alleles was based on a model comparison of alleles from cattle with alleles from outgroup species: Water Buffalo, Sheep, and White-Tailed Deer. </p> <p>The frequency of cattle alleles are determined using 79 representative individuals from 1000 Bull Genomics Project. We utilized multiple sequence alignments of 110 species (78 ruminants and 32 mammalian outgroup species), available from http://animal.omics.pro/code/index.php/RGD/loadByGet?address[]=RGD/Download/comSynDownload.php, to determine the alleles in Water Buffalo, Sheep, and White-Tailed Deer at each locus.</p> <p>We employed the est-sfs software with the K2 model to infer the probability (Pancs) of the major allele in cattle being ancestral. Alleles were determined to be ancestral if they were the major allele at a site with Pancs > 0.8 or the minor allele at a site with Pancs < 0.2.</p> <p>Please email bft990914@163.com for any queries.</p> <p>The columns of this dataframe are</p> <p>chrome: chromosome index.</p> <p>pos: physical location of SNV.</p> <p>cattle_ref: reference allele of cattle.</p> <p>cattle_alt: alternative allele of cattle.</p> <p>cattle_maj: major allele of cattle.</p> <p>water_buffalo: the sequence of water_buffalo.</p> <p>sheep: the sequence of sheep.</p> <p>white_tailed_deer: the sequence of white_tailed_deer.</p> <p>p_maj_anc: the probability of the major allele of cattle being ancestral.</p> <p>ancestral_allele: the inferred ancestral allele.</p>
Application Case 3: Data sets consisting of 3D scans, 3D model and the derived metadata, from two different software programs
<p>In this repository we provide 3D scan projects and the 3D models processed from them with their metadata using the example of a wood sample. The metadata was generated using our metadata generation script, which is described in the referenced publication.</p> <p>The 3D scan projects were created in different software (atos v6.2, atos 2016 and zeiss 2023). For each there is a scan project, a 3D model and the generated metadata with and without uri in this repository.</p> <p>The publication in which this application case is included: Homburg, T., Cramer, A., Raddatz, L. <em>et al.</em> Metadata schema and ontology for capturing and processing of 3D cultural heritage objects. <em>Herit Sci</em> <strong>9</strong>, 91 (2021). <a href="https://doi.org/10.1186/s40494-021-00561-w">https://doi.org/10.1186/s40494-021-00561-w</a></p> <p>Python scripts for exporting metadata can be found here: <a href="https://github.com/i3mainz/3dcap-md-gen/tree/0.1.3">GitHub - i3mainz/3dcap-md-gen</a></p>
Quality Evaluation Models or Frameworks for Open Source Software: A Systematic Literature Review (Matching articles with categories)
<p>This document includes which primary study falls into which category with respect to the RQs in the following study: “Quality Evaluation Models or Frameworks for Open Source Software: A Systematic Literature Review”</p>
Quality Evaluation Models or Frameworks for Open Source Software: A Systematic Literature Review (Matching articles with categories)
<p>This document includes which primary study falls into which category with respect to the RQs in the following study: “Quality Evaluation Models or Frameworks for Open Source Software: A Systematic Literature Review”</p>
Quality Evaluation Models or Frameworks for Open Source Software: A Systematic Literature Review (Matching articles with categories)
<p>This document includes which primary study falls into which category with respect to the RQs in the following study: “Quality Evaluation Models or Frameworks for Open Source Software: A Systematic Literature Review”</p>
Dataset: A Study on the Mental Models of Users Concerning Existing Software
<p>In 2022, we conducted a study on the mental models of users concerning existing software.</p> <p>Information on the execution of the study are presented in the paper linked below:</p> <p>https://doi.org/10.1007/978-3-030-98464-9_18</p>
Predicting Software Refactoring - joblib models
<p>Zip file contains Machine Learning models trained as a partial result of our work described in our paper</p>
Towards Developing and Analysing The Metric-Based Software Defect Severity Prediction Model
<p>This is a metric based approach to solve software defect severity prediction problem. In addition to that, this work proposes a new evaluation scheme that comprised of five metrics to analyze the performances.</p>
Cloud computing is one of the most popular and sophisticated technologies adopted by organizations worldwide. Some world-leading organizations enhance their efficiency and effectiveness by using cloud computing technology. Working from home (WFH) has been a popular trend among organizations during the coronavirus (COVID-19) pandemic. The COVID-19 saw a breakthrough in work cultures and environments where working from home was a remarkable success in remote working environments, despite being a rare phenomenon in Sri Lanka. Yet, it is argued that the deployment of work from home has not been effective among Sri Lankan business organizations due to a lack of IT infrastructure, facilities, and knowledge. The purpose of the study is to investigate the impact of cloud computing, embracing the service models (Infrastructure as a Service, Platform as a Service, and Software as a Service) as theoretical lenses and testing the COVID-19 as the moderator. The study has been conducted based on a deductive approach and adopted a stratified random sampling method. The sample consisted of 384 IT employees among those who had experienced working from home. The study utilized multiple regression and found that cloud computing service models significantly impact work from home with the moderating effect of COVID-19.
<p>Cloud computing is one of the most popular and sophisticated technologies adopted by organizations worldwide. Some world-leading organizations enhance their efficiency and effectiveness by using cloud computing technology. Working from home (WFH) has been a popular trend among organizations during the coronavirus (COVID-19) pandemic. The COVID-19 saw a breakthrough in work cultures and environments where working from home was a remarkable success in remote working environments, despite being a rare phenomenon in Sri Lanka. Yet, it is argued that the deployment of work from home has not been effective among Sri Lankan business organizations due to a lack of IT infrastructure, facilities, and knowledge. The purpose of the study is to investigate the impact of cloud computing, embracing the service models (Infrastructure as a Service, Platform as a Service, and Software as a Service) as theoretical lenses and testing the COVID-19 as the moderator. The study has been conducted based on a deductive approach and adopted a stratified random sampling method. The sample consisted of 384 IT employees among those who had experienced working from home. The study utilized multiple regression and found that cloud computing service models significantly impact work from home with the moderating effect of COVID-19.</p>
Evaluating Software Modelling Recommendations: Towards Systematic Guidelines for Modelling
<p>The dataset contains four supporting documents for the paper title, "Evaluating Software Modelling Recommendations: Towards Systematic Guidelines for Modelling". </p> <p>The first documment is a pdf file containing the student survey questions.</p> <p>The second docummnet is an excel sheet containing the discussion of a focus group study. </p> <p>The third docummet is an excel sheet containing interview transcripts of 4 of the participants of this study (who agreed to publish their statements). We had to modify the transcript and omit a few discussions as it involves iedntification of names. <br><br><br>The final documment is a grading rubric used in one of the courses for grading. </p>
Applying short text topic models to instant messaging communication of software developers
<p>Content related to paper "Applying short text topic models to instant messaging communication of software developers" published in the Journal of Systems and Software.</p> <p><strong>Data available:</strong></p> <ul> <li>Data sets used: JSONs with messages from Gitter chat rooms (downloaded with previous Gitter API - <a href="https://developer.gitter.im/docs/welcome" rel="nofollow">https://developer.gitter.im/docs/welcome</a>): <ul> <li>"Android.json"</li> <li>"ConsenSys.json"</li> <li>"WebpackDocs.json"</li> <li>"Jenkinsci.json"</li> <li>"Locomotive.json"</li> <li>"SpringSecurity.json"</li> <li>"Flutter.rar" - json file was compressed due to its size</li> <li>"GitterHQ.rar" - json file was compressed due to its size</li> <li>"Laravel.rar" - json file was compressed due to its size</li> </ul> </li> <li>"stopwords_list": Customized list of stop words</li> <li>"topics_sttm_results.csv": Topics obtained with each combination of model and corpus (both lemmatized and stemmed corpora)</li> <li>"intrusion_tasks.csv": Results of the survey for the Intrusion Tasks and its participants' background</li> <li>"topicnaming_tasks.csv": Results of the survey for the Topic Naming Tasks and its participants' background</li> <li>"intrinsic_metrics.csv": Scores of topic coherence metrics at topic level ('average' represents the score at model level)</li> <li>"topics_themes_chatrooms.csv": Results of the exercise described in Section 5.2 with the topics and themes identified in each of the 87 Gitter chat rooms.</li> <li>"sensitivity_analysis": Results of a smaller-scale sensitivity analysis to check the impact of the number of topics on the main findings of the paper.</li> </ul>
Supplementary Material for "Investigating Software Development Teams Members' Perceptions of Data Privacy in the Use of Large Language Models (LLMs)"
<h3>ABSTRACT<strong>: </strong></h3> <p><strong>Context</strong>: Large Language Models (LLMs) have revolutionized natural language generation and understanding. However, they raise significant data privacy concerns, especially when sensitive data is processed and stored by third parties. <br><strong>Goal</strong>: This paper investigates the perception of software development teams members regarding data privacy when using LLMs in their professional activities. Additionally, we examine the challenges faced and the practices adopted by these practitioners. <br><strong>Method</strong>: We conducted a survey with 78 ICT practitioners from five regions of the country. <br><strong>Results</strong>: Software development teams members have basic knowledge about data privacy and LGPD, but most have never received formal training on LLMs and possess only basic knowledge about them. Their main concerns include the leakage of sensitive data and the misuse of personal data. To mitigate risks, they avoid using sensitive data and implement anonymization techniques. The primary challenges practitioners face are ensuring transparency in the use of LLMs and minimizing data collection. Software development teams members consider current legislation inadequate for protecting data privacy in the context of LLM use. <br><strong>Conclusions</strong>: The results reveal a need to improve knowledge and practices related to data privacy in the context of LLM use. According to software development teams members, organizations need to invest in training, develop new tools, and adopt more robust policies to protect user data privacy. They advocate for a multifaceted approach that combines education, technology, and regulation to ensure the safe and responsible use of LLMs.</p>
Software sustainability of global impact models (Dataset and analysis script)
<p><strong><em>slocount.py</em></strong>: This script calculates the number of comment lines, total lines of code (TLOC) and source lines of code (SLOC). It uses a code line counter developed by Ben Boyter, which must be installed (https://github.com/boyter/scc.). The source code links to the global impact models (GIMs) can be found in the 'ISIMIP_models.xlsx' file.</p> <p><strong><em>active_dev.py</em></strong>: This script plots the number of active developers for each GIM across 10 sectors. It utilizes data from the 'active_dev.csv' file, which lists the GIMs and their respective number of developers.</p> <p><strong><em>cocomo.py</em></strong>: This script estimates the effort required for software development using the methodology proposed by Sachan et al. 2016 (https://doi.org/10.1016/j.procs.2016.06.107). It also generates plots for these estimates.</p> <p><strong><em>comment_density_modularity.py</em></strong>: This script calculates the comment density and evaluates the modularity of the modules. It also produces plots for these metrics.</p> <p><strong><em>code_standard.py</em></strong>: This script uses Pylint (<a href="https://pylint.readthedocs.io/en/latest/user_guide/usage/output.html">https://pylint.readthedocs.io/en/latest/user_guide/usage/output.html</a>) to check if the source code, either in part or in its entirety, adheres to the PEP8 coding standard. It also generates lint scores for the source code.</p> <p><strong><em>line_count.zip</em></strong>: This file contains the results of counting the number of comment lines, TLOC and SLOC for each GIM.</p> <p><strong><em>lint_score.zip</em></strong>: This file contains the results of running pylint on GIMs that include Python in their source code. Results also include lint score per GIM</p>
Mars topical ice model software [dataset]
<p>Data set used to model Mars topical ice spatial temporal distribution. NASA Grant 80NSSC19K1223.</p>
ReqExp: BERT-based ML Model for Extracting Software Requirements
<p>Datasets that were used during experiments in ReqExp project.</p>
Topic modeling in software engineering research
<p>Raw data collected from 111 papers applying topic modeling techniques in software engineering studies.</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.