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.
13
datasets available to search
ShareScore release 0.7.1
Dataset results
13 results for “TensorFlow”
TensorFlow models for CK object detection
<p>Tarball containing the yolo model for the tensorflow object detection program in CK repositories</p> <p> </p>
code and data for A new method applied for the determination of relative weight ratios under the TensorFlow platform when estimating coseismic slip distribution
<p>The zip file contains three folders:"Data for Illapel earthquake", "HVCE and ABIC method implement on matlab" and "GDED method implement on tensorflow". Take the simulation experiments 1.2 and actual Illapel earthquakes as examples. the code for GDED method are placed on "GDED method implement on tensorflow" folders, and the code for the ABIC method and the HVCE method are place on "HVCE and ABIC method implement on matlab" folders.</p> <p>In the file"HVCE and ABIC method implement on matlab", the meaning of each code are represent as following</p> <p><br> ABIC_SIM.m:the slip distribution inversion results with the relative weight ratios determined by ABIC method Of simulation experiments and Illapel earthquakes</p> <p><br> HVCE.m:the slip distribution inversion results with the relative weight ratios determined by HVCE method Of simulation experiments and Illapel earthquakes</p> <p><br> GDED.m:the slip distribution inversion results with the relative weight ratios determined by GDED method Of simulation experiments and Illapel earthquakes(the relative weight ratios are from the "GDED method implement on tensorflow")</p> <p>savedata.m: that code are used for save matrix or data for the GDED method implement on tensorflow</p> <p>In the file"GDED method implement on tensorflow", the meaning of each code are represent as following<br> joint_inver_tensor_ex_1.0(1.1).py: the code for determining the relative weight ratios by the GDED method with(without) plot figures, which implement on Tensorflow platform<br> <br> the InSAR data and GPS data of Illapel earthquakes are palce on the folder" Data for Illapel earthquake/GPS_ori.txt and InSAR_ori.txt"</p>
Input Data for A Fast Surrogate Model for 3D-Earth Glacial Isostatic Adjustment using Tensorflow (v2.8.0) Artificial Neural Networks
<p>Training datasets for the manuscript A Fast Surrogate Model for 3D-Earth Glacial Isostatic Adjustment using Tensorflow (v2.8.0) Artificial Neural Networks. Two separate datasets are contained for training the ANNs: the 3D-spherically-symmetric (SS) rate-of-change of relative sea level (ROCRSL) and the 3D-SS rate of change of radial displacement (ROCRAD) as a function of SS profiles. Two other datasets contain RSL projections from the explicit (i.e. Seakon 3D - Seakon SS + NMSS ) model and the NMSS model, labelled Seakon_plus_NMSS_RSL and NMSS respectively.</p> <p>Filenames denote the structure of the SS profile: </p> <p>???_?.??_??.*.csv = LT_UMV_LMV.*.{csv,nc}<br> </p> <p>LT = elastic lithosphere thickness (km)</p> <p>UMV = upper mantle viscosity (1E21 Pa s)</p> <p>LMV = lower mantle viscosity (1E21 Pa s)</p> <p>i.e. 96_0.5_10.seakon_S40RTS_lr18-SS.rrad.roc.r360x180.P5.density_wSSRRADROC.csv.bz2 has the SS profile</p> <p>96km elastic lithosphere, 0.5E21 Pa s upper mantle viscosity, 10E21 Pa s lower mantle viscosity</p> <p> </p> <p>The columns of the input files are as follows:</p> <p>LT, UMV, LMV, longitude, latitude, time(t=0), ice(t=0), SS_ROC_RSL (t=0), time(t=-1), ice(t=-1), time(t=-2), ice(t=-2), time(t=-3), ice(t=-3), time(t=-4), ice(t=-4), 3D-SS_ROC_RSL(t=0)</p> <p>units for the above are as follows:</p> <p>km, 1E21 Pas, 1E2 Pas, degrees east (0->360), degrees (-180->180), days since 2000, m, mm/year, days since 2000, m, days since 2000, m, days since 2000, m, days since 2000, m, mm/year</p> <p>where 'days since 2000' assumes exactly 365.25 days per year.</p>
Replication Package of the Paper "How do Papers Make into Machine Learning Frameworks: A Preliminary Study on TensorFlow"
<p>This replication package contains datasets and scripts related to the paper: "<em>How do Papers Make into Machine Learning Frameworks: A Preliminary Study on TensorFlow</em>"</p> <ul> <li> <p><code>Contributor_Classification.csv</code>: contains the assignment of each contributor to a specific classification. The file contains the following columns:</p> <ul> <li><em>Date</em> : contains the date of each comment</li> <li><em>Type</em>: describe the type of a pull request (if it is Close, Commit, DESCR, Merge, PC, RC)</li> <li><em>ID</em> : specific ID of the comment</li> <li><em>Body</em> : contains the body of the comment analyzed</li> <li><em>Url</em> : link at each comments</li> <li><em>NumberPR</em> : number of a PR</li> <li><em>Name_Contributor</em>: contains the name of a contributor for each comment</li> <li><em>Contributor_classification</em>: contains the assignment of a specific classification (academic, bot, ML expert, software engineer, unknown), obtained after manual analysis, for each contributor of a comment</li> </ul> </li> <li> <p><code>Contributors_ManualAnalysis.csv</code>: contains the manual analysis performed by two authors to assign a classification for each contributor. The file contains the following columns:</p> <ul> <li><em>Contributors</em>: contains the name of the contributor for each comment</li> <li><em>Link GitHub</em>: contains the link to the GitHub page for each contributor</li> <li><em># PR</em>: contains the number of PRs in which a specific contributor is involved</li> <li><em>Annotator1</em>: manual classification of the first annotator</li> <li><em>Annotator2</em>: manual classification of the second annotator</li> <li><em>Final Classification</em>: contains the final label (academic, bot, ML expert, software engineer, unknown)assigned for each contributor</li> <li><em>Organization</em>: contains the organization, if any (Google, Hugging Face, Microsoft, OpenAI)</li> </ul> </li> <li> <p><code>ManualAnalysis.csv</code>: contains the manual analysis performed regarding Comment Type, Nature of Comment and Artifact. The .csv contains the following columns:</p> <ul> <li><em>URL</em>: contains the link to each comment</li> <li><em>NumberPR</em> : number of pull request</li> <li><em>CommentType1</em>: contains the classification of the first annotator in merit of comment type (Conventional review, Initial implementation, Management, ML review, Other)</li> <li><em>CommentType2</em>: contains the classification of the second annotator in merit of comment type (Conventional review, Initial implementation, Management, ML review, Other)</li> <li><em>NatureComment1</em>: contains the classification of the first annotator about the nature of the comment (Approval, Bug fix, Buid error, Clarification, Code, Code convention and spacing, Code review, Comment, Enhancement request, Explanation, Feedback, Introducing alternative implementation, Pinging, Plan for merging into TF, Question, References and referrals, Request a review, Request documentation improvement, Request test, Request verification, Review, Review assignment)</li> <li><em>NatureComment2</em>: contains the classification of the second annotator about the nature of the comment (Approval, Bug fix, Buid error, Clarification, Code, Code convention and spacing, Code review, Comment, Enhancement request, Explanation, Feedback, Introducing alternative implementation, Pinging, Plan for merging into TF, Question, References and referrals, Request a review, Request documentation improvement, Request test, Request verification, Review, Review assignment)</li> <li><em>Artifact1</em>: contains the classification of the first annotator with respect to the artifact (Article, Code, Commit, Issue/bug, Link, Review, Other)</li> <li><em>Artifact2</em>: contains the classification of the second annotator with respect to the artifact (Article, Code, Commit, Issue/bug, Link, Review, Other)</li> <li><em>FINALCommentType</em>: contains the final classification of the comment type after the resolution of the conflicts</li> <li><em>FINALNatureComment</em>: contains the final classification of the nature of the comment after resolution of conflicts</li> <li><em>FINALArtifact</em>: contains the final classification of the artifact after the resolution of conflicts</li> </ul> </li> <li> <p><code>Summary_PR.csv</code>: contains the details about the composition of each PRs. The file contains the following columns:</p> <ul> <li><em>#PullRequest</em>: contains the number of all pull requests analyzed</li> <li><em>#events</em>: contains the number of all the events analyzed for each PR</li> <li><em>#comments</em>: contains the number of all comments for each PR</li> <li><em>#Commit</em>:contains the number of Commit for each PR</li> <li><em>PC</em>: contains the number of PC for each PR</li> <li><em>RC</em>: contains the number of RC for each PR</li> </ul> </li> <li> <p><code>Total_PR_Comments.csv</code>: contains information about all comments analyzed. The columns are:</p> <ul> <li><em>Date</em>: contains the date of each comment</li> <li><em>Type</em>: describes the type of a pull request (if it is Close, Commit, DESCR, Merge, PC, RC)</li> <li><em>ID</em>: SHAn of the comment</li> <li><em>NumberPR</em>: PR number</li> <li><em>Name_Contributor</em>: contains the name of a contributor for each comment</li> <li><em>Body</em>: contains the body of the comment analyzed</li> <li><em>Url</em>: link at each comment</li> </ul> </li> </ul> <p>The replication also contains a directory <code>results</code> in which there are quantitative results. The directory contains:</p> <ul> <li> <p><code>Artifacts.csv</code>: This file contains the results for the artifact. The columns are:</p> <ul> <li><em>#PullRequest</em>: number of the pull request analyzed</li> <li><em>Article</em>: contains the percentage of the occurrences of the article in the specific pull request</li> <li><em>Code</em>: contains the percentage of the occurrences of the code in the specific pull request</li> <li><em>Commit</em>: contains the percentage of the occurrences of the commit in the specific pull request</li> <li><em>Issue reference</em>: contains the percentage of the occurrences of the issue reference in the specific pull request</li> <li><em>External link</em>: contains the percentage of the occurrences of the external link in the specific pull request</li> <li><em>Review</em>: contains the percentage of the occurrences of the review in the specific pull request</li> <li><em>Other</em>: contains the percentage of the occurrences of the other in the specific pull request</li> </ul> <p>ßAlso, the <code>Mean_Value</code> row contains the mean value of all occurrences for each column (Article, Code, Commit, Issue reference, External link, Review, Other)</p> </li> <li> <p><code>CommentType.csv</code>: this file contains the results for the comment type. The columns are:</p> <ul> <li><em>#PullRequest</em>:number of the pull request analyzed</li> <li><em>Conventional review</em>: contains the percentage of the occurrences of the conventional review in the specific pull request</li> <li><em>Initial implementation</em>: contains the percentage of the occurrences of the initial implementation in the specific pull request</li> <li><em>Management</em>: contains the percentage of the occurrences of the management in the specific pull request</li> <li><em>ML review</em>: contains the percentage of the occurrences of the ML review in the specific pull request</li> <li><em>Other</em>: contains the percentage of the occurrences of the Other in the specific pull request</li> </ul> <p>Also, the <code>Mean_Value</code> row contains the mean value of all occurrences for each column (Conventional review, Initial implementation, Management, ML review, Other)</p> </li> <li> <p><code>Contributor.csv</code>: this file contains the results for the contributors. The columns are:</p> <ul> <li><em>#PullRequest</em>: number of the pull requests analyzed</li> <li><em>academic</em>: contains the percentage of the occurrences of the academic in the specific pull request</li> <li><em>bot</em>: contains the percentage of the occurrences of the bot in the specific pull request</li> <li><em>ML expert</em>: contains the percentage of the occurrences of the ML expert in the specific pull request</li> <li><em>software engineer</em>: contains the percentage of the occurrences of the software engineer in the specific pull request</li> <li><em>unknown</em>: contains the percentage of the occurrences of unknown in the specific pull request</li> </ul> <p>Also, the <code>Mean_Value</code> row contains the mean value of all occurrences for each column (academic, bot, ML expert, software engineer, unknown)</p> </li> </ul>
Detect, Fix, and Verify TensorFlow API Misuses - SANER 2022 - Experimental Data
<p>Detect, Fix, and Verify TensorFlow API Misuses - SANER 2022</p> <p>Experimental data</p>
Tensorflow MusicVAE Model for SAMPLES
<p>Download and unzip to use MusicVAE functionalities with SAMPLES.</p>
TensorFlow Flower Detection Dataset
<p>TensorFlow Flower Dataset (https://www.tensorflow.org/datasets/catalog/tf_flowers) is a public open-access flower dataset for classification with images characterized by distinct flower types, backgrounds, and resolutions. TensorFlow Flower Detection Dataset consist of the same images with the associated annotations in the YOLO format which can be utilized for flower detection. We use the CVAT software to annotate more than 3 500 images, which resulted in more than 14 000 bounding boxes.</p> <p>The images and annotations are stored in an archive with the following structure:</p> <p><em>TensorFlowFlowerDetectionDataset/</em></p> <ol> <li><em>labels/</em></li> <li><em>images/</em></li> </ol> <p>Each annotation file links to its image by the file name, so if an image is named <strong>"2431737309_1468526f8b.jpg</strong><em><strong>"</strong></em>, its annotation files are named <strong>"2431737309_1468526f8b.txt"</strong> in YOLO format.</p>
Wlutz TensorFlow Training Data
<p>Wlutz TensorFlow Training Data</p>
ai-matrix CNN_Tensorflow graphs_NCHW
<p>Large files in ai-matrix.</p>
ai-matrix CNN_Tensorflow graphs_NHWC
<p>Large files in ai-matrix.</p>
ai-matrix CNN_Tensorflow
<p>Large files in ai-matrix.</p>
Wlutz TensorFlow Training Data
<p>Wlutz TensorFlow Training Data</p>
ai-matrix SSD_Tensorflow
<p>Large files in ai-matrix.</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.