Skip to main content
ConductScienceScienceDex
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.

4,347

datasets available to search

ShareScore release 0.9.0

Reset

Dataset results

4,347 results for “tools”

Learn how ShareScore rates datasets ↗
zenodo40/100

Vulnerability tools - Swiss Jura (Switzerland)

<p><span>The MOVING project has developed accessible <strong>tools </strong>designed to assess susceptibility and vulnerability within the region, ready to be used by both experts and the general audience. This document synthesises crucial information for the Swiss Jura Region, particularly focusing on the Participatory Vulnerability Matrix and the Spatial Vulnerability Map. Furthermore, it includes <strong>supplementary maps and figures </strong>detailing various aspects such as the delineation of Reference Landscape, distribution of land systems, areas affected by wildfires, susceptibility to floods across different return periods, severity of forest disturbances, rainfall erosivity, and more.</span></p>

opencc-by-4.0Apr 2024View details →
zenodo40/100

Vulnerability tools - Eastern Alps (Italy)

<p><span>The MOVING project has developed accessible <strong>tools </strong>designed to assess susceptibility and vulnerability within the region, ready to be used by both experts and the general audience. This document synthesises crucial information for the Eastern Alps Region, particularly focusing on the Participatory Vulnerability Matrix and the Spatial Vulnerability Map. Furthermore, it includes&nbsp;<strong>supplementary maps and figures </strong>detailing various aspects such as the delineation of Reference Landscape, distribution of land systems, areas affected by wildfires, susceptibility to floods across different return periods, severity of forest disturbances, rainfall erosivity, and more.</span></p>

opencc-by-4.0Apr 2024View details →
zenodo40/100

Vulnerability tools - Drôme Valley (France)

<p>The MOVING project has developed accessible <strong>tools </strong>designed to assess susceptibility and vulnerability within the region, ready to be used by both experts and the general audience. This document synthesises crucial information for the Dr&ocirc;me Valley Region, particularly focusing on the Participatory Vulnerability Matrix and the Spatial Vulnerability Map. Furthermore, it includes <strong>supplementary maps and figures </strong>detailing various aspects such as the delineation of Reference Landscape, distribution of land systems, areas affected by wildfires, susceptibility to floods across different return periods, severity of forest disturbances, rainfall erosivity, and more.</p>

opencc-by-4.0Apr 2024View details →
zenodo40/100

Vulnerability tools - Beydaglari (Turkey)

<p><span>The MOVING project has developed accessible <strong>tools </strong>designed to assess susceptibility and vulnerability within the region, ready to be used by both experts and the general audience. This document synthesises crucial information for the Beydaglari Region, particularly focusing on the Participatory Vulnerability Matrix and the Spatial Vulnerability Map. Furthermore, it includes <strong>supplementary maps and figures </strong>detailing various aspects such as the delineation of Reference Landscape, distribution of land systems, areas affected by wildfires, susceptibility to floods across different return periods, severity of forest disturbances, rainfall erosivity, and more.</span></p>

opencc-by-4.0Apr 2024View details →
dryad40/100

Data from: Tool use increases mechanical foraging success and tooth health in southern sea otters (Enhydra lutris nereis)

<p>Although it is well documented that tool use can enable the utilization of novel resources, the fitness benefits associated with this innovative behavior are difficult to test. Using longitudinal data from 196 radio-tagged southern sea otters, we found that individuals, particularly females, with frequent tool use gained access to harder, larger prey items. In turn, the mechanical advantages of tool use during food processing translated to reduced tooth damage in tool users. We also found that tool use diminishes trade-offs between access to different prey types, tooth health, and caloric intake that are highly dependent on the relative availability of prey in the environment. Overall, tool use allows individuals to maintain caloric requirements through the processing of alternative prey that are otherwise inaccessible without the use of tools, indicating that this innovative behavior is a necessity for the survival of southern sea otters in environments with depleted preferred prey.</p>

opencc-zeroApr 2024View details →
zenodo40/100

Demonstrations of witness visualization using the Witness Visualizer Tool

<p>We have three datasets that display visualized <a href="https://sv-comp.sosy-lab.org/">SVCOMP</a> witnesses generated with the help of the <a href="https://github.com/ispras/cv">Witness Visualizer tool</a>. Each dataset comprises two directories:&nbsp;<code>witnesses</code>, which contains the original witnesses provided by SVCOMP tools, and <code>visualization</code>, which contains our visual representations of the respective witnesses in HTML format. The visualization file name contains the prefix <code>error_trace-</code>, for example, <code>error_trace-witness.2ls.html</code> corresponds to a witness named <code>witness.2ls.graphml</code>.</p> <h3>1. Overall thoroughness for all SVCOMP tools (<a href="../records/10988025/files/dataset_1.zip?download=1" target="_blank" rel="noopener">dataset_1.zip</a>)</h3> <p>This dataset includes a single random witness for each SVCOMP tool, accompanied by its corresponding visualization. The visualizations showcase the various witness elements such as function calls, conditions, assumptions, thread specifics, and other operations. Cells marked with <code>+/-</code> indicate that some elements were present in the error trace, but not all of them. All witnesses are presented in the table below:</p> <table> <tbody> <tr> <td>Witness</td> <td>SV-COMP Tool</td> <td>Function calls</td> <td>Threads</td> <td>Assumptions</td> <td>Conditions</td> <td>Link to sources</td> </tr> <tr> <td>witness.2ls.graphml</td> <td>2LS</td> <td>-</td> <td>-</td> <td>+</td> <td>-</td> <td>+</td> </tr> <tr> <td>witness.aprove.graphml</td> <td>AProVE (2022)</td> <td>-</td> <td>-</td> <td>-</td> <td>+</td> <td>+</td> </tr> <tr> <td>witness.brick.graphml</td> <td>BRICK</td> <td>-</td> <td>-</td> <td>+</td> <td>-</td> <td>+</td> </tr> <tr> <td>witness.bubaak.graphml</td> <td>Bubaak</td> <td>-</td> <td>-</td> <td>+</td> <td>-</td> <td>+</td> </tr> <tr> <td>witness.cbmc.graphml</td> <td>CBMC</td> <td>-</td> <td>+</td> <td>+</td> <td>-</td> <td>+</td> </tr> <tr> <td>witness.cpa-bam-bnb.graphml</td> <td>CPA-BAM-BnB</td> <td>+</td> <td>-</td> <td>+</td> <td>+</td> <td>+</td> </tr> <tr> <td>witness.cpa-bam-smg.graphml</td> <td>CPA-BAM-SMG</td> <td>+</td> <td>-</td> <td>+</td> <td>+</td> <td>+</td> </tr> <tr> <td>witness.cpalockator.graphml</td> <td>CPALockator</td> <td>+</td> <td>+</td> <td>+</td> <td>+</td> <td>+</td> </tr> <tr> <td>witness.cpachecker.graphml</td> <td>CPAChecker</td> <td>+</td> <td>+</td> <td>+</td> <td>+</td> <td>+</td> </tr> <tr> <td>witness.crux.graphml</td> <td>Crux</td> <td>-</td> <td>-</td> <td>+</td> <td>-</td> <td>+</td> </tr> <tr> <td>witness.cseq.graphml</td> <td>Cseq</td> <td>+</td> <td>+</td> <td>+</td> <td>-</td> <td>+</td> </tr> <tr> <td>witness.dartagnan.graphml</td> <td>Dartagnan</td> <td>-</td> <td>+</td> <td>-</td> <td>-</td> <td>+</td> </tr> <tr> <td>witness.deagle.graphml</td> <td>Deagle</td> <td>-</td> <td>+</td> <td>+</td> <td>-</td> <td>+</td> </tr> <tr> <td>-</td> <td>DIVINE (until 2022)</td> <td>empty</td> </tr> <tr> <td>-</td> <td>EBF</td> <td>empty</td> </tr> <tr> <td>witness.esbmc-incr.graphml</td> <td>ESBMC-incr</td> <td>-</td> <td>+</td> <td>+</td> <td>-</td> <td>+</td> </tr> <tr> <td>witness.esbmc-kind.graphml</td> <td>ESBMC-kind</td> <td>-</td> <td>+</td> <td>+</td> <td>-</td> <td>+</td> </tr> <tr> <td>-</td> <td>Frama-C-SV</td> <td>empty</td> </tr> <tr> <td>witness.gazer-theta.graphml</td> <td>Gazer-Theta</td> <td>+</td> <td>-</td> <td>+</td> <td>-</td> <td>wrong path</td> </tr> <tr> <td>witness.gdart.graphml</td> <td>Gdart-LLVM</td> <td>-</td> <td>-</td> <td>+</td> <td>-</td> <td>+</td> </tr> <tr> <td>-</td> <td>Goblint</td> <td>empty</td> </tr> <tr> <td>witness.graves_cpa.graphml</td> <td>Graves-CPA</td> <td>+</td> <td>+</td> <td>+</td> <td>+</td> <td>+</td> </tr> <tr> <td>witness.graves_par.graphml</td> <td>Graves-Par</td> <td>+</td> <td>+</td> <td>+</td> <td>+</td> <td>+</td> </tr> <tr> <td>-</td> <td>Infer</td> <td>empty</td> </tr> <tr> <td>witness.korn.graphml</td> <td>Korn</td> <td>-</td> <td>-</td> <td>+</td> <td>-</td> <td>+</td> </tr> <tr> <td>witness.lart.graphml</td> <td>LART (2022)</td> <td>-</td> <td>-</td> <td>+</td> <td>-</td> <td>+</td> </tr> <tr> <td>witness.lazy-cseq.graphml</td> <td>Lazy-CSeq</td> <td>+</td> <td>+</td> <td>+</td> <td>+</td> <td>+</td> </tr> <tr> <td>witness.lfchecker.graphml</td> <td>LF-checker</td> <td>-</td> <td>+</td> <td>+</td> <td>-</td> <td>+</td> </tr> <tr> <td>-</td> <td>Locksmith</td> <td>empty</td> </tr> <tr> <td>-</td> <td>Mopsa</td> <td>empty</td> </tr> <tr> <td>witness.pesco_cpa.graphml</td> <td>PeSCo-CPA</td> <td>+</td> <td>+</td> <td>+</td> <td>+</td> <td>+</td> </tr> <tr> <td>witness.pichecker.graphml</td> <td>PIChecker</td> <td>+</td> <td>-</td> <td>+</td> <td>+</td> <td>+</td> </tr> <tr> <td>witness.pinaka.graphml</td> <td>Pinaka</td> <td>-</td> <td>-</td> <td>+</td> <td>-</td> <td>+</td> </tr> <tr> <td>witness.predator.graphml</td> <td>PredatorHP</td> <td>-</td> <td>-</td> <td>-</td> <td>-</td> <td>+</td> </tr> <tr> <td>-</td> <td>SESL (2022)</td> <td>empty</td> </tr> <tr> <td>witness.smack.graphml</td> <td>SMACK (until 2022)</td> <td>-</td> <td>-</td> <td>+</td> <td>-</td> <td>+</td> </tr> <tr> <td>witness.symbiotic.graphml</td> <td>Symbiotic</td> <td>-</td> <td>+</td> <td>+</td> <td>-</td> <td>+</td> </tr> <tr> <td>witness.theta.graphml</td> <td>Theta</td> <td>different format</td> </tr> <tr> <td>witness.uatomozer.graphml</td> <td>UAutomizer</td> <td>+/-</td> <td>+</td> <td>+</td> <td>+</td> <td>+</td> </tr> <tr> <td>witness.ucutter.graphml</td> <td>UgemCutter</td> <td>+/-</td> <td>+</td> <td>+</td> <td>+</td> <td>+</td> </tr> <tr> <td>witness.ukojak.graphml</td> <td>UKojak</td> <td>+/-</td> <td>-</td> <td>+</td> <td>+</td> <td>+</td> </tr> <tr> <td>witness.utaipan.graphml</td> <td>UTaipan</td> <td>+/-</td> <td>+</td> <td>+</td> <td>+</td> <td>+</td> </tr> <tr> <td>witness.veriabs.graphml</td> <td>VeriAbs</td> <td>-</td> <td>-</td> <td>+</td> <td>-</td> <td>wrong path</td> </tr> <tr> <td>witness.veriabsl.graphml</td> <td>VeriAbsL</td> <td>+</td> <td>-</td> <td>+</td> <td>+</td> <td>wrong path</td> </tr> <tr> <td>witness.verifuzz.graphml</td> <td>VeriFuzz</td> <td>-</td> <td>-</td> <td>+</td> <td>-</td> <td>+</td> </tr> <tr> <td>witness.verioover.graphml</td> <td>VeriOover</td> <td>-</td> <td>-</td> <td>+</td> <td>-</td> <td>+</td> </tr> </tbody> </table> <h3>2. Thoroughness by property (<a href="../records/10988025/files/dataset_2.zip?download=1" target="_blank" rel="noopener">dataset_2.zip</a>)</h3> <p>This dataset comprises a selected witness for each SVCOMP property (ReachSafety, MemSafety, Termination, NoOverflow, ConcurrencySafety). The witnesses are presented in the following table:</p> <p>&nbsp;</p> <table> <tbody> <tr> <td>Witness</td> <td>SV-COMP Tool</td> <td>Property</td> <td>Mandatory elements</td> <td>Description</td> </tr> <tr> <td>witness.smg_memory.graphml</td> <td>CPA-BAM-SMG</td> <td>MemSafety</td> <td>Assumptions / conditions, function calls</td> <td>There is a double free operation. Employing function calls <code>append </code>aids in comprehending the structure of the list, while assumptions reveal which branch was chosen.</td> </tr> <tr> <td>witness.graves_overflow.graphml</td> <td>Graves-CPA</td> <td>NoOverflow</td> <td>Assumptions / conditions</td> <td>The witness showcases an explicit (<code>-2147483648</code>, which represents the minimal value for the <code>int</code>&nbsp;type), which has the potential to cause overflow in specific program.</td> </tr> <tr> <td>witness.cpachecker_termination.graphml</td> <td>CPAChecker</td> <td>NoTermination</td> <td>Assumptions / conditions</td> <td>There is a condition leading to an infinite loop.</td> </tr> <tr> <td>witness.cpachecker_unreach.graphml</td> <td>CPAChecker</td> <td>ReachSafety</td> <td>Function calls</td> <td>The error trace indicates a potential scenario where a <code>mutex</code> was unlocked<br>without the corresponding <code>mutex_unlock</code> operation.</td> </tr> <tr> <td>witness.cpachecker_conc.graphml</td> <td>CPAChecker</td> <td>ConcurrencySafety</td> <td>Function calls, thread operations</td> <td>The error trace illustrates the creation of threads and highlights the assignments made within each thread that ultimately resulted in the violation of the property.</td> </tr> </tbody> </table> <div> <h3>3. Known bug (<a href="../records/10988025/files/dataset_2.zip?download=1" target="_blank" rel="noopener">dataset_3.zip</a>)</h3> <p>This dataset contains witnesses for a known bug from SVCOMP (<code>linux-3.14--drivers--usb--misc--adutux.ko.cil.i</code>) involving a data race on <code>dev-&gt;udev</code>, where concurrent writes occur without corresponding locks. Only two tools were able to solve the corresponding verification task: ESBMC-kind and CPALockator. The ESBMC error trace (<code>witness.esbmc_2020.graphml</code>) includes only thread specifics and assumptions, while the CPALockator witness (<code>witness.lockator.graphml</code>) comprises all witness elements and is presented in a human-readable format.</p> <h3>4. Comparison with the validation rate</h3> <p>This section presents a comparison between witness thoroughness and the actual validation rate for each property. We considered all tools that participated in the respective category and generated at least 10 error traces, then calculated the validation rate. This comparison demonstrates how effectively thoroughness can approximate the validation rate. The following tables provide details for each property, with the relevant elements used to calculate thoroughness highlighted:</p> <ul> <li>MemSafety property:</li> </ul> <table> <tbody> <tr> <td>SV-COMP Tool</td> <td><strong>Function calls</strong></td> <td>Threads</td> <td><strong>Assumptions</strong></td> <td><strong>Conditions</strong></td> <td>Thoroughness</td> <td>Error traces</td> <td>Validation rate</td> </tr> <tr> <td>Bubaak</td> <td><strong>0</strong></td> <td>0</td> <td><strong>1</strong></td> <td><strong>0</strong></td> <td>33.33</td> <td>64</td> <td>67.19</td> </tr> <tr> <td>CBMC</td> <td><strong>0</strong></td> <td>1</td> <td><strong>1</strong></td> <td><strong>0</strong></td> <td>33.33</td> <td>27</td> <td>11.11</td> </tr> <tr> <td>CPA-BAM-SMG</td> <td><strong>1</strong></td> <td>0</td> <td><strong>1</strong></td> <td><strong>1</strong></td> <td>100</td> <td>46</td> <td>78.26</td> </tr> <tr> <td>CPAChecker</td> <td><strong>1</strong></td> <td>1</td> <td><strong>1</strong></td> <td><strong>1</strong></td> <td>100</td> <td>37</td> <td>67.57</td> </tr> <tr> <td>ESBMC-kind</td> <td><strong>0</strong></td> <td>1</td> <td><strong>1</strong></td> <td><strong>0</strong></td> <td>33.33</td> <td>25</td> <td>20</td> </tr> <tr> <td>Graves-CPA</td> <td><strong>1</strong></td> <td>1</td> <td><strong>1</strong></td> <td><strong>1</strong></td> <td>100</td> <td>44</td> <td>56.82</td> </tr> <tr> <td>Graves-Par</td> <td><strong>1</strong></td> <td>1</td> <td><strong>1</strong></td> <td><strong>1</strong></td> <td>100</td> <td>18</td> <td>77.78</td> </tr> <tr> <td>PeSCo-CPA</td> <td><strong>1</strong></td> <td>1</td> <td><strong>1</strong></td> <td><strong>1</strong></td> <td>100</td> <td>37</td> <td>67.57</td> </tr> </tbody> </table> <ul> <li>NoOverflow property:</li> </ul> <table> <tbody> <tr> <td>SV-COMP Tool</td> <td>Function calls</td> <td>Threads</td> <td><strong>Assumptions</strong></td> <td>Conditions</td> <td>Thoroughness</td> <td>Error traces</td> <td>Validation rate</td> </tr> <tr> <td>2LS</td> <td>0</td> <td>0</td> <td><strong>1</strong></td> <td>0</td> <td>100</td> <td>2071</td> <td>95.7</td> </tr> <tr> <td>Bubaak</td> <td>0</td> <td>0</td> <td><strong>1</strong></td> <td>0</td> <td>100</td> <td>2233</td> <td>94.67</td> </tr> <tr> <td>CBMC</td> <td>0</td> <td>1</td> <td><strong>1</strong></td> <td>0</td> <td>100</td> <td>3296</td> <td>62.14</td> </tr> <tr> <td>CPAChecker</td> <td>1</td> <td>1</td> <td><strong>1</strong></td> <td>1</td> <td>100</td> <td>196</td> <td>100</td> </tr> <tr> <td>Crux</td> <td>0</td> <td>0</td> <td><strong>1</strong></td> <td>0</td> <td>100</td> <td>222</td> <td>95.05</td> </tr> <tr> <td>ESBMC-kind</td> <td>0</td> <td>1</td> <td><strong>1</strong></td> <td>0</td> <td>100</td> <td>3296</td> <td>66.69</td> </tr> <tr> <td>Frama-C-SV</td> <td>0</td> <td>0</td> <td><strong>0</strong></td> <td>0</td> <td>0</td> <td>676</td> <td>0</td> </tr> <tr> <td>Graves-Par</td> <td>1</td> <td>1</td> <td><strong>1</strong></td> <td>1</td> <td>100</td> <td>750</td> <td>2</td> </tr> <tr> <td>Infer</td> <td>0</td> <td>0</td> <td><strong>0</strong></td> <td>0</td> <td>0</td> <td>583</td> <td>0</td> </tr> <tr> <td>Pinaka</td> <td>0</td> <td>0</td> <td><strong>1</strong></td> <td>0</td> <td>100</td> <td>2232</td> <td>100</td> </tr> <tr> <td>Symbiotic</td> <td>0</td> <td>1</td> <td><strong>1</strong></td> <td>0</td> <td>100</td> <td>1418</td> <td>100</td> </tr> <tr> <td>UAutomizer</td> <td>0.5</td> <td>1</td> <td><strong>1</strong></td> <td>1</td> <td>100</td> <td>2222</td> <td>100</td> </tr> <tr> <td>UKojak</td> <td>0.5</td> <td>0</td> <td><strong>1</strong></td> <td>1</td> <td>100</td> <td>168</td> <td>100</td> </tr> <tr> <td>UTaipan</td> <td>0.5</td> <td>1</td> <td><strong>1</strong></td> <td>1</td> <td>100</td> <td>0</td> <td>100</td> </tr> <tr> <td>VeriFuzz</td> <td>0</td> <td>0</td> <td><strong>1</strong></td> <td>0</td> <td>100</td> <td>185</td> <td>90.81</td> </tr> </tbody> </table> <ul> <li>NoTermination property:</li> </ul> <table> <tbody> <tr> <td>SV-COMP Tool</td> <td>Function calls</td> <td>Threads</td> <td><strong>Assumptions</strong></td> <td><strong>Conditions</strong></td> <td>Thoroughness</td> <td>Error traces</td> <td>Validation rate</td> </tr> <tr> <td>2LS</td> <td>0</td> <td>0</td> <td><strong>1</strong></td> <td><strong>0</strong></td> <td>50</td> <td>663</td> <td>69.08</td> </tr> <tr> <td>Bubaak</td> <td>0</td> <td>0</td> <td><strong>1</strong></td> <td><strong>0</strong></td> <td>50</td> <td>578</td> <td>34.78</td> </tr> <tr> <td>CPAChecker</td> <td>1</td> <td>1</td> <td><strong>1</strong></td> <td><strong>1</strong></td> <td>100</td> <td>501</td> <td>97.01</td> </tr> <tr> <td>Symbiotic</td> <td>0</td> <td>1</td> <td><strong>1</strong></td> <td><strong>0</strong></td> <td>50</td> <td>591</td> <td>52.96</td> </tr> <tr> <td>UAutomizer</td> <td>0.5</td> <td>1</td> <td><strong>1</strong></td> <td><strong>1</strong></td> <td>100</td> <td>512</td> <td>98.24</td> </tr> <tr> <td>VeriFuzz</td> <td>0</td> <td>0</td> <td><strong>1</strong></td> <td><strong>0</strong></td> <td>50</td> <td>492</td> <td>71.34</td> </tr> </tbody> </table> <ul> <li>ReachSafety property:</li> </ul> <table> <tbody> <tr> <td>SV-COMP Tool</td> <td><strong>Function calls</strong></td> <td>Threads</td> <td>Assumptions</td> <td>Conditions</td> <td>Thoroughness</td> <td>Error traces</td> <td>Validation rate</td> </tr> <tr> <td>Bubaak</td> <td><strong>0</strong></td> <td>0</td> <td>1</td> <td>0</td> <td>0</td> <td>24</td> <td>54.17</td> </tr> <tr> <td>CBMC</td> <td><strong>0</strong></td> <td>1</td> <td>1</td> <td>0</td> <td>0</td> <td>392</td> <td>1.28</td> </tr> <tr> <td>CPA-BAM-BnB</td> <td><strong>1</strong></td> <td>0</td> <td>1</td> <td>1</td> <td>100</td> <td>69</td> <td>85.51</td> </tr> <tr> <td>CPA-BAM-SMG</td> <td><strong>1</strong></td> <td>0</td> <td>1</td> <td>1</td> <td>100</td> <td>67</td> <td>85.07</td> </tr> <tr> <td>CPAChecker</td> <td><strong>1</strong></td> <td>1</td> <td>1</td> <td>1</td> <td>100</td> <td>45</td> <td>88.89</td> </tr> <tr> <td>Crux</td> <td><strong>0</strong></td> <td>0</td> <td>1</td> <td>0</td> <td>0</td> <td>1572</td> <td>0.13</td> </tr> <tr> <td>ESBMC-kind</td> <td><strong>0</strong></td> <td>1</td> <td>1</td> <td>0</td> <td>0</td> <td>64</td> <td>21.88</td> </tr> <tr> <td>Graves-CPA</td> <td><strong>1</strong></td> <td>1</td> <td>1</td> <td>1</td> <td>100</td> <td>66</td> <td>87.88</td> </tr> <tr> <td>Graves-Par</td> <td><strong>1</strong></td> <td>1</td> <td>1</td> <td>1</td> <td>100</td> <td>24</td> <td>58.33</td> </tr> <tr> <td>PeSCo-CPA</td> <td><strong>1</strong></td> <td>1</td> <td>1</td> <td>1</td> <td>100</td> <td>63</td> <td>85.71</td> </tr> </tbody> </table> <ul> <li>ConcurrencySafety property:</li> </ul> <table> <tbody> <tr> <td>SV-COMP Tool</td> <td><strong>Function calls</strong></td> <td><strong>Threads</strong></td> <td>Assumptions</td> <td>Conditions</td> <td>Thoroughness</td> <td>Error traces</td> <td>Validation rate</td> </tr> <tr> <td>CBMC</td> <td><strong>0</strong></td> <td><strong>1</strong></td> <td>1</td> <td>0</td> <td>50</td> <td>277</td> <td>87</td> </tr> <tr> <td>CPA-Lockator</td> <td><strong>1</strong></td> <td><strong>1</strong></td> <td>1</td> <td>1</td> <td>100</td> <td>83</td> <td>26.51</td> </tr> <tr> <td>CPAChecker</td> <td><strong>1</strong></td> <td><strong>1</strong></td> <td>1</td> <td>1</td> <td>100</td> <td>257</td> <td>100</td> </tr> <tr> <td>Cseq</td> <td><strong>1</strong></td> <td><strong>1</strong></td> <td>1</td> <td>0</td> <td>100</td> <td>277</td> <td>94.58</td> </tr> <tr> <td>Dartagnan</td> <td><strong>0</strong></td> <td><strong>1</strong></td> <td>0</td> <td>0</td> <td>50</td> <td>281</td> <td>92.17</td> </tr> <tr> <td>Deagle</td> <td><strong>0</strong></td> <td><strong>1</strong></td> <td>1</td> <td>0</td> <td>50</td> <td>280</td> <td>96.07</td> </tr> <tr> <td>DIVINE</td> <td><strong>0</strong></td> <td><strong>0</strong></td> <td>0</td> <td>0</td> <td>0</td> <td>230</td> <td>80.87</td> </tr> <tr> <td>EBF</td> <td><strong>0</strong></td> <td><strong>0</strong></td> <td>0</td> <td>0</td> <td>0</td> <td>282</td> <td>89.01</td> </tr> <tr> <td>ESBMC-incr</td> <td><strong>0</strong></td> <td><strong>1</strong></td> <td>1</td> <td>0</td> <td>50</td> <td>68</td> <td>79.41</td> </tr> <tr> <td>ESBMC-kind</td> <td><strong>0</strong></td> <td><strong>1</strong></td> <td>1</td> <td>0</td> <td>50</td> <td>263</td> <td>89.73</td> </tr> <tr> <td>Graves-CPA</td> <td><strong>1</strong></td> <td><strong>1</strong></td> <td>1</td> <td>1</td> <td>100</td> <td>261</td> <td>99.23</td> </tr> <tr> <td>Graves-Par</td> <td><strong>1</strong></td> <td><strong>1</strong></td> <td>1</td> <td>1</td> <td>100</td> <td>28</td> <td>100</td> </tr> <tr> <td>Infer</td> <td><strong>0</strong></td> <td><strong>0</strong></td> <td>0</td> <td>0</td> <td>0</td> <td>634</td> <td>0</td> </tr> <tr> <td>Lazy-CSeq</td> <td><strong>1</strong></td> <td><strong>1</strong></td> <td>1</td> <td>1</td> <td>100</td> <td>274</td> <td>94.89</td> </tr> <tr> <td>LF-checker</td> <td><strong>0</strong></td> <td><strong>1</strong></td> <td>1</td> <td>0</td> <td>50</td> <td>286</td> <td>85.31</td> </tr> <tr> <td>PeSCo-CPA</td> <td><strong>1</strong></td> <td><strong>1</strong></td> <td>1</td> <td>1</td> <td>100</td> <td>256</td> <td>100</td> </tr> <tr> <td>PIChecker</td> <td><strong>1</strong></td> <td><strong>0</strong></td> <td>1</td> <td>1</td> <td>50</td> <td>269</td> <td>98.14</td> </tr> <tr> <td>Symbiotic</td> <td><strong>0</strong></td> <td><strong>1</strong></td> <td>1</td> <td>0</td> <td>50</td> <td>110</td> <td>92.73</td> </tr> <tr> <td>UAutomizer</td> <td><strong>0.5</strong></td> <td><strong>1</strong></td> <td>1</td> <td>1</td> <td>75</td> <td>297</td> <td>94.95</td> </tr> <tr> <td>UgemCutter</td> <td><strong>0.5</strong></td> <td><strong>1</strong></td> <td>1</td> <td>1</td> <td>75</td> <td>283</td> <td>96.47</td> </tr> <tr> <td>UTaipan</td> <td><strong>0.5</strong></td> <td><strong>1</strong></td> <td>1</td> <td>1</td> <td>75</td> <td>293</td> <td>96.25</td> </tr> </tbody> </table> <h3>5. Overall distance for all possible combinations of elements for thoroughness</h3> <p>This section presents the overall difference (i.e., the sum of differences between witness thoroughness and validation rates for each tool) when thoroughness is calculated based on all possible combinations of witness elements (assumptions, conditions, thread specifics, and function calls). The set of witnesses is the same as in the previous section. The following tables provide details for each property, with the minimum difference highlighted:</p> <ul> <li>MemSafety property:</li> </ul> <table> <tbody> <tr> <td>Combination</td> <td>Overall difference</td> </tr> <tr> <td>Function calls</td> <td>250.3</td> </tr> <tr> <td>Thread specifics</td> <td>444.6</td> </tr> <tr> <td>Assumptions</td> <td>353.7</td> </tr> <tr> <td>Conditions</td> <td>250.3</td> </tr> <tr> <td>Function calls, Thread specifics</td> <td>294.6</td> </tr> <tr> <td>Assumptions, Function calls</td> <td>238.08</td> </tr> <tr> <td>Conditions, Function calls</td> <td>250.3</td> </tr> <tr> <td>Assumptions, Thread specifics</td> <td>344.6</td> </tr> <tr> <td>Conditions, Thread specifics</td> <td>294.6</td> </tr> <tr> <td>Assumptions, Conditions</td> <td>238.08</td> </tr> <tr> <td>Assumptions, Function calls, Thread specifics</td> <td>277.94</td> </tr> <tr> <td>Conditions, Function calls, Thread specifics</td> <td>244.59</td> </tr> <tr> <td><strong>Assumptions, Conditions, Function calls</strong></td> <td><strong>221.41</strong></td> </tr> <tr> <td>Assumptions, Conditions, Thread specifics</td> <td>277.94</td> </tr> <tr> <td>Assumptions, Conditions, Function calls, Thread specifics</td> <td>244.6</td> </tr> </tbody> </table> <ul> <li>NoOverflow property:</li> </ul> <table> <tbody> <tr> <td>Combination</td> <td>Overall difference</td> </tr> <tr> <td>Function calls</td> <td>953.06</td> </tr> <tr> <td>Thread specifics</td> <td>745.4</td> </tr> <tr> <td><strong>Assumptions</strong></td> <td><strong>192.94</strong></td> </tr> <tr> <td>Conditions</td> <td>803.06</td> </tr> <tr> <td>Function calls, Thread specifics</td> <td>778.06</td> </tr> <tr> <td>Assumptions, Function calls</td> <td>478.06</td> </tr> <tr> <td>Conditions, Function calls</td> <td>878.06</td> </tr> <tr> <td>Assumptions, Thread specifics</td> <td>445.4</td> </tr> <tr> <td>Conditions, Thread specifics</td> <td>703.06</td> </tr> <tr> <td>Assumptions, Conditions</td> <td>403.06</td> </tr> <tr> <td>Assumptions, Function calls, Thread specifics</td> <td>528.8</td> </tr> <tr> <td>Conditions, Function calls, Thread specifics</td> <td>786.41</td> </tr> <tr> <td>Assumptions, Conditions, Function calls</td> <td>586.43</td> </tr> <tr> <td>Assumptions, Conditions, Thread specifics</td> <td>478.79</td> </tr> <tr> <td>Assumptions, Conditions, Function calls, Thread specifics</td> <td>590.56</td> </tr> </tbody> </table> <ul> <li>NoTermination property:</li> </ul> <table> <tbody> <tr> <td>Combination</td> <td>Overall difference</td> </tr> <tr> <td>Function calls</td> <td>279.39</td> </tr> <tr> <td>Thread specifics</td> <td>226.99</td> </tr> <tr> <td>Assumptions</td> <td>176.59</td> </tr> <tr> <td>Conditions</td> <td>232.91</td> </tr> <tr> <td>Function calls, Thread specifics</td> <td>204.39</td> </tr> <tr> <td><strong>Assumptions, Function calls</strong></td> <td><strong>84.83</strong></td> </tr> <tr> <td>Conditions, Function calls</td> <td>254.39</td> </tr> <tr> <td>Assumptions, Thread specifics</td> <td>107.43</td> </tr> <tr> <td>Conditions, Thread specifics</td> <td>182.91</td> </tr> <tr> <td>Assumptions, Conditions</td> <td>63.35</td> </tr> <tr> <td>Assumptions, Function calls, Thread specifics</td> <td>106.82</td> </tr> <tr> <td>Conditions, Function calls, Thread specifics</td> <td>212.73</td> </tr> <tr> <td>Assumptions, Conditions, Function calls</td> <td>112.74</td> </tr> <tr> <td>Assumptions, Conditions, Thread specifics</td> <td>93.67</td> </tr> <tr> <td>Assumptions, Conditions, Function calls, Thread specifics</td> <td>116.89</td> </tr> </tbody> </table> <ul> <li>ReachSafety property:</li> </ul> <table> <tbody> <tr> <td>Combination</td> <td>Overall difference</td> </tr> <tr> <td><strong>Function calls</strong></td> <td><strong>212.74</strong></td> </tr> <tr> <td>Thread specifics</td> <td>607.58</td> </tr> <tr> <td>Assumptions</td> <td>557.82</td> </tr> <tr> <td>Conditions</td> <td>312.74</td> </tr> <tr> <td>Function calls, Thread specifics</td> <td>357.58</td> </tr> <tr> <td>Assumptions, Function calls</td> <td>316.16</td> </tr> <tr> <td>Conditions, Function calls</td> <td>262.74</td> </tr> <tr> <td>Assumptions, Thread specifics</td> <td>507.32</td> </tr> <tr> <td>Conditions, Thread specifics</td> <td>407.58</td> </tr> <tr> <td>Assumptions, Conditions</td> <td>366.16</td> </tr> <tr> <td>Assumptions, Function calls, Thread specifics</td> <td>373.98</td> </tr> <tr> <td>Conditions, Function calls, Thread specifics</td> <td>307.56</td> </tr> <tr> <td>Assumptions, Conditions, Function calls</td> <td>299.48</td> </tr> <tr> <td>Assumptions, Conditions, Thread specifics</td> <td>407.32</td> </tr> <tr> <td>Assumptions, Conditions, Function calls, Thread specifics</td> <td>332.32</td> </tr> </tbody> </table> <ul> <li>ConcurrencySafety property:</li> </ul> <table> <tbody> <tr> <td>Combination</td> <td>Overall difference</td> </tr> <tr> <td>Function calls</td> <td>1016.62</td> </tr> <tr> <td>Thread specifics</td> <td>442.72</td> </tr> <tr> <td>Assumptions</td> <td>430.78</td> </tr> <tr> <td>Conditions</td> <td>980.44</td> </tr> <tr> <td>Function calls, Thread specifics</td> <td>637.9</td> </tr> <tr> <td>Assumptions, Function calls</td> <td>641.62</td> </tr> <tr> <td>Conditions, Function calls</td> <td>980.78</td> </tr> <tr> <td><strong>Assumptions, Thread specifics</strong></td> <td><strong>427.06</strong></td> </tr> <tr> <td>Conditions, Thread specifics</td> <td>626.72</td> </tr> <tr> <td>Assumptions, Conditions</td> <td>630.44</td> </tr> <tr> <td>Assumptions, Function calls, Thread specifics</td> <td>512.89</td> </tr> <tr> <td>Conditions, Function calls, Thread specifics</td> <td>735.42</td> </tr> <tr> <td>Assumptions, Conditions, Function calls</td> <td>739.14</td> </tr> <tr> <td>Assumptions, Conditions, Thread specifics</td> <td>510.03</td> </tr> <tr> <td>Assumptions, Conditions, Function calls, Thread specifics</td> <td>614.56</td> </tr> </tbody> </table> </div>

opencc-by-4.0Apr 2024View details →
zenodo40/100

Figures 6–9 in The potential of Malaise traps as an important tool in butterfly (Lepidoptera, Papilionoidea) inventories, based on studies conducted in Republic of Congo

Figures 6–9 – Examples showing the condition of larger butterflies sampled in Malaise traps in Parc National de Nouabalé-Ndoki, Republic of Congo. 6 – Papilio (Princeps) hesperus hesperus Westwood. 7 – Papilio (Princeps) chrapkowskoides nurettini Koçak. 8 – Laodice mycerina nausicaa (Staudinger). 9 – Charaxes nobilis nobilis Druce.

opencc-by-4.0Jul 2024View details →
zenodo40/100

Figures 2–5 in The potential of Malaise traps as an important tool in butterfly (Lepidoptera, Papilionoidea) inventories, based on studies conducted in Republic of Congo

Figures 2–5 – Malaise traps deployed in various localities and habitat types in Parc National de Nouabalé-Ndoki, Republic of Congo. 2 – Bomassa Forest (Gressitt &amp; Gressitt-type trap over streambed). 3 – Makao Forest (Townes-type trap over streambed). 4 – Mondika Camp (Gressitt &amp; Gressitt-type trap across forest path). 5 – Mombongo Camp (Gressitt &amp; Gressitttype trap across disused forest road). Photographs: Violette Dérozier.

opencc-by-4.0Jul 2024View details →
zenodo40/100

Figure 1 – Parc National d in The potential of Malaise traps as an important tool in butterfly (Lepidoptera, Papilionoidea) inventories, based on studies conducted in Republic of Congo

Figure 1 – Parc National d'Nouabalé-Ndoki (PNNN) and the surrounding Unité Forestière d'Aménagement. Sampling localities: 1. Mombongo Camp; 2. Bomassa Forest; 3. Wali Forest; 4. Mondika Camp; 5. Mbeli Camp; 6. Ndoki Formation; 7. Makao Forest.

opencc-by-4.0Jul 2024View details →
zenodo40/100

FIG. 2 in Finite element analysis of the proximal phalanx of the thumb in Hominoidea during simulated stone tool use

FIG. 2. — Free-body diagram of the phalanx in the different scenarios. This figure depicts the boundary conditions, areas of insertion of muscles, and direction of forces. For all loading configurations, joint reaction forces resulted from the rigid boundary constraints that were fixed at the distal joint in X, Y and Z-axes (light blue area), and at the proximal joint in the X-axis (dark blue area). The hammer reaction force (HRF) was applied to the entire palmar surface of the bone. 3.29 N for the HRF was simulated for Sc 1 and 3, and 7.65 N for Sc 2 and 4. Phalanges are shown in palmar (right) and radial (left) views.

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

FIG. 5 in Finite element analysis of the proximal phalanx of the thumb in Hominoidea during simulated stone tool use

FIG. 5. — Box-plots of von Mises stress (MPa) distribution for all species under different scenarios, until Q95 (Sc 1 in grey, Sc 2 in yellow, Sc 3 in green and Sc 4 in red). The first row shows stress distribution of the models using the extant human as a reference to scale muscular forces in all other specimens, whereas the second one shows the results when the chimpanzee is used as a reference. Species are ordered from higher to lower peak stresses.

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

FIG. 1 in Finite element analysis of the proximal phalanx of the thumb in Hominoidea during simulated stone tool use

FIG. 1. — Biomechanical model of hammerstone use: B, corresponds to a zoom in palmar view of the area of interest during A, the grip of a human individual (based on Marzke et al. 1998). B, shows the angles of the muscular forces acting on the PP1. HRF is in 90° relative to the horizontal line for scenarios 1 and 2 and in 45° for scenarios 2 and 4. This force was applied on the entire palmar surface of the PP1 except in the joint areas and is represented with a hatched rectangle. Angles of the muscle forces are shown relative to the horizontal line. Abbreviations: FAP, Adductor Pollicis Force; FAPB, Abductor Pollicis Brevis Force; FFPB, Flexor Pollicis Brevis Force; EPB, direction force was applied in 16.7° and is not showed here as it attached on the dorsal surface of the PP1. Grey rectangles represent the origin areas of the muscles.

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

FIG. 3 in Finite element analysis of the proximal phalanx of the thumb in Hominoidea during simulated stone tool use

FIG. 3. — Von Mises stress maps for all analyzed species under different loading scenarios using the extant human as reference to scale the simulated muscular forces in all other specimens. Species are ordered from higher to lower peak stresses values. Phalanges are shown at the same length. MPa bar is set at 12 MPa.

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

FIG. 4 in Finite element analysis of the proximal phalanx of the thumb in Hominoidea during simulated stone tool use

FIG. 4. — Von Mises stress maps for all analyzed species under different loading scenarios using the chimpanzee as reference to scale the simulated muscular forces in all other specimens. Species are ordered from higher to lower peak stresses values. Images are not scaled. MPa is set at 25 MPa.

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

TABLE 2 in Finite element analysis of the proximal phalanx of the thumb in Hominoidea during simulated stone tool use

<p>TABLE 2. &mdash; Percentage of main locomotor behavoir of the non-human sample, according to Hunt (2004).</p><table><tbody><tr><th><b>Taxon</b></th><th><b>Climb</b></th><th><b>Braquiate</b></th><th><b>Clamber</b></th><th><b>Walk</b></th></tr></tbody><tbody><tr><th>Chimpanzee</th><td>6.5</td><td>0.8</td><td>0.0</td><td>89.9</td></tr><tr><th>Gorilla</th><td>19.7</td><td>3.6</td><td>0.0</td><td>64.4</td></tr><tr><th>Orangutan</th><td>31.3</td><td>15.5</td><td>40.7</td><td>12.0</td></tr><tr><th>Gibbon</th><td>34.2</td><td>51.2</td><td>0.0</td><td>0.0</td></tr></tbody></table>

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

Ecosystem-based marine spatial planning assessment tool video tutorial

<p><span>Aiming at promoting the capacity building of competent authorities, scientists and consultants, a novel tool is proposed for assessing the alignment of marine spatial planning processes with ecosystem-based approach principles and to guide its operationalization.</span></p> <p><span>The EB-MSP assessment tool is developed with the ambition of providing a fit-for-purpose tool to overcome the ecosystem-based marine spatial planning implementation barriers reported by experts and managers.</span></p> <p><span>The EB-MSP assessment tool is designed to apply to any spatial plan, regardless of its stage of development: assessment of existing plans, plans in progress; or different national plans in a transboundary region.</span></p> <p><span>The EB-MSP tool can be accessed at https://aztidata.es/EB-MSP</span></p> <p><span>The EB-MSP assessment tool leads users through a step-by-step procedure for evaluating a specific plan.</span></p> <p><span>Upon first access, the user must register. This way, the users can conduct multiple assessments in a single session or different sessions, and can retrieve the information from previous sessions.</span></p> <p><span>The evaluation can be conducted by documenting the actions adopted during the planning process stages, or by examining how ecosystem-based marine spatial planning cross-cutting topics, have been incorporated into the plan.</span></p> <p><span>The user has to provide information about 130 statements that reflect the actions or tasks adopted during the planning process.</span></p> <p><span>For each action, six complementary fields of information have to be provided by the user:</span></p> <ol> <li><span><span><span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</span></span></span><span>the degree of implementation of the action; </span></li> <li><span><span><span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</span></span></span><span>the relevance of the action for the assessed planning site; </span></li> <li><span><span><span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </span></span></span><span>the main source of knowledge base supporting the action; </span></li> <li><span><span><span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </span></span></span><span>the respondent's confidence; </span></li> <li><span><span><span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </span></span></span><span>approaches, tools and methods implemented; and </span></li> <li><span><span><span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </span></span></span><span>justification of the responses</span></li> </ol> <p><span>Once the assessment is performed, the results are displayed as dynamic graphs that can be downloaded.</span></p> <p><span>The responses are also stored in a table, which can be downloaded as an Excel spreadsheet.</span></p>

opencc-by-4.0Nov 2024View details →
zenodo40/100

Climate-Oriented Seed Sourcing Tool (COSST)

<p><strong>Description</strong></p> <p>R code for the article "COSST: a tool to facilitate seed provenancing for climate-smart ecosystem restoration" by Silva <em>et al</em>. (2024) <em>J. Appl. Ecol</em>.</p> <p><strong>Abstract</strong></p> <p>Selecting the best seed sources is a key step in ecological restoration planning especially under climate change. Seed provenancing strategies include composite, aiming to reproduce natural gene flow; predictive, focusing on future climate adaptation; and climate-adjusted, a combination of composite and predictive. Yet, implementing different seed provenancing principles remains a challenge. To fill this methodological gap, we developed the Climate-Oriented Seed Sourcing Tool (COSST), a tool built in R capable of suggesting priority areas for seed sourcing according to composite, predictive, or climate-adjusted strategies, as well as the restoration site and focal species. The tool derives its inputs from Species Distribution Models (SDMs), which require occurrence and climate data only. COSST accommodates multiple climatic variables, weights the variables according to species-specific sensitivities, and accounts for uncertainties between climate forecasts. We demonstrated the flexibility of COSST using <em>Caryocar brasiliense</em> (pequi), a tree native to the Brazilian Cerrado, as a case study. The tool identified optimal areas for collecting C. brasiliense seeds and estimated the proportion of seeds to be sourced from various suppliers. We made available an R code for running COSST along with a Shiny application for data visualization. Our tool can guide where to source seeds for species lacking range-wide information on genetic structure, which is the case for a substantial proportion of the tropical flora, where ecosystem restoration is of paramount importance.</p>

opencc-by-4.0Dec 2024View details →
zenodo40/100

Dataset supporting the tool 'delfies: a Python package for the detection of DNA breakpoints with neo-telomere addition'

<h2>Purpose</h2> <p><br>These data can be used to test my tool&nbsp;<a href="https://github.com/bricoletc/delfies">delfies </a>on real data, to get a concrete sense of its inputs/outputs and test that it is&nbsp;<br>properly installed.</p> <h2>Description</h2> <h3>Genome</h3> <p>I downloaded the genome of&nbsp;<em>Oscheius onirici</em>, accession: <a href="https://www.ebi.ac.uk/ena/browser/view/GCA_932521025.1">GCA_932521025</a>.</p> <p>I subsampled the genome to the last 2kbp of chromosome I, which contains an elimination breakpoint,&nbsp;<br>using `seqkit` v2.8.2, giving the FASTA file in this release.</p> <h3>Sequencing data</h3> <p>I then downloaded the following sequencing data for *O. onirici*, from the European Nucleotide Archive:</p> <ul> <li>ERR5967937: Illumina NovaSeq 6000 paired end short reads. Reads are 2x150bp with average per-base quality of Q27.</li> <li>ERR10796202: Oxford Nanopore PromethION long reads. Reads have average length 11.9kbp and average per-base quality Q11.4.</li> <li>ERR7979900: Pacific Biosciences (PacBio) Sequel II long reads. Reads have average length 11.1kbp and average per-base quality Q28.<br><br></li> </ul> <p>And aligned them to the above genome with `minimap2` version 2.26-r1175, using the following presets:&nbsp;<br>"map-ont" for the Nanopore data, "map-hifi" for the PacBio data, "sr" for the Illumina data.</p> <p>After sorting with `samtools`, this gives the BAM files in this release.</p> <h3>Running delfies</h3> <p>I then ran `delfies` version 0.6.0 on each BAM and genome, as:</p> <p>```sh<br>delfies --threads 16 \<br>&nbsp; &nbsp; --telo_forward_seq TTAGGC \<br>&nbsp; &nbsp; --breakpoint_type all \<br>&nbsp; &nbsp; --min_mapq 20 \<br>&nbsp; &nbsp; --min_supporting_reads 6 \<br>&nbsp; &nbsp; \${genome} \${bam} \${odirname}<br>```</p> <p>The three resulting output directories are in this release, prefixed with `delfies_`.</p> <p><strong>A single, identical breakpoint is found using all three BAMs</strong> (see files '*breakpoint_locations.bed').</p> <h3>Data source</h3> <p>The above raw data were produced and released by the Wellcome Sanger Institute as part of projects&nbsp;<br><a href="https://www.ebi.ac.uk/ena/browser/view/PRJEB51305">PRJEB51305</a> and <a href="https://www.ebi.ac.uk/ena/browser/view/PRJEB59023">PRJEB59023.</a></p>

opencc-by-4.0Nov 2024View details →
zenodo40/100

Tabula sapiens scvi-tools models for scvi hub

<p>These are pre-trained models and AnnData datasets based on Tabula sapiens. Models were subsequentially uploaded to scvi-hub and this repository is there to restore the models on hugging face.</p> <p>Data is preprocessed data downloaded from&nbsp;<a href="https://cellxgene.cziscience.com/collections/e5f58829-1a66-40b5-a624-9046778e74f5">https://cellxgene.cziscience.com/collections/e5f58829-1a66-40b5-a624-9046778e74f5</a>. Please refer to their data usage guide before reusing the data.</p>

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

Data set from: Can laboratory-based XAFS compete with XRD and Mössbauer spectroscopy as a tool for quantitative species analysis?

<p><strong>Abstract:</strong> This work investigated the capability of quantitative laboratory X-ray Absorption Fine Structure Spectroscopy (lab-XAFS) via Linear Combination Fitting (LCF) of reference spectra in comparison with quantitative X-ray diffraction (XRD) and M&ouml;ssbauer spectroscopy. While lab-XAFS already show good results when performing LCF with significant different spectra of the species to be identified, the method is challenging when the reference spectra and possibly species in the sample are very similar as it is the case for &alpha;-Fe<sub>2</sub>O<sub>3</sub>, &gamma;- Fe<sub>2</sub>O<sub>3</sub> and Fe<sub>3</sub>O<sub>4</sub>. For this investigation an iron oxide mineral with origin from Mexico (here named Mexican Magnetite) with different iron oxide phases was used and measured using all three methods.</p> <p>&nbsp;</p> <p>This data set contains the raw data of the work &ldquo;<em>Can laboratory-based XAFS compete with XRD and M&ouml;ssbauer spectroscopy as a tool for quantitative species analysis? Critical evaluation using the example of a natural iron ore</em>&rdquo; of XAFS, XRD and M&ouml;ssbauer measurements. This includes XAFS, M&ouml;ssbauer and XRD spectra of the reference materials &alpha;-Fe<sub>2</sub>O<sub>3</sub>, Fe<sub>3</sub>O<sub>4</sub> and the sample Mexican magnetite, the XAFS spectra of the reference material &gamma;- Fe<sub>2</sub>O<sub>3</sub> and the XAFS, XRD and M&ouml;ssbauer spectra of three different &alpha;-Fe<sub>2</sub>O<sub>3</sub>/Fe<sub>3</sub>O<sub>4</sub> mixtures.</p> <p>&nbsp;</p> <p><u>Sample information/sample list</u></p> <p><strong>sample/references:</strong> The sample and the corresponding short cut name used in the data files is listed. Furthermore the method the sample was measured with is also listed.</p> <table> <tbody> <tr> <td> <p><strong>Short cut name</strong></p> </td> <td> <p><strong>&nbsp;Sample/reference</strong></p> </td> <td> <p><strong>Measured with</strong></p> </td> </tr> <tr> <td> <p>MexicanMagnetite</p> </td> <td> <p>&nbsp;Iron oxide mineral with origin in Mexico</p> </td> <td> <p>XAFS, XRD, M&ouml;ssbauer</p> </td> </tr> <tr> <td> <p>Fe2O3</p> </td> <td> <p>Fe2O3-alpha / Hematite</p> </td> <td> <p>XAFS, XRD, M&ouml;ssbauer</p> </td> </tr> <tr> <td> <p>Fe3O4</p> </td> <td> <p>Fe3O4 / Magnetite</p> </td> <td> <p>XAFS, XRD, M&ouml;ssbauer</p> </td> </tr> <tr> <td> <p>Fe</p> </td> <td> <p>Iron powder</p> </td> <td> <p>XAFS</p> </td> </tr> <tr> <td> <p>Fe2O3-alpha</p> </td> <td> <p>Fe2O3-alpha / Hematite</p> </td> <td> <p>XAFS</p> </td> </tr> <tr> <td> <p>Fe2O3-gamma</p> </td> <td> <p>Fe2O3-gamma / Maghemite</p> </td> <td> <p>XAFS</p> </td> </tr> <tr> <td> <p>30-70</p> </td> <td> <p>Mixture of&nbsp; 30 % Fe2O3-alpha/ 70 %Fe3O4</p> </td> <td> <p>XAFS, XRD, M&ouml;ssbauer</p> </td> </tr> <tr> <td> <p>50-50</p> </td> <td> <p>Mixture of&nbsp; 50 % Fe2O3-alpha/ 50 %Fe3O4</p> </td> <td> <p>XAFS, XRD, M&ouml;ssbauer</p> </td> </tr> <tr> <td> <p>70-30</p> </td> <td> <p>Mixture of&nbsp; 70 % Fe2O3-alpha/ 30 %Fe3O4</p> </td> <td> <p>XAFS, XRD, M&ouml;ssbauer</p> </td> </tr> </tbody> </table> <p>&nbsp;</p> <p><strong>Mixtures ratios:</strong> The prepared Fe2O3-Fe3O4 model mixtures with the weight-in ratios and the actual achieved mass percentage ratio between the two iron species, taken impurities of the used materials into account, are listed below. The short cut name is the name used in the data files (see table above).</p> <table> <tbody> <tr> <td> <p><strong>Short cut name</strong></p> </td> <td> <p><strong>Actual achieved weigh-in ratios</strong></p> <p><strong>m(Fe2O3)/m(Fe3O4)*</strong></p> </td> <td> <p><strong>Actual achieved mass percentage ratios &omega;rel(Fe2O3) / &omega;rel(Fe3O4)</strong></p> </td> </tr> <tr> <td> <p>30-70</p> </td> <td> <p>0.31380 g / 0.7059 g</p> </td> <td> <p>31.8 / 68.2</p> </td> </tr> <tr> <td> <p>50-50</p> </td> <td> <p>0.5140 g / 0.5174 g</p> </td> <td> <p>50.6 / 49.4</p> </td> </tr> <tr> <td> <p>70-30</p> </td> <td> <p>0.7037 g / 0.3041 g</p> </td> <td> <p>70.5 / 29.5</p> </td> </tr> </tbody> </table> <p>*the given masses here, ar the masses of the materials of the mixtures before sampel prepration. For the sample prepration the mass&nbsp; applied on the tape or mixed with wax is about 5-10 mg.</p> <p><u>Spectrometer Specifications</u></p> <p><strong>XAFS:</strong> The experimental setup for the laboratory XAFS measurement is based on the Highly Annealed Pyrolytic Graphite (HAPG) von H&aacute;mos spectrometer with the use of a cylindrically shaped crystal.</p> <p>As detector unit the pixelated X-ray hybrid-CMOS detector Dectris Eiger2 R 500k was used. The area of detection is 77.3 mm x 38.6 mm with a pixel size of 75 &micro;m x 75 &micro;m. The X-ray source was a water-cooled micro focus X-ray tube with molybdenum as anode material, a power of 30 Watt optimised at 15 kV and a spot size of 70 &micro;m.</p> <p><strong>Sample preparation</strong>: &alpha;-Fe<sub>2</sub>O<sub>3</sub>, Fe<sub>3</sub>O<sub>4</sub>, the three &alpha;-Fe<sub>2</sub>O<sub>3</sub>/Fe<sub>3</sub>O<sub>4</sub> mixtures and the sample Mexican magnetite were applied on adhesive tape, sliced in 1cm x 1cm pieces characterized with XRF to determine the iron content as [<em>Q</em>] = mg/cm&sup2; and then stacked by taking the iron content of each slice into account to achieve an absorption of <em>&micro;*Q</em> of about 1 at the edge.</p> <p>The &gamma;- Fe<sub>2</sub>O<sub>3</sub> and also the three &alpha;-Fe<sub>2</sub>O<sub>3</sub>/Fe<sub>3</sub>O<sub>4</sub> mixtures were prepared as Pellet. Here the sample material was mixed with Hoechst Wax C in a ratio of 1:6, mixed in a vortex shaker and then pressed with a hydraulic press with a Pellet diameter of 13 mm. The amount of the wax/sample powder material was weight before inserting in the press to the amount of <em>Q</em> to achieve a <em>&micro;*Q</em> of about 1 with a 13 mm Pellet.</p> <p>Shifts of the energy axis as well as a widening or compression of this axis could be present when comparing the data with other data sets of other spectrometer or synchrotron radiation facilities, since no precise energy calibration was carried out due to the reason that the samples were compared to the measured references and would have the same shift, widening or compression.</p> <p>&nbsp;</p> <p><strong>XRD:</strong> Two different commercial XRD set ups have been used. For the Mexican magnetite the Benchtop XRD spectrometer Bruker D2Phaser with a Cobalt X-ray source and a SSD160 detector (active length = 12 mm) was used. The measurement range was 10&deg;- 90&deg; 2theta with 0.014&deg; step size and 4.8 s/step, resulting in a total measurement time of 8h. During the measurement the sample was rotated with 10 rpm. The sample was filled in PMMA-holders (&Oslash; 2.5 mm) using the top-loading technique. The analysis was carried out using a 1-mm fixed divergence slit, a 2.5&deg; primary and a 4&deg; secondary soller collimator, a fixed knife edge (3 mm above the sample surface), and an Fe K&beta; filter (2.5).</p> <p>For the X-ray diffraction measurements of the &alpha;-Fe2O3/Fe3O4 mixtures and the pure references a Panalytical X&rsquo;Pert PRO diffractometer with a Bragg-Brentano setup was used. The diffractometer operates with a Cu anode and without a monochromator (Cu-Kalpha radiation) at 40 kV and 30 mA. The diffraction data were obtained over a measurement range of 10&ndash;120&deg; 2theta. Samples were applied flat on a cut-off Si wafer attached to the sample holder.</p> <p><em>&nbsp;</em></p> <p><strong>M&ouml;ssbauer:</strong> M&ouml;ssbauer spectroscopy was performed at a MIMOS II type spectrometer with a <sup>57</sup>Co source (in rhodium matrix). For the analyses the <sup>57</sup>Fe-&gamma;-line E = 14.4 keV was used and &alpha;-iron (&alpha;-Fe foil) was applied for the velocity calibration before the samples were analyzed. The samples were prepared in plastic powder sample holders and measured in transmission mode at room temperature. The measurement time varied between 12 h and 120 h depending on the sample.</p> <p>&nbsp;</p> <p><strong>Information on data sets</strong></p> <p>XAFS - this folder contains the XAFS spectra as intensity file with I0 (without the sample) and the It (transmission signal through the sample) for each sample. Multiple samples (It) share the same I0 and are therefore in the same data set. The Number in the filename between &ldquo;XAFS&ldquo; and &ldquo;data-set..&rdquo; is the date of the measurement in the following format: YYYY_MM_DD. The first column in each file is the energy in unit eV. The abbreviation &ldquo;WP&rdquo; after each sample name in the header means &ldquo;<strong>W</strong>ax <strong>P</strong>ellet&rdquo; and indicates that the measurement was performed on a sample prepared as a wax pellet, the number (WP<strong>1</strong>) indicates the number of the pellet. Two pellets of each mixture were prepared to investigate the influence of the sample preparation. If the sample name is missing &ldquo;WP#&rdquo; the sample was prepared on adhesive tape as described above. The information on the contents of each data set as well as the measurement time (t = #h) for each It of the sample/reference can be found in data_dictionary_v2.txt.</p> <p>The intensity is normalized to counts per 1800 seconds in a 0.25 eV (for data-set-1) and 1 eV (for data-set-2, data-set-3 and data-set-4) energy interval with the indicated central bin energy.</p> <p>&nbsp;</p> <p>XRD - this folder contains the raw intensity files over 2theta (ASC-file). Each sample has its own file with the first column for the 2theta in unit degree and the second column for the measured intensity.</p> <p>The Number in the file name between XRD and sample name (e. g. Fe2O3, 30-70) is the date of the measurement in the following format: YYYY_MM_DD.</p> <p>&nbsp;</p> <p>MOESSBAUER - this folder contains the recoil Lorentz site analysis fit data of the samples. The files&nbsp; consist of the observed intensity (Iobs) over the velocity (v (mm/s)), including the calcucalted intensity (Icalc) and the fits of the subspectra (Sextet Site 1, etc. ).&nbsp; Each sample has it owns file. While the references substances&nbsp;<br>Fe2O3 and Fe3O4 were measured between 2016 and 2019, the MexicanMagnetite was measured 2020. An exact measurement date can&rsquo;t be determined anymore.</p> <p>&nbsp;</p> <p>The corresponding sample to the short cut name (e. g. Fe2O3, 30-70,..) in the files can be found above and is listed in the <em>data_dictionary.txt</em> file as well.</p> <p>&nbsp;</p>

opencc-by-4.0May 2024View 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

ScienceDex for faculty

Your academic CV and NIH biosketch

Make your CV in your school's format and your NIH biosketch from it, then download both as Word files.