Skip to main content
Powered by ShareScore

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.

1,356

datasets available to search

ShareScore release 0.9.0

Reset

Dataset results

1,356 results for “Human Activities”

Learn how ShareScore rates datasets ↗
zenodo52/100

Human Kino-Dynamic Measurements Dataset for Factory-like Activities

<p>This dataset was created as a part of the study presented in IEEE Transactions on Human-Machine Systems with the title &quot;An Online Multi-Index Approach to Human Ergonomics Assessment in the Workplace&quot; by Marta Lorenzini, Wansoo Kim and Arash Ajoudani. This paper introduces an online approach to monitor kinematic and dynamic quantities on the workers, providing on the spot an estimate of the physical load required in their daily jobs. A set of ergonomic indexes is defined to account for multiple potential contributors to work-related musculoskeletal disorders (WMSDs), which remain one of the major occupational safety and health problems in the European Union nowadays. Thus, the continuous tracking of workers&rsquo; exposure to the factors that may contribute to their development is paramount. To evaluate the proposed framework, a throughout experimental analysis was conducted.</p> <p>Twelve healthy adult subjects were recruited in the experimental study to perform, in the laboratory settings, occupational activities that are commonly carried out by workers in the current industrial scenario. Three tasks were selected to encompass the most significant risk factors in the workplace: mechanical overloading of the body joints, variable and high-intensity interaction forces, and repetitive and monotonous movements. Accordingly, lifting/lowering of a heavy object, drilling, and painting with a lightweight tool were considered, respectively, in this study. While the subjects were carrying out such activities, the data regarding the whole-body motion and the forces exchanged with the environment (both ground reaction force (GRF) and interaction forces at the end-effector) were collected. In addition, ten surface electromyography (sEMG) sensors were placed on the body of each subject to measure muscle activity as a reference to the effective physical effort required for the tasks.</p> <p>The whole experimental procedure was carried out in accordance with the Declaration of Helsinki and the protocol was approved by the ethics committee azienda sanitaria locale (ASL) Genovese N.3 (Protocol IIT_HRII_ERGOLEAN 156/2020).</p>

opencc-by-4.0Oct 2021View details →
zenodo48/100

Inactive to active transition of human Thymidine Kinase 1 revealed by Molecular Dynamics simulations

<p>The trajectories and input files for the manuscript <em>Inactive to active transition of human Thymidine</em></p> <p><em>Kinase 1 revealed by Molecular Dynamics simulations</em> (<a href="https://doi.org/10.1021/acs.jcim.1c01157">https://doi.org/10.1021/acs.jcim.1c01157</a>)&nbsp;</p> <p>ABSTRACT</p> <p>Despite its importance for the nucleoside (and nucleoside prodrug) metabolism, the structure<br> of the active conformation of human Thymidine Kinase 1 (hTK1) remains elusive. We perform<br> microsecond molecular dynamics simulations of the inactive enzyme form bound to a<br> bisubstrate inhibitor that was shown experimentally to activate another TK1-like kinase,<br> Thermotoga maritima TK (TmTK). Our results are in excellent agreement with the<br> experimental findings for the TmTK closed-to-open state transition. We show that the inhibitor<br> induces an increase of the enzyme radius of gyration due to the expansion on one of the dimer<br> interfaces; the structural changes observed, including the active site pocket volume increase,<br> decrease in monomer-monomer buried surface area and of the number of hydrogen bonds (as<br> compared to the inactive enzyme control simulation), show that the catalytically competent<br> (open) conformation of hTK1 can be assumed in the presence of an activating ligand.</p>

opencc-by-4.0Dec 2021View details →
zenodo48/100

Dataset Activation of Lactate Receptor HCAR1 Down-modulates Neuronal Activity in Rodent and Human Brain Tissue

<p>This dataset is related to the study:&nbsp;</p> <p>Briquet M, Rocher AB, Alessandri M, Rosenberg N, de Castro Abrantes H, Wellbourne-Wood J, Schmuziger C, Ginet V, Puyal J, Pralong E, Daniel RT, Offermanns S, Chatton JY. Activation of lactate receptor HCAR1 down-modulates neuronal activity in rodent and human brain tissue. J Cereb Blood Flow Metab. 2022 Mar 3:271678X221080324. doi: 10.1177/0271678X221080324. Epub ahead of print. PMID: 35240875.</p>

opencc-by-4.0Mar 2022View details →
zenodo48/100

PALEODEM/ What burned the forest? Wildfires, climate change and human activity during the Mesolithic – Neolithic transition in SE Iberian Peninsula

<p>This repository contains new XRD data from the Villena paleolake, archaeological radiocarbon evidence from the Villena area and the R code used to produce Summed Probability distribution analyses.&nbsp;&nbsp;</p> <p>They correspond to the following reference:&nbsp;&nbsp;</p> <p>S&aacute;nchez-Garc&iacute;a, C., Revelles, J., Burjachs, F., Euba, I., Exp&oacute;sito, I., Ib&aacute;&ntilde;ez, J., Schulte, L., Fern&aacute;ndez-L&oacute;pez de Pablo, J.&nbsp;What burned the forest? Wildfires, climate change and human activity during the Mesolithic &ndash; Neolithic transition in SE Iberian Peninsula (submitted to Catena).&nbsp;</p> <p>We specify the content of file further down:</p> <ul> <li>Vinalopo.csv: the list of radiocarbon dates from Villena spanning ca.9500-5500 cal BP from the following sites: Arenal de la Virgen, Cueva del Lagrimal and Casa Corona.&nbsp;</li> <li>ngrip.csv: NGRIP GICC05 paleotemperature record based on oxygen isotope series from Rasmussen SO&nbsp;<em>et al.</em>2006 A new Greenland ice core chronology for the last glacial termination.&nbsp;<em>J. Geophys. Res. Atmos.</em><strong>111</strong>. (doi:10.1029/2005JD006079) and&nbsp;Andersen KK&nbsp;<em>et al.</em>2006 The Greenland Ice Core Chronology 2005, 15&ndash;42ka.&nbsp;Part 1: constructing the time scale.&nbsp;<em>Quat. Sci. Rev.</em>25, 3246&ndash;3257.</li> <li>Char.csv:&nbsp;&nbsp;Sedimentary charcoal data set from the Villena Paleolake (VL3 core) published by Jones, S.E., Burjachs, F., Fern&aacute;ndez-L&oacute;pez de Pablo (2018)&nbsp;DOI/10.5281/zenodo.1244003, according to the new Bacon chronological model of the Villena paleolake (Fern&aacute;ndez-L&oacute;pez de Pablo et al., 2022&nbsp;. Impacts of Early Holocene environmental dynamics on open-air occupation patterns in the Western Mediterranean: insights from El Arenal de la Virgen (Alicante, Spain).&nbsp;<a href="https://doi.org/10.31235/osf.io/5yqsr">https://doi.org/10.31235/osf.io/5yqsr</a>)</li> <li>SPD_analysis.R: R script with the code to reproduce the SPD analysis presented in the manuscript.&nbsp;</li> <li>SupplMat1xlsl: an excel file&nbsp;This file is composed by 8 spreadsheets:</li> </ul> <ol> <li>&lsquo;Selected variables 12.6-5.5&rsquo;: all the data included in the time frame 12600-5500 cal BP, interpolated to 50 yr time windows. These data have been used for the Spearmans&rsquo;rs correlation analysis (see spreadsheet &lsquo;Spearmans&rsquo;rs 12.6-5.5&rsquo; to track the results), Detrended Correspondence Analysis (see spreadsheet &lsquo;Figure 5_DCA 12.6-5.5&rsquo; to track the results) and have been plotted in Figure 3 and 7.&nbsp;</li> <li>&#39;Selected variables 9.1-5.5&rsquo;: data included in the analysis focused on the time period 9.1-5.5 cal BP, interpolated to 50 yr time windows. These data have been used for the Spearmans&rsquo;rs correlation analysis (see spreadsheet &lsquo;Spearmans&rsquo;rs 9.1-5.5&rsquo; to track the results), Detrended Correspondence Analysis (see spreadsheet &lsquo;Figure 6_DCA 9.1-5.5&rsquo; to track the results) and have been plotted in Figure 8.</li> <li>&lsquo;Spearmans&rsquo;rs 12.6-5.5&rsquo;: Spearmans&rsquo;rs correlation analysis applied to the 12600-5500 cal BP dataset (data from &lsquo;Selected variables 12.6-5.5&rsquo;).</li> <li>&lsquo;Spearmans&rsquo;rs 9.1-5.5 cal BP&rsquo; Spearmans&rsquo;rs correlation analysis applied to the 9100-5500 cal BP dataset, including here high-resolution XRD data (data from &lsquo;Selected variables 9.1-5.5&rsquo;).</li> <li>&lsquo;Figure 2 charcoal results&rsquo;: original sedimentary charcoal results provided in this work. Data plotted in Figure 2.&nbsp;</li> <li>&lsquo;Figure 4 XRD results&rsquo;: original XRD results provided in this work. Data plotted in Figure 4.</li> <li>&lsquo;Figure 5 DCA 12.6-5.5&rsquo;: results of Detrended Correspondence analysis focused on the time period from 12600 to 5500 cal BP. Data plotted in Figure 5.</li> <li>&lsquo;Figure 6 DCA 9.1-5.5&rsquo; results of Detrended Correspondence analysis focused on the time period from 9100 to 5500 cal BP, including here high-resolution XRD data. Data plotted in Figure 6.</li> </ol>

opencc-by-4.0Nov 2022View details →
zenodo48/100

Non-invasive modulation of human corticostriatal activity [Dataset]

<p>This dataset contains resting-state functional MRI data used in the study &quot;Non-invasive modulation of human corticostriatal activity&quot; (Caballero-Insaurriaga et al, PNAS, 2023).</p> <p>In this study two datasets were used: one from a transcranial static-magnetic-field stimulation (tSMS) experiment (tSMS20) and another one from the Human Connectome Project (HCP100). The tSMS20 dataset was originally acquired for a previous study tSMS over the Supplementary Motor Area (Pineda-Pardo et al, Commun Biol, 2019). The regions used in the study are also provided.</p> <p>As for the tSMS20 dataset, the stimulation protocol consisted of 30-minute tSMS using a single magnet placed over the supplementary motor area (SMA). Each subject underwent two stimulation sessions (real and sham) in two separate days, whose order was randomized. In each session, structural MRI was acquired before tSMS, and resting-state fMRI before and after. Structural images were T1-weighted (T1w), with 1 mm isotropic voxel. Functional data was acquired in 10 minutes-long sessions, TR/TE 2400/30 ms (250 volumes per session), with 3mm isotropic voxel. The preprocessed resting-state fMRI data are included in this repository (see dataset_description.txt file and Pineda-Pardo et al, Commun Biol, 2019 for more details)</p> <p>As for the HCP100 dataset, only the subject list is included, as data are already publicly available from the HCP initiative.</p> <p>If you use this data in a publication, please cite:</p> <p>Pineda-Pardo, J. A., Obeso, I., Guida, P., Dileone, M., Strange, B. A., Obeso, J. A., Oliviero, A. &amp; Foffani, G. Static magnetic field stimulation of the supplementary motor area modulates resting-state activity and motor behavior. <em>Communications Biology</em> <strong>2,</strong> (2019)</p> <p>Caballero-Insaurriaga, J., Pineda-Pardo, J. A., Obeso, I., Oliviero, A. &amp; Foffani, G. Non-invasive modulation of human corticostriatal activity. <em>Proceedings of the National Academy of Sciences of the United States of America</em> (2023)</p>

opencc-by-4.0Mar 2023View details →
zenodo44/100

Human Hyperpolarization Activated Cyclic Nucleotide Gated Ion Channel 4 (HCN4); A Target Enabling Package

<p>HCN4 is one of four hyperpolarisation activated cyclic nucleotide gated ion channels. It is responsible for the pacemaker or funny (If) current in the heart and is required for maintenance of a stable heartbeat. Mutations in HCN4 lead to a number of arrhythmias. HCN4 is the target for the angina drug ivabradine, which reduces HCN4 activity. However, ivabradine is non-selective, affecting all of the four HCN channels. HCN4 is a close homologue of HCN2, which is a target for neuropathic and inflammatory pain treatment. We have solved the structure of HCN4 both in complex with cyclic AMP and without nucleotide. Comparison of our HCN4 structure with that of the related HCN1 channel (86% identity) allows us to suggest ways to design selectivity for small molecule inhibitors between these closely related channels. &nbsp;</p>

opencc-by-4.0Oct 2018View details →
zenodo44/100

Image captioning dataset for human activities

<p>An image captioning dataset including images of humans performing various activities. The included images include the following activities: <code>walking, running, sleeping, swimming, sitting, jumping, riding, climbing, drinking and reading.</code></p>

opencc-by-4.0Jan 2021View details →
zenodo44/100

Wallhack1.8k Dataset | Data Augmentation Techniques for Cross-Domain WiFi CSI-Based Human Activity Recognition

<p>This repository contains the <strong>Wallhack1.8k dataset</strong> for WiFi-based long-range activity recognition in Line-of-Sight (LoS) and Non-Line-of-Sight (NLoS)/Through-Wall scenarios, as proposed in [1,2], as well as the <strong>CAD models</strong> (of 3D-printable parts) of the WiFi systems proposed in [2].</p> <p><strong>PyTroch Dataloader</strong></p> <p>A minimal PyTorch dataloader for the Wallhack1.8k dataset is provided at: <a href="https://github.com/StrohmayerJ/wallhack1.8k" target="_blank" rel="noopener">https://github.com/StrohmayerJ/wallhack1.8k</a></p> <p><strong>Dataset Description</strong></p> <p>The Wallhack1.8k dataset comprises 1,806 CSI amplitude spectrograms (and raw WiFi packet time series) corresponding to three activity classes: "no presence," "walking," and "walking + arm-waving." WiFi packets were transmitted at a frequency of 100 Hz, and each spectrogram captures a temporal context of approximately 4 seconds (400 WiFi packets).</p> <p>To assess cross-scenario and cross-system generalization, WiFi packet sequences were collected in LoS and through-wall (NLoS) scenarios, utilizing two different WiFi systems (BQ: biquad antenna and PIFA: printed inverted-F antenna). The dataset is structured accordingly:</p> <ul> <li>LOS/BQ/ &lt;- WiFi packets collected in the LoS scenario using the BQ system</li> <li>LOS/PIFA/ &lt;-&nbsp;WiFi packets collected in the LoS scenario using the PIFA system</li> <li>NLOS/BQ/ &lt;-&nbsp;WiFi packets collected in the NLoS scenario using the BQ system</li> <li>NLOS/PIFA/ &lt;-&nbsp;WiFi packets collected in the NLoS scenario using the PIFA system</li> </ul> <p>These directories contain the raw WiFi packet time series (see Table 1).&nbsp;Each row represents a single WiFi packet with the complex CSI vector <em>H</em> being stored in the "data" field and the class label being stored in the "class" field. <em>H </em>is of the form [I, R, I, R, ..., I, R], where two consecutive entries represent imaginary and real parts of complex numbers (the Channel Frequency Responses of subcarriers).&nbsp;Taking the absolute value of&nbsp;<em>H</em>&nbsp;(e.g., via <em>numpy.abs(H)</em>) yields the subcarrier amplitudes <em>A</em>.</p> <p>To extract the 52 L-LTF subcarriers used in [1], the following indices of <em>A</em>&nbsp;are to be selected:</p> <pre><code># 52 L-LTF subcarriers csi_valid_subcarrier_index = [] csi_valid_subcarrier_index += [i for i in range(6, 32)] csi_valid_subcarrier_index += [i for i in range(33, 59)]</code></pre> <p>Additional 56 HT-LTF subcarriers can be selected via:</p> <pre><code># 56 HT-LTF subcarriers csi_valid_subcarrier_index += [i for i in range(66, 94)] csi_valid_subcarrier_index += [i for i in range(95, 123)]</code></pre> <p>For more details on subcarrier selection, see <a href="https://docs.espressif.com/projects/esp-idf/en/stable/esp32/api-guides/wifi.html">ESP-IDF</a> (Section Wi-Fi Channel State Information) and&nbsp;<a href="https://github.com/espressif/esp-csi">esp-csi</a>.</p> <p>Extracted amplitude spectrograms with the corresponding label files of the train/validation/test split: "trainLabels.csv," "validationLabels.csv," and "testLabels.csv," can be found in the <em>spectrograms/</em> directory.</p> <p>The columns in the label files correspond to the following: [Spectrogram index, Class label, Room label]</p> <ul> <li>Spectrogram index: [0, ..., n]</li> <li>Class label: [0,1,2], where 0 = "no presence", 1 = "walking", and 2 = "walking + arm-waving."</li> <li>Room label: [0,1,2,3,4,5], where labels 1-5 correspond to the room number in the NLoS scenario (see Fig. 3 in [1]). The label 0 corresponds to no room and is used for the "no presence" class.</li> </ul> <p><strong>Dataset Overview:</strong></p> <p>Table 1: Raw WiFi packet sequences.</p> <table> <tbody> <tr> <td><strong>Scenario</strong></td> <td><strong>System</strong></td> <td><em>"no presence" / &nbsp;label 0</em></td> <td><em>"walking"&nbsp; / label 1</em></td> <td><em>"walking + arm-waving" /&nbsp; label 2</em></td> <td><strong>Total</strong></td> </tr> <tr> <td>LoS</td> <td>BQ</td> <td>b1.csv</td> <td>w1.csv, w2.csv, w3.csv, w4.csv and w5.csv</td> <td>ww1.csv, ww2.csv, ww3.csv, ww4.csv and ww5.csv</td> <td>&nbsp;</td> </tr> <tr> <td>LoS</td> <td>PIFA</td> <td>b1.csv</td> <td>w1.csv, w2.csv, w3.csv, w4.csv and w5.csv</td> <td>ww1.csv, ww2.csv, ww3.csv, ww4.csv and ww5.csv</td> <td>&nbsp;</td> </tr> <tr> <td>NLoS</td> <td>BQ</td> <td>b1.csv</td> <td>w1.csv, w2.csv, w3.csv, w4.csv and w5.csv</td> <td>ww1.csv, ww2.csv, ww3.csv, ww4.csv and ww5.csv</td> <td>&nbsp;</td> </tr> <tr> <td>NLoS</td> <td>PIFA</td> <td>b1.csv</td> <td>w1.csv, w2.csv, w3.csv, w4.csv and w5.csv</td> <td>ww1.csv, ww2.csv, ww3.csv, ww4.csv and ww5.csv</td> <td>&nbsp;</td> </tr> <tr> <td>&nbsp;</td> <td>&nbsp;</td> <td>4</td> <td>20</td> <td>20</td> <td><strong>44</strong></td> </tr> </tbody> </table> <p>Table 2: Sample/Spectrogram distribution across activity classes in Wallhack1.8k.</p> <table> <tbody> <tr> <td><strong>Scenario</strong></td> <td><strong>System</strong></td> <td> <p><em>"no presence" / </em>&nbsp;label 0</p> </td> <td> <p><em>"walking"</em>&nbsp; / label 1</p> </td> <td><em>"walking + arm-waving" /&nbsp; </em>label 2</td> <td><strong>Total</strong></td> </tr> <tr> <td>LoS</td> <td>BQ</td> <td>149</td> <td>154</td> <td>155</td> <td>&nbsp;</td> </tr> <tr> <td>LoS</td> <td>PIFA</td> <td>149</td> <td>160</td> <td>152</td> <td>&nbsp;</td> </tr> <tr> <td>NLoS</td> <td>BQ</td> <td>148</td> <td>150</td> <td>152</td> <td>&nbsp;</td> </tr> <tr> <td>NLoS</td> <td>PIFA</td> <td>143</td> <td>147</td> <td>147</td> <td>&nbsp;</td> </tr> <tr> <td>&nbsp;</td> <td>&nbsp;</td> <td>589</td> <td>611</td> <td>606</td> <td><strong>1,806</strong></td> </tr> </tbody> </table> <p>&nbsp;</p> <p><strong>Download and Use</strong><br>This data may be used for non-commercial research purposes only. If you publish material based on this data, we request that you include a reference to one of our papers [1,2].</p> <p>[1] Strohmayer, Julian, and Martin Kampel. (2024). &ldquo;Data Augmentation Techniques for Cross-Domain WiFi CSI-Based Human Activity Recognition&rdquo;,&nbsp;<em>In IFIP International Conference on Artificial Intelligence Applications and Innovations</em>&nbsp;(pp. 42-56). Cham: Springer Nature Switzerland<em>,</em>&nbsp;doi:&nbsp;<a href="https://doi.org/10.1007/978-3-031-63211-2_4" target="_blank" rel="noopener">https://doi.org/10.1007/978-3-031-63211-2_4</a>.</p> <p>[2] Strohmayer, Julian, and Martin Kampel., &ldquo;Directional Antenna Systems for Long-Range Through-Wall Human Activity Recognition,&rdquo;&nbsp;<em>2024 IEEE International Conference on Image Processing (ICIP)</em>, Abu Dhabi, United Arab Emirates, 2024, pp. 3594-3599, doi:&nbsp;<a href="https://doi.org/10.1109/ICIP51287.2024.10647666" target="_blank" rel="noopener">https://doi.org/10.1109/ICIP51287.2024.10647666</a>.</p> <p>BibTeX citations:</p> <pre>@inproceedings{strohmayer2024data, title={Data Augmentation Techniques for Cross-Domain WiFi CSI-Based Human Activity Recognition}, author={Strohmayer, Julian and Kampel, Martin}, booktitle={IFIP International Conference on Artificial Intelligence Applications and Innovations}, pages={42--56}, year={2024}, organization={Springer}}<br><br>@INPROCEEDINGS{10647666,<br>&nbsp; author={Strohmayer, Julian and Kampel, Martin},<br>&nbsp; booktitle={2024 IEEE International Conference on Image Processing (ICIP)},&nbsp;<br>&nbsp; title={Directional Antenna Systems for Long-Range Through-Wall Human Activity Recognition},&nbsp;<br>&nbsp; year={2024},<br>&nbsp; volume={},<br>&nbsp; number={},<br>&nbsp; pages={3594-3599},<br>&nbsp; keywords={Visualization;Accuracy;System performance;Directional antennas;Directive antennas;Reflector antennas;Sensors;Human Activity Recognition;WiFi;Channel State Information;Through-Wall Sensing;ESP32},<br>&nbsp; doi={10.1109/ICIP51287.2024.10647666}}<br><br><br></pre>

opencc-by-4.0Oct 2024View details →
zenodo44/100

Dataset: WiFi-based Human Activity Recognition using Raspberry Pi

<p>This dataset contains 980 802.11 Channel State Information&nbsp;captures for 11 activities performed in a small apartment by 1 subject. For full description, check README.md.</p>

openmit-licenseOct 2021View details →
zenodo44/100

Dataset for Stimulus-specific plasticity in human visual gamma-band activity and functional connectivity

<p>Per-trial dataset accompanying the publication Stauch, Peter, Schuler, and Fries (2020): Stimulus-specific plasticity in human visual gamma-band activity and functional connectivity.<br> Additionaly, preprocessing code is provided as Codebase.zip.</p>

opencc-by-4.0Nov 2020View details →
zenodo44/100

Prefrontal cortex activation and functional connectivity during human male orgasm measured with fNIRS

<p>A portable fNIRS system Brite MKII (Artinis, NE) was placed on the PFC of the self-experimenting participant (Male, 43 years). Ten sources and eight detectors are combined into 22 long separation channels (30mm) and two short-separation channels (SSC) to cover the PFC (Figure 1A). The experiment lasted 392s where the participant was subject to pornographic video clips (V) and performed genital self-stimulation (M) until orgasm was reached (O).<br>Citation of the article related to this dataset:</p> <div> <div><strong>Guevara, E.</strong> (2024). <em>Prefrontal cortex activation and functional connectivity during human male orgasm measured with fNIRS</em> [Preprint]. OSF. <a href="https://doi.org/10.31219/osf.io/6y2ze">https://doi.org/10.31219/osf.io/6y2ze</a></div> </div>

opencc-by-4.0Oct 2023View details →
zenodo44/100

Data from: Selectivity of Guanine Nucleotide Exchange Factor-mediated Cdc42 activation in primary human endothelial cells

<p>Data that was reported in &quot;Selectivity of Guanine Nucleotide Exchange Factor-mediated Cdc42 activation in primary human endothelial cells&quot; by&nbsp;</p> <p>Nathalie R. Reinhard<sup>1</sup>, Sanne van der Niet<sup>1</sup>, Anna Chertkova<sup>1</sup>, Marten Postma<sup>1</sup>, Theodorus W.J. Gadella Jr.<sup>1</sup>, Peter L. Hordijk<sup>1,2</sup>, and Joachim Goedhart<sup>1*</sup><br> &nbsp;</p> <p><strong>Affiliations:</strong></p> <p><sup>1&nbsp;</sup>University of Amsterdam, Molecular Cytology, Swammerdam Institute for Life Sciences, van Leeuwenhoek Centre for Advanced Microscopy, Amsterdam, the Netherlands</p> <p><sup>2&nbsp;</sup>Department of Physiology, Free University Medical Center, Amsterdam, The Netherlands</p> <p>&nbsp;</p> <p>*Correspondence to: j.goedhart@uva.nl</p>

opencc-by-4.0Jan 2019View details →
zenodo44/100

Human activity classification

<p>Collected dataset comprises body position recordings for various persons of diverse profile while performing six&nbsp;physical activities.</p> <p>The values include:&nbsp;</p> <p>- Cod_pat is the unique code for each person;<br> - Time is the timestamp;<br> - Ax, Ay, Az represent the axis of the acceleration;<br> - Mx, My, Mz represent the axis of the magnetometer;<br> - Ch is the compass heading;<br> - Label is the Class that provide the activity of the person.</p> <p>&nbsp;</p>

opencc-by-4.0Dec 2018View details →
zenodo44/100

Shape, membrane morphology, and morphodynamic response of metabolically active human mitochondria revealed by scanning ion conductance microscopy

<p>This contains the hole data set as well as all analysed data for the paper published in Beilstein Journal of Nanotechnology "Shape, membrane morphology and morphodynamic response of metabolically active human mitochondria revealed by Scanning Ion Conductance Microscopy".</p> <p>Most of the images were taken with the SICM. These uncompressed tiff files can be read and processed with the Gwyddion software or other scanning probe image processing software.</p>

opencc-by-4.0Dec 2023View details →
zenodo44/100

Comparable respiratory activity in attached and suspended human fibroblasts

<p>Zdrazilova L, Hansikova H, Gnaiger E (2021) Comparable respiratory activity in attached and suspended human fibroblasts. MitoFit Preprints 2021.7. <a href="http://dx.doi.org/10.26124/mitofit:2021-0007">doi:10.26124/mitofit:2021-0007</a></p> <p>All respirometric data are expressed in SI units and are made available here Open Access.</p>

opencc-by-4.0Sep 2021View details →
zenodo44/100

Chromatin activity identifies differential gene regulation across human ancestries

<p>This repository contains data related to:</p> <p>Chromatin activity identifies differential gene regulation across human ancestries</p> <p>Kade P. Pettie, Maxwell Mumbach, Amanda J. Lea, Julien Ayroles, Howard Y. Chang, Maya Kasowski, Hunter B. Fraser</p> <p>&nbsp;</p>

opencc-by-4.0Nov 2022View details →
zenodo44/100

Datasets for "Targeted insertion and reporter transgene activity at a gene safe harbor of the human blood fluke, Schistosoma mansoni"

<p>To identify sites that could serve as potential genomic safe harbours (GSHs)&nbsp;for transgene integration, we conducted a genome-wide bioinformatic search based on established, widely accepted criteria, along with newly introduced criteria (below), that would satisfy benign and stable gene expression.&nbsp;</p> <p>At the outset, we identified <strong>euchromatic</strong> regions in all developmental stages of&nbsp;<em>S. mansoni&nbsp;</em>to avoid silencing genes to be integrated upon CRISPR/Cas manipulation. With these criteria, we enriched for regions that were, (i) close to peaks of H3K4me3, a histone modification that is associated with euchromatin and transcription start sites, (ii) regions that did not include H3K27me3, a histone modification that is associated with heterochromatin, (iii) regions of open euchromatin accessible to Tn5 integration, in an Assay of Transposase Accessible Chromatin sequencing (ATAC-seq) providing a positive display of integration events, and (iv) given that HIV-1 integrates preferentially into euchromatin in human cell lines, we used sites of HIV proviral integration known from&nbsp;<em>S. mansoni</em>&nbsp;to likewise support predictions of euchromatic regions.</p> <p>Examination of the draft genome of&nbsp;<em>S. mansoni</em>&nbsp;in Worm Base Parasite, version 7 (WormBase Parasite)&nbsp;identified 6,884 regions with enrichment of H3K4me3 in the absence of H3K27me3 in available developmental stages (H3K4me3 not K3K27me3). In mature, adult schistosomes, we found consistently 10,533 ATAC positive regions. There were 4,027 ATAC regions that overlapped with H3K4me3 but not K3K27me3, and 2,915 genes overlapped with (ATAC and H3K4me3 not H3K27me3).&nbsp;Forty-two unambiguous HIV integration sites were identified, and eight genes were &le; 11 kb upstream or downstream from these integration sites.&nbsp;Repeats were masked with RepeatMasker V4.1.0 using a specific repeat library produced with RepeatModeler2 V2.0.1 and stored as a GFF file.</p> <p>To identify intergenic GSH, we located 10,149 intergenic regions.&nbsp;&nbsp;There were 9,985 regions beyond 2 kb upstream and 8,837 regions outside long non-coding-RNA (lncRNA), which were intersected to 95,587 unique intergenic regions outside 2 kb and lncRNA of &ge;100 bp.&nbsp;&nbsp;Two hundred regions were identified intersecting with merged ATAC H3K4me3 signal. Four of these were situated &le;&nbsp;11 kb distance from HIV integration sites.&nbsp;</p> <p>Made at George Washington University,&nbsp;Justus Liebig University Giessen,&nbsp;Khon Kaen University,&nbsp;Naresuan University,&nbsp;Aberystwyth University,&nbsp;Schistosomiasis Resource Center,&nbsp;IHPE.&nbsp;</p>

opencc-by-4.0Dec 2022View details →
zenodo44/100

A Dataset of Bot and Human Activities in GitHub

<p><strong>A Dataset of Bot and Human Activities in GitHub</strong></p> <p>This repository provides an updated version of a&nbsp;dataset of GitHub contributor activities that is accompanied&nbsp;by a paper published at MSR 2023 in the <strong>Data and Tool Showcase Track</strong>. The paper is entitled <strong>A Dataset of Bot and Human Activities in GitHub</strong> and is co-authored by Natarajan Chidambaram, Alexandre Decan and Tom Mens (Software Engineering Lab, University of Mons, Belgium). DOI: <a href="https://www.doi.org/10.1109/MSR59073.2023.00070">https://www.doi.org/10.1109/MSR59073.2023.00070</a>. This work is done as a part of Natarajan Chdiambaram's PhD research in the context of <a href="https://www.digitalwallonia.be/ia/">DigitalWallonia4.AI research project ARIAC (grant number 2010235)</a> and <a href="https://trail.ac/en/">TRAIL</a>.</p> <p>The dataset contains 1,015,422&nbsp;high-level activities made by 350 bots and 620&nbsp;human&nbsp;contributors on GitHub between 25 November 2022 and 15&nbsp;April&nbsp;2023. The activities were generated from 1,221,907&nbsp;low-level events obtained from the GitHub's Event API and cover 24 distinct activity types. This dataset facilitates the characterisation of bot and human behaviour in GitHub repositories, by enabling the analysis of activity sequences and activity patterns of bot and human contributors. This dataset could lead to better bot identification tools and empirical studies on how bots play a role in collaborative software development.</p> <p><strong>Files description</strong></p> <p>The following files are provided as part of the archive:</p> <ul> <li>bot_activities.json - A JSON file containing 754,165&nbsp;activities made by 350 bot contributors;</li> <li>human_activities.json - A JSON file containing 261,258&nbsp;activities made by 620&nbsp;human contributors (anonymized);</li> <li>JsonSchema.json - A JSON schema that validates the above datasets;</li> <li>bots.txt - A TEXT file containing&nbsp;login names of all the 350 bots</li> </ul> <p><strong>Example</strong></p> <p>Below is an example of a <em>Closing pull request</em> activity:</p> <pre><code>{ "date": "2022-11-25T18:49:09+00:00", "activity": "Closing pull request", "contributor": "typescript-bot", "repository": "DefinitelyTyped/DefinitelyTyped", "comment": { "length": 249, "GH_node": "IC_kwDOAFz6BM5PJG7l" }, "pull_request": { "id": 62328, "title": "[qunit] Add `test.each()`", "created_at": "2022-09-19T17:34:28+00:00", "status": "closed", "closed_at": "2022-11-25T18:49:08+00:00", "merged": false, "GH_node": "PR_kwDOAFz6BM4_N5ib" }, "conversation": { "comments": 19 }, "payload": { "pr_commits": 1, "pr_changed_files": 5 } }</code></pre> <p><strong>List of activity types</strong></p> <p>In total, we have identified 24 different high-level activity types from 15 different low-level event types. They are <em>Creating repository</em>, <em>Creating branch</em>, <em>Creating tag</em>, <em>Deleting tag</em>, <em>Deleting repository</em>, <em>Publishing a release</em>, <em>Making repository public</em>, <em>Adding collaborator to repository</em>, <em>Forking repository</em>, <em>Starring repository</em>, <em>Editing wiki page</em>, <em>Opening issue</em>, <em>Closing issue</em>, <em>Reopening issue</em>, <em>Transferring issue</em>, <em>Commenting issue</em>, <em>Opening pull request</em>, <em>Closing pull request</em>, <em>Reopening pull request</em>, <em>Commenting pull request</em>, <em>Commenting pull request changes</em>, <em>Reviewing code</em>, <em>Commenting commits</em>, <em>Pushing commits</em>.</p> <p><strong>List of fields</strong></p> <p>Not only does the dataset contain a list of activities made by bot and human contributors, but it also contains some details about these activities. For example, <em>commenting issue</em> activities provide details about the author of the comment, the repository and issue in which the comment was created, and so on.</p> <p>For all activity types, we provide the <strong>date</strong> of the activity, the <strong>contributor</strong> that made the activity, and the <strong>repository</strong> in which the activity took place. Depending on the activity type, additional fields are provided. In this section, we describe for each activity type the different fields that are provided in the JSON file. It is worth to mention that we also provide the corresponding JSON schema alongside with the datasets.</p> <p><em><strong>Properties</strong></em></p> <ul> <li><strong>date</strong> <ul> <li>Date on which the activity is performed</li> <li>Type: <code>string</code></li> <li>e.g., "2022-11-25T09:55:19+00:00"</li> <li>String format must be a "date-time"</li> </ul> </li> <li><strong>activity</strong> <ul> <li>The activity performed by the contributor</li> <li>Type: <code>string</code></li> <li>e.g., "Commenting pull request"</li> </ul> </li> <li><strong>contributor</strong> <ul> <li>The login name of the contributor who performed this activity</li> <li>Type: <code>string</code></li> <li>e.g., "analysis-bot", "anonymised" in the case of a human contributor</li> </ul> </li> <li><strong>repository</strong> <ul> <li>The repository in which the activity is performed</li> <li>Type: <code>string</code></li> <li>e.g., "apache/spark", "anonymised" in the case of a human contributor</li> </ul> </li> <li><strong>issue</strong> <ul> <li>Issue information - provided for <em>Opening issue</em>, <em>Closing issue, Reopening issue</em>, <em>Transferring issue</em> and <em>Commenting issue</em></li> <li>Type: <code>object</code></li> <li><em><strong>Properties</strong></em> <ul> <li><strong>id</strong> <ul> <li>Issue number</li> <li>Type: <code>integer</code></li> <li>e.g., 35471</li> </ul> </li> <li><strong>title</strong> <ul> <li>Issue title</li> <li>Type: <code>string</code></li> <li>e.g., "error building handtracking gpu example with bazel", "anonymised" in the case of a human contributor</li> </ul> </li> <li><strong>created_at</strong> <ul> <li>The date on which this issue is created</li> <li>Type: <code>string</code></li> <li>e.g., "2022-11-10T13:07:23+00:00"</li> <li>String format must be a "date-time"</li> </ul> </li> <li><strong>status</strong> <ul> <li>Current state of the issue</li> <li>Type: <code>string</code></li> <li>"open" or "closed"</li> </ul> </li> <li><strong>closed_at</strong> <ul> <li>The date on which this issue is closed. "null" will be provided if the issue is open</li> <li>Types: <code>string</code>, <code>null</code></li> <li>e.g., "2022-11-25T10:42:39+00:00"</li> <li>String format must be a "date-time"</li> </ul> </li> <li><strong>resolved</strong> <ul> <li>The issue is resolved or not_planned/still open</li> <li>Type: <code>boolean</code></li> <li>true or false</li> </ul> </li> <li><strong>GH_node</strong> <ul> <li>The GitHub node of this issue</li> <li>Type: <code>string</code></li> <li>e.g., "IC_kwDOC27xRM5PHTBU", "anonymised" in the case of a human contributor</li> </ul> </li> </ul> </li> </ul> </li> <li><strong>pull_request</strong> <ul> <li>Pull request information - provided for <em>Opening pull request</em>, <em>Closing pull request</em>, <em>Reopening pull request</em>, <em>Commenting pull request changes</em> and <em>Reviewing code</em></li> <li>Type: <code>object</code></li> <li><em><strong>Properties</strong></em> <ul> <li><strong>id</strong> <ul> <li>Pull request number</li> <li>Type: <code>integer</code></li> <li>e.g., 35471</li> </ul> </li> <li><strong>title</strong> <ul> <li>Pull request title</li> <li>Type: <code>string</code></li> <li>e.g., "error building handtracking gpu example with bazel", "anonymised" in the case of a human contributor</li> </ul> </li> <li><strong>created_at</strong> <ul> <li>The date on which this pull request is created</li> <li>Type: <code>string</code></li> <li>e.g., "2022-11-10T13:07:23+00:00"</li> <li>String format must be a "date-time"</li> </ul> </li> <li><strong>status</strong> <ul> <li>Current state of the pull request</li> <li>Type: <code>string</code></li> <li>"open" or "closed"</li> </ul> </li> <li><strong>closed_at</strong> <ul> <li>The date on which this pull request is closed. "null" will be provided if the pull request is open</li> <li>Types: <code>string</code>, <code>null</code></li> <li>e.g., "2022-11-25T10:42:39+00:00"</li> <li>String format must be a "date-time"</li> </ul> </li> <li><strong>merged</strong> <ul> <li>The PR is merged or rejected/still open</li> <li>Type: <code>boolean</code></li> <li>true or false</li> </ul> </li> <li><strong>GH_node</strong> <ul> <li>The GitHub node of this pull request</li> <li>Type: <code>string</code></li> <li>e.g., "PR_kwDOC7Q2kM5Dsu3-", "anonymised" in the case of a human contributor</li> </ul> </li> </ul> </li> </ul> </li> <li><strong>review</strong> <ul> <li>Pull request review information - provided for <em>Reviewing code</em></li> <li>Type: <code>object</code></li> <li><em><strong>Properties</strong></em> <ul> <li><strong>status</strong> <ul> <li>Status of the review</li> <li>Type: <code>string</code></li> <li>"changes_requested" or "approved" or "dismissed"</li> </ul> </li> <li><strong>GH_node</strong> <ul> <li>The GitHub node of this review</li> <li>Type: <code>string</code></li> <li>e.g., "PRR_kwDOEBHXU85HLfIn", "anonymised" in the case of a human contributor</li> </ul> </li> </ul> </li> </ul> </li> <li><strong>conversation</strong> <ul> <li>Comments information in issue or pull request - Provided for <em>Opening issue</em>, <em>Closing issue</em>, <em>Reopening issue</em>, <em>Transferring issue</em>, <em>Commenting issue</em>, <em>Opening pull request</em>, <em>Closing pull request</em>, <em>Reopening pull request</em> and <em>Commenting pull request</em></li> <li>Type: <code>object</code></li> <li><em><strong>Properties</strong></em> <ul> <li><strong>comments</strong> <ul> <li>Number of comments present in the corresponding issue or pull request</li> <li>Type: <code>integer</code></li> <li>e.g., 5</li> </ul> </li> </ul> </li> </ul> </li> <li><strong>comment</strong> <ul> <li>Comment information - Provided for all the activities for which the field issue or pull_request is reported and additionally for commit comment</li> <li>Type: <code>object</code></li> <li><em><strong>Properties</strong></em> <ul> <li><strong>length</strong> <ul> <li>Length of the comment text (or description text if comment is not provided)</li> <li>Type: <code>integer</code></li> <li>e.g., 25</li> </ul> </li> <li><strong>GH_node</strong> <ul> <li>The GitHub node of this comment or description. "null" will be provided if there is no comment expected</li> <li>Types: <code>string</code>, <code>null</code></li> <li>e.g., "IC_kwDOEj6V8c5PHT78", "anonymised" in the case of a human contributor</li> </ul> </li> </ul> </li> </ul> </li> <li><strong>gitref</strong> <ul> <li>Tag information - provided for <em>Creating branch</em>, <em>Creating tag</em>, <em>Deleting branch</em>, <em>Deleting tag</em>, <em>Editing wiki page</em> and <em>Publishing a release</em></li> <li>Type: <code>object</code></li> <li><em><strong>Properties</strong></em> <ul> <li><strong>type</strong> <ul> <li>Type of the gitref</li> <li>Type: <code>string</code></li> <li>"tag" or "branch" or "commit"</li> </ul> </li> <li><strong>name</strong> <ul> <li>Name of the gitref</li> <li>Type: <code>string</code></li> <li>e.g., "cherry-pick-11-to-release-4.10"</li> </ul> </li> <li><strong>description_length</strong> <ul> <li>Length of the description text provided while creating the gitref. "null" be provided if the type is "branch" or "commit" as they do not have any description</li> <li>Type: <code>integer</code>, <code>null</code></li> <li>e.g., 23</li> </ul> </li> </ul> </li> </ul> </li> <li><strong>release</strong> <ul> <li>Release information - provided for <em>Publishing a release</em></li> <li>Type: <code>object</code></li> <li><em><strong>Properties</strong></em> <ul> <li><strong>name</strong> <ul> <li>The name of the release that is created. "null" will be provided if the name is not provided</li> <li>Type: <code>string</code>, <code>null</code></li> <li>e.g., "v0.65.9"</li> </ul> </li> <li><strong>description_length</strong> <ul> <li>Length of the description of the release that is created</li> <li>Type: <code>integer</code></li> <li>e.g., 888</li> </ul> </li> <li><strong>created_at</strong> <ul> <li>The date at which the release is created (activity date is the release published date)</li> <li>Type: <code>string</code></li> <li>e.g., "2022-11-25T11:34:48+00:00"</li> <li>String format must be a "date-time"</li> </ul> </li> <li><strong>prerelease</strong> <ul> <li>If the release that is created is a prerelease or not</li> <li>Type: <code>boolean</code></li> <li>true or false</li> </ul> </li> <li><strong>new_tag</strong> <ul> <li>If a new tag is created for this release or another tag is re-used</li> <li>Type: <code>boolean</code></li> <li>true or false</li> </ul> </li> <li><strong>GH_node</strong> <ul> <li>The corresponding release node ID</li> <li>Type: <code>string</code></li> <li>e.g., "RE_kwDOCm6M2s4FBGxT", "anonymised" in the case of a human contributor</li> </ul> </li> </ul> </li> </ul> </li> <li><strong>page</strong> <ul> <li>Page information - provided for <em>Editing wiki page</em></li> <li>Type: <code>object</code></li> <li><em><strong>Properties</strong></em> <ul> <li><strong>name</strong> <ul> <li>Name of the page</li> <li>Type: <code>string</code></li> <li>e.g., "Workflow-status"</li> </ul> </li> <li><strong>title</strong> <ul> <li>Title of the page</li> <li>Type: <code>string</code></li> <li>e.g., "Workflow status"</li> </ul> </li> <li><strong>new</strong> <ul> <li>If the page is created new or existing page is edited</li> <li>Type: <code>boolean</code></li> <li>true or false</li> </ul> </li> </ul> </li> </ul> </li> <li><strong>payload</strong> <ul> <li>Other additional details - Provided for <em>Opening pull request</em>, <em>Closing pull request</em>, <em>Reopening pull request</em> and <em>pushing commits</em></li> <li>Type: <code>object</code></li> <li><em><strong>Properties</strong></em> <ul> <li><strong>pr_commits</strong> <ul> <li>The number of commits in this pull request</li> <li>Type: <code>integer</code></li> <li>e.g., 3</li> </ul> </li> <li><strong>pr_changed_files</strong> <ul> <li>The number of files that are changed in this pull request</li> <li>Type: <code>integer</code></li> <li>e.g., 2</li> </ul> </li> <li><strong>pushed_commits</strong> <ul> <li>The number of commits present in this push</li> <li>Type: <code>integer</code></li> <li>e.g., 4</li> </ul> </li> <li><strong>distinct_pushed_commits</strong> <ul> <li>The distinct number of commits present in this push</li> <li>Type: <code>integer</code></li> <li>e.g., 1</li> </ul> </li> <li><strong>github_push_id</strong> <ul> <li>The corresponding GitHub push ID</li> <li>Type: <code>integer</code></li> <li>e.g., 11790446870, "anonymised" in the case of a human contributor</li> </ul> </li> </ul> </li> </ul> </li> </ul> <p><strong>Mapping between activities and events</strong></p> <p>For many activity types, the corresponding activity can be observed by the occurrence of a single event type. For example, the activity types <em>Forking repository</em> and <em>Starring repository</em> would require the occurrence of a single event type for each as given below.</p> <table> <tbody><tr> <th>Activity type</th> <th>Event type</th> <th>Payload</th> </tr> </tbody><tbody> <tr> <td><em>Forking repository</em></td> <td><code>ForkEvent</code></td> <td>-</td> </tr> <tr> <td><em>Starring repository</em></td> <td><code>WatchEvent</code></td> <td>action = "started"</td> </tr> </tbody> </table> <p>However, in some cases, the same event type yields different activity types depending on the value present in the payload. For example, three different activity types can be generated from the same low-level event type CreateEvent, depending on the value of its ref_type (either "repository", "branch", or "tag") present in the payload.</p> <table> <tbody><tr> <th>Activity type</th> <th>Event type</th> <th>Payload</th> </tr> </tbody><tbody> <tr> <td><em>Creating repository</em></td> <td><code>CreateEvent</code></td> <td>ref_type = "repository"</td> </tr> <tr> <td><em>Creating branch</em></td> <td><code>CreateEvent</code></td> <td>ref_type = "branch"</td> </tr> <tr> <td><em>Creating tag</em></td> <td><code>CreateEvent</code></td> <td>ref_type = "tag"</td> </tr> </tbody> </table> <p>In some cases, there is no one-to-one mapping between events and activities. This is because some actions on GitHub may generate more than a single event and lead to a sequence of one mandatory event and a second optional event (marked with&nbsp;<em>?</em>). For example, for the activity type <em>Publishing a release</em>, event type ReleaseEvent is mandatory with payload's action value = "published", while event type CreateEvent is optional as it is required only when a new tag is created along with the published release.</p> <table> <tbody><tr> <th>Activity type</th> <th>Event type</th> <th>Payload</th> </tr> </tbody><tbody> <tr> <td><em>Publishing a release</em></td> <td><code>ReleaseEvent</code></td> <td>action = "published"</td> </tr> <tr> <td>&nbsp;</td> <td><em>?</em> <code>CreateEvent</code></td> <td>ref_type = "tag"</td> </tr> </tbody> </table> <p>All the identified activities along with their events type(s) and payload information is given in the following table.</p> <table> <tbody><tr> <th>Activity type</th> <th>Event type</th> <th>Payload</th> </tr> </tbody><tbody> <tr> <td><em>Creating repository</em></td> <td><code>CreateEvent</code></td> <td>ref_type = "repository"</td> </tr> <tr> <td><em>Creating branch</em></td> <td><code>CreateEvent</code></td> <td>ref_type = "branch"</td> </tr> <tr> <td><em>Creating tag</em></td> <td><code>CreateEvent</code></td> <td>ref_type = "tag"</td> </tr> <tr> <td><em>Deleting tag</em></td> <td><code>DeleteEvent</code></td> <td>ref_type = "tag"</td> </tr> <tr> <td><em>Deleting repository</em></td> <td><code>DeleteEvent</code></td> <td>ref_type = "branch"</td> </tr> <tr> <td><em>Publishing a release</em></td> <td><code>ReleaseEvent</code></td> <td>action = "published"</td> </tr> <tr> <td>&nbsp;</td> <td><em>?</em> <code>CreateEvent</code></td> <td>ref_type = "tag"</td> </tr> <tr> <td><em>Making repository public</em></td> <td><code>PublicEvent</code></td> <td>-</td> </tr> <tr> <td><em>Adding collaborator to repository</em></td> <td><code>MemberEvent</code></td> <td>action = "added"</td> </tr> <tr> <td><em>Forking repository</em></td> <td><code>ForkEvent</code></td> <td>-</td> </tr> <tr> <td><em>Starring repository</em></td> <td><code>WatchEvent</code></td> <td>action = "started"</td> </tr> <tr> <td><em>Editing wiki page</em></td> <td><code>GollumEvent</code></td> <td>pages--&gt;action = "created" or "edited"</td> </tr> <tr> <td><em>Opening issue</em></td> <td><code>IssuesEvent</code></td> <td>action = "opened"</td> </tr> <tr> <td><em>Closing issue</em></td> <td><code>IssuesEvent</code></td> <td>action = "closed"</td> </tr> <tr> <td>&nbsp;</td> <td><em>?</em> <code>IssueCommentEvent</code></td> <td>action = "created"</td> </tr> <tr> <td><em>Reopening issue</em></td> <td><code>IssuesEvent</code></td> <td>action = "reopened"</td> </tr> <tr> <td>&nbsp;</td> <td><em>?</em> <code>IssueCommentEvent</code></td> <td>action = "created"</td> </tr> <tr> <td><em>Transferring issue</em></td> <td><code>IssuesEvent</code></td> <td>action = "opened"</td> </tr> <tr> <td><em>Commenting issue</em></td> <td><code>IssueCommentEvent</code></td> <td>action = "created"</td> </tr> <tr> <td><em>Opening pull request</em></td> <td><code>PullRequestEvent</code></td> <td>action = "opened"</td> </tr> <tr> <td><em>Closing pull request</em></td> <td><code>PullRequestEvent</code></td> <td>action = "closed"</td> </tr> <tr> <td>&nbsp;</td> <td><em>?</em> <code>IssueCommentEvent</code></td> <td>action = "created"</td> </tr> <tr> <td><em>Reopening pull request</em></td> <td><code>PullRequestEvent</code></td> <td>action = "opened"</td> </tr> <tr> <td>&nbsp;</td> <td><em>?</em> <code>IssueCommentEvent</code></td> <td>action = "created"</td> </tr> <tr> <td><em>Commenting pull request</em></td> <td><code>IssueCommentEvent</code></td> <td>action = "created"</td> </tr> <tr> <td><em>Commenting pull request changes</em></td> <td><code>PullrequestReviewCommentEvent</code></td> <td>action = "created"</td> </tr> <tr> <td>&nbsp;</td> <td><em>?</em> <code>PullRequestReviewEvent</code></td> <td>action = "created"</td> </tr> <tr> <td><em>Reviewing code</em></td> <td><code>PullRequestReviewEvent</code></td> <td>action = "created"</td> </tr> <tr> <td><em>Commenting commits</em></td> <td><code>CommitCommentEvent</code></td> <td>action = "created"</td> </tr> <tr> <td><em>Pushing commits</em></td> <td><code>PushEvent</code></td> <td>-</td> </tr> </tbody> </table> <p>&nbsp;</p>

opencc-by-4.0Mar 2023View details →
zenodo44/100

CollecTRI Data for Investigation of SETBP1 gene expression and transcription factor activity across human tissues

<p>Here we provide the human CollecTRI prior (accessed May 2023) for inference of TF activity across 31 GTEx tissues using multivariate linear modeling method decoupleR.<br> <br> The `human_prior_tri.csv` includes 1,178 unique TFs (referred to as the source) that target 6,627 unique genes (referred to as targets) to give us 42,595 interactions in the CollecTRI prior input. Interactions are represented as a + or - 1 (mor).</p>

opencc-by-4.0Aug 2023View details →
zenodo40/100

Dataset related to article "NKp46-expressing human gut-resident intraepithelial Vδ1 T cell subpopulation exhibits high antitumor activity against colorectal cancer"

<p>&gamma;&delta; T cells account for a large fraction of human intestinal intraepithelial lymphocytes (IELs) endowed with potent antitumor activities. However, little is known about their origin, phenotype, and clinical relevance in colorectal cancer (CRC). To determine &gamma;&delta; IEL gut specificity, homing, and functions, &gamma;&delta; T cells were purified from human healthy blood, lymph nodes, liver, skin, and intestine, either disease-free, affected by CRC, or generated from thymic precursors. The constitutive expression of NKp46 specifically identifies a subset of cytotoxic V&delta;1 T cells representing the largest fraction of gut-resident IELs. The ontogeny and gut-tropism of NKp46+/V&delta;1 IELs depends both on distinctive features of V&delta;1 thymic precursors and gut-environmental factors. Either the constitutive presence of NKp46 on tissue-resident V&delta;1 intestinal IELs or its induced expression on IL-2/IL-15-activated V&delta;1 thymocytes are associated with antitumor functions. Higher frequencies of NKp46+/V&delta;1 IELs in tumor-free specimens from CRC patients correlate with a lower risk of developing metastatic III/IV disease stages. Additionally, our in vitro settings reproducing CRC tumor microenvironment inhibited the expansion of NKp46+/V&delta;1 cells from activated thymic precursors. These results parallel the very low frequencies of NKp46+/V&delta;1 IELs able to infiltrate CRC, thus providing insights to either follow-up cancer progression or to develop adoptive cellular therapies.</p> <p>&nbsp;</p> <p>This dataset is created with fcs files form, in order to guarantee the access we attach a pdf information about</p>

opencc-by-4.0Mar 2020View details →

ScienceDex guides

Understand access before you commit

These curated guides explain access requirements, typical timelines, costs, and reuse considerations for widely used research datasets.

Compare curated 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.

allen-brain-atlas
neuroscienceopenDocumentation, web resources, and API references are available online.
Last verified 2026-04-30Open record

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.

abode-home-cage
behavioral-neuroscienceopenThe DataShare record exposes download links for annotations, documentation, license text, and the zipped per-snippet data directory.
Last verified 2026-04-30Open record

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.

dandi-nwb
electrophysiologyopenPublished Dandiset metadata and archive endpoints are available through the production DANDI API.
Last verified 2026-04-30Open record

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.

ibl
behavioral-neuroscienceopenPublic sessions can be searched and loaded from the IBL public data server through ONE.
Last verified 2026-04-29Open record

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.

openneuro
neuroscienceopenPublished datasets are available on demand over the internet.
Last verified 2026-04-29Open record