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.
14,965
datasets available to search
ShareScore release 0.7.1
Dataset results
14,965 results for “evolution”
Fig. 12 in Evolution of the hectocotylus in Sepiolinae (Cephalopoda: Sepiolidae) and description of four new genera
Fig. 12. Hectocotylus of Inioteuthis japonica Verrill, 1881. A. Oral view. B. Lateral view. The brackets P and D comprise the proximal and distal structures of the copulatory apparatus ventral side, respectively; an X marks the longitudinal crest between the two structures. The curved line embraces the swollen dorsal margin of the copulatory apparatus, whose modified pedicels (indicated by arrows) look like trabeculae holding the joining web. Scale bars: 2 mm.
Fig. 15 in Evolution of the hectocotylus in Sepiolinae (Cephalopoda: Sepiolidae) and description of four new genera
Fig. 15. Pair of dorsal arms of Sepiola pfefferi Grimpe, 1921; the hectocotylus is on the right-hand side. The letters V indicate the ventral modified pedicels of the copulatory apparatus merging with the muscular ridge (square bracket) arising from the lateral side of basal part (after Goud & de Heij 2012, modified).
Data from: Australian rodents reveal conserved craniofacial evolutionary allometry across 10 million years of murid evolution
<p>Among vertebrates, placental mammals are particularly variable in the covariance between cranial shape and body size (allometry), with rodents a major exception. Australian murid rodents allow an assessment of the cause of this anomaly because they radiated on an ecologically diverse continent notably lacking other terrestrial placentals. Here we use 3D geometric morphometrics to quantify species-level and evolutionary allometries in 38 species (317 crania) from all Australian murid genera. We ask if ecological opportunity resulted in greater allometric diversity compared to other rodents, or if conserved allometry suggests intrinsic constraints and/or stabilizing selection. We also assess whether cranial shape variation follows the proposed "rule of craniofacial evolutionary allometry" (CREA), whereby larger species have relatively longer snouts and smaller braincases. To ensure we could differentiate parallel versus non-parallel species-level allometric slopes, we compared the slopes of rarefied samples across all clades. We found exceedingly conserved allometry and CREA-like patterns across the 10 million year split between <i>Mus</i> and Australian murids. This could support both intrinsic constraints and stabilizing selection hypotheses for conserved allometry. Large-bodied frugivores evolved faster than other species along the allometric trajectory, which could suggest stabilizing selection on the shape of the masticatory apparatus as body size changes.</p>
Nutritional constraints on brain evolution: sodium and nitrogen limit brain size
Nutrition has been hypothesized as an important constraint on brain evolution. However, it is unclear whether the availability of specific nutrients or the difficulty of locating high quality diets limits brain evolution, especially over long periods of time. We show that dietary nutrient content predicted brain size across 42 species of butterflies. Brain size, relative to body size, was associated with the sodium and nitrogen content of a species' diet. There was no evidence that host plant apparency (measured by plant height) was related to brain evolution. The timing of diet shifts varied from 3.5 to 90 million years ago, but nutritional constraints did not lessen over time as species adapted to a diet. While nutrition was linked to overall brain volume, there was no evidence that nutrition was related to the relative size of individual brain regions. Lab rearing experiments confirmed the underlying assumption of most comparative studies that the majority of interspecific trait variation stems from species differences rather than an individual's current developmental environment. This study highlights a novel role of sodium and nitrogen in brain evolution, which is additionally interesting given current anthropogenic change in the availability of these nutrients.
Figs 98-106 in Classification, Natural History, and Evolution of the Subfamily Peloniinae O (Coleoptera: Cleroidea: Cleridae). Part IX. Taxonomic revision of the New World genus Muisca S
Figs 98-106: Phalli. (98) Muisca dilatata. (99) M. insigna. (100) M. apicalis. (101) M. dozieri. (102) M. irrorata. (103) M. hirtula. (104) M. togata. (105) M. xanthura. (106) M. fera.
Figs 82-83 in Classification, Natural History, and Evolution of the Subfamily Peloniinae O (Coleoptera: Cleroidea: Cleridae). Part IX. Taxonomic revision of the New World genus Muisca S
Figs 82-83: Various organs. (82) M. octonotata, head, ventral view. (83) M. octonotata, forebody, ventral view.
Figs 2-13 in Classification, Natural History, and Evolution of the Subfamily Peloniinae O (Coleoptera: Cleroidea: Cleridae). Part IX. Taxonomic revision of the New World genus Muisca S
Figs 2-13: Various structures of Muisca testacea. (2) Head, frontal view. (3) Head, ventral view. (4) Head, dorsal view. (5) Prothorax, ventral view. (6) Antenna, male. (7) Spicular fork. (8) Maxilla. (9) Labrum. (10) Metendosternite. (11) Mandible. (12) Labium. (13) Metathoracic wing.
Figure 2 in The contribution of molecular data to our understanding of cephalopod evolution and systematics: a review
Figure 2. Polyploidy scenario suggested by and reproduced from Bonnaud et al. (2004). Updated diploid chromosome numbers (see Table 2) for the various branches are now Nautiloidea 52; Octopoda 56–60; Sepiolida 74; Sepiida 48–112; Myopsida 86–92 (?22-?172).
Figure 6 in The contribution of molecular data to our understanding of cephalopod evolution and systematics: a review
Figure 6. Relationships among Sepiida. (A) Consensus tree based on 12S rRNA, 16S rRNA, cytochrome oxidase subunit II (Bonnaud et al. 2006); (B) maximum likelihood tree of cytochrome oxidase subunit I, cytochrome b and ND5 combined (Yoshida et al. 2010); (C) whole evidence approach using four to ten genes (Lindgren et al. 2012). Trees redrawn from original sources.
Figure 7 in The contribution of molecular data to our understanding of cephalopod evolution and systematics: a review
Figure 7. Relationships within Onychoteuthidae. (A) Neighbour-joining tree based on 16S ribosomal RNA (Bonnaud et al. 1998); (B) maximum likelihood tree of five genes (see text) combined (Lindgren 2010); (C) maximum likelihood tree based on whole evidence approach using four to ten genes (Lindgren et al. 2012). All trees redrawn from original sources. Nomenclature uses systematic revision of Bolstad (2010).
Dataset for: The Evolution of the Manosphere Across the Web
<p><strong>The Evolution of the Manosphere Across the Web</strong></p> <p>We make available data related to subreddit and standalone forums from the manosphere.</p> <p>We also make available Perspective API annotations for all posts.</p> <p>You can find the code in <a href="https://github.com/manoelhortaribeiro/manosphere_analysis">GitHub</a>.</p> <p>Please cite this paper if you use this data:</p> <pre><code>@article{ribeiroevolution2021, title={The Evolution of the Manosphere Across the Web}, author={Ribeiro, Manoel Horta and Blackburn, Jeremy and Bradlyn, Barry and De Cristofaro, Emiliano and Stringhini, Gianluca and Long, Summer and Greenberg, Stephanie and Zannettou, Savvas}, booktitle = {{Proceedings of the 15th International AAAI Conference on Weblogs and Social Media (ICWSM'21)}}, year={2021} } </code></pre> <p><strong>1. Reddit data</strong></p> <p>We make available data for forums and for relevant subreddits (56 of them, as described in <code>subreddit_descriptions.csv</code>).<br> These are available, 1 line per post in each subreddit Reddit in <code>/ndjson/reddit.ndjson</code>.<br> A sample for example is:</p> <pre><code>{ "author": "Handheld_Gaming", "date_post": 1546300852, "id_post": "abcusl", "number_post": 9.0, "subreddit": "Braincels", "text_post": "Its been 2019 for almost 1 hour And I am at a party with 120 people, half of them being foids. The last year had been the best in my life. I actually was happy living hope because I was redpilled to the death. \n\nNow that I am blackpilled I see that I am the shortest of all men and that I am the only one with a recessed jaw. \n\nIts over. Its only thanks to my age old friendship with chads and my social skills I had developed in the past year that a lot of men like me a lot as a friend.\n\nNo leg lengthening syrgery is gonna save me. Ignorance was a bliss. Its just horror now seeing that everyone can make out wirth some slin hoe at the party. \n\n I actually feel so unbelivably bad for turbomanlets. Life as an unattractive manlet is a pain, I cant imagine the hell being an ugly turbomanlet is like. I would have roped instsntly if I were one. Its so unfair. \n\nTallcels are fakecels and they all can (and should) suck my cock. \n\nIf I were 17cm taller my life would be a heaven and I would be the happiest man alive. \n\nJust cope and wait for affordable body tranpslants.", "thread": "t3_abcusl" } </code></pre> <p><strong>2. Forums</strong></p> <p>We here describe the <code>.sqlite</code> and <code>.ndjson</code> files that contain the data from the following forums.</p> <pre><code>(avfm) --- https://d2ec906f9aea-003845.vbulletin.net (incels) --- https://incels.co/ (love_shy) --- http://love-shy.com/lsbb/ (redpilltalk) --- https://redpilltalk.com/ (mgtow) --- https://www.mgtow.com/forums/ (rooshv) --- https://www.rooshvforum.com/ (pua_forum) --- https://www.pick-up-artist-forum.com/ (the_attraction) --- http://www.theattractionforums.com/ </code></pre> <p>The files are in folders <code>/sqlite/</code> and <code>/ndjson</code>.</p> <p><strong><code>2.1 .sqlite</code></strong></p> <p>All the tables in the <code>sqlite.</code> datasets follow a very simple <code>{key:value}</code> format.<br> Each <code>key</code> is a thread name (for example <code>/threads/housewife-is-like-a-job.123835/</code>) and each value is a python dictionary or a list.<br> This file contains three tables:</p> <ul> <li> <p><code>idx</code> each key is the relative address to a thread and maps to a post. Each post is represented by a dict:</p> <pre><code>"type": (list) in some forums you can add a descriptor such as [RageFuel] to each topic, and you may also have special types of posts, like sticked/pool/locked posts. "title": (str) title of the thread; "link": (str) link to the thread; "author_topic": (str) username that created the thread; "replies": (int) number of replies, may differ from number of posts due to difference in crawling date; "views": (int) number of views; "subforum": (str) name of the subforum; "collected": (bool) indicates if raw posts have been collected; "crawled_idx_at": (str) datetime of the collection. </code></pre> </li> <li> <p><code>processed_posts</code> each key is the relative address to a thread and maps to a list with posts (in order). Each post is represented by a dict:</p> <pre><code>"author": (str) author's username; "resume_author": (str) author's little description; "joined_author": (str) date author joined; "messages_author": (int) number of messages the author has; "text_post": (str) text of the main post; "number_post": (int) number of the post in the thread; "id_post": (str) unique post identifier (depends), for sure unique within thread; "id_post_interaction": (list) list with other posts ids this post quoted; "date_post": (str) datetime of the post, "links": (tuple) nice tuple with the url parsed, e.g. ('https', 'www.youtube.com', '/S5t6K9iwcdw'); "thread": (str) same as key; "crawled_at": (str) datetime of the collection. </code></pre> </li> <li> <p><code>raw_posts</code> each key is the relative address to a thread and maps to a list with unprocessed posts (in order). Each post is represented by a dict:</p> <pre><code>"post_raw": (binary) raw html binary; "crawled_at": (str) datetime of the collection. </code></pre> </li> </ul> <p><strong><code>2.2 .ndjson</code></strong></p> <p>Each line consists of a json object representing a different comment with the following fields:</p> <pre><code> "author": (str) author's username; "resume_author": (str) author's little description; "joined_author": (str) date author joined; "messages_author": (int) number of messages the author has; "text_post": (str) text of the main post; "number_post": (int) number of the post in the thread; "id_post": (str) unique post identifier (depends), for sure unique within thread; "id_post_interaction": (list) list with other posts ids this post quoted; "date_post": (str) datetime of the post, "links": (tuple) nice tuple with the url parsed, e.g. ('https', 'www.youtube.com', '/S5t6K9iwcdw'); "thread": (str) same as key; "crawled_at": (str) datetime of the collection. </code></pre> <p><strong>3. Perspective</strong></p> <p>We also run each post and reddit post through perspective, the files are located in the <code>/perspective/</code> folder.<br> They are compressed with gzip.<br> One example output</p> <pre><code>{ "id_post": 5200, "hate_output": { "text": "I still can\u2019t wrap my mind around both of those articles about these c\~\~\~s sleeping with poor Haitian Men. Where\u2019s the uproar?, where the hell is the outcry?, the \u201cpig\u201d comments or the \u201ccreeper comments\u201d. F\~\~\~ing hell, if roles were reversed and it was an article about Men going to Europe where under 18 sex in legal, you better believe they would crucify the writer of that article and DEMAND an apology by the paper that wrote it.. This is exactly what I try and explain to people about the double standards within our modern society. A bunch of older women, wanna get their kicks off by sleeping with poor Men, just before they either hit or are at menopause age. F~~~ing unreal, I\u2019ll never forget going to Sweden and Norway a few years ago with one of my buddies and his girlfriend who was from there, the legal age of consent in Norway is 16 and in Sweden it\u2019s 15. I couldn\u2019t believe it, but my friend told me \u201c hey, it\u2019s normal here\u201d . Not only that but the age wasn\u2019t a big different in other European countries as well. One thing i learned very quickly was how very Misandric Sweden as well as Denmark were.", "TOXICITY": 0.6079781, "SEVERE_TOXICITY": 0.53744453, "INFLAMMATORY": 0.7279288, "PROFANITY": 0.58842486, "INSULT": 0.5511079, "OBSCENE": 0.9830818, "SPAM": 0.17009115 } } </code></pre> <p><strong>4. Working with sqlite</strong></p> <p>A nice way to read some of the files of the dataset is using <code>SqliteDict</code>, for example:</p> <pre><code>from sqlitedict import SqliteDict processed_posts = SqliteDict("./data/forums/incels.sqlite", tablename="processed_posts") for key, posts in processed_posts.items(): for post in posts: # here you could do something with each post in the dataset pass </code></pre> <p><strong>5. Helpers</strong></p> <p>Additionally, we provide two <code>.sqlite</code> files that are helpers used in the analyses.<br> These are related to reddit, and not to the forums!<br> They are:</p> <ul> <li> <p><code>channel_dict.sqlite</code> a sqlite where each key corresponds to a subreddit and values are lists of dictionaries users who posted on it, along with timestamps.</p> </li> <li> <p><code>author_dict.sqlite</code> a sqlite where each key corresponds to an author and values are lists of dictionaries of the subreddits they posted on, along with timestamps.</p> </li> </ul> <p>These are used in the paper for the migration analyses.</p> <p><strong>6. Examples and particularities for forums</strong></p> <p>Although we did our best to clean the data and be consistent across forums, this is not always possible. In the following subsections we talk about the particularities of each forum, directions to improve the parsing which were not pursued as well as give some examples on how things work in each forum.</p> <p><strong>6.1 incels</strong></p> <p>Check out an archived version of the <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/screenshots/incels_front_page.png">front page</a>, the <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/screenshots/incels_thread_page.png">thread page</a> and a <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/screenshots/incels_post_page.png">post page</a>, as well as a dump of the data stored for a <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/examples/incels_thread_page_example.txt">thread page</a> and a <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/examples/incels_post_page_example.txt">post page</a>.</p> <ul> <li> <p><em>types</em>: for the incel forums the special types associated with each thread in the <code>idx</code> table are “Sticky”, “Pool”, “Closed”, and the custom types added by users, such as <code>[LifeFuel]</code>. These last ones are all in brackets. You can see some examples of these in the on the example thread page.</p> </li> <li> <p><em>quotes</em>: quotes in this forum were quite nice and thus, all quotations are deterministic.</p> </li> </ul> <p><strong>6.2 LoveShy</strong></p> <p>Check out an archived version of the <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/screenshots/love_shy_front_page.png">front page</a>, the <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/screenshots/love_shy_thread_page.png">thread page</a> and a <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/screenshots/love_shy_thread_page.png">post page</a>, as well as a dump of the data stored for a <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/examples/love_shy_thread_page_example.txt">thread page</a> and a <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/examples/love_shy_post_page_example.txt">post page</a>.</p> <ul> <li> <p><em>types</em>: no types were parsed. There are some rules in the forum, but not significant.</p> </li> <li> <p><em>quotes</em>: quotes were obtained from exact text+author match, or author match + a jaccard similarity of more than 0.9 in the tokens of the text split on spaces.</p> </li> <li> <p><em>other</em>: this forum apparently deleted a bunch of posts (or hid them from new users).</p> </li> </ul> <p><strong>6.3 MGTOW</strong></p> <p>Check out an archived version of the <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/screenshots/mgtow_front_page.png">front page</a>, the <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/screenshots/mgtow_thread_page.png">thread page</a> and a <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/screenshots/mgtow_thread_page.png">post page</a>, as well as a dump of the data stored for a <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/examples/mgtow_thread_page_example.txt">thread page</a> and a <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/examples/mgtow_post_page_example.txt">post page</a>.</p> <ul> <li> <p><em>types</em>: no types were parsed. There are some rules in the forum, but not significant.</p> </li> <li> <p><em>quotes</em>: quotes in this forum were quite nice and thus, all quotations are deterministic.</p> </li> <li> <p><em>other</em>: collecting users for this forum was hard because info like number of threads and join date do not show on the threads. Thus there was a 2-step collection. Some users may be missing because of this.</p> </li> </ul> <p><strong>6.4 A Voice for Men</strong></p> <p>Check out an archived version of the <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/screenshots/avfm_front_page.png">front page</a>, the <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/screenshots/avfm_thread_page.png">thread page</a> and a <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/screenshots/avfm_thread_page.png">post page</a>, as well as a dump of the data stored for a <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/examples/avfm_thread_page_example.txt">thread page</a> and a <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/examples/avfm_post_page_example.txt">post page</a>.</p> <ul> <li> <p><em>types</em>: “sticky” is the only existing type.</p> </li> <li> <p><em>quotes</em>: quotes in this forum were quite nice and thus, all quotations are deterministic.</p> </li> </ul> <p><strong>6.5 Red Pill Talk (formerly <a href="http://sluthate.com">sluthate.com</a>)</strong></p> <p>Check out an archived version of the <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/screenshots/avfm_front_page.png">front page</a>, the <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/screenshots/avfm_thread_page.png">thread page</a> and a <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/screenshots/avfm_thread_page.png">post page</a>, as well as a dump of the data stored for a <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/examples/avfm_thread_page_example.txt">thread page</a> and a <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/examples/avfm_post_page_example.txt">post page</a>.</p> <ul> <li> <p><em>types</em>: no types were parsed.</p> </li> <li> <p><em>quotes</em>: quotes were obtained from exact text+author match, or author match + a jaccard similarity of more than 0.9 in the tokens of the text split on spaces.</p> </li> </ul> <p><strong>6.6 The Attraction</strong></p> <p>Check out an archived version of the <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/screenshots/the_attraction_front_page.png">front page</a>, the <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/screenshots/the_attraction_thread_page.png">thread page</a> and a <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/screenshots/the_attraction_thread_page.png">post page</a>, as well as a dump of the data stored for a <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/examples/the_attraction_thread_page_example.txt">thread page</a> and a <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/examples/the_attraction_post_page_example.txt">post page</a>.</p> <ul> <li> <p><em>types</em>: “sticky” is the only existing type.</p> </li> <li> <p><em>quotes</em>: quotes in this forum were quite nice and thus, all quotations are deterministic.</p> </li> <li> <p><em>other</em>: there is the possibility to parse stuff like age and location, but this was not done.</p> </li> </ul> <p><strong>6.7 PUA Forum</strong></p> <p>Check out an archived version of the <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/screenshots/pua_forum_front_page.png">front page</a>, the <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/screenshots/pua_forum_thread_page.png">thread page</a> and a <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/screenshots/pua_forum_thread_page.png">post page</a>, as well as a dump of the data stored for a <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/examples/pua_forum_thread_page_example.txt">thread page</a> and a <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/examples/pua_forum_post_page_example.txt">post page</a>.</p> <ul> <li> <p><em>types</em>: There are several types parsed: Sticky, Announcement, General Announcement, Locked, to name a few.</p> </li> <li> <p><em>quotes</em>: quotes were obtained from exact text match, or a jaccard similarity of more than 0.9 in the tokens of the text split on spaces. There are actually some problems with quotes with other quotes inside (check example .txt).</p> </li> </ul> <p><strong>6.8 Rooshv</strong></p> <p>Check out an archived version of the <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/screenshots/rooshv_front_page.png">front page</a>, the <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/screenshots/rooshv_thread_page.png">thread page</a> and a <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/screenshots/pua_forum_thread_page.png">post page</a>, as well as a dump of the data stored for a <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/examples/rooshv_thread_page_example.txt">thread page</a> and a <a href="https://github.com/manoelhortaribeiro/manosphere_analysis/blob/master/data/forums/examples/rooshv_post_page_example.txt">post page</a>.</p> <ul> <li> <p><em>types</em>: Two types parsed: <code>sticky</code>, <code>announcement</code>.</p> </li> <li> <p><em>quotes</em>: quotes in this forum were quite nice and thus, all quotations are deterministic.</p> </li> <li> <p><em>other</em>: lots of posts have some problem with dates, which is quite annoying (~5%). Some threads could not be captured also, website behaves a bit weird. Some don’t exist.</p> </li> </ul>
DATA of "Resolving the 2D temporal evolution of subglacial water flow with dense seismic array observations."
<p>The data set contains all data presented in the paper: <strong>Observing the subglacial hydrology network and its dynamics with a dense seismic array</strong> published in PNAS ( <a href="https://doi.org/10.1073/pnas.2023757118">https://doi.org/10.1073/pnas.2023757118</a> )</p> <p>See our online presentation of this dataset: https://meetingorganizer.copernicus.org/EGU2020/EGU2020-10710.html.</p> <p>The present data and code concerns the source location obtained with matched-field-processing analysis and the hydraulic potential calculation (Shreve, R. L. Movement of Water in Glaciers. <em>J. Glaciol.</em> <strong>11</strong>, 205–214 (1972)).</p> <p>We perform source location over 1-sec long signal segment of the vertical component only. We filter the signal within the [3-7] Hz frequency range and coherently apply the MFP each 0.1 Hz within this range. To maximize our algorithm efficiency and minimize computational costs we use a gradient-based minimization algorithm (Nelder-Mead optimization) to converge to the best match between the trial and the observed phase delays rather than an exhaustive grid-search exploration. The convergence criterion is reached when the variance of values obtained over the last 5 iterations of the optimization is smaller than 1e<sup>-2</sup> with a maximum of 3000 iterations. Our 29 different starting points used for optimization are located 250 m below the glacier surface and they uniformly cover an area of 800 x 800 m<sup>2</sup> centered on the array. We set the initial velocity to 1800 m.sec <sup>-1</sup>. The 29 punctual locations found per signal segment (1 sec) after convergence are located all in the same place if a clear global convergence exists (i.e. high MFP output) or at up to 29 different locations if up to 29 local minima exist (i.e. low MFP output).</p> <p>Timeseries of physical quantities can be found here <a href="https://doi.org/10.5281/zenodo.3701520">https://doi.org/10.5281/zenodo.3701520</a></p> <p>Spatial observations acquired during the same period can be found here <a href="https://doi.org/10.5281/zenodo.3971815">https://doi.org/10.5281/zenodo.3971815</a></p> <p> </p> <p>The RESOLVE project has been supported by a grant from LabEx OSUG@2020 (Investissement d’avenir – ANR10LABX56) and by the IDEX Université Grenoble Alpes. Most of the computations presented in this paper were performed using the GRICAD infrastructure (https://gricad.univ-grenoble-alpes.fr), which is supported by Grenoble research communities, and with the CiGri tool (https://github.com/oar-team/cigri) developed by Gricad, Grid5000 (https://www.grid5000.fr) and LIG (<a href="https://www.liglab.fr/">https://www.liglab.fr/</a>).</p> <p> </p> <p>You can find more information on the method and seismic dataset used in this paper here: <a href="https://zenodo.org/deposit/5645545">https://zenodo.org/deposit/5645545</a></p>
Architectural Feature Re-Modularization for Software Product Line Evolution
<p>Extensive maintenance leads to the Software Product Line Architecture<br> (PLA) degradation over time. When there is the need of<br> evolving the Software Product Line (SPL) to include new features,<br> or move to a new platform, a degraded PLA requires considerable<br> effort to understand and modify, demanding expensive refactoring<br> activity. In the state of the art, search-based algorithms are used to<br> improve PLA at package level. However, recent studies have shown<br> that the most variability and implementation details of an SPL are<br> described in the level of classes. There is a gap between existing<br> approaches and existing practical needs. In this work, we extend<br> the current state of the art to deal with feature modularization in<br> the level of classes by introducing a new search operator and a set<br> of objective functions to deal with feature modularization in a finer<br> granularity of the architectural elements, namely at class level. We<br> evaluated the proposal in an exploratory study with a PLA widely<br> investigated and a real-world PLA. The results of quantitative and<br> qualitative analysis point out that our proposal provides solutions<br> to properly re-modularize features in a PLA, being preferred by<br> practitioners, in order to support the evolution of SPLs.</p>
Data accompanying the manuscript "Protocol Discovery for the Quantum Control of Majoranas by Differentiable Programming and Natural Evolution Strategies"
<p>Dataset for figures 2, A6 and A8 for the manuscript: "Protocol Discovery for the Quantum Control of Majoranas by Differentiable Programming and Natural Evolution Strategies." The dataset contains the optimal protocols for Majorana transport in both the Kitaev Chain model as well as the Proximity Coupled Semiconduncting Nanowire model obtained with Differentiable Programming and Natural Evolution Strategies. Also the Simulated Annealing (SA) optimal protocols for the Kitaev chain are included.</p>
Data and analysis scripts associated with the paper 'Long-term experimental evolution of HIV-1 reveals effects of environment and mutational history''
<p><em>Eva Bons, Christine Leemann, Karin J. Metzner, Roland R. Regoes</em></p> <p>This repository contains all the data and analysis scripts associated with the paper 'Long-term experimental evolution of HIV-1 reveals effects of environment and mutational history'</p> <p>See the readme after unpacking the .zip for a description of the files</p>
Evolution enhances mutational robustness and suppresses the emergence of a new phenotype
<p>Source codes and data sets for arXiv:2012.03030. For details, see readme.txt file.</p>
Reversible H2 oxidation and evolution by hydrogenase embedded in a redox polymer film
<p>This data set contains the source data of the nature catalysis manuscript NATCATAL-20033655A.</p> <p>All files are named according to the respective figure numbers of the manuscript. </p>
Reversible H2 oxidation and evolution by hydrogenase embedded in a redox polymer film
<p>This Upload contains the source data sets of all measurements shown in the Nature Catalysis manuscript NATCATAL-20033655A.</p> <p>All folder and file names correspond to the respective figure numbers of the manuscript.</p>
On the Co-evolution of ML Pipelines and Source Code - Empirical Study of DVC Projects
<p>This is a replication package of our paper submission to the Saner 2021 entitled:</p> <p>On the Co-evolution of ML Pipelines and Source Code - Empirical Study of DVC Projects</p>
FIG. 8 in Late Triassic to Early Jurassic radiolarian, conodont and ammonite assemblages from the Tavuscayiri block, Mersin Mélange, southern Turkey: Time constraints for the T/J boundary and sedimentary evolution of the southern margin of the northern Neotethys
FIG. 8. — Photomicrographs of the radiolarians from the Orbuklukeli section; A-H, Acanthotetrapaurinella kennecottensis (Carter in Longridge, Carter, Smith & Tipper, 2007); A-E, G, Orbuk-26, F, H, Orbuk-27; I-O, Paurinella liassica Tekin, n. sp.; I, Holotype, Orbuk-27; J-O, Paratypes; J, N, Orbuk-27; K-M, Orbuk-32; O, Orbuk-26; P-V, Tetrapaurinella sphaerica Tekin, n. sp.; P, Holotype, Orbuk-32; Q-V, Paratypes; Q, Orbuk-32; R-T, Orbuk-27, U, Orbuk-26; V, Orbuk-31; W-Y, Orbiculiformella callosa (Yeh, 1987); W, X, Orbuk-36; Y, Orbuk-41. Scale bar: G-H, 100 µm; A-F, I-V, 150 µm; W-Y, 200 µm.
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.