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.
338
datasets available to search
ShareScore release 0.9.0
Dataset results
338 results for “Leverage”
Classification of web-based Digital Humanities projects leveraging information visualisation techniques
<h2>Description</h2> <p>This dataset contains a list of 186 Digital Humanities projects leveraging information visualisation methods. Each project has been classified according to visualisation and interaction techniques, narrativity and narrative solutions, domain, methods for the representation of uncertainty and interpretation, and the employment of critical and custom approaches to visually represent humanities data.</p> <p> </p> <h2>Classification schema: categories and columns</h2> <p>The <code>project_id</code> column contains unique internal identifiers assigned to each project. Meanwhile, the <code>last_access</code> column records the most recent date (in DD/MM/YYYY format) on which each project was reviewed based on the web address specified in the <code>url</code> column.<br>The remaining columns can be grouped into descriptive categories aimed at characterising projects according to different aspects:</p> <p> </p> <p><strong>Narrativity.</strong> It reports the presence of information visualisation techniques employed within narrative structures. Here, the term narrative encompasses both author-driven linear data stories and more user-directed experiences where the narrative sequence is determined by user exploration [1]. We define 2 columns to identify projects using visualisation techniques in narrative, or non-narrative sections. Both conditions can be true for projects employing visualisations in both contexts. Columns:</p> <ul> <li> <p><code>non_narrative</code> (boolean)</p> </li> <li> <p><code>narrative</code> (boolean)</p> </li> </ul> <p> </p> <p><strong>Domain.</strong> The humanities domain to which the project is related. We rely on [2] and the chapters of the first part of [3] to abstract a set of general domains. Column:</p> <ul> <li> <p><code>domain</code> (categorical):</p> </li> <ul> <li> <p>History and archaeology</p> </li> <li> <p>Art and art history</p> </li> <li> <p>Language and literature</p> </li> <li> <p>Music and musicology</p> </li> <li> <p>Multimedia and performing arts</p> </li> <li> <p>Philosophy and religion</p> </li> <li> <p>Other: both extra-list domains and cases of collections without a unique or specific thematic focus.</p> </li> </ul> </ul> <p> </p> <p><strong>Visualisation of uncertainty and interpretation.</strong> Buiding upon the frameworks proposed by [4] and [5], a set of categories was identified, highlighting a distinction between precise and impressional communication of uncertainty. Precise methods explicitly represent quantifiable uncertainty such as missing, unknown, or uncertain data, precisely locating and categorising it using visual variables and positioning. Two sub-categories are interactive distinction, when uncertain data is not visually distinguishable from the rest of the data but can be dynamically isolated or included/excluded categorically through interaction techniques (usually filters); and visual distinction, when uncertainty visually “emerges” from the representation by means of dedicated glyphs and spatial or visual cues and variables. On the other hand, impressional methods communicate the constructed and situated nature of data [6], exposing the interpretative layer of the visualisation and indicating more abstract and unquantifiable uncertainty using graphical aids or interpretative metrics. Two sub-categories are: ambiguation, when the use of graphical expedients—like permeable glyph boundaries or broken lines—visually convey the ambiguity of a phenomenon; and interpretative metrics, when expressive, non-scientific, or non-punctual metrics are used to build a visualisation. Column:</p> <ul> <li> <p><code>uncertainty_interpretation</code> (categorical):</p> </li> <ul> <li> <p>Interactive distinction</p> </li> <li> <p>Visual distinction</p> </li> <li> <p>Ambiguation</p> </li> <li> <p>Interpretative metrics</p> </li> </ul> </ul> <p> </p> <p><strong>Critical adaptation.</strong> We identify projects in which, with regards to at least a visualisation, the following criteria are fulfilled: 1) avoid repurposing of prepackaged, generic-use, or ready-made solutions; 2) being tailored and unique to reflect the peculiarities of the phenomena at hand; 3) avoid simplifications to embrace and depict complexity, promoting time-consuming visualisation-based inquiry. Column:</p> <ul> <li> <p><code>critical_adaptation</code> (boolean)</p> </li> </ul> <p> </p> <p><strong>Non-temporal visualisation techniques.</strong> We adopt and partially adapt the terminology and definitions from [7]. A column is defined for each type of visualisation and accounts for its presence within a project, also including stacked layouts and more complex variations. Columns and inclusion criteria:</p> <ul> <li> <p><code>plot</code> (boolean): visual representations that map data points onto a two-dimensional coordinate system.</p> </li> <li> <p><code>cluster_or_set</code> (boolean): sets or cluster-based visualisations used to unveil possible inter-object similarities.</p> </li> <li> <p><code>map</code> (boolean): geographical maps used to show spatial insights. While we do not specify the variants of maps (e.g., pin maps, dot density maps, flow maps, etc.), we make an exception for maps where each data point is represented by another visualisation (e.g., a map where each data point is a pie chart) by accounting for the presence of both in their respective columns.</p> </li> <li> <p><code>network</code> (boolean): visual representations highlighting relational aspects through nodes connected by links or edges.</p> </li> <li> <p><code>hierarchical_diagram</code> (boolean): tree-like structures such as tree diagrams, radial trees, but also dendrograms. They differ from networks for their strictly hierarchical structure and absence of closed connection loops.</p> </li> <li> <p><code>treemap</code> (boolean): still hierarchical, but highlighting quantities expressed by means of area size. It also includes circle packing variants.</p> </li> <li> <p><code>word_cloud</code> (boolean): clouds of words, where each instance’s size is proportional to its frequency in a related context</p> </li> <li> <p><code>bars</code> (boolean): includes bar charts, histograms, and variants. It coincides with “bar charts” in [7] but with a more generic term to refer to all bar-based visualisations.</p> </li> <li> <p><code>line_chart</code> (boolean): the display of information as sequential data points connected by straight-line segments.</p> </li> <li> <p><code>area_chart</code> (boolean): similar to a line chart but with a filled area below the segments. It also includes density plots.</p> </li> <li> <p><code>pie_chart</code> (boolean): circular graphs divided into slices which can also use multi-level solutions.</p> </li> <li> <p><code>plot_3d</code> (boolean): plots that use a third dimension to encode an additional variable.</p> </li> <li> <p><code>proportional_area</code> (boolean): representations used to compare values through area size. Typically, using circle- or square-like shapes.</p> </li> <li> <p><code>other</code> (boolean): it includes all other types of non-temporal visualisations that do not fall into the aforementioned categories.</p> </li> </ul> <p> </p> <p><strong>Temporal visualisations and encodings.</strong> In addition to non-temporal visualisations, a group of techniques to encode temporality is considered in order to enable comparisons with [7]. Columns:</p> <ul> <li> <p><code>timeline</code> (boolean): the display of a list of data points or spans in chronological order. They include timelines working either with a scale or simply displaying events in sequence. As in [7], we also include structured solutions resembling Gantt chart layouts.</p> </li> </ul> <ul> <li> <p><code>temporal_dimension</code> (boolean): to report when time is mapped to any dimension of a visualisation, with the exclusion of timelines. We use the term “dimension” and not “axis” as in [7] as more appropriate for radial layouts or more complex representational choices.</p> </li> <li> <p><code>animation</code> (boolean): temporality is perceived through an animation changing the visualisation according to time flow.</p> </li> <li> <p><code>visual_variable</code> (boolean): another visual encoding strategy is used to represent any temporality-related variable (e.g., colour).</p> </li> </ul> <p> </p> <p><strong>Interaction techniques.</strong> A set of categories to assess affordable interaction techniques based on the concept of user intent [8] and user-allowed data actions [9]. The following categories roughly match the “processing”, “mapping”, and “presentation” actions from [9] and the manipulative subset of methods of the “how” an interaction is performed in the conception of [10]. Only interactions that affect the visual representation or the aspect of data points, symbols, and glyphs are taken into consideration. Columns:</p> <ul> <li> <p><code>basic_selection</code> (boolean): the demarcation of an element either for the duration of the interaction or more permanently until the occurrence of another selection.</p> </li> <li> <p><code>advanced_selection</code> (boolean): the demarcation involves both the selected element and connected elements within the visualisation or leads to brush and link effects across views. Basic selection is tacitly implied.</p> </li> <li> <p><code>navigation</code> (boolean): interactions that allow moving, zooming, panning, rotating, and scrolling the view but only when applied to the visualisation and not to the web page. It also includes “drill” interactions (to navigate through different levels or portions of data detail, often generating a new view that replaces or accompanies the original) and “expand” interactions generating new perspectives on data by expanding and collapsing nodes.</p> </li> <li> <p><code>arrangement</code> (boolean): methods to organise visualisation elements (symbols, glyphs, etc.) or multi-visualisation layouts spatially through drag and drop or according to a criterion via more automatic triggers.</p> </li> <li> <p><code>change</code> (boolean): visual encoding alterations involving different aspects of visualisation as a whole: the same content is presented with another visualisation technique; the change involves symbols or glyphs aspect (colour, size, shape, etc.); the visualisation type is unaltered, but the layout variant changes (e.g., to stacked layouts); or other changes like axes inversion and scale modifications. The presence of all the visualisation techniques involved in a change is reported.</p> </li> <li> <p><code>visualisation_filter</code> (boolean): filters to exclude or include visualisation elements with respect to defined criteria, without reloading or generating a new visualisation. Unlike options triggering the fetch of new data to alter the visualisation content, filters seamlessly operate on existing visual elements.</p> </li> <li> <p><code>collection_filter</code> (boolean): the interaction with visualised elements acts as a filter for a related collection or list of items (e.g., clicking a region on a map filters a list of items according to spatial metadata).</p> </li> <li> <p><code>aggregation</code> (boolean): changes to the granularity of visual elements according to a variable. It produces either visual data summarisations or segregations.</p> </li> <li> <p><code>btfw_interaction</code> (boolean): to identify the use of “breaking the fourth wall interactions” as defined [11]. It applies only to narratives.</p> </li> </ul> <p> </p> <p><strong>Narrative flow factors.</strong> Other categories aim to identify patterns in the design of narrative solutions. It is worth noticing that a project with multiple and diverse narratives can potentially report multiple design choices for the same column. Part of the factors and definitions from [12] are here re-used and adapted.</p> <p><em>Story layout </em>columns define the layout, or genre, of the narrative format:</p> <ul> <li> <p><code>document_layout</code> (boolean)</p> </li> <li> <p><code>slideshow_layout</code> (boolean)</p> </li> <li> <p><code>hybrid_layout</code> (boolean): mixing document and slideshow layouts.</p> </li> <li> <p><code>other_layout</code> (boolean): more complex solutions.</p> </li> </ul> <p><em>Role of visualisation</em> columns describe the role visualisations detain with respect to the entire story, in particular, with reference to the textual part of the narratives:</p> <ul> <li><code>equal_role</code> (boolean): visualisations and text play an equal role in the narrative.</li> <li><code>figure_role</code> (boolean): visualisations are supporting elements compared to the role of text.</li> <li><code>annotated_role</code> (boolean): visualisations are the drivers of the narrative.</li> </ul> <p><em>Story progression</em> columns categorise the shape of possible story paths:</p> <ul> <li> <p><code>linear_progression</code> (categorical): strongly author-driven or user-directed narrative. Possible values specify the potential to skip certain parts while not having a fully explorative experience:</p> </li> <ul> <li> <p>Skip</p> </li> <li> <p>No-skip</p> </li> </ul> <li> <p><code>user_directed</code> (bool): users can select a path among multiple alternatives and compose narrative pieces, providing a broder degree of interaction and exploration possibilities [1]. If a linear path can be suggested, here it remains merely one option among many others. Differently from a linear-skip approach, it has a low level of guidance oriented towards linear navigation.</p> </li> </ul> <p><em>Navigation input </em>columns define the ways users can move through the narrative:</p> <ul> <li> <p><code>button_input</code> (boolean)</p> </li> <li> <p><code>scroll_input</code> (boolean)</p> </li> <li> <p><code>slider_input</code> (boolean)</p> </li> </ul> <p><em>Navigation progress </em>columns describe methods through which the reader perceives its placement within the narrative:</p> <ul> <li> <p><code>text_progression</code> (boolean): text or numbers act as signifiers for user position.</p> </li> <li> <p><code>dots_progression</code> (boolean)</p> </li> <li> <p><code>visualisation_progression</code> (boolean): the visualisation used in the narrative, or a visualised progress widget acts as a signifier for user position.</p> </li> </ul> <p><em>Level of control </em>columns describe how much control a reader has over the text, visualisations, and animated transitions. Control could be discrete (D) when it triggers the motion, continuous (C) when it can act throughout all the keyframes, or hybrid (H) if it supports aspects of both. When animation is absent, control can be not available (NA). In particular, while visualisation control is related to the visualisation as a whole (e.g., the entire scatter plot moving up or down the page), the animated transition is related to more specific, data-relevant motion.<br>Columns:</p> <ul> <li> <p><code>text_control</code> (categorical):</p> </li> <ul> <li> <p>D</p> </li> <li> <p>C</p> </li> <li> <p>H</p> </li> </ul> <li> <p><code>visualisation_control</code> (categorical):</p> </li> <ul> <li> <p>D</p> </li> <li> <p>C</p> </li> <li> <p>H</p> </li> </ul> <li> <p><code>animation_control</code> (categorical):</p> </li> <ul> <li> <p>D</p> </li> <li> <p>C</p> </li> <li> <p>H</p> </li> <li> <p>NA</p> </li> </ul> </ul> <p> </p> <h2>References</h2> <p>[1] E. Segel and J. Heer, “Narrative Visualization: Telling Stories with Data,” IEEE Trans. Visual. Comput. Graphics, vol. 16, no. 6, pp. 1139–1148, 2010, doi: 10.1109/TVCG.2010.179.</p> <p>[2] M. Terras, J. Nyhan, and E. Vanhoutte, Defining Digital Humanities: A Reader. Routledge, 2016.</p> <p>[3] S. Schreibman, R. G. Siemens, and J. Unsworth, Eds., A companion to digital humanities. in Blackwell companions to literature and culture, no. 26. Malden, MA: Blackwell Pub, 2004.</p> <p>[4] C. Kinkeldey, A. M. MacEachren, and J. Schiewe, “How to Assess Visual Communication of Uncertainty? A Systematic Review of Geospatial Uncertainty Visualisation User Studies,” The Cartographic Journal, vol. 51, no. 4, pp. 372–386, 2014, doi: 10.1179/1743277414Y.0000000099.</p> <p>[5] G. Panagiotidou, H. Lamqaddam, J. Poblome, K. Brosens, K. Verbert, and A. Vande Moere, “Communicating Uncertainty in Digital Humanities Visualization Research,” IEEE Transactions on Visualization and Computer Graphics, vol. 29, no. 1, pp. 635–645, Jan. 2023, doi: 10.1109/TVCG.2022.3209436.</p> <p>[6] J. Drucker, “Humanities Approaches to Graphical Display,” Digital Humanities Quarterly, vol. 5, no. 1, 2011, Accessed: Sep. 17, 2024. [Online]. Available: <a href="https://www.digitalhumanities.org/dhq/vol/5/1/000091/000091.html">https://www.digitalhumanities.org/dhq/vol/5/1/000091/000091.html</a></p> <p>[7] F. Windhager et al., “Visualization of Cultural Heritage Collection Data: State of the Art and Future Challenges,” IEEE Trans. Visual. Comput. Graphics, vol. 25, no. 6, pp. 2311–2330, Jun. 2019, doi: 10.1109/TVCG.2018.2830759.</p> <p>[8] J. S. Yi, Y. A. Kang, J. Stasko, and J. A. Jacko, “Toward a Deeper Understanding of the Role of Interaction in Information Visualization,” IEEE Trans. Visual. Comput. Graphics, vol. 13, no. 6, pp. 1224–1231, 2007, doi: 10.1109/TVCG.2007.70515.</p> <p>[9] E. Dimara and C. Perin, “What is Interaction for Data Visualization?,” IEEE Transactions on Visualization and Computer Graphics, vol. 26, no. 1, pp. 119–129, Jan. 2020, doi: 10.1109/TVCG.2019.2934283.</p> <p>[10] M. Brehmer and T. Munzner, “A Multi-Level Typology of Abstract Visualization Tasks,” IEEE Trans. Visual. Comput. Graphics, vol. 19, no. 12, pp. 2376–2385, 2013, doi: 10.1109/TVCG.2013.124.</p> <p>[11] Y. Shi, T. Gao, X. Jiao, and N. Cao, “Breaking the Fourth Wall of Data Stories Through Interaction,” IEEE Trans. Visual. Comput. Graphics, pp. 1–11, 2022, doi: 10.1109/TVCG.2022.3209409.</p> <p>[12] S. McKenna, N. Henry Riche, B. Lee, J. Boy, and M. Meyer, “Visual Narrative Flow: Exploring Factors Shaping Data Visualization Story Reading Experiences,” Computer Graphics Forum, vol. 36, no. 3, pp. 377–387, 2017, doi: 10.1111/cgf.13195.</p> <p> </p> <h2>Fundings</h2> <p>Project funded by the European Union – NextGenerationEU under the National Recovery and Resilience Plan (NRRP), Investment I.4.1 - Borse PNRR Patrimonio Culturale.</p>
Technical Leverage Analysis in the Python Ecosystem
<p>Technical Leverage Analysis in the Python Ecosystem</p> <p>This dataset is the original dataset used in the publication [1]. It includes 21205 distinct package versions from the top 600 Python packages. An online demo for computing the proposed metrics for real-world software libraries is also available under the following URL: https://techleverage.eu/.</p> <p>This work has been partially funded by the EU under the H2020 Program AssureMOSS (Grant n. 952647). </p> <p>[1] DOI: 10.1007/s10664-023-10355-2</p>
Technical Leverage Dataset for Java Dependencies in Maven
<p>In finance, leverage is the ratio between assets borrowed from others and one's own assets. A matching situation is present in software: by using free open-source software (FOSS) libraries a developer leverages on other people's code to multiply the offered functionalities with a much smaller own codebase. In finance as in software, leverage magnifies profits when returns from borrowing exceed costs of integration, but it may also magnify losses, in particular in the presence of security vulnerabilities. We aim to understand the level of technical leverage in the FOSS ecosystem and whether it can be a potential source of security vulnerabilities. Also, we introduce two metrics change distance and change direction to capture the amount and the evolution of the dependency on third-party libraries. Our analysis published in [1] shows that small and medium libraries (less than 100KLoC) have disproportionately more leverage on FOSS dependencies in comparison to large libraries. We show that leverage pays off as leveraged libraries only add a 4% delay in the time interval between library releases while providing four times more code than their own. However, libraries with such leverage (i.e., 75% of libraries in our sample) also have 1.6 higher odds of being vulnerable in comparison to the libraries with lower leverage.</p> <p>This dataset is the original dataset used in the publication [1]. It includes 8494 distinct library versions from the FOSS Maven-based Java libraries An online demo for computing the proposed metrics for real-world software libraries is also available under the following URL: https://techleverage.eu/.</p> <p>The original publication is [1]. An executive summary of the results is avialble as the publication [2]. This work has been funded by the European Union with the project AssureMOSS (https://www.assuremoss.eu).</p> <p>[1] Massacci, F., & Pashchenko, I. (2021, May). Technical leverage in a software ecosystem: Development opportunities and security risks. In <em>2021 IEEE/ACM 43rd International Conference on Software Engineering (ICSE)</em> (pp. 1386-1397). IEEE.</p> <p>[2] Massacci, F., & Pashchenko, I. (2021). Technical Leverage: Dependencies Are a Mixed Blessing. <em>IEEE Secur. Priv.</em>, <em>19</em>(3), 58-62.</p>
Not So Weak-PICO: Leveraging weak supervision for Participants, Interventions, and Outcomes recognition for systematic review automation
<p>EBM-PICO is a widely used dataset with PICO annotations at two levels: span-level or coarse-grained and entity-level or fine-grained. Span-level annotations encompass the full information about each class. Entity-level annotations cover the more fine-grained information at the entity level, with PICO classes further divided into fine-grained subclasses. For example, the coarse-grained Participant span is further divided into participant age, gender, condition and sample size in the randomised controlled trial. This dataset comes pre-divided into a training set (n=4,933) annotated through crowd-sourcing and an expert annotated gold test set (n=191) for evaluation.</p> <p>The <a href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6174533/bin/NIHMS988059-supplement-Appendix.pdf">EBM-PICO annotation guidelines</a> caution about variable annotation quality. <a href="http://ceur-ws.org/Vol-2429/paper1.pdf">Abaho et al.</a> developed a framework to post-hoc correct EBM-PICO outcomes annotation inconsistencies. <a href="https://arxiv.org/pdf/1904.09557.pdf">Lee et al.</a> studied annotation span disagreements suggesting variability across the annotators. Low annotation quality in the training dataset is excusable, but the errors in the test set can lead to faulty evaluation of the downstream ML methods. We evaluate 1% of the EBM-PICO training set tokens to gauge the possible reasons for the fine-grained labelling errors and use this exercise to conduct an error-focused PICO re-annotation for the EBM-PICO gold test set. The file 'test_ebm_correctedlabels.tsv' has error corrected EBM-PICO gold test set.</p> <p> </p> <p>The upload also contains two zip files containing labelling sources mentioned in the Distant-PICO paper. </p> <ol> <li>ds_cto_dict.zip: contains the four distant supervision dictionaries (P: participant.txt, I = intervention.txt, intervetion_syn.txt, O: outcome.txt) generated from clinicaltrials.gov using the methodology described in Distant-CTO. </li> <li>handcrafted_dictionaries.zip: contains three files <ul> <li>gender_sexuality.txt: contains a list of possible genders and sexual orientations found across the web. The list is not comprehensive.</li> <li>endpoints_dict.txt: contains outcome names and the names of questionnaires used to measure outcomes assembled from PROM questionnaires and PROMs.</li> <li>comparator_dict: contains a list of idiosyncratic comparator terms like a sham, saline, placebo, etc., compiled from the literature search. The list is not comprehensive.</li> </ul> </li> </ol>
GWAS Summary Statistics for Publication: Identifying novel genetic and phenotypic associations to genomic features by leveraging off-target reads in exome sequencing data
<p>This dataset contains summary statistics for genome-wide association studies (GWAS) conducted on genomic features derived from off-target reads in whole-exome sequencing (WES) data. The study utilized tools like Seeing Beyond the Target (SBT) and ImReP to construct novel phenotypic features from unmapped reads in ~50,000 participants in the UK Biobank. Features include mitochondrial DNA (mtDNA) copy number, ribosomal DNA (rDNA) copy number (5S, 18S, 28S), immune repertoire metrics (e.g., T-cell receptor alpha diversity), and microvial genome load (viral and fungal).</p> <p>Summary statistics can be used for replication studies, meta-analyses, or further exploration of these phenotypes.</p>
Leveraging Serverless Computing for Continuous Integration and Delivery
<p>This work has been a first implementation of the usage of AWS Lambda for running CI/CD tasks. This has been implemented in TeamCity, a CI/CD tool by JetBrains. We investigated the possible solutions for using AWS Lambda for running CI/CD tasks, but also did a depth analysis on how it compares to Amazon ECS for running CI/CD tasks.</p> <p>We were able to understand that there are CI/CD tasks that can be optimised by making use of FaaS. These tasks must be able to be executed in under 15 minutes (or be splittable into 15 minutes tasks), and would benefit more if they're either a high throughput of tasks in a small period of time, or very little executions over time. These tasks will benefit from both a higher performance and cost efficiency.</p> <p>This package includes: </p> <ul> <li>TeamCity Backup - backup with all of the CI/CD configurations used for these experiments. It is important to mention that the replication of these experiments does require a license for TeamCity and to apply a new connection to AWS;</li> <li>Tasks Performance tests - all of the results obtained during the experiments led to our conclusions.</li> </ul>
M3-OCTA:Leveraging Multimodal Fusion for Enhanced Diagnosis of Multiple Retinal Diseases in Ultra-wide OCTA
<p>Ultra-wide optical coherence tomography angiography (UW-OCTA) is an emerging imaging technique that offers significant advantages over traditional OCTA by providing an exceptionally wide scanning range of up to 24 x 20 mm^{2}, covering both the anterior and posterior regions of the retina. However, the currently accessible UW-OCTA datasets suffer from limited comprehensive hierarchical information and corresponding disease annotations. To address this limitation, we have curated the pioneering M3OCTA dataset, which is the first multimodal (i.e., multilayer), multi-disease, and widest field-of-view UW-OCTA dataset. Furthermore, the effective utilization of multi-layer ultra-wide ocular vasculature information from UW-OCTA remains underdeveloped. To tackle this challenge, we propose the first cross-modal fusion framework that leverages multi-modal information for diagnosing multiple diseases. Through extensive experiments conducted on our openly available M3OCTA dataset, we demonstrate the effectiveness and superior performance of our method, both in fixed and varying modalities settings. The construction of the M3OCTA dataset, the first multimodal OCTA dataset encompassing multiple diseases, aims to advance research in the ophthalmic image analysis community.</p> <p>Our proposed M3OCTA is the first multi-modal based ultra-wide retinal OCTA dataset, involving 1637 scans from 1046 eyes of 620 individuals imaged in Zigong First People’s Hospital through 24×20 scan mode. Specifically, 1067 scans contains choroid large vessel image; images of 1310 scans from 496 people are labeled as six classes in multi-label setting, including healthy, diabetic retinopathy (DR), diabetic macular edema (DME), Retinal Vein Occlusion (RVO), Hypertension (HBP) and Vitreous Hemorrhage (VH), and then split into train, validation and test set as 6:2:2. The remaining unlabeled data are only used in the pretraining step. Details of our M3OCTA and other public ones are listed in Table.1. Compared with others, M3OCTA dataset demonstrates superiorities in several aspects including the number of modalities, number of patients, image resolution, and FOV.</p> <p> </p> <p><strong>You can request this dataset through signing the attached agreement. The download link will send to you. </strong></p>
Datasets for "Advancing Drug-Target Interactions Prediction: Leveraging a Large-Scale Dataset with a Rapid and Robust Chemogenomic Algorithm"
<p>All datasets required to reproduce the results of publication "Drug-Target Interactions Prediction at Scale: the Komet Algorithm with the LCIdb Dataset"</p>
Sensitivity Datasets - Leveraging Implicit Knowledge in Neural Networks for Functional Dissection and Engineering of Proteins
<p><strong>Leveraging Implicit Knowledge in Neural Networks for Functional Dissection and Engineering of Proteins</strong></p> <p>The Sensitivity datasets cover more than 800 proteins and are structured as follows. The sensitivity values are the mean of four DeeProtein replicates.</p> <p>It is uploaded as tar.gz. and contains one directory.</p> <p>File names contain the PDB<sup>1</sup> identifier and the respective chain identifier. </p> <p>The sequences and secondary structure information were downloaded from the RCSB Protein Databank and are available here: <a href="https://cdn.rcsb.org/etl/kabschSander/ss_dis.txt.gz">https://cdn.rcsb.org/etl/kabschSander/ss_dis.txt.gz</a> This URL can be found with some explanation at <a href="http://www.rcsb.org/pdb/static.do?p=download/http/index.html">http://www.rcsb.org/pdb/static.do?p=download/http/index.html</a></p> <p>The secondary structure annotation relies on the DSSP Algorithm by Kabsch and Sander<sup>2</sup>.</p> <p> </p> <p><strong>The files are tab-separated and contain the following columns:</strong></p> <ul> <li><strong>Pos</strong> Position in the sequence, starting from zero</li> <li><strong>AA</strong> Amino acid in that position</li> <li><strong>sec</strong> Secondary structure as annotated in the RCSB Protein Databank</li> <li><strong>dis</strong> if a region has not been experimentally observed (sometimes explains mismatches with crystal structures)</li> <li><strong>GO:_______</strong> Sensitivity for the GO term</li> </ul> <p><strong>References</strong></p> <ol> <li>The Protein Data Bank H.M. Berman, J. Westbrook, Z. Feng, G. Gilliland, T.N. Bhat, H. Weissig, I.N. Shindyalov, P.E. Bourne (2000) Nucleic Acids Research, 28: 235-242. doi:10.1093/nar/28.1.235</li> <li>Kabsch, W. & Sander, C. Dictionary of protein secondary structure: pattern recognition of hydrogen-bonded and geometrical features. Biopolymers 22, 2577-2637, doi:10.1002/bip.360221211 (1983).</li> </ol>
Data for: "Comprehensive sampling of coverage effects in catalysis by leveraging generalization in neural network models"
<p>This repository contains the raw data to reproduce the paper: "Comprehensive sampling of coverage effects in catalysis by leveraging generalization in neural network models". Within the .tar.gz file, you will find the directory structure described above.</p> <h2>Directory Structure</h2> <h3>`data`</h3> <p>Contains the data to reproduce all figures in the manuscript. Used primarily by the Jupyter Notebooks that plot the data from the paper.</p> <h3>`eval`</h3> <p>Contains the predicted energies according to a MACE model for the following systems and facets:<br>- covsplit (100, 111, 211, 331, 410, 711): The NN model is trained on low-coverage structures and tested on high-coverage structures for a single facet<br>- evencov (100, 111, 211, 331, 410, 711): The NN is trained on even coverages and tested on odd coverages for a single facet<br>- facet (100, 111, 211, 331, 410, 711): the NN is trained on the facet indicated by the folder name (e.g., facet-100 means that the model was trained on Cu(100)) and tested on all of the other facets.<br>- full: the model was trained on all facets and all coverages<br>- slopes (various versions and configurations): the models were trained with different body-order correlation (v) for the Cu(711) facet and tested only on the Cu(711) facet<br>- Rh111: Energies for the Rh(111) + CHOH + CO systems.</p> <h3>`mcmc`</h3> <p>Contains the data for MCMC (Markov Chain Monte Carlo) evaluations for two systems: Cu and Rh<br>- copper-mcmc-public.tar.gz<br>- rhodium-mcmc-public.tar.gz</p> <h3>`models`</h3> <p>Contains the weights and parameters of the best-performing MACE models trained in this work, as selected by the validation loss:</p> <p>File formats: `.model` and `_swa.model` relate to the first-stage of training and the second-stage of training.</p> <h3>`pyscripts`</h3> <p>Python scripts to perform the MCMC sampling given the custom configuration file `sample_cfg.json`.</p> <h3>`scripts`</h3> <p>Shell scripts for evaluation and training the MACE models, along with the hyperparameters used in doing so.</p> <p>- Evaluation scripts (eval-*.sh)<br>- Training scripts (train-*.sh)</p> <h3>`train`</h3> <p>Training, validation, and testing data for all Cu and Rh facets in this work, according to the naming scheme described above.</p> <p>- Rh111<br>- covsplit<br>- evencov<br>- facet<br>- full<br>- slopes</p>
Data and R-scripts for "Land-use trajectories for sustainable land system transformations: identifying leverage points in a global biodiversity hotspot" (V2)
<p>Sustainable land system transformations are necessary to avert biodiversity and climate collapse. However, it remains unclear where entry points for transformations exist in complex land systems. Here, we conceptualize land systems along land-use trajectories, which allows us to identify and evaluate leverage points; i.e., entry points on the trajectory where targeted interventions have particular leverage to influence land-use decisions. We apply this framework in the biodiversity hotspot Madagascar. In the Northeast, smallholder agriculture results in a land-use trajectory originating in old-growth forests, spanning forest fragments, and reaching shifting hill rice cultivation and vanilla agroforests. Integrating interdisciplinary empirical data on seven taxa, five ecosystem services, and three measures of agricultural productivity, we assess trade-offs and co-benefits of land-use decisions at three leverage points along the trajectory. These trade-offs and co-benefits differ between leverage points: two leverage points are situated at the conversion of old-growth forests and forest fragments to shifting cultivation and agroforestry, resulting in considerable trade-offs, especially between endemic biodiversity and agricultural productivity. Here, interventions enabling smallholders to conserve forests are necessary. This is urgent since ongoing forest loss threatens to eliminate these leverage points due to path-dependency. The third leverage point allows for the restoration of land under shifting cultivation through vanilla agroforests and offers co-benefits between restoration goals and agricultural productivity. The co-occurring leverage points highlight that conservation and restoration are simultaneously necessary. Methodologically, the framework shows how leverage points can be identified, evaluated, and harnessed for land system transformations under the consideration of path-dependency along trajectories.</p>
The datasets for "Automated Recovery of Issue-Commit Links Leveraging Both Textual and Non-textual Data" paper
<p>Paper title: Automated Recovery of Issue-Commit Links Leveraging Both Textual and Non-textual Data</p> <p>Conference: ICSME 2021</p>
Supplementary Material for 'Leveraging the GIDAS Database for the Criticality Analysis of Automated Driving Systems'
<p>This repository contains the supplementary material for the publication 'Leveraging the GIDAS Database for the Criticality Analysis of Automated Driving Systems'.<br> It consists of four files:</p> <ol> <li>Criticality-Phenomena-Catalog.CSV: The catalog of criticality phenomena (CP)</li> <li>Criticality-Phenomena-Phi-Coefficient.CSV: The calculation of the Phi coefficient between all pairs of CP</li> <li>Criticality-Phenomena-Risk-Calculation.CSV: The case-phenomenon relation matrix, including the calculated values for the risk of each CP for all three severity levels</li> <li>Criticality-Phenomena-Sorted-By-Risk.CSV: A list of the CP from the CP catalog sorted by risk for all three severity classes</li> </ol>
Dataset for Automatic Refactoring Candidate Identification Leveraging Effective Code Representation
<p>The dataset consists of positive and negative case methods for Extract Method refactoring for selected GitHub repositories.<br> <br> <em>Each sample format - </em></p> <pre><code class="language-json">{ "repo_name": "...", "repo_url": "...", "positive_case_methods": ["...", "...", ...], "negative_case_methods": ["...", "...", ...] }</code></pre> <p> </p>
Retrieving Affected Versions by Leveraging the Life Cycle of Defects
<p>This is the online appendix for our paper submission entitled "Retrieving Affected Versions by Leveraging the Life Cycle of Defects"</p>
Data for "The potential of water security in leveraging Agenda 2030"
<p>Data set of the linkages that water security has on other SDGs. The data are based on literature review and final data consists of 120 publications. The linkages are graded from -3 (cancelling) to +3 (indivisible) according Nilsson et al. classification. </p> <p>Prior to data collection, all the reviewers participated in training on SDGs and water security, and on review training before the work. Only papers with a link from water security to SDGs (not vice versa) were included. The resulting subset of 170 papers was then read and evaluated by all the authors independently, with a 10% random overlap on the papers (i.e. 17 of the papers were reviewed at least twice, by different people). During this process, another 50 papers were found to be irrelevant (e.g. due to full paper inaccessibility or questionnaire analysis with no inclusion of SDGs) and were therefore eliminated. The results are thus based on the 120 reviewed papers that we found to be suitable for the analysis. See the journal paper methods for more information, and Supplementary material for author bias analysis. </p> <p>The list of paper ID's can be found rom the journal paper in One Earth. Column "Review" indicates whether the analyzed publication was a review or an original research paper.</p> <p>1_waterresources_sec = an identified linkage to the water resources dimension of the water security concept</p> <p>2_human_sec = an identified linkage to the human security dimension of the water security concept</p> <p>3_national_sec = = an identified linkage to the national security dimension of the water security concept</p> <p>4_climate_sec = an identified linkage to the climate security dimension of the water security concept</p> <p>5_energy_sec = an identified linkage to the energy security dimension of the water security concept</p> <p>6_food_sec = an identified linkage to the food security dimension of the water security concept</p> <p>sdg_counts = the total number of SDGs with reported linkage of water security</p> <p>year = publication year </p>
Leveraging on Digital Signage Networks to Bring Connectivity to IoT Devices
<p>This dataset contains the open data related to the research paper:</p> <p><br /> J. David de Hoz, Jose Saldana, Julián Fernández-Navajas, José Ruiz-Mas, Rebeca Guerrero Rodríguez, Félix de Jesús Mar Luna, Raúl Iván Herrera González, "Leveraging on Digital Signage Networks to Bring Connectivity to IoT Devices," Telcon UNI 2015, Lima, Peru, Oct. 2015.</p> <p><br /> This work has been partly financed by CONACYT (PEI 682/2014); Servicios d TI de Durango S.A. de C.V.; Ateire S.A.C., and de ER H2020 Wi 5 project (Grant Agreement no: 644262). </p> <p><br /> The name of each of the files indicates the figure of the paper: for example, "figure_15.csv" includes the information used to generate the figure 15. In some cases, ".csv" and ".xlsx" files are provided, but they include the same information.</p> <p><br /> In the "measurements" folder, the results are provided, and also the scripts used to obtain them.</p>
Data for "Leveraging a Disdrometer Network to Develop a Probabilistic Precipitation Phase Model in Eastern Canada"
<p><a name="_Toc157072893"></a><strong>Abstract</strong>. This study presents a probabilistic model that partitions the precipitation phase based on hourly measurements from a network of radar-based disdrometers in eastern Canada. The network consists of 27 meteorological stations located in a boreal climate for the years 2020-2023. Precipitation phase observations showed a 2-m air temperature interval between 0-4°C where probabilities of occurrence of solid, liquid, or mixed precipitation significantly overlapped. Single-phase precipitation was also found to occur more frequently than mixed-phase precipitation. Probabilistic phase-guided partitioning (PGP) models of increasing complexity using random forest algorithms were developed. The PGP models classified the precipitation phase and partitioned the precipitation accordingly into solid and liquid amounts. PGP_basic is based on 2-m air temperature and site elevation, while PGP_hydromet integrates relative humidity. PGP_full includes all the above data plus atmospheric reanalysis data. The PGP models were compared to benchmark precipitation phase partitioning methods. These included a single temperature threshold model set at 1.5°C, a linear transition model with dual temperature thresholds of –0.38 and 5°C, and a psychrometric balance model. Among the benchmark models, the single temperature threshold had the best classification performance due to a low count of mixed-phase events. The other benchmark models tended to over-predict mixed-phase precipitation in order to decrease partitioning error. All PGP models showed significant phase classification improvement by reproducing the observed overlapping precipitation phases based on 2-m air temperature. In terms of partitioning error, PGP_full had the lowest RMSE and the least variability in performance. The RMSE of the single temperature threshold model was the highest and showed the greatest performance variability. The improvement of mixed-phase prediction remains a challenge. This study establishes a basis for integrating automated phase observations into a hydrometeorological observation network and developing probabilistic precipitation phase models.</p>
Data from: Leveraging satellite observations to reveal ecological drivers of pest densities across landscapes
<p>Landscape ecologists have long suggested that pest abundances increase in simplified, monoculture landscapes. However, tests of this theory often fail to predict pest population sizes in real-world agricultural fields. These failures may arise not only from variations in pest ecology but also from the widespread use of categorical land-use maps that do not adequately characterize habitat availability for pests. We used 1163 field-year observations of <em>Lygus hesperus</em> (Western Tarnished Plant Bug) densities in California cotton fields to determine whether integrating remotely sensed metrics of vegetation productivity and phenology into pest models could improve pest abundance analysis and prediction. Because <em>L. hesperus</em> often overwinters in non-crop vegetation, we predicted that pest abundances would peak on farms surrounded by more non-crop vegetation, especially when the non-crop vegetation is initially productive but then dries down early in the year, causing the pest to disperse into cotton fields. We found that the effect of non-crop habitat on pest densities varied across latitudes, with a positive relationship in the north and a negative one in the south. Aligning with our hypotheses, models predicted that <em>L. hesperus</em> densities were 35 times higher on farms surrounded by high versus low productivity non-crop vegetation (EVI area 350 vs. 50) and 2.8 times higher when dormancy occurred earlier versus later in the year (May 15 vs. June 30). Despite these strong and significant effects, we found that integrating these remote-sensing variables into land-use models only marginally improved pest density predictions in cotton compared to models with categorical land cover metrics alone. Together, our work suggests that the remote sensing variables analyzed here can advance our understanding of pest ecology, but not yet substantively increase the accuracy of pest abundance predictions.</p>
Data and results for the paper: "From Bugs to Benefits: Improving User Stories by Leveraging Crowd Knowledge with CrUISE-AC"
<div> <div>We provide the following files used in the study "From Bugs to Benefits: Improving User Stories by Leveraging Crowd Knowledge with CrUISE-AC".</div> <div>The paper has been accepted for presentation in the research track of the IEEE/ACM International Conference on Software Engineering (ICSE) 2025 and will be included in the conference proceedings.</div> <div>The preprint is available on <a href="http://arxiv.org/abs/2501.15181" target="_blank" rel="noopener">arXiv</a>.</div> <br> <div><strong>User stories e-commerce.xlsx</strong></div> <div>307 real-world user stories from 3 different eCommerce projects.</div> <br> <div><em>Project A</em> defines a complete set of requirements for a B2C focused onlineshop of a publishing house who aims do sell his own publications directly.</div> <div><em>Project B</em> contains a partial set of requirements for a B2C focused onlineshop of a bookseller.</div> <div><em>Project C</em> includes a subset of B2C and B2B requirements for an online bookstore, supplemented by an eProcurement module designed to provide information and automation for industrial customers.</div> <div>Most of the user stories come with additional acceptance criteria, written in unstructured natural language.</div> <br> <div>The user stories have been anonymized and the merchant's real names were replaced with neutral terms.</div> <br> <div>Columns</div> <div>- ID: a unique ID we assigned across all projects</div> <div>- Project: user story belongs to project A, B or C</div> <div>- Connextra: user story in connextra pattern</div> <div>- Acceptance Criteria: acceptance criteria that came with the user story</div> <br> <div><strong>User stories CMS.xlsx</strong></div> <div>34 CMS related user stories from a dataset that was originally created by</div> <div>*Lucassen, G., Dalpiaz, F., van der Werf, J.M.E., Brinkkemper, S.: Visualizing user</div> <div>story requirements at multiple granularity levels via semantic relatedness. In: Con-</div> <div>ceptual Modeling: 35th International Conference, ER 2016, Gifu, Japan, November</div> <div>14-17, 2016, Proceedings 35. pp. 463–478. Springer (2016)*</div> <br> <div>Columns</div> <div>- ID: a unique ID we assigned</div> <div>- Connextra: user story in connextra pattern</div> <br> <div><strong>Issues e-commerce.xlsx</strong></div> <div>54,396 issues, we harvested from seven different issue trackers between June 2011 and July 2024</div> <div>- magento2 (https://github.com/magento/magento2/issues)</div> <div>- nopCommerce (https://github.com/nopSolutions/nopCommerce/issues)</div> <div>- OpenCart (https://github.com/opencart/opencart/issues)</div> <div>- PrestaShop (https://github.com/PrestaShop/PrestaShop/issues)</div> <div>- Shopware5 (https://issues.shopware.com/?products=SW-5)</div> <div>- Shopware6 (https://issues.shopware.com/?products=SW-6)</div> <div>- WooCommerce (https://github.com/woocommerce/woocommerce/issues)</div> <br> <div>Columns</div> <div>- id: unique ID we have assigned</div> <div>- Issue Tracker: issue tracker this issue originates from</div> <div>- Title: title of the original issue</div> <div>- Body: body / description of the original issue</div> <div>- Preprocessed: result of preprocessing the issue as described in the paper</div> <div>- Sample: issue was part of our 3,500 sample issues we used to evaluate CrUISE-AC</div> <br> <div><strong>Issues CMS.xlsx</strong></div> <div>64,500 issues, we harvested from two different issue trackers between April 2002 and August 2024</div> <div>- Moodle (https://github.com/magento/magento2/issues)</div> <div>- Umbraco (https://github.com/nopSolutions/nopCommerce/issues)</div> <br> <div>Columns are the the same as for "Issues e-commerce.xlsx"</div> <br> <div><strong>trivia-trainingdata.csv</strong></div> Manually labelled dataset to train the trivia classifier. <div>The dataset contains 1916 phrases with an even distribution of 958 trivia and 958 non-trivia phrases.</div> <br> <div>- Label = 1: this sentence is trivia</div> <div>- Label = 0: this sentence is not considered trivia</div> <br> <div>Any source code was replaced by [CODE] to simplify the classification process. Source code in markdown could be identified easily as it is enclosed by a special character https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks</div> <br><strong>Prompts</strong><br> <div><em>prompt_match.txt</em>: prompt we used across all LLMs to assess, if an issue potentially might affect a given user story</div> <em>prompt_generate.txt</em>: GPT4-turbo prompt to convert an issue text into gherkin-style acceptance criteria for a given user story<br> <div><em>prompt_evaluate.txt</em>: GPT4-turbo prompt to assess the usefulness of a newly generated acceptance criteria for a given user story</div> <br> <div><strong>Evaluation e-commerce.xlsx</strong></div> issue / user story pairs, generated acceptance criteria and result of manual evaluation.<br> <div> </div> <div>Columns</div> <div>- StoryID: unique ID of the user story (refer to User stories e-commerce.xlsx)</div> <div>- IssueID: unique ID of the issue (refer to Issues e-commerce.xlsx)</div> <div>- Issue: preprocessed issue text used as basis to generate the acceptance criterion</div> <div>- Connextra: user story in connextra pattern</div> <div>- Existing AC: acceptance criteria that originally came with the user story</div> <div>- AC: by CrUISE-AC generated acceptance criterion</div> <div>- AC_Explanation: explanation generated by CrUISE-AC why this AC adds new knowledge to the current user story</div> <div>- E1: evaluation result by expert 1 (1 = AC adds relevant knowledge; 0 = AC is irrelevant)</div> <div>- E2: evaluation result by expert 2 (1 = AC adds relevant knowledge; 0 = AC is irrelevant)</div> <div>- E3: evaluation result by expert 3 (1 = AC adds relevant knowledge; 0 = AC is irrelevant)</div> <div>- E4: evaluation result by expert 4 (1 = AC adds relevant knowledge; 0 = AC is irrelevant)</div> <div>- 3/4 majority: did at least 3 experts assess this AC as relevant (1 = yes; 0 = no)</div> <br> <div><strong>Evaluation CMS.xlsx</strong></div> <div>- StoryID: unique ID of the user story (refer to User stories CMS.xlsx)</div> <div>- IssueID: unique ID of the issue (refer to Issues CMS.xlsx)</div> <div>- Issue: preprocessed issue text used as basis to generate the acceptance criterion</div> <div>- Connextra: user story in connextra pattern</div> <div>- AC: by CrUISE-AC generated acceptance criterion</div> <div>- AC_Explanation: explanation generated by CrUISE-AC why this AC adds new knowledge to the current user story</div> <div>- E1: evaluation result by expert 1 (1 = AC adds relevant knowledge; 0 = AC is irrelevant)</div> <div>- E4: evaluation result by expert 4 (1 = AC adds relevant knowledge; 0 = AC is irrelevant)</div> <div>- E5: evaluation result by expert 5 (1 = AC adds relevant knowledge; 0 = AC is irrelevant)</div> <div>- 2/3 majority: did at least 2 experts assess this AC as relevant (1 = yes; 0 = no)</div> </div>
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.