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

PROGRAMS project. Machine tool data from Aurrenak S. Coop. on 2020 Week 26

<p>These data were collected from FIDIA machine tool controller during milling operation.</p>

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

CVE-2020-12399: research data and tooling

<p>This dataset and software tools are for reproducing the research results related to <a href="https://nvd.nist.gov/vuln/detail/CVE-2020-12399">CVE-2020-12399</a>, resulting from the manuscript &quot;D&eacute;j&agrave; vu: Side-channel analysis of Mozilla&#39;s NSS&quot;, to appear at <a href="https://www.sigsac.org/ccs/CCS2020/">ACM CCS 2020</a>.</p> <ul> <li>The data is from a remote timing attack against the NSS v3.51 implementation of DSA signing.</li> <li>The client machine was a 3.1 GHz 64-bit Intel i5-2400 CPU (Sandy Bridge).</li> <li>The server machine was a Raspberry Pi 3 Model B plus board containing a 1.4 GHz 64-bit quad-core Cortex-A53 processor.</li> <li>The client and server were connected by a Cisco 9300 series enterprise switch over Gbit Ethernet.</li> <li>The data contains pow(2,18) samples.</li> <li>The data was used to produce Figure 1 in the paper and contains all the remote timing attack data from Section 4.</li> </ul> <p>Data description</p> <p>The file <code>remote_timings.json</code> contains a single JSON array. Each entry is a dictionary representation of one digital signature. A description of the dictionary fields follows.</p> <ul> <li><code>p</code>: prime (DSA parameter).</li> <li><code>q</code>: generator order (DSA parameter).</li> <li><code>g</code>: generator (DSA parameter).</li> <li><code>x</code>: the DSA private key.</li> <li><code>y</code>: the corresponding public key.</li> <li><code>r</code>: first component of the DSA signature.</li> <li><code>s</code>: second component of the DSA signature.</li> <li><code>k</code>: the ground truth nonce generated during DSA signing.</li> <li><code>k_len</code>: the ground truth number of bits in said nonce.</li> <li><code>msg</code>: message digitally signed.</li> <li><code>h</code>: SHA-256 hash of said message. (Truncated to the same bitlen as q.)</li> <li><code>id</code>: ignored.</li> <li><code>latency</code>: the measured wall clock time (CPU clock cycles) to produce the digital signature.</li> </ul> <p>Prerequisites</p> <pre><code>sudo apt install openssl python3-ijson xxd jq</code></pre> <p>Data setup</p> <p>Extract the JSON:</p> <pre><code>tar xf remote_timings_rpi.tar.gz</code></pre> <p>Key setup</p> <p>Generate the public key (<code>public.pem</code> here) from the provided private key (<code>private.pem</code> here):</p> <pre><code>$ openssl pkey -in private.pem -pubout -out public.pem</code></pre> <p>Examine the keys if you want.</p> <pre><code>$ openssl pkey -in private.pem -text -noout $ openssl pkey -in public.pem -text -noout -pubin</code></pre> <p>Example: Verify key material</p> <pre><code>$ openssl pkey -in private.pem -text -noout Private-Key: (2048 bit) priv: 1f:87:68:eb:57:e1:f4:f1:29:a6:c8:ca:03:c8:db: 49:1d:8e:2b:81:bd:72:92:64:0c:1c:d6:6d pub: 00:9d:fa:bc:47:00:cb:11:fa:51:45:c1:bd:b1:88: 2d:dd:a2:79:5b:c3:43:0a:af:bb:83:e2:d5:84:d1: 07:01:ab:f9:ae:76:2d:dd:f2:a5:75:f5:3e:94:4d: 3b:c6:f6:ce:17:c6:60:09:5b:49:3d:cb:a0:db:ec: 29:91:85:8b:c3:f5:6c:6a:3c:01:87:12:85:ae:fc: 9e:bf:67:81:1b:1d:b1:9d:12:bd:79:8c:54:08:48: 11:13:6d:ab:b0:16:ef:11:4a:27:a7:0a:80:b3:db: 72:c1:cc:1e:e8:4a:39:b7:00:ca:97:b7:3a:6e:e9: 25:22:2e:5c:57:ee:62:be:23:d0:5e:53:a3:9f:05: d4:7d:7f:b5:b6:cb:4b:27:90:14:79:72:a5:43:97: c6:6a:7d:f7:32:b3:67:58:90:fc:c3:65:34:57:89: 1b:43:28:68:43:24:12:5e:f1:43:76:3c:e9:bc:9c: 5d:7d:ae:d6:3a:31:32:ca:df:a4:07:88:a2:55:6e: a4:8c:da:13:c8:30:b7:2a:1c:23:0f:32:da:9e:7f: e1:f7:3d:2d:1c:58:f5:1d:f2:7d:fb:67:45:8d:dd: 84:eb:83:c4:b0:00:a6:c2:09:b0:48:48:f9:4e:a8: d7:ab:e1:c6:e8:bf:5c:fa:e3:f2:cd:c6:f1:e7:f2: 2c:90 P: 00:e5:4e:f4:32:f8:4a:ec:28:3c:dd:32:a8:05:e3: 5a:fa:a5:81:47:98:d9:a7:94:ba:34:b0:f9:7b:20: c5:fb:52:12:3e:82:d7:6e:6f:f5:50:be:5e:9f:df: 82:9b:4e:0c:9d:a2:9f:3f:0a:f3:72:c2:55:7c:46: 6e:fe:48:00:88:b6:4e:4f:9b:19:8c:98:3b:71:42: 56:d2:b4:1c:47:69:6e:fc:f0:e6:26:04:0e:e2:63: ed:06:0f:fb:a8:a9:94:73:e1:41:e0:6b:5a:b4:d9: 86:cd:7b:46:d3:39:ba:18:13:da:f2:3a:7b:dc:41: 21:83:e8:0d:25:13:31:90:5d:bd:82:41:9b:ea:6b: 8a:ba:8a:48:b1:1d:d2:3d:5e:c4:1b:29:5e:7f:b6: 56:1b:e6:91:65:ec:84:82:c2:f6:a1:b0:14:1b:0b: 08:d8:2b:2a:06:17:d7:2a:9b:c3:aa:fb:28:26:14: 3f:5d:0a:48:1a:48:45:c0:fd:ea:ec:90:6c:ec:93: c8:af:a3:31:4b:3a:d8:cd:20:ae:8f:14:58:26:49: 18:1f:7a:99:c9:da:c3:f0:76:b8:52:8d:eb:b2:e2: 98:6b:a5:47:15:c3:ff:c8:e7:6c:d3:db:c7:fb:4c: 36:3e:15:eb:45:e1:4a:5d:01:ed:3b:87:f7:69:c1: 31:59 Q: 00:ca:6d:df:fc:7b:96:2e:35:30:27:4f:1f:cf:57: 2f:e9:4c:40:97:53:a1:fa:d0:89:56:8d:2c:25 G: 43:26:04:66:b3:80:c3:3f:8d:f5:5a:29:79:58:7a: 0b:8c:72:b9:cb:23:61:5d:c1:45:c5:38:7f:33:4e: 93:63:75:8a:b0:44:61:8f:59:df:fd:2f:3f:1f:22: 73:66:ba:53:65:53:2a:57:5b:d9:40:34:be:4c:78: 22:4a:bf:94:5d:23:15:65:66:e1:1f:6b:93:12:00: f0:ac:f5:64:0d:6d:6c:a3:eb:26:83:6d:68:95:e0: 2c:bf:75:62:fa:5f:95:0f:b0:40:68:ce:66:3b:58: ed:c1:63:e3:d8:35:5c:cc:db:b8:12:e6:62:e4:63: b6:29:e0:86:75:79:bc:95:27:74:d1:fd:94:b9:7f: 6e:57:b4:e5:39:a2:15:41:94:3f:47:90:43:a5:da: dd:08:a4:92:c5:bf:ef:34:4e:2e:7e:82:5c:07:0e: dc:5d:6b:79:10:04:53:cc:b2:8e:bd:65:61:80:49: ad:c7:dd:5f:5a:9b:74:ae:bc:e0:49:f1:ad:4c:1e: 8f:4e:9d:39:e9:fe:57:4d:39:b7:ba:69:03:e3:7e: 4d:0d:9b:65:c3:55:77:ff:2c:86:27:21:c7:3e:60: a3:23:a5:e8:7e:0d:29:15:1c:5e:04:91:91:25:03: f3:97:77:6c:11:24:34:58:c9:ec:b7:ca:ce:74:cd: a7</code></pre> <p>This shows the keys indeed match (JSON <code>x,y</code>, above <code>priv,pub</code>):</p> <pre><code>$ grep --max-count=1 '"x"' remote_timings.json "x": "0x1F8768EB57E1F4F129A6C8CA03C8DB491D8E2B81BD7292640C1CD66D", $ grep --max-count=1 '"y"' remote_timings.json "y": "0x9DFABC4700CB11FA5145C1BDB1882DDDA2795BC3430AAFBB83E2D584D10701ABF9AE762DDDF2A575F53E944D3BC6F6CE17C660095B493DCBA0DBEC2991858BC3F56C6A3C01871285AEFC9EBF67811B1DB19D12BD798C54084811136DABB016EF114A27A70A80B3DB72C1CC1EE84A39B700CA97B73A6EE925222E5C57EE62BE23D05E53A39F05D47D7FB5B6CB4B2790147972A54397C66A7DF732B3675890FCC3653457891B4328684324125EF143763CE9BC9C5D7DAED63A3132CADFA40788A2556EA48CDA13C830B72A1C230F32DA9E7FE1F73D2D1C58F51DF27DFB67458DDD84EB83C4B000A6C209B04848F94EA8D7ABE1C6E8BF5CFAE3F2CDC6F1E7F22C90",</code></pre> <p>This shows the DSA parameters match (JSON <code>p,q,g</code>, above <code>P,Q,G</code>):</p> <pre><code>$ grep --max-count=1 '"p"' remote_timings.json "p": "0xE54EF432F84AEC283CDD32A805E35AFAA5814798D9A794BA34B0F97B20C5FB52123E82D76E6FF550BE5E9FDF829B4E0C9DA29F3F0AF372C2557C466EFE480088B64E4F9B198C983B714256D2B41C47696EFCF0E626040EE263ED060FFBA8A99473E141E06B5AB4D986CD7B46D339BA1813DAF23A7BDC412183E80D251331905DBD82419BEA6B8ABA8A48B11DD23D5EC41B295E7FB6561BE69165EC8482C2F6A1B0141B0B08D82B2A0617D72A9BC3AAFB2826143F5D0A481A4845C0FDEAEC906CEC93C8AFA3314B3AD8CD20AE8F14582649181F7A99C9DAC3F076B8528DEBB2E2986BA54715C3FFC8E76CD3DBC7FB4C363E15EB45E14A5D01ED3B87F769C13159", $ grep --max-count=1 '"q"' remote_timings.json "q": "0xCA6DDFFC7B962E3530274F1FCF572FE94C409753A1FAD089568D2C25", $ grep --max-count=1 '"g"' remote_timings.json "g": "0x43260466B380C33F8DF55A2979587A0B8C72B9CB23615DC145C5387F334E9363758AB044618F59DFFD2F3F1F227366BA5365532A575BD94034BE4C78224ABF945D23156566E11F6B931200F0ACF5640D6D6CA3EB26836D6895E02CBF7562FA5F950FB04068CE663B58EDC163E3D8355CCCDBB812E662E463B629E0867579BC952774D1FD94B97F6E57B4E539A21541943F479043A5DADD08A492C5BFEF344E2E7E825C070EDC5D6B79100453CCB28EBD65618049ADC7DD5F5A9B74AEBCE049F1AD4C1E8F4E9D39E9FE574D39B7BA6903E37E4D0D9B65C35577FF2C862721C73E60A323A5E87E0D29151C5E0491912503F397776C11243458C9ECB7CACE74CDA7",</code></pre> <p>Example: Extract a single entry</p> <p>Here we use the python script <code>pickone.py</code> to extract the entry at index 2 (starting from 0).</p> <pre><code>$ python3 pickone.py remote_timings.json 2 | jq . &gt; 2.json $ cat 2.json { "latency": "399901598", "y": "0x9DFABC4700CB11FA5145C1BDB1882DDDA2795BC3430AAFBB83E2D584D10701ABF9AE762DDDF2A575F53E944D3BC6F6CE17C660095B493DCBA0DBEC2991858BC3F56C6A3C01871285AEFC9EBF67811B1DB19D12BD798C54084811136DABB016EF114A27A70A80B3DB72C1CC1EE84A39B700CA97B73A6EE925222E5C57EE62BE23D05E53A39F05D47D7FB5B6CB4B2790147972A54397C66A7DF732B3675890FCC3653457891B4328684324125EF143763CE9BC9C5D7DAED63A3132CADFA40788A2556EA48CDA13C830B72A1C230F32DA9E7FE1F73D2D1C58F51DF27DFB67458DDD84EB83C4B000A6C209B04848F94EA8D7ABE1C6E8BF5CFAE3F2CDC6F1E7F22C90", "g": "0x43260466B380C33F8DF55A2979587A0B8C72B9CB23615DC145C5387F334E9363758AB044618F59DFFD2F3F1F227366BA5365532A575BD94034BE4C78224ABF945D23156566E11F6B931200F0ACF5640D6D6CA3EB26836D6895E02CBF7562FA5F950FB04068CE663B58EDC163E3D8355CCCDBB812E662E463B629E0867579BC952774D1FD94B97F6E57B4E539A21541943F479043A5DADD08A492C5BFEF344E2E7E825C070EDC5D6B79100453CCB28EBD65618049ADC7DD5F5A9B74AEBCE049F1AD4C1E8F4E9D39E9FE574D39B7BA6903E37E4D0D9B65C35577FF2C862721C73E60A323A5E87E0D29151C5E0491912503F397776C11243458C9ECB7CACE74CDA7", "h": "0xC7DEAC64C95157992CB0D77CF944CB107C756F3E30D1C49C0C48A6EA", "k": "0x742A7562E2A192996440AE2A4FDF5D37E1A532E1E6A50BCA3964BBDA", "q": "0xCA6DDFFC7B962E3530274F1FCF572FE94C409753A1FAD089568D2C25", "p": "0xE54EF432F84AEC283CDD32A805E35AFAA5814798D9A794BA34B0F97B20C5FB52123E82D76E6FF550BE5E9FDF829B4E0C9DA29F3F0AF372C2557C466EFE480088B64E4F9B198C983B714256D2B41C47696EFCF0E626040EE263ED060FFBA8A99473E141E06B5AB4D986CD7B46D339BA1813DAF23A7BDC412183E80D251331905DBD82419BEA6B8ABA8A48B11DD23D5EC41B295E7FB6561BE69165EC8482C2F6A1B0141B0B08D82B2A0617D72A9BC3AAFB2826143F5D0A481A4845C0FDEAEC906CEC93C8AFA3314B3AD8CD20AE8F14582649181F7A99C9DAC3F076B8528DEBB2E2986BA54715C3FFC8E76CD3DBC7FB4C363E15EB45E14A5D01ED3B87F769C13159", "s": "0x79FD73D901BB077D14334D8CC714804577515A1E0ADC9F995BB7534C", "r": "0x61F949D772E22EA9EFBB36442BC229767B28BE2A8061FA7339AFDDC8", "msg": "0x318198301A06092A864886F70D010903310D060B2A864886F70D0109100104301C06092A864886F70D010905310F170D3230303432343131333135375A302B060B2A864886F70D010910020C311C301A30183016041470AD64D33E65A855E6C332AA52736F71D58E7527302F06092A864886F70D0109043122042090C90BFC7A8C459EDB5AF58A8878EE826B6FD02A20E2BAAF2C73984FA380FDD2", "x": "0x1F8768EB57E1F4F129A6C8CA03C8DB491D8E2B81BD7292640C1CD66D", "id": "335451053151725", "k_len": "223" }</code></pre> <p>Example: Dump message to binary file</p> <p>Extract the <code>msg</code> field from the target JSON and dump it as binary.</p> <pre><code>$ sed -n 's/^ "msg": "0x\(.*\)",$/\1/p' 2.json | xxd -r -p &gt; 2.msg $ xxd -g1 2.msg 00000000: 31 81 98 30 1a 06 09 2a 86 48 86 f7 0d 01 09 03 1..0...*.H...... 00000010: 31 0d 06 0b 2a 86 48 86 f7 0d 01 09 10 01 04 30 1...*.H........0 00000020: 1c 06 09 2a 86 48 86 f7 0d 01 09 05 31 0f 17 0d ...*.H......1... 00000030: 32 30 30 34 32 34 31 31 33 31 35 37 5a 30 2b 06 200424113157Z0+. 00000040: 0b 2a 86 48 86 f7 0d 01 09 10 02 0c 31 1c 30 1a .*.H........1.0. 00000050: 30 18 30 16 04 14 70 ad 64 d3 3e 65 a8 55 e6 c3 0.0...p.d.&gt;e.U.. 00000060: 32 aa 52 73 6f 71 d5 8e 75 27 30 2f 06 09 2a 86 2.Rsoq..u'0/..*. 00000070: 48 86 f7 0d 01 09 04 31 22 04 20 90 c9 0b fc 7a H......1". ....z 00000080: 8c 45 9e db 5a f5 8a 88 78 ee 82 6b 6f d0 2a 20 .E..Z...x..ko.* 00000090: e2 ba af 2c 73 98 4f a3 80 fd d2 ...,s.O....</code></pre> <p>Note the <code>xxd</code> output matches the <code>msg</code> byte string from the target JSON.</p> <p>Example: Dump hash to binary file</p> <p>Extract the <code>h</code> field from the target JSON and dump it as binary.</p> <pre><code>$ sed -n 's/^ "h": "0x\(.*\)",$/\1/p' 2.json | xxd -r -p &gt; 2.hash $ xxd -g1 2.hash 00000000: c7 de ac 64 c9 51 57 99 2c b0 d7 7c f9 44 cb 10 ...d.QW.,..|.D.. 00000010: 7c 75 6f 3e 30 d1 c4 9c 0c 48 a6 ea |uo&gt;0....H..</code></pre> <p>Note the <code>xxd</code> output matches the <code>h</code> byte string from the target JSON.</p> <p>Example: Hash is consistent</p> <pre><code>$ sha256sum 2.msg c7deac64c95157992cb0d77cf944cb107c756f3e30d1c49c0c48a6ea809e6d58 2.msg</code></pre> <p>Note the first 28 bytes of <code>sha256sum</code> output match the <code>h</code> byte string from the target JSON. (DSA maps to GF(q) with truncation.)</p> <p>Example: Dump signature to DER</p> <p>The <code>hex2der.sh</code> script takes as an argument the target JSON filename, and outputs the DER-encoded DSA signature to stdout by extracting the <code>r</code> and <code>s</code> fields from the target JSON.</p> <pre><code>$ ./hex2der.sh 2.json &gt; 2.der $ openssl asn1parse -in 2.der -inform DER 0:d=0 hl=2 l= 60 cons: SEQUENCE 2:d=1 hl=2 l= 28 prim: INTEGER :61F949D772E22EA9EFBB36442BC229767B28BE2A8061FA7339AFDDC8 32:d=1 hl=2 l= 28 prim: INTEGER :79FD73D901BB077D14334D8CC714804577515A1E0ADC9F995BB7534C</code></pre> <p>Note the <code>asn1parse</code> output contains a sequence with two integers, matching the <code>r</code> and <code>s</code> fields from the target JSON.</p> <p>Example: Verify the signature (post-hash)</p> <p>We use <code>pkeyutl</code> here to verify the raw hash directly.</p> <pre><code>$ openssl pkeyutl -in 2.hash -inkey public.pem -pubin -verify -sigfile 2.der Signature Verified Successfully</code></pre> <p>Note it fails for other hashes (messages), a fundamental security property for digital signatures:</p> <pre><code>$ dd if=/dev/urandom of=bad.hash bs=1 count=28 28+0 records in 28+0 records out 28 bytes copied, 0.000647097 s, 43.3 kB/s $ openssl pkeyutl -in bad.hash -inkey public.pem -pubin -verify -sigfile 2.der Signature Verification Failure</code></pre> <p>Example: Verify the signature (pre-hash)</p> <p>We use <code>dgst</code> here to verify by recomputing the hash.</p> <pre><code>$ openssl dgst -sha256 -verify public.pem -signature 2.der 2.msg Verified OK</code></pre> <p>Example: Message analysis</p> <p>The <code>msg</code> JSON field is an <a href="https://tools.ietf.org/html/rfc3161">RFC 3161</a> Time Stamp Request. You can examine it:</p> <pre><code>$ openssl asn1parse -in 2.msg -inform DER 0:d=0 hl=3 l= 152 cons: SET 3:d=1 hl=2 l= 26 cons: SEQUENCE 5:d=2 hl=2 l= 9 prim: OBJECT :contentType 16:d=2 hl=2 l= 13 cons: SET 18:d=3 hl=2 l= 11 prim: OBJECT :id-smime-ct-TSTInfo 31:d=1 hl=2 l= 28 cons: SEQUENCE 33:d=2 hl=2 l= 9 prim: OBJECT :signingTime 44:d=2 hl=2 l= 15 cons: SET 46:d=3 hl=2 l= 13 prim: UTCTIME :200424113157Z 61:d=1 hl=2 l= 43 cons: SEQUENCE 63:d=2 hl=2 l= 11 prim: OBJECT :id-smime-aa-signingCertificate 76:d=2 hl=2 l= 28 cons: SET 78:d=3 hl=2 l= 26 cons: SEQUENCE 80:d=4 hl=2 l= 24 cons: SEQUENCE 82:d=5 hl=2 l= 22 cons: SEQUENCE 84:d=6 hl=2 l= 20 prim: OCTET STRING [HEX DUMP]:70AD64D33E65A855E6C332AA52736F71D58E7527 106:d=1 hl=2 l= 47 cons: SEQUENCE 108:d=2 hl=2 l= 9 prim: OBJECT :messageDigest 119:d=2 hl=2 l= 34 cons: SET 121:d=3 hl=2 l= 32 prim: OCTET STRING [HEX DUMP]:90C90BFC7A8C459EDB5AF58A8878EE826B6FD02A20E2BAAF2C73984FA380FDD2</code></pre> <p>Example: Statistics</p> <p>The <code>stats.py</code> script shows how to extract the desired fields from the JSON. It computes the median latency over each nonce bit length.</p> <pre><code>$ python3 stats.py remote_timings.json Len Median 205 121.2 206 121.2 207 120.6 208 138.3 209 122.9 210 123.0 211 123.0 212 123.0 213 125.0 214 125.0 215 125.0 216 125.0 217 127.1 218 127.1 219 127.1 220 127.1 221 129.1 222 129.1 223 129.1 224 129.1</code></pre> <p>You can verify these medians are consistent with Figure 1 in the paper.</p> <p>The <code>stats.py</code> script can be easily modified for more advanced analysis.</p> <p>Credits</p> <p>Some parts borrowed from <a href="https://doi.org/10.5281/zenodo.3736311">this artifact</a>.</p> <p>Authors</p> <ul> <li>Sohaib ul Hassan (Tampere University, Tampere, Finland)</li> <li>Iaroslav Gridin (Tampere University, Tampere, Finland)</li> <li>Ignacio M. Delgado-Lozano (Tampere University, Tampere, Finland)</li> <li>Cesar Pereida Garc&iacute;a (Tampere University, Tampere, Finland)</li> <li>Jes&uacute;s-Javier Chi-Dom&iacute;nguez (Tampere University, Tampere, Finland)</li> <li>Alejandro Cabrera Aldaya (Tampere University, Tampere, Finland)</li> <li>Billy Bob Brumley (Tampere University, Tampere, Finland)</li> </ul> <p>Funding</p> <p>This project has received funding from the European Research Council (ERC) under the European Union&rsquo;s Horizon 2020 research and innovation programme (grant agreement No 804476).</p> <p>License</p> <p>This project is distributed under <a href="LICENSE">MIT license</a>.</p>

openmit-licenseAug 2020View details →
zenodo40/100

Data set associated to the publication "An active source seismo-acoustic experiment using tethered balloons to validate instrument concepts and modelling tools for atmospheric seismology"

<p>Data set of the scientific publication entitled &quot;An active source seismo-acoustic experiment using tethered balloons to validate instrument concepts and modelling tools for atmospheric seismology&quot;:</p> <p>Seismological sensors</p> <p>Microphones</p> <p>Barometers</p> <p>Accelerometers</p> <p>Detailed test report.</p>

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

OggyBug: A Test Automation Tool in Chatbots

<p>Backup video for the presentation of the paper titled &quot;OggyBug: A Test Automation Tool in Chatbots&quot;, published in SAST - CBSoft 2020</p>

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

Dataset for the paper: TaskTracker tool: a Toolkit for Tracking of Code Snapshots and Activity Data During Solution of Programming Tasks (SIGCSE Technical Symposium 2021))

<pre>It is a dataset for the <em>TaskTracker-tool: a Toolkit for Tracking of Code Snapshots and Activity Data During Solution of Programming Tasks</em> paper from <a href="https://sigcse2021.sigcse.org/">SIGCSE Technical Symposium 2021</a>. The dataset consists of code snapshots, IDE actions, and demographic information gathered by <a href="https://github.com/JetBrains-Research/codetracker">this</a> tool. We had 148 participants, aged 11 to 40 (mean age is 19 years), take part in the data gathering process. </pre> <pre>During data gathering, solutions were accepted in one of four languages: Python, Java, Kotlin, or C++. However, some of the students chose not to submit tasks or solved some tasks incorrectly. At the same time, some students solved some tasks many times in multiple languages. All submitted solutions are included in the final dataset.</pre> <pre>To get more information see the <em>README</em> file.</pre>

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

Point, polygon, or marker? In search of the best geographic entity for mapping Cultural Ecosystem Services using the online PPGIS tool, "My Green Place."

<p>Excel files include the raw database and the processed data that led to the quadrat analyses. The &quot;Matrix_raw data&quot; file includes the raw data as downloaded from the server. This data was cleaned and organized for its posterior use. &quot;Quadrat analyzes &quot;file includes all the quadrat analyses resulting in each research question in the paper except question four. Question 4 can be seen in the file &quot;Water analysis_Blaarmeersen.&quot; All excel files come with a &quot;CODE&quot; tab that describes each of the codes used, their meaning, and ways that were calculated where necessary. Two zip files include all the GIS files. The first one includes the GIS files from which &quot;Matrix_raw data&quot; was built from. The second folder includes the resulting maps from the quadrat analyses. In order to visualize them as in the paper, configure the symbology tab at the GIS software in quantile and the categories number, as shown in the paper.</p> <p>The production of the files in the &quot;GIS_Processed data&quot; folder was done via a repetitive line of commands in ArcGIS pro. The same process was followed for each one of the quadrat analysis described in the paper. Refer to &quot;<a href="https://zenodo.org/api/files/72403e0b-78a9-4bbf-8dca-ed9b8702e3ae/Reproduction%20commands%20and%20parameters.pdf">Reproduction commands and parameters.pdf</a>&quot; for further information.</p>

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

Automated prediction of visual complexity of web pages: Tools and evaluations

<p>This dataset includes the screenshots of the web pages used for the evaluation of ViCRAM which is described in the following paper:</p> <p>Eleni Michailidou, Sukru Eraslan, Yeliz Yesilada, and Simon Harper. 2020. Automated Prediction of Visual Complexity of Web Pages: Tools and Evaluations. International Journal of Human-Computer Studies (SCI-E, SSCI), 145, 102523.</p>

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

Description of tools for the sustainability assessment of farms and farming systems

<p><strong>The &ldquo;summary&rdquo; table shows the papers and names of the tools and the link to the main publication as well as the use of the paper in each part of the analysis. We presented the variables for all the methods in a table called &ldquo;method&rdquo; with the result of the classification. In the table &ldquo;dimension&rdquo;, we presented the extraction of the dimension of sustainability and classification of methods. We did the same for the &ldquo;themes&rdquo; with a colour that we used for providing the descriptive statistics on the number of themes per dimension. We used three tables for each indicator that present the name of the indicator as extracted in the publication.</strong></p>

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

DEVILS: a tool for the visualization of large datasets with a high dynamic range

<p>This repository accompanying the article &ldquo;DEVILS: a tool for the visualization of large datasets with a high dynamic range&rdquo; contains the following:</p> <ul> <li>Extended Material of the article</li> <li>An example raw dataset corresponding to the images shown in Fig. 3</li> <li>A workflow description that demonstrates the use of the DEVILS workflow with BigStitcher.</li> <li>Two scripts (&ldquo;CLAHE_Parameters_test.ijm&rdquo; and a &ldquo;DEVILS_Parallel_tests.groovy&rdquo;) used for Figure S2, S3 and S4.</li> </ul>

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

Test Suites from Test-Generation Tools (Test-Comp 2021)

<p>Test Suites</p> <p>This file describes the contents of an archive of the 3rd Competition on Software Testing (Test-Comp 2021).<br> <a href="https://test-comp.sosy-lab.org/2021/">https://test-comp.sosy-lab.org/2021/</a></p> <p>The competition was run by Dirk Beyer, LMU Munich, Germany.<br> More information is available in the following article:<br> Dirk Beyer. <em>Status Report on Software Testing: Test-Comp 2021.</em> In Proceedings of the 24th International Conference on Fundamental Approaches to Software Engineering (FASE 2021, Luxembourg, March 27 - April 1), 2021. Springer.</p> <p>Copyright (C) Dirk Beyer<br> <a href="https://www.sosy-lab.org/people/beyer/">https://www.sosy-lab.org/people/beyer/</a></p> <p>SPDX-License-Identifier: CC-BY-4.0<br> <a href="https://spdx.org/licenses/CC-BY-4.0.html">https://spdx.org/licenses/CC-BY-4.0.html</a></p> <p>Contents</p> <ul> <li><code>LICENSE.txt</code>: specifies the license</li> <li><code>README.txt</code>: this file</li> <li><code>witnessFileByHash/</code>: This directory contains test suites (witnesses for coverage). Each witness in this directory is stored in a file whose name is the SHA2 256-bit hash of its contents followed by the filename extension .zip. The format of each test suite is described on the format web page: <a href="https://gitlab.com/sosy-lab/software/test-format">https://gitlab.com/sosy-lab/software/test-format</a> A test suite contains also metadata in order to relate it to the test problem for which it was produced.</li> <li><code>witnessInfoByHash/</code>: This directory contains for each test suite (witness) in directory witnessFileByHash/ a record in JSON format (also using the SHA2 256-bit hash of the witness as filename, with .json as filename extension) that contains the meta data.</li> <li><code>witnessListByProgramHashJSON/</code>: For convenient access to all test suites for a certain program, this directory represents a function that maps each program (via its SHA2256-bit hash) to a set of test suites (JSON records for test suites as described above) that the test tools have produced for that program. For each program for which test suites exist, the directory contains a JSON file (using the SHA2 256-bit hash of the program as filename, with .json as filename extension) that contains all JSON records for test suites for that program.</li> </ul> <p>A similar data structure was used by SV-COMP and is described in the following article:<br> Dirk Beyer. <em>A Data Set of Program Invariants and Error Paths.</em> In Proceedings of the 2019 IEEE/ACM 16th International Conference on Mining Software Repositories (MSR 2019, Montreal, Canada, May 26-27), pages 111-115, 2019. IEEE.<br> <a href="https://doi.org/10.1109/MSR.2019.00026">https://doi.org/10.1109/MSR.2019.00026</a></p> <p>Other Archives</p> <p>Overview over archives from Test-Comp 2021 that are available at Zenodo:</p> <ul> <li><a href="https://doi.org/10.5281/zenodo.4459466">https://doi.org/10.5281/zenodo.4459466</a> Witness store (containing the generated test suites)</li> <li><a href="https://doi.org/10.5281/zenodo.4459470">https://doi.org/10.5281/zenodo.4459470</a> Results (XML result files, log files, file mappings, HTML tables)</li> <li><a href="https://doi.org/10.5281/zenodo.4459132">https://doi.org/10.5281/zenodo.4459132</a> Test tasks, version testcomp21</li> <li><a href="https://doi.org/10.5281/zenodo.4317433">https://doi.org/10.5281/zenodo.4317433</a> BenchExec, version 3.6</li> </ul> <p>All benchmarks were executed for Test-Comp 2021 <a href="https://test-comp.sosy-lab.org/2021/">https://test-comp.sosy-lab.org/2021/</a><br> by Dirk Beyer, LMU Munich, based on the following components:</p> <ul> <li><a href="https://gitlab.com/sosy-lab/test-comp/archives-2021">https://gitlab.com/sosy-lab/test-comp/archives-2021</a> testcomp21-0-gdacd4bf</li> <li><a href="https://gitlab.com/sosy-lab/software/sv-benchmarks">https://gitlab.com/sosy-lab/software/sv-benchmarks</a> testcomp21-0-gefea738258</li> <li><a href="https://gitlab.com/sosy-lab/software/benchexec">https://gitlab.com/sosy-lab/software/benchexec</a> 3.6-0-gb278ebbb</li> <li><a href="https://gitlab.com/sosy-lab/benchmarking/competition-scripts">https://gitlab.com/sosy-lab/benchmarking/competition-scripts</a> testcomp21-0-g8339740</li> <li><a href="https://gitlab.com/sosy-lab/test-comp/bench-defs">https://gitlab.com/sosy-lab/test-comp/bench-defs</a> testcomp21-0-g9d532c9</li> </ul> <p>Contact</p> <p>Feel free to contact me in case of questions: <a href="https://www.sosy-lab.org/people/beyer/">https://www.sosy-lab.org/people/beyer/</a></p>

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

Verification Witnesses from Verification Tools (SV-COMP 2021)

<p>Verification Witnesses</p> <p>This file describes the contents of an archive of the 10th Competition on Software Verification (SV-COMP 2021).<br> <a href="https://sv-comp.sosy-lab.org/2021/">https://sv-comp.sosy-lab.org/2021/</a></p> <p>The competition was run by Dirk Beyer, LMU Munich, Germany.<br> More information is available in the following article:<br> Dirk Beyer. <em>Software Verification: 10th Comparative Evaluation (SV-COMP 2021).</em> In Proceedings of the 27th International Conference on Tools and Algorithms for the Construction and Analysis of Systems (TACAS 2021, Luxembourg, March 27 - April 1), 2021. Springer.</p> <p>Copyright (C) Dirk Beyer<br> <a href="https://www.sosy-lab.org/people/beyer/">https://www.sosy-lab.org/people/beyer/</a></p> <p>SPDX-License-Identifier: CC-BY-4.0<br> <a href="https://spdx.org/licenses/CC-BY-4.0.html">https://spdx.org/licenses/CC-BY-4.0.html</a></p> <p>Contents</p> <ul> <li><code>LICENSE.txt</code>: specifies the license</li> <li><code>README.txt</code>: this file</li> <li><code>witnessFileByHash/</code>: This directory contains verification witnesses. Each verification witness in this directory is stored in a file whose name is the SHA2 256-bit hash of its contents followed by the filename extension .graphml. The format of each verification witness is described on the format web page: <a href="https://github.com/sosy-lab/sv-witnesses/">https://github.com/sosy-lab/sv-witnesses/</a> A verification witness contains also metadata in order to relate it to the verification task for which it was produced.</li> <li><code>witnessInfoByHash/</code>: This directory contains for each verification witness in directory witnessFileByHash/ a record in JSON format (also using the SHA2 256-bit hash of the witness as filename, with .json as filename extension) that contains the meta data.</li> <li><code>witnessListByProgramHashJSON/</code>: For convenient access to all verification witnesses for a certain program, this directory represents a function that maps each program (via its SHA2256-bit hash) to a set of verification witnesses (JSON records for verification witnesses as described above) that the verification tools have produced for that program. For each program for which verification witnesses exist, the directory contains a JSON file (using the SHA2 256-bit hash of the program as filename, with .json as filename extension) that contains all JSON records for verification witnesses for that program.</li> </ul> <p>The data structure is described in the following article:<br> Dirk Beyer. <em>A Data Set of Program Invariants and Error Paths.</em> In Proceedings of the 2019 IEEE/ACM 16th International Conference on Mining Software Repositories (MSR 2019, Montreal, Canada, May 26-27), pages 111-115, 2019. IEEE.<br> <a href="https://doi.org/10.1109/MSR.2019.00026">https://doi.org/10.1109/MSR.2019.00026</a></p> <p>Other Archives</p> <p>Overview over archives from SV-COMP 2021 that are available at Zenodo:</p> <ul> <li><a href="https://doi.org/10.5281/zenodo.4459196">https://doi.org/10.5281/zenodo.4459196</a> Witness store (containing the generated verification witnesses)</li> <li><a href="https://doi.org/10.5281/zenodo.4458215">https://doi.org/10.5281/zenodo.4458215</a> Results (XML result files, log files, file mappings, HTML tables)</li> <li><a href="https://doi.org/10.5281/zenodo.4459126">https://doi.org/10.5281/zenodo.4459126</a> Verification tasks, version svcomp21</li> <li><a href="https://doi.org/10.5281/zenodo.4317433">https://doi.org/10.5281/zenodo.4317433</a> BenchExec, version 3.6</li> </ul> <p>All benchmarks were executed for SV-COMP 2021 <a href="https://sv-comp.sosy-lab.org/2021/">https://sv-comp.sosy-lab.org/2021/</a><br> by Dirk Beyer, LMU Munich, based on the following components:</p> <ul> <li><a href="https://gitlab.com/sosy-lab/sv-comp/archives-2021">https://gitlab.com/sosy-lab/sv-comp/archives-2021</a> svcomp21-0-g08c7a98</li> <li><a href="https://gitlab.com/sosy-lab/software/sv-benchmarks">https://gitlab.com/sosy-lab/software/sv-benchmarks</a> svcomp21-0-g4cc6b6d96a</li> <li><a href="https://gitlab.com/sosy-lab/software/benchexec">https://gitlab.com/sosy-lab/software/benchexec</a> 3.6-0-gb278ebbb</li> <li><a href="https://gitlab.com/sosy-lab/benchmarking/competition-scripts">https://gitlab.com/sosy-lab/benchmarking/competition-scripts</a> svcomp21-0-g8339740</li> <li><a href="https://gitlab.com/sosy-lab/sv-comp/bench-defs">https://gitlab.com/sosy-lab/sv-comp/bench-defs</a> svcomp21-0-ga57fe48</li> </ul> <p>Contact</p> <p>Feel free to contact me in case of questions: <a href="https://www.sosy-lab.org/people/beyer/">https://www.sosy-lab.org/people/beyer/</a></p>

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

Datasets used in the Lab Validation of the RADON Verification Tool

<p>This repository contains the datasets that have been used to perform the lab validation of the RADON verification tool. In order to replicate the experiments, please unzip the file &quot;validation-datasets.zip&quot; and&nbsp;run the following command:</p> <pre><code class="language-bash">./run_all.rb {path_to_VT} list.json</code></pre> <p>&nbsp;</p>

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

A Tool for Uncertainty Quantification in Reconstructing Sparse Water Quality Time Series Data to Assess Risk Metrics for Watershed Health and TMDL Analysis

<p>The uploaded file contains the input and output data which can be used to reproduce the results in the research article &#39;Uncertainty Quantification in Reconstruction of Sparse Water Quality Time Series: Implications for Watershed Health and Risk-Based TMDL Assessment&#39;. Please refer to the file &#39;<a href="https://zenodo.org/api/files/31b59cce-8eb2-4ee7-93aa-61474c6f6359/dst_2019_SJRW_TP_TDS.zip?versionId=2af2b54d-d5fb-4720-919d-de2e827595e2">dst_2019_SJRW_TP_TDS.zip&#39;</a> for updated files..</p>

opencc-by-4.0Oct 2019View details →
zenodo40/100

The Software Sustainability Institute's Collaborations Workshop 2015 (CW15) attendees computational tools dataset

<p>Contains the question, raw data, and cleaned data for producing the most used software word cloud for those who attended the Software Sustainability Institute&#39;s Collaborations Workshop 2015 (CW15) held at the Oxford e-Research Institute, Oxford, UK from 25-27 March 2015</p>

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

PDEStrIAn: A phosphodiesterase structure and ligand interaction annotated database as a tool for structure-based drug design

<p>A systematic analysis is presented of the 220 phosphodiesterase (PDE) catalytic domain crystal structures present in the Protein Data Bank (PDB) with a focus on PDE-ligand interactions. The consistent structural alignment of 57 PDE ligand binding site residues enables the systematic analysis of PDE-ligand Interaction FingerPrints (IFPs), the identification of subtype-specific PDE-ligand interaction features, and the classification of ligands according to their binding modes. We illustrate how systematic mining of this phosphodiesterase structure and ligand interaction annotated (PDEStrIAn) database provides new insights into how conserved and selective PDE interaction hot spots can accommodate the large diversity of chemical scaffolds in PDE ligands. A substructure analysis of the co-crystalized PDE ligands in combination with those in the ChEMBL database provides a toolbox for scaffold hopping and ligand design. These analyses lead to an improved understanding of the structural requirements of PDE binding that will be useful in future drug discovery studies.</p>

opencc-zeroFeb 2016View details →
zenodo40/100

ultraLM and miniLM: Locator tools for smart tracking of fluorescent cells in correlative light and electron microscopy

<p>Data for submission to Wellcome Open Research entitled "ultraLM and miniLM: Locator tools for smart tracking of fluorescent cells in correlative light and electron microscopy".</p> <p>Data_ultraLM.tif is an image stack from the fluorescence microscope mounted on the ultramicrotome.</p> <p>Data_miniLM.tif is an image stack from the fluorescence microscope mounted in the SBF-SEM.</p> <p>Data_miniLM_EM.tif is an image stack from the SBF-SEM while the miniLM was in-situ.</p>

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

Data and results for manuscript "Multi-frequency electrical impedance tomography as a non-invasive tool to characterize and monitor crop root systems "

<p>Root systems are essential in nutrient uptake and translocation, but are difficult to characterize non-invasively with existing methods. We propose electrical impedance tomography (EIT) as a new tool for the imaging and monitoring of crop root systems. In a laboratory experiment we demonstrate the capability of the method to capture physiological responses of root systems with high spatial and temporal resolution. We conclude that EIT is a promising functional imaging technique for crop roots.</p> <p>This package contains measured raw EIT data, electrical imaging results, spectral results from the Debye decomposition, and the Python scripts used to generate the plots in the manuscript.</p>

opencc-by-4.0Jan 2017View details →
zenodo40/100

Figure 9. from: Data sharing tools adopted by the European Biodiversity Observation Network Project - Research Ideas and Outcomes 2: e9390 (31 May 2016) https://doi.org/10.3897/rio.2.e9390

Figure 9. - Information flows between EU BON and LTER Europe, as envisaged on the 3rd EU BON Stakeholder Roundtable in Granada on 9-11 December 2015.

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

Figure 8. from: Data sharing tools adopted by the European Biodiversity Observation Network Project - Research Ideas and Outcomes 2: e9390 (31 May 2016) https://doi.org/10.3897/rio.2.e9390

Figure 8. - The patchiness of survey coverage in Europe illustrated by the distribution map of Plantago lanceolata taken from GBIF in 2016. This species is one of the commonest and most widespread in Europe, it should occur in almost all areas of this map, but in fact the data traces out the borders of countries and area who have published data on GBIF.

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

Figure 6. from: Data sharing tools adopted by the European Biodiversity Observation Network Project - Research Ideas and Outcomes 2: e9390 (31 May 2016) https://doi.org/10.3897/rio.2.e9390

Figure 6. - Individual Metacat instances can be connected to DataOne which replicates public files. Thus the data is still available if a single instance goes offline.https://search.dataone.org/#data/page/0

opencc-by-4.0Feb 2017View 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.