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.
3,956
datasets available to search
ShareScore release 0.9.0
Dataset results
3,956 results for “Virtualization”
Supporting Data for: Information Retrieval Interfaces in Virtual Reality - A Scoping Review Focused on Current Generation Technology
<p>This is the full data set of all reviewed research items obtained from Google Scholar, Web of Science and Scopus for the Scoping Literature Review <em><a href="https://doi.org/10.1371/journal.pone.0246398">Information Retrieval Interfaces in Virtual Reality - A Scoping Review Focused on Current Generation VR technology</a>.</em></p>
Virtually Real eyetracking data (beeswarm) for the short film "Lux" (2019) by Wendy Pillonel
<p>Two short feature films were recorded with a virtual background by using a green screen in a film studio and previously scanned 3D spaces in a virtual production environment and conventionally (in the corresponding real spaces) to compare the aesthetics and perception of these films. One scene of each film is shown in two variants (real vs. virtual background) to make a comparison.</p> <p>These quicktime movie represent the Eye-Tracking Data for Scenes 1,2 and 3 of "Lux" (2019) by Wendy Pillonel in beeswarm form for both the real and the virtual version of the film.</p> <p>Virtually Real is a research project by the Zurich University of the Arts, Institute for the Performing Arts and Film and the University of Bern, Institute of Psychology.</p>
Virtually Real short film "LUX" by Wendy Pillonel, versions with real and virtual backgrounds, 7min18sec, swiss-german, ProRes 1998 × 1080
<p>Two short feature films were recorded with a virtual background by using a green screen in a film studio and previously scanned 3D spaces in a virtual production environment and conventionally (in the corresponding real spaces) to compare the aesthetics and perception of these films. One scene of each film is shown in two variants (real vs. virtual background) to make a comparison.</p> <p>These 2 QuickTime files represents both the "real" and "virtual" version of the short Film "Lux" by Wendy Pillonel. The real version was shot on location using real backgrounds, the virtual version was shot in the studio in front of a green-screen using virtual backgrounds that were added in post production. </p> <p>Running time: 7min18sec. This is the highest quality version available. </p> <p>Virtually Real is a research project by the Zurich University of the Arts, Institute for the Performing Arts and Film and the University of Bern, Institute of Psychology.</p>
On demand customizable Virtual Environments with JupyterHub explainer comic strip
<p>This comic strip explains at a high level the convergence between JupyterHub and Binder to enable institutions to deploy a service for their members and users provisionning on demand customizable Jupyter-based Virtual Environments.</p> <p>Files:</p> <ul> <li>Community.png: main picture</li> <li>Community_text.svg: svg export: just the text</li> <li>Community_wo_text.svg: svg export: just the background image (e.g. for translations)</li> </ul>
ForensicVM Windows 11 Virtualization Dataset: Cloud and Local Application Data Retrieval with Virtualization and Password Bypass Challenge
<p>A Windows 11 Pro dataset designed in VirtualBox, complete with local and cloud apps, is to be virtually analyzed for crucial evidence. Bypassing the straightforward 'Bart' password is essential for access, yet original passwords should remain unchanged for others to attempt the same challenge. The task involves determining the password's nature, Bart's motives, identifying involved cloud applications, and extracting data both offline and online. The viability of dead box forensics for complete data retrieval is questioned, alongside what additional information network access could unveil. The challenge includes identifying two financial applications, extracting their data, and gathering cryptocurrency-related information, presented as an engaging forensicVM showcase by Nuno Mourinho, Mario Candeias, and Rogerio Bravo (Escola Superior de Tecnologia e Gestão de Beja, Instituto Politécnico de Beja).</p>
Auralization of virtual microphone array sensors considering coherence loss by atmospheric turbulence for two moving monopole sources
Open the record for dataset details and reuse information.
Subset Data 1: 2700 Thoracolumbar Osteo-Ligamentous Spine Virtual FE Meshes (Models 1 to 2700)
<p><em><strong>Subset Data 1: 2700 Thoracolumbar Osteo-Ligamentous Spine Virtual FE Meshes (Models 1 to 2700)</strong></em></p> <ul> <li>2700 FE input files representing thoracolumbar spine hexahedral models, including point coordinates. To reduce the size of shared virtual finite element (FE) models, only point coordinates are shared here. The mean FE input file "<a href="../api/files/bdc067d7-cb7d-40b7-9974-5ada43e1a0c5/Mean_Model%20%28Template%29.inp">Mean_Model (Template).inp</a>" is also shared, which includes point coordinates, mesh connectivity IDs, and element sets. To generate virtual FE input files, the corresponding shared point coordinates can be replaced into the mean FE input file (<a href="../api/files/bdc067d7-cb7d-40b7-9974-5ada43e1a0c5/Mean_Model%20%28Template%29.inp">Mean_Model (Template).inp</a>). Mesh connectivity IDs, and element sets are the same in all of FE input files. Mean FE input file includes vertebras and IVDs hexahedral meshes; pelvis, sacrum, and the femoral head triangulated meshes; and ligaments. Each point coordinate file is almost 38MB.</li> <li>An excel file: "<a href="../api/files/bdc067d7-cb7d-40b7-9974-5ada43e1a0c5/Descriptive_List%20%2816807_FE_virtual_models%29.xlsx">Descriptive_List (16807_FE_virtual_models).xlsx</a>" reporting measured spinopelvic parameters for virtual FE hexahedral models. The Excel file includes measured spinopelvic parameters (PI, PT, SS, LL, LL-PI, GT, RPV, RLL, LDI, RSA, TPA, and scoliosis cobb angle), GAP and IVD centric thickness for FE virtual cohort. Model ID in the excel file is correspondent to the model’s name.</li> <li>One video file: "<a href="../records/8107354/files/how_to_replace_point_coordinates.mp4?download=1">how_to_replace_point_coordinates.mp4</a>". It shows how you can replace point coordinates here to the mean FE input file "<a href="../api/files/bdc067d7-cb7d-40b7-9974-5ada43e1a0c5/Mean_Model%20%28Template%29.inp">Mean_Model (Template).inp</a>" in order to generate specific FE input file.</li> </ul> <p><em><strong>Notes:</strong></em></p> <p>1- Model number in "<a href="../api/files/bdc067d7-cb7d-40b7-9974-5ada43e1a0c5/Descriptive_List%20%2816807_FE_virtual_models%29.xlsx">Descriptive_List (16807_FE_virtual_models).xlsx</a>" is correspondent to the same model number in the 16807 stereolithography (stl) files (.stl extension) representing the virtual thoracolumbar spine triangulated meshes (DOI: <a href="https://doi.org/10.5281/zenodo.8108354">10.5281/zenodo.8108354</a>; <a href="../records/8108354/files/stl.part01.rar?download=1">stl.part01.rar</a> to <a href="../records/8108354/files/stl.part09.rar?download=1">stl.part09.rar</a>).</p> <p>2-These point coordinates are sampled by combining the first 5 shape modes of the morphed-mesh statistical shape model in which each shape mode is discretized into 7 standard deviations: -3, -2, -1, 0, 1, 2, 3.</p> <p>3- Generated FE inp files can be opened by Abaqus 2019 and later. Any other FE software which supports .inp extension also can open the files.</p> <p><em><strong>Developed by: </strong></em>Morteza Rasouligandomani (Ph.D. in biomedical engineering, Pompeu Fabra university, BCN Med-Tech group, DTIC department, Barcelona, Spain).</p> <p>Email contact: jerome.noailly@upf.edu</p>
Subset Data 2: 2700 Thoracolumbar Osteo-Ligamentous Spine Virtual FE Meshes (Models 2701 to 5400)
<p><em><strong>Subset Data 2: 2700 Thoracolumbar Osteo-Ligamentous Spine Virtual FE Meshes (Models 2701 to 5400)</strong></em></p> <ul> <li>2700 FE input files representing thoracolumbar spine hexahedral models, including point coordinates. To reduce the size of shared virtual finite element (FE) models, only point coordinates are shared here. The mean FE input file "<a href="../api/files/bdc067d7-cb7d-40b7-9974-5ada43e1a0c5/Mean_Model%20%28Template%29.inp">Mean_Model (Template).inp</a>" is also shared, which includes point coordinates, mesh connectivity IDs, and element sets. To generate virtual FE input files, the corresponding shared point coordinates can be replaced into the mean FE input file (<a href="../api/files/bdc067d7-cb7d-40b7-9974-5ada43e1a0c5/Mean_Model%20%28Template%29.inp">Mean_Model (Template).inp</a>). Mesh connectivity IDs, and element sets are the same in all of FE input files. Mean FE input file includes vertebras and IVDs hexahedral meshes; pelvis, sacrum, and the femoral head triangulated meshes; and ligaments. Each point coordinate file is almost 38MB.</li> <li>An excel file: "<a href="../api/files/bdc067d7-cb7d-40b7-9974-5ada43e1a0c5/Descriptive_List%20%2816807_FE_virtual_models%29.xlsx">Descriptive_List (16807_FE_virtual_models).xlsx</a>" reporting measured spinopelvic parameters for virtual FE hexahedral models. The Excel file includes measured spinopelvic parameters (PI, PT, SS, LL, LL-PI, GT, RPV, RLL, LDI, RSA, TPA, and scoliosis cobb angle), GAP and IVD centric thickness for FE virtual cohort. Model ID in the excel file is correspondent to the model’s name.</li> <li>One video file: "<a href="../records/8107354/files/how_to_replace_point_coordinates.mp4?download=1">how_to_replace_point_coordinates.mp4</a>". It shows how you can replace point coordinates here to the mean FE input file "<a href="../api/files/bdc067d7-cb7d-40b7-9974-5ada43e1a0c5/Mean_Model%20%28Template%29.inp">Mean_Model (Template).inp</a>" in order to generate specific FE input file.</li> </ul> <p><em><strong>Notes:</strong></em></p> <p>1- Model number in "<a href="../api/files/bdc067d7-cb7d-40b7-9974-5ada43e1a0c5/Descriptive_List%20%2816807_FE_virtual_models%29.xlsx">Descriptive_List (16807_FE_virtual_models).xlsx</a>" is correspondent to the same model number in the 16807 stereolithography (stl) files (.stl extension) representing the virtual thoracolumbar spine triangulated meshes (DOI: <a href="https://doi.org/10.5281/zenodo.8108354">10.5281/zenodo.8108354</a>; <a href="../records/8108354/files/stl.part01.rar?download=1">stl.part01.rar</a> to <a href="../records/8108354/files/stl.part09.rar?download=1">stl.part09.rar</a>).</p> <p>2-These point coordinates are sampled by combining the first 5 shape modes of the morphed-mesh statistical shape model in which each shape mode is discretized into 7 standard deviations: -3, -2, -1, 0, 1, 2, 3.</p> <p>3- Generated FE inp files can be opened by Abaqus 2019 and later. Any other FE software which supports .inp extension also can open the files.</p> <p><em><strong>Developed by: </strong></em>Morteza Rasouligandomani (Ph.D. in biomedical engineering, Pompeu Fabra university, BCN Med-Tech group, DTIC department, Barcelona, Spain).</p> <p>Email contact: jerome.noailly@upf.edu</p>
Subset Data 6: 2700 Thoracolumbar Osteo-Ligamentous Spine Virtual FE Meshes (Models 13501 to 16200)
<p><em><strong>Subset Data 6: 2700 Thoracolumbar Osteo-Ligamentous Spine Virtual FE Meshes (Models 13501 to 16200)</strong></em></p> <ul> <li>2700 FE input files representing thoracolumbar spine hexahedral models, including point coordinates. To reduce the size of shared virtual finite element (FE) models, only point coordinates are shared here. The mean FE input file "<a href="../api/files/bdc067d7-cb7d-40b7-9974-5ada43e1a0c5/Mean_Model%20%28Template%29.inp">Mean_Model (Template).inp</a>" is also shared, which includes point coordinates, mesh connectivity IDs, and element sets. To generate virtual FE input files, the corresponding shared point coordinates can be replaced into the mean FE input file (<a href="../api/files/bdc067d7-cb7d-40b7-9974-5ada43e1a0c5/Mean_Model%20%28Template%29.inp">Mean_Model (Template).inp</a>). Mesh connectivity IDs, and element sets are the same in all of FE input files. Mean FE input file includes vertebras and IVDs hexahedral meshes; pelvis, sacrum, and the femoral head triangulated meshes; and ligaments. Each point coordinate file is almost 38MB.</li> <li>An excel file: "<a href="../api/files/bdc067d7-cb7d-40b7-9974-5ada43e1a0c5/Descriptive_List%20%2816807_FE_virtual_models%29.xlsx">Descriptive_List (16807_FE_virtual_models).xlsx</a>" reporting measured spinopelvic parameters for virtual FE hexahedral models. The Excel file includes measured spinopelvic parameters (PI, PT, SS, LL, LL-PI, GT, RPV, RLL, LDI, RSA, TPA, and scoliosis cobb angle), GAP and IVD centric thickness for FE virtual cohort. Model ID in the excel file is correspondent to the model’s name.</li> <li>One video file: "<a href="../records/8107354/files/how_to_replace_point_coordinates.mp4?download=1">how_to_replace_point_coordinates.mp4</a>". It shows how you can replace point coordinates here to the mean FE input file "<a href="../api/files/bdc067d7-cb7d-40b7-9974-5ada43e1a0c5/Mean_Model%20%28Template%29.inp">Mean_Model (Template).inp</a>" in order to generate specific FE input file.</li> </ul> <p><em><strong>Notes:</strong></em></p> <p>1- Model number in "<a href="../api/files/bdc067d7-cb7d-40b7-9974-5ada43e1a0c5/Descriptive_List%20%2816807_FE_virtual_models%29.xlsx">Descriptive_List (16807_FE_virtual_models).xlsx</a>" is correspondent to the same model number in the 16807 stereolithography (stl) files (.stl extension) representing the virtual thoracolumbar spine triangulated meshes (DOI: <a href="https://doi.org/10.5281/zenodo.8108354">10.5281/zenodo.8108354</a>; <a href="../records/8108354/files/stl.part01.rar?download=1">stl.part01.rar</a> to <a href="../records/8108354/files/stl.part09.rar?download=1">stl.part09.rar</a>).</p> <p>2-These point coordinates are sampled by combining the first 5 shape modes of the morphed-mesh statistical shape model in which each shape mode is discretized into 7 standard deviations: -3, -2, -1, 0, 1, 2, 3.</p> <p>3- Generated FE inp files can be opened by Abaqus 2019 and later. Any other FE software which supports .inp extension also can open the files.</p> <p><em><strong>Developed by: </strong></em>Morteza Rasouligandomani (Ph.D. in biomedical engineering, Pompeu Fabra university, BCN Med-Tech group, DTIC department, Barcelona, Spain).</p> <p>Email contact: jerome.noailly@upf.edu</p>
Subset Data 4: 2700 Thoracolumbar Osteo-Ligamentous Spine Virtual FE Meshes (Models 8101 to 10800)
<p><em><strong>Subset Data 4: 2700 Thoracolumbar Osteo-Ligamentous Spine Virtual FE Meshes (Models 8101 to 10800)</strong></em></p> <ul> <li>2700 FE input files representing thoracolumbar spine hexahedral models, including point coordinates. To reduce the size of shared virtual finite element (FE) models, only point coordinates are shared here. The mean FE input file "<a href="../api/files/bdc067d7-cb7d-40b7-9974-5ada43e1a0c5/Mean_Model%20%28Template%29.inp">Mean_Model (Template).inp</a>" is also shared, which includes point coordinates, mesh connectivity IDs, and element sets. To generate virtual FE input files, the corresponding shared point coordinates can be replaced into the mean FE input file (<a href="../api/files/bdc067d7-cb7d-40b7-9974-5ada43e1a0c5/Mean_Model%20%28Template%29.inp">Mean_Model (Template).inp</a>). Mesh connectivity IDs, and element sets are the same in all of FE input files. Mean FE input file includes vertebras and IVDs hexahedral meshes; pelvis, sacrum, and the femoral head triangulated meshes; and ligaments. Each point coordinate file is almost 38MB.</li> <li>An excel file: "<a href="../api/files/bdc067d7-cb7d-40b7-9974-5ada43e1a0c5/Descriptive_List%20%2816807_FE_virtual_models%29.xlsx">Descriptive_List (16807_FE_virtual_models).xlsx</a>" reporting measured spinopelvic parameters for virtual FE hexahedral models. The Excel file includes measured spinopelvic parameters (PI, PT, SS, LL, LL-PI, GT, RPV, RLL, LDI, RSA, TPA, and scoliosis cobb angle), GAP and IVD centric thickness for FE virtual cohort. Model ID in the excel file is correspondent to the model’s name.</li> <li>One video file: "<a href="../records/8107354/files/how_to_replace_point_coordinates.mp4?download=1">how_to_replace_point_coordinates.mp4</a>". It shows how you can replace point coordinates here to the mean FE input file "<a href="../api/files/bdc067d7-cb7d-40b7-9974-5ada43e1a0c5/Mean_Model%20%28Template%29.inp">Mean_Model (Template).inp</a>" in order to generate specific FE input file.</li> </ul> <p><em><strong>Notes:</strong></em></p> <p>1- Model number in "<a href="../api/files/bdc067d7-cb7d-40b7-9974-5ada43e1a0c5/Descriptive_List%20%2816807_FE_virtual_models%29.xlsx">Descriptive_List (16807_FE_virtual_models).xlsx</a>" is correspondent to the same model number in the 16807 stereolithography (stl) files (.stl extension) representing the virtual thoracolumbar spine triangulated meshes (DOI: <a href="https://doi.org/10.5281/zenodo.8108354">10.5281/zenodo.8108354</a>; <a href="../records/8108354/files/stl.part01.rar?download=1">stl.part01.rar</a> to <a href="../records/8108354/files/stl.part09.rar?download=1">stl.part09.rar</a>).</p> <p>2-These point coordinates are sampled by combining the first 5 shape modes of the morphed-mesh statistical shape model in which each shape mode is discretized into 7 standard deviations: -3, -2, -1, 0, 1, 2, 3.</p> <p>3- Generated FE inp files can be opened by Abaqus 2019 and later. Any other FE software which supports .inp extension also can open the files.</p> <p><em><strong>Developed by: </strong></em>Morteza Rasouligandomani (Ph.D. in biomedical engineering, Pompeu Fabra university, BCN Med-Tech group, DTIC department, Barcelona, Spain).</p> <p>Email contact: jerome.noailly@upf.edu</p>
Subset Data 5: 2700 Thoracolumbar Osteo-Ligamentous Spine Virtual FE Meshes (Models 10801 to 13500)
<p><em><strong>Subset Data 5: 2700 Thoracolumbar Osteo-Ligamentous Spine Virtual FE Meshes (Models 10801 to 13500)</strong></em></p> <ul> <li>2700 FE input files representing thoracolumbar spine hexahedral models, including point coordinates. To reduce the size of shared virtual finite element (FE) models, only point coordinates are shared here. The mean FE input file "<a href="../api/files/bdc067d7-cb7d-40b7-9974-5ada43e1a0c5/Mean_Model%20%28Template%29.inp">Mean_Model (Template).inp</a>" is also shared, which includes point coordinates, mesh connectivity IDs, and element sets. To generate virtual FE input files, the corresponding shared point coordinates can be replaced into the mean FE input file (<a href="../api/files/bdc067d7-cb7d-40b7-9974-5ada43e1a0c5/Mean_Model%20%28Template%29.inp">Mean_Model (Template).inp</a>). Mesh connectivity IDs, and element sets are the same in all of FE input files. Mean FE input file includes vertebras and IVDs hexahedral meshes; pelvis, sacrum, and the femoral head triangulated meshes; and ligaments. Each point coordinate file is almost 38MB.</li> <li>An excel file: "<a href="../api/files/bdc067d7-cb7d-40b7-9974-5ada43e1a0c5/Descriptive_List%20%2816807_FE_virtual_models%29.xlsx">Descriptive_List (16807_FE_virtual_models).xlsx</a>" reporting measured spinopelvic parameters for virtual FE hexahedral models. The Excel file includes measured spinopelvic parameters (PI, PT, SS, LL, LL-PI, GT, RPV, RLL, LDI, RSA, TPA, and scoliosis cobb angle), GAP and IVD centric thickness for FE virtual cohort. Model ID in the excel file is correspondent to the model’s name.</li> <li>One video file: "<a href="../records/8107354/files/how_to_replace_point_coordinates.mp4?download=1">how_to_replace_point_coordinates.mp4</a>". It shows how you can replace point coordinates here to the mean FE input file "<a href="../api/files/bdc067d7-cb7d-40b7-9974-5ada43e1a0c5/Mean_Model%20%28Template%29.inp">Mean_Model (Template).inp</a>" in order to generate specific FE input file.</li> </ul> <p><em><strong>Notes:</strong></em></p> <p>1- Model number in "<a href="../api/files/bdc067d7-cb7d-40b7-9974-5ada43e1a0c5/Descriptive_List%20%2816807_FE_virtual_models%29.xlsx">Descriptive_List (16807_FE_virtual_models).xlsx</a>" is correspondent to the same model number in the 16807 stereolithography (stl) files (.stl extension) representing the virtual thoracolumbar spine triangulated meshes (DOI: <a href="https://doi.org/10.5281/zenodo.8108354">10.5281/zenodo.8108354</a>; <a href="../records/8108354/files/stl.part01.rar?download=1">stl.part01.rar</a> to <a href="../records/8108354/files/stl.part09.rar?download=1">stl.part09.rar</a>).</p> <p>2-These point coordinates are sampled by combining the first 5 shape modes of the morphed-mesh statistical shape model in which each shape mode is discretized into 7 standard deviations: -3, -2, -1, 0, 1, 2, 3.</p> <p>3- Generated FE inp files can be opened by Abaqus 2019 and later. Any other FE software which supports .inp extension also can open the files.</p> <p><em><strong>Developed by: </strong></em>Morteza Rasouligandomani (Ph.D. in biomedical engineering, Pompeu Fabra university, BCN Med-Tech group, DTIC department, Barcelona, Spain).</p> <p>Email contact: jerome.noailly@upf.edu</p>
Subset Data 3: 2700 Thoracolumbar Osteo-Ligamentous Spine Virtual FE Meshes (Models 5401 to 8100)
<p><em><strong>Subset Data 3: 2700 Thoracolumbar Osteo-Ligamentous Spine Virtual FE Meshes (Models 5401 to 8100)</strong></em></p> <ul> <li>2700 FE input files representing thoracolumbar spine hexahedral models, including point coordinates. To reduce the size of shared virtual finite element (FE) models, only point coordinates are shared here. The mean FE input file "<a href="../api/files/bdc067d7-cb7d-40b7-9974-5ada43e1a0c5/Mean_Model%20%28Template%29.inp">Mean_Model (Template).inp</a>" is also shared, which includes point coordinates, mesh connectivity IDs, and element sets. To generate virtual FE input files, the corresponding shared point coordinates can be replaced into the mean FE input file (<a href="../api/files/bdc067d7-cb7d-40b7-9974-5ada43e1a0c5/Mean_Model%20%28Template%29.inp">Mean_Model (Template).inp</a>). Mesh connectivity IDs, and element sets are the same in all of FE input files. Mean FE input file includes vertebras and IVDs hexahedral meshes; pelvis, sacrum, and the femoral head triangulated meshes; and ligaments. Each point coordinate file is almost 38MB.</li> <li>An excel file: "<a href="../api/files/bdc067d7-cb7d-40b7-9974-5ada43e1a0c5/Descriptive_List%20%2816807_FE_virtual_models%29.xlsx">Descriptive_List (16807_FE_virtual_models).xlsx</a>" reporting measured spinopelvic parameters for virtual FE hexahedral models. The Excel file includes measured spinopelvic parameters (PI, PT, SS, LL, LL-PI, GT, RPV, RLL, LDI, RSA, TPA, and scoliosis cobb angle), GAP and IVD centric thickness for FE virtual cohort. Model ID in the excel file is correspondent to the model’s name.</li> <li>One video file: "<a href="../records/8107354/files/how_to_replace_point_coordinates.mp4?download=1">how_to_replace_point_coordinates.mp4</a>". It shows how you can replace point coordinates here to the mean FE input file "<a href="../api/files/bdc067d7-cb7d-40b7-9974-5ada43e1a0c5/Mean_Model%20%28Template%29.inp">Mean_Model (Template).inp</a>" in order to generate specific FE input file.</li> </ul> <p><em><strong>Notes:</strong></em></p> <p>1- Model number in "<a href="../api/files/bdc067d7-cb7d-40b7-9974-5ada43e1a0c5/Descriptive_List%20%2816807_FE_virtual_models%29.xlsx">Descriptive_List (16807_FE_virtual_models).xlsx</a>" is correspondent to the same model number in the 16807 stereolithography (stl) files (.stl extension) representing the virtual thoracolumbar spine triangulated meshes (DOI: <a href="https://doi.org/10.5281/zenodo.8108354">10.5281/zenodo.8108354</a>; <a href="../records/8108354/files/stl.part01.rar?download=1">stl.part01.rar</a> to <a href="../records/8108354/files/stl.part09.rar?download=1">stl.part09.rar</a>).</p> <p>2-These point coordinates are sampled by combining the first 5 shape modes of the morphed-mesh statistical shape model in which each shape mode is discretized into 7 standard deviations: -3, -2, -1, 0, 1, 2, 3.</p> <p>3- Generated FE inp files can be opened by Abaqus 2019 and later. Any other FE software which supports .inp extension also can open the files.</p> <p><em><strong>Developed by: </strong></em>Morteza Rasouligandomani (Ph.D. in biomedical engineering, Pompeu Fabra university, BCN Med-Tech group, DTIC department, Barcelona, Spain).</p> <p>Email contact: jerome.noailly@upf.edu</p>
Subset Data 7: 607 Thoracolumbar Osteo-Ligamentous Spine Virtual FE Meshes (Models 16201 to 16807)
<p><em><strong>Subset Data 7: 607 Thoracolumbar Osteo-Ligamentous Spine Virtual FE Meshes (Models 16201 to 16807)</strong></em></p> <ul> <li>607 FE input files representing thoracolumbar spine hexahedral models, including point coordinates. To reduce the size of shared virtual finite element (FE) models, only point coordinates are shared here. The mean FE input file "<a href="../api/files/bdc067d7-cb7d-40b7-9974-5ada43e1a0c5/Mean_Model%20%28Template%29.inp">Mean_Model (Template).inp</a>" is also shared, which includes point coordinates, mesh connectivity IDs, and element sets. To generate virtual FE input files, the corresponding shared point coordinates can be replaced into the mean FE input file (<a href="../api/files/bdc067d7-cb7d-40b7-9974-5ada43e1a0c5/Mean_Model%20%28Template%29.inp">Mean_Model (Template).inp</a>). Mesh connectivity IDs, and element sets are the same in all of FE input files. Mean FE input file includes vertebras and IVDs hexahedral meshes; pelvis, sacrum, and the femoral head triangulated meshes; and ligaments. Each point coordinate file is almost 38MB.</li> <li>An excel file: "<a href="../api/files/bdc067d7-cb7d-40b7-9974-5ada43e1a0c5/Descriptive_List%20%2816807_FE_virtual_models%29.xlsx">Descriptive_List (16807_FE_virtual_models).xlsx</a>" reporting measured spinopelvic parameters for virtual FE hexahedral models. The Excel file includes measured spinopelvic parameters (PI, PT, SS, LL, LL-PI, GT, RPV, RLL, LDI, RSA, TPA, and scoliosis cobb angle), GAP and IVD centric thickness for FE virtual cohort. Model ID in the excel file is correspondent to the model’s name.</li> <li>One video file: "<a href="../records/8107354/files/how_to_replace_point_coordinates.mp4?download=1">how_to_replace_point_coordinates.mp4</a>". It shows how you can replace point coordinates here to the mean FE input file "<a href="../api/files/bdc067d7-cb7d-40b7-9974-5ada43e1a0c5/Mean_Model%20%28Template%29.inp">Mean_Model (Template).inp</a>" in order to generate specific FE input file.</li> </ul> <p><em><strong>Notes:</strong></em></p> <p>1- Model number in "<a href="../api/files/bdc067d7-cb7d-40b7-9974-5ada43e1a0c5/Descriptive_List%20%2816807_FE_virtual_models%29.xlsx">Descriptive_List (16807_FE_virtual_models).xlsx</a>" is correspondent to the same model number in the 16807 stereolithography (stl) files (.stl extension) representing the virtual thoracolumbar spine triangulated meshes (DOI: <a href="https://doi.org/10.5281/zenodo.8108354">10.5281/zenodo.8108354</a>; <a href="../records/8108354/files/stl.part01.rar?download=1">stl.part01.rar</a> to <a href="../records/8108354/files/stl.part09.rar?download=1">stl.part09.rar</a>).</p> <p>2-These point coordinates are sampled by combining the first 5 shape modes of the morphed-mesh statistical shape model in which each shape mode is discretized into 7 standard deviations: -3, -2, -1, 0, 1, 2, 3.</p> <p>3- Generated FE inp files can be opened by Abaqus 2019 and later. Any other FE software which supports .inp extension also can open the files.</p> <p><em><strong>Developed by: </strong></em>Morteza Rasouligandomani (Ph.D. in biomedical engineering, Pompeu Fabra university, BCN Med-Tech group, DTIC department, Barcelona, Spain).</p> <p>Email contact: jerome.noailly@upf.edu</p>
Example data from a virtual mass comparison using the Digital Calibration Certificate (DCC) scheme
<p><strong>The example data is an outcome of a project on a fully automated evaluation of a virtual mass comparison using the Digital Calibration </strong><strong>Certificate (DCC) schema.</strong></p> <p>We present the proof of concept for the first fully automated evaluation of a virtual mass comparison. The focus of this comparison is to demonstrate a possibility of digital transformation in metrology using an automated evaluation chain of different tools as well as machine-interpretable files for data transfer and final report. This publication provides the example data being used as input and output of the automated comparison evaluation tool.</p>
Dataset underlying the manuscript: MAViS: Modular Autonomous Virtualization System for Two-Dimensional Semiconductor Quantum Dot Arrays
<p>Datasets underlying the manuscript. Information on how to run the scripts is detailed in the README file.</p>
CREATTIVE3D multimodal dataset of user behavior in virtual reality
<p>In the context of the <a href="https://project.inria.fr/creattive3d/">ANR CREATTIVE3D</a> project, we join the expertise of computer science, neuroscience, and clinical practitioners, with the aim to analyze the impact that a simulated low-vision condition has on user navigation behavior in complex road crossing scenes: a common daily situation where the difficulty to access and process visual information (e.g., traffic lights, approaching cars) in a timely fashion can lead to serious consequences on a person's safety and well-being. As a secondary objective, we also aim to investigate the potential role virtual reality could play in rehabilitation and training protocols for low-vision patients.</p> <p>This dataset contains the data as part of the study described in <a href="https://hal.science/hal-04102737">An Integrated Framework for Understanding Multimodal Embodied Experiences in Interactive Virtual Reality</a>.</p> <p>The dataset is metadata for the pre-print <a href="https://inria.hal.science/hal-04429351">Exploring, walking, and interacting in virtual reality with simulated low vision: a living contextual dataset</a></p> <p>To use this dataset, please cite:</p> <blockquote> <pre>@unpublished{wu:hal-04429351, TITLE = {{Exploring, walking, and interacting in virtual reality with simulated low vision: a living contextual dataset}}, AUTHOR = {Wu, Hui-Yin and Robert, Florent Alain Sauveur and Gallo, Franz Franco and <br> Pirkovets, Kateryna and Quere, Cl{\'e}ment and Delachambre, Johanna and <br> Ramano{\"e}l, Stephen and Gros, Auriane and Winckler, Marco and Sassatelli, Lucile and <br> Hayotte, Meggy and Menin, Aline and Kornprobst, Pierre}, URL = {https://inria.hal.science/hal-04429351}, NOTE = {working paper or preprint}, YEAR = {2023}, MONTH = Dec, KEYWORDS = {Virtual reality ; Dataset ; Context ; Low vision ; 3D environments ; User study}, PDF = {https://inria.hal.science/hal-04429351/file/2023_CREATTIVE3D_dataset_arxiv_.pdf}, HAL_ID = {hal-04429351}, HAL_VERSION = {v1}, }<br><br>@inproceedings{robert2023integrated, title={An integrated framework for understanding multimodal embodied experiences in interactive virtual reality}, author={Robert, Florent and Wu, Hui-Yin and Sassatelli, Lucile and Ramanoel, Stephen and <br> Gros, Auriane and Winckler, Marco}, booktitle={Proceedings of the 2023 ACM International Conference on Interactive Media Experiences}, pages={14--26}, year={2023} }</pre> </blockquote> <h3> </h3> <h3>Versions</h3> <p>2024-12-18: Updated readme with description of labels, columns, and suggestions on how to start exploring the dataset. We also provide the questionnaire responses and observation notes in English (questionnaire_translation_EN.csv).</p>
Subjective Quality Assessment of Foveated Omnidirectional Images in Virtual Reality (FOIQA)
<p>This study presents a novel dataset called 'Foveated Omnidirectional Image Quality Assessment' (FOIQA) for the subjective quality evaluation of foveated 2D omnidirectional images. This dataset addresses the limitations of existing datasets by leveraging a high-resolution head-mounted display and a gaze-contingent evaluation approach. We provide individual opinion scores, mean opinion scores, and gaze data associated with both the test and reference images. </p>
Virtual RHI lidar scans retrieved in high-fidelity wake vortex simulations of landing aircraft under turbulent crosswind conditions - LES Lidar Simulator (LLS)
<p>This dataset contains two types of virtual measurements of multiple pulsed lidar integrated into high-fidelity hybrid RANS-LES wake vortex simulations of a landing Airbus A340 aircraft. Simulations have been performed for four different atmospheric conditions, varying in crosswind and therefore turbulence in the atmosphere.</p> <p>The two lidar simulator types are:</p> <ul> <li>LLS: LES Lidar Simulator (no noise, Signal to Noise Ratio >> 1). The analysis is based on the Range Gate Weighting function (RWF) [based on formulations in for example [1]]. Given the assumption of no instrument noise, no spectral analysis in the frequency domain is required.</li> <li>LLSn: LES Lidar Simulator with noise (realisitic Signal to Noise Ratio). Based on formulations in [2], where non-linear low-pass spatial filters accurately model real field measurements. Both background noise and aerosol noise contained in real lidar measurements are modeled. </li> </ul> <p>Provided are the raw lidar scans in RHI format, with the position and strength of the wake vortices within each lidar scan given by a pressure-vorticity tracking algorithm from the wake vortex simulation (simulation truth, ST). Misidentifications have been removed from the provided dataset. In addition to the labels for each wake vortex lidar scan, also wind background scans are provided for the crosswind simulation cases. These background scans give a better understanding of the prevailing atmospheric condition within which the aircraft lands. </p> <p>Furthermore the evaluation of the LLS scans using the Method of Radial Velocities (RV method) [3], a state-of-the-art wake vortex characterization method for lidar scans is provided for a subset of the LLS dataset. For analysing the impact of the RWF for LLS scans, selected lidar scans are also given in a 'naive' fashion (lidar scans assuming point measurements are possible).</p> <p><strong>--------------------------------------------------------------------------------------------------------------------------------------------</strong></p> <h3><strong>Overview</strong></h3> <p><strong>In total each dataset (LLS and LLSn) contains 8 Aircraft landing simulation with associated </strong><strong>virtual lidar RHI scans:</strong></p> <ul> <li>2x no wind</li> <li>6x crosswind (specified at height b_0)</li> <li>0.5w_0 from port direction</li> <li>0.5w_0 from starboard direction</li> <li>1.0w_0 from port direction</li> <li>1.0w_0 from starboard direction</li> <li>2.0w_0 from port direction</li> <li>2.0w_0 from starboard direction</li> </ul> <p><strong>--------------------------------------------------------------------------------------------------------------------------------------------</strong></p> <h3><strong>The dataset has 13 folders:</strong></h3> <div> <p><strong>POS1_POS2_POS8_scans = Individual scans of various simulations as well as background wind scans (no wake vortices). </strong></p> <p>POS1_POS2: 0_0, 0_5, 1_0, 2_0 corresponds to the wind, same as POS1_POS2 below</p> <p>POS8: LLS or LLSn, corresponding to the type of lidar simulator (without or with instrument noise, respectively)</p> </div> <div> </div> <div>Scan naming convention: POS1_POS2_POS3_POS4_POS5_POS6_POS7.csv</div> <div> </div> <div>Example: 0_5_D_248_8_161.2201878198302_168.4201878198237.csv</div> <div> </div> <div> <ul> <li>POS1_POS2: Together they form a factor which is multiplied with the initial descend speed of the wake vortex pair, w_0. The definition for w_0 can be found in [4]. It is common for the crosswind speed to be set according to the multiples of w_0. Due to the landing of the A340 aircraft, and the logarithmic nature of the wind simulation, we set the crosswind at the b_0 altitude of the simulation. For a definition of b_0, also see [4]. For the above example, 0.5w_0 is the crosswind speed. Note that every 26 lidar positions (POS4), the direction of the crosswind changes, if there is a crosswind.</li> </ul> </div> <div> - Crosswind approaches from port side: POS4: 0-25, 52-77, 104-129, 156-181, 208-233, 260-285</div> <div> - Crosswind approaches from starboard side: POS4: 26-51, 78-103, 130-155, 182-207, 234-259, 286-311</div> <div> <ul> <li>POS3: Label indicating which part of the numerical simulation this scan belongs to (a full landing simulation consists of A-D). A: Hybrid RANS-LES, B,C,D: temporal LES (in order). For the above example, D indicates that the lidar scan was recorded during the last part of the simulation. W: Prior to the wake vortex simulations with crosswind, a background wind scan for each lidar position is recorded.</li> </ul> </div> <div> <ul> <li>POS4: Specifies the number of the lidar, implications are the longitudinal position along the glide path of the aircraft. In the packs of lidar positions described in the description of POS1_POS2, the last lidar position is the closest to the touchdown point of the aircraft, smaller lidar positions within this pack are further away (in order) - also see the lid_plane_info directory. Note that the lidar position also adjusts the spectrum of the elevation angles used (and thus the size of the lidar scan). For that see the associated virtual lidar scan raw data. In the above example we have lidar position 248, thus crosswind approaching from starboard and rather mid-way of the longitudinal glide path direction.</li> </ul> </div> <div> <ul> <li>POS5: Specifies the number of the scan for this lidar position (POS4) and simulation (POS1__POS2). In the above example this is scan number 8.</li> </ul> </div> <div> <ul> <li>POS6_POS7: Specifies the simulation time within which the scan was measured during the aircraft landing simulation (POS1__POS2). In the above example this is 161.2201878198302 s to 168.4201878198237 s.</li> </ul> </div> <div>The scans purely with wind, an no wake vortices are stored in an additional directory within conv_scans. The case '0_0' (no wind) does not require wind scans. </div> <div> </div> <div>Within the scan files, we have a four (LLS) or five (LLSn) columns:</div> <div> <ul> <li>t: Simulation time</li> <li>ELE: Elevation angle [deg] of the lidar beam</li> <li>R: Range from lidar [m]</li> <li>v_r: LOS velocity (radial velocity) along lidar beam</li> <li>snr: Signal to Noise Ratio </li> </ul> <p> </p> <p><strong>wind_POS8_scans = Simulated lidar scans of the background wind for LLS and LLSn.</strong></p> <p>POS8: LLS or LLSn, corresponding to the type of lidar simulator (without or with instrument noise, respectively)</p> <p>Scans simulated here are in the same format as <em>POS1_POS2_POS8_scans</em>. Wind scans for point measurement scans are found in <em>naive_scan_subset </em>- the scans with POS4 = 0 should be used if more are available.</p> <p> </p> <p><strong>naive_scan_subset = Simulated lidar scans simulating velocity point measurements.</strong></p> </div> <div> <p>The format is the same as for <em>POS1_POS2_POS8_scans</em>, with the difference of being sorted first by wind subdirectories and then lidar number (LID).</p> <p> </p> <p><strong>labels = Labels of wake vortices for the above wake vortex scans. </strong></p> </div> <div>We have 4 main files, where each file represents the targets for one wind strength 0.0w_0, 0.5w_0, 1.0w_0, 2.0w_0.</div> <div>Within the labels files, we have a multitude of columns with different data:</div> <div> <ul> <li>#Time: Simulation (not scan) time.</li> <li>y_uw : lateral position in simulation domain of upwind (port) vortex.</li> <li>z_uw : height position in simulation domain of upwind (port) vortex.</li> <li>y_dw : lateral position in simulation domain of downwind (starboard) vortex.</li> <li>z_dw : height position in simulation domain of downwind (starboard) vortex.</li> <li>G_515_uw: Gamma 515 Circulation strength (see additional notes) of upwind (port) vortex [m^2/s].</li> <li>G_515_dw: Gamma 515 Circulation strength (see additional notes) of downwind (starboard) vortex [m^2/s].</li> <li>cr_uw: Core radius of upwind (port) vortex (in meters).</li> <li>cr_dw: Core radius of downwind (starboard) vortex (in meters).</li> <li>uw distance from lidar [m]: Horizontal distance of upwind (port) vortex from respective lidar.</li> <li>dw distance from lidar [m]: Horizontal distance of downwind (starboard) vortex from respective lidar.</li> <li>uw height [m]: Vertical distance of upwind (port) vortex from respective lidar (floor, as lidars are place at an altitude of 0 m).</li> <li>dw height [m]: Vertical distance of downwind (starboard) vortex from respective lidar (floor, as lidars are place at an altitude of 0 m).</li> <li>vortex age uw [s]: Age of upwind (port) vortex (after first generated by aircraft at respective measurement plane of lidar).</li> <li>vortex age dw [s]: Age of downwind (starboard) vortex (after first generated by aircraft at respective measurement plane of lidar).</li> <li>scan: Associated scan.</li> <li>LID: Associated lidar number.</li> </ul> <p>On top of the summarizing files for each simulation, in the subdirectory <em>individual</em>, the label for each scan is given in a separate file.</p> <p>The above gives information on the simulation truth, furthermore the file <em>labels_with_rv.csv</em> can be found here, where the following extra label columns are given for a subset of scans: [in the following Conv and Naive refer to LLS scans and point measurement scans, respectively]</p> <ul> <li>wind: Strength of crosswind, same as POS1_POS2 in <em>POS1_POS2_scans. </em>The sign corresponds to the wind direction. Negative is a crosswind from the port side of the aircraft, positive is a crosswind from the starboard side of the aircraft.</li> <li>Conv RV: 1 indicates the RV method has been evaluated for LLS scans, 0 if not.</li> <li>Naive RV: 1 indicates the RV method has been evaluated for point measurement scans, 0 if not.</li> <li>conv rv G_515_uw: Gamma 515 Circulation strength (see additional notes) of upwind (port) vortex computed using the RV method on LLS scans [m^2/s].</li> <li>conv rv G_515_dw: Gamma 515 Circulation strength (see additional notes) of downwind (starboard) vortex computed using the RV method on LLS scans [m^2/s].</li> <li>conv rv uw distance from lidar [m]: Horizontal distance of upwind (port) vortex from respective lidar using the RV method on LLS scans.</li> <li>conv rv dw distance from lidar [m]: Horizontal distance of downwind (starboard) vortex from respective lidar using the RV method on LLS scans.</li> <li>conv rv uw height [m]: Vertical distance of upwind (port) vortex from respective lidar (floor, as lidars are place at an altitude of 0 m) using the RV method on LLS scans.</li> <li>conv rv dw height [m]: Vertical distance of downwind (starboard) vortex from respective lidar (floor, as lidars are place at an altitude of 0 m) using the RV method on LLS scans.</li> <li>naive rv G_515_uw: Gamma 515 Circulation strength (see additional notes) of upwind (port) vortex computed using the RV method on point measurement scans [m^2/s].</li> <li>naive rv G_515_dw: Gamma 515 Circulation strength (see additional notes) of downwind (starboard) vortex computed using the RV method on point measurement scans [m^2/s].</li> <li>naive rv uw distance from lidar [m]: Horizontal distance of upwind (port) vortex from respective lidar using the RV method on point measurement scans.</li> <li>naive rv dw distance from lidar [m]: Horizontal distance of downwind (starboard) vortex from respective lidar using the RV method on point measurement scans.</li> <li>naive rv uw height [m]: Vertical distance of upwind (port) vortex from respective lidar (floor, as lidars are place at an altitude of 0 m) using the RV method on point measurement scans.</li> <li>naive rv dw height [m]: Vertical distance of downwind (starboard) vortex from respective lidar (floor, as lidars are place at an altitude of 0 m) using the RV method on point measurement scans.</li> <li>uw phi [deg]: Elevation angle to the center of the upwind (port) vortex from the simulation truth.</li> <li>uw range [m]: Range from the lidar to the center of the upwind (port) vortex from the simulation truth.</li> <li>dw phi [deg]: Elevation angle to the center of the downwind (starboard) vortex from the simulation truth.</li> <li>dw range [m]: Range from the lidar to the center of the downwind (starboard) vortex from the simulation truth.</li> <li>conv rv uw phi [deg]: Elevation angle to the center of the upwind (port) vortex using the RV method on LLS scans.</li> <li>conv rv uw range [m]: Range from the lidar to the center of the upwind (port) vortex using the RV method on LLS scans.</li> <li>conv rv dw phi [deg]: Elevation angle to the center of the downwind (starboard) vortex using the RV method on LLS scans.</li> <li>conv rv dw range [m]: Range from the lidar to the center of the downwind (starboard) vortex using the RV method on LLS scans.</li> <li>naive rv uw phi [deg]: Elevation angle to the center of the upwind (port) vortex using the RV method on point measurement scans.</li> <li>naive rv uw range [m]: Range from the lidar to the center of the upwind (port) vortex using the RV method on point measurement scans.</li> <li>naive rv dw phi [deg]: Elevation angle to the center of the downwind (starboard) vortex using the RV method on point measurement scans.</li> <li>naive rv dw range [m]: Range from the lidar to the center of the downwind (starboard) vortex using the RV method on point measurement scans.</li> <li>y err conv uw [m]: Cartesian localization error (RV minus ST) in y-direction (lateral) between simulation truth and RV method of upwind (port) vortex center on LLS scans.</li> <li>y err conv dw [m]: Cartesian localization error (RV minus ST) in y-direction (lateral) between simulation truth and RV method of downwind (starboard) vortex center on LLS scans.</li> <li>z err conv uw [m]: Cartesian localization error (RV minus ST) in z-direction (vertical) between simulation truth and RV method of upwind (port) vortex center on LLS scans.</li> <li>z err conv dw [m]: Cartesian localization error (RV minus ST) in z-direction (vertical) between simulation truth and RV method of downwind (starboard) vortex center on LLS scans.</li> <li>y err naive uw [m]: Cartesian localization error (RV minus ST) in y-direction (lateral) between simulation truth and RV method of upwind (port) vortex center on point measurement scans.</li> <li>y err naive dw [m]: Cartesian localization error (RV minus ST) in y-direction (lateral) between simulation truth and RV method of downwind (starboard) vortex center on point measurement scans.</li> <li>z err naive uw [m]: Cartesian localization error (RV minus ST) in z-direction (vertical) between simulation truth and RV method of upwind (port) vortex center on point measurement scans.</li> <li>z err naive dw [m]: Cartesian localization error (RV minus ST) in z-direction (vertical) between simulation truth and RV method of downwind (starboard) vortex center on point measurement scans.</li> <li>D err conv uw [m]: Euclidean distance error for the Cartesian coordinates to the vortex center between simulation truth and RV method of upwind (port) vortex center on LLS scans.</li> <li>D err conv dw [m]: Euclidean distance for the Cartesian coordinates to the vortex center between simulation truth and RV method of downwind (starboard) vortex center on LLS scans.</li> <li>D err naive uw [m]: Euclidean distance error for the Cartesian coordinates to the vortex center between simulation truth and RV method of upwind (port) vortex center on point measurement scans.</li> <li>D err naive dw [m]: Euclidean distance for the Cartesian coordinates to the vortex center between simulation truth and RV method of downwind (starboard) vortex center on point measurement scans.</li> <li>plus_minus_phi: Indicates whether a RHI lidar scan features a positive lidar scanning rate (plus), or a negative one (negative).</li> <li>conv err G_515_uw: Circulation error (RV minus ST) between simulation truth and RV method of upwind (port) on LLS scans [m^2/s]. </li> <li>conv err G_515_dw: Circulation error (RV minus ST) between simulation truth and RV method of downwind (starboard) on LLS scans [m^2/s]. </li> <li>naive err G_515_uw: Circulation error (RV minus ST) between simulation truth and RV method of upwind (port) on point measurement scans [m^2/s]. </li> <li>naive err G_515_dw: Circulation error (RV minus ST) between simulation truth and RV method of downwind (starboard) on point measurement scans [m^2/s]. </li> <li>conv err uw phi: Elevation angle error (RV minus ST) between simulation truth and RV method of upwind (port) vortex center on LLS scans [deg].</li> <li>conv err dw phi: Elevation angle error (RV minus ST) between simulation truth and RV method of downwind (starboard) vortex center on LLS scans [deg].</li> <li>naive err uw phi: Elevation angle error (RV minus ST) between simulation truth and RV method of upwind (port) vortex center on LLS scans [deg].</li> <li>naive err dw phi: Elevation angle error (RV minus ST) between simulation truth and RV method of downwind (starboard) vortex center on point measurement scans [deg].</li> <li>conv err uw range: Range from lidar error (RV minus ST) between simulation truth and RV method of upwind (port) vortex center on LLS scans [m].</li> <li>conv err dw range: Range from lidar error (RV minus ST) between simulation truth and RV method of downwind (starboard) vortex center on LLS scans [m].</li> <li>naive err uw range: Range from lidar error (RV minus ST) between simulation truth and RV method of upwind (port) vortex center on point measurement scans [m].</li> <li>naive err dw range: Range from lidar error (RV minus ST) between simulation truth and RV method of downwind (starboard) vortex center on point measurement scans [m].</li> </ul> <p><em>0_0_movement.csv</em> gives insight on the vertical movement on selected vortices in selected lidar scans of the 0_0 wind case. </p> <p>The following data columns exist within the file (note csv file with ; separator):</p> <ul> <li>Str_dw: Vertical movement of the downwind (starboard) vortex, 0 is neutral, -1 is downward, and 1 is upward.</li> <li>Prt_uw: Vertical movement of the upwind (port) vortex, 0 is neutral, -1 is downward, and 1 is upward.</li> <li>scan_code: Identfies associated lidar scan with POS3_POS4_POS5 as in <em>POS1_POS2_scans.</em></li> </ul> <p> </p> <p><strong>lid_plane_info = Additional guidance on the simulated lidars.</strong></p> <p>Each simulation case has a separate file due to minimal ground speed changes of the aircraft. </p> <p>The following data columns exist within each file:</p> <ul> <li>Index: Gives the lidar number corresponding to POS4 and LID.</li> <li>Plane Pos [x]: Gives the longitudinal position of the lidar with respect to the glide path of the aircraft in meters.</li> <li>time plane passed [s]: Gives the simulation time when the aircraft first passes the measurement plane (related to the previous column.</li> <li>height plane passed [m]: Aircraft altitude at the respective lidar positon.</li> <li>lateral position lidar from GP [m]: Lateral position of the lidar from the glide path of the aircraft.</li> </ul> <p><strong>--------------------------------------------------------------------------------------------------------------------------------------------</strong></p> </div> <h3>Additional Notes: </h3> <div> <ul> <li>Gamma 515 circulation [4]: The Gamma 515 circulation is the averaged circulation of a vortex evaluated at radii 5-15m from the vortex center. </li> </ul> </div> <div> <div> <ul> <li>Lidar scans may contain 2 or 1 vortex. In the case of 1 vortex, the other has G_515_?? set to nan. Note that the position may still available in the labels data sets, but only vortices with available G_515_?? values should be used.</li> <li>The upwind and downwind definitions should purely be taken as names, rather than physical meaning. The names are derived from the simulation, due to mirroring and other post-processing these can be misleading however.</li> </ul> </div> </div> <div><strong>--------------------------------------------------------------------------------------------------------------------------------------------</strong></div> <div> <p><strong>Funding</strong>: This dataset was generated within the mFUND <a href="https://bmdv.bund.de/SharedDocs/DE/Artikel/DG/mfund-projekte/kiwi.html">KIWI project</a> funded by the Federal Ministry for Digital and Transportation Germany and the DLR undertaking "Wetter und Disruptive Ereignisse".</p> <p><strong>--------------------------------------------------------------------------------------------------------------------------------------------</strong></p> <p><strong>Acknowledgements:</strong></p> <p>The necessary RANS simulations were performed as part of the EU-funded AWIATOR by DLR's Institute of Aerodynamics and Flow Technology.</p> <p>We acknowledge Airbus for the allowance to use the RANS data.</p> <p>The LES was performed with the incompressible Navier-Stokes code MGLET [5] and kindly provided by the Technical University of Munich, Hydromechanics.</p> <p>The wake vortex simulations were computed on the high performance computer SuperMUC-NG by Leibniz-Rechenzentrum (LRZ).</p> </div> <div><strong>--------------------------------------------------------------------------------------------------------------------------------------------</strong></div> <div> </div> <div><strong>References</strong>: </div> <div> </div> <div>[1] Robey, Rachel, and Julie K. Lundquist. "Behavior and mechanisms of Doppler wind lidar error in varying stability regimes." <em>Atmospheric Measurement Techniques</em> 15.15 (2022): 4585-4622.</div> <div> </div> <div>[2] Stephan, Anton, Norman Wildmann, and Igor Smalikho. "Effectiveness of the MFAS Method for Determining the Wind Velocity Vector from Windcube 200s Lidar Measurements." <em>Atmospheric and Oceanic Optics</em> 32.5 (2019): 555-563.</div> <div> </div> <div>[3] Smalikho, Igor., et al. "Method of radial velocities for the estimation of aircraft wake vortex parameters from data measured by coherent Doppler lidar." <em>Optics Express</em> 23.19 (2015): A1194-A1207.</div> <div> </div> <div>[4] Gerz, Thomas, Frank Holzäpfel, and Denis Darracq. "Commercial aircraft wake vortices." <em>Progress in Aerospace Sciences</em> 38.3 (2002): 181-208. </div> <div> </div> <div>[5] Manhart, Michael. "A zonal grid algorithm for DNS of turbulent boundary layers." <em>Computers & fluids</em> 33.3 (2004): 435-461.</div>
Dataset of behavioral and neurophysiological data of a virtual sailing task published in: "Providing task instructions during motor training enhances performance and modulates attentional brain networks"
<p>Dataset belonging to the behavioral and neurophysiological data of the publication: "Providing task instructions during motor training enhances performance and modulates attentional brain networks". The two uploaded Zip files contain kinematic and electroencephalographic data of 36 participants for the Obstacle and HorizonTask.</p>
Webinar Nuberu: Reliable RAN Virtualization in Shared Platforms @ IMDEA Networks
<p><strong>VIEW IN OUR YOUTUBE CHANNEL:</strong> <a href="https://youtu.be/iAoyuzHuZP0">https://youtu.be/iAoyuzHuZP0</a></p> <p>RAN virtualization will become a key technology for the last mile of next-generation mobile networks driven by initiatives such as the O-RAN alliance. However, due to the computing fluctuations inherent to wireless dynamics and resource contention in shared computing infrastructure, the price to migrate from dedicated to shared platforms may be too high. Indeed, we show in this paper that the baseline architecture of a base station¿s distributed unit (DU) collapses upon moments of deficit in computing capacity. Recent solutions to accelerate some signal processing tasks certainly help but do not tackle the core problem: a DU pipeline that requires predictable computing to provide carrier-grade reliability. We present Nuberu, a novel pipeline architecture for 4G/5G DUs specifically engineered for non-deterministic computing platforms. Our design has one key objective to attain reliability: to guarantee a minimum set of signals that preserve synchronization between the DU and its users during computing capacity shortages and, provided this, maximize network throughput. To this end, we use techniques such as tight deadline control, jitter-absorbing buffers, predictive HARQ, and congestion control. Using an experimental prototype, we show that Nuberu attains >95% of the theoretical spectrum efficiency in hostile environments, where state-of-art approaches lose connectivity, and at least 80% resource savings.</p>
ScienceDex guides
Understand access before you commit
These curated guides explain access requirements, typical timelines, costs, and reuse considerations for widely used research datasets.
Allen Brain Atlas
Allen Brain Atlas is an Allen Institute collection of brain map atlases, datasets, APIs, and analysis tools covering mouse, human, and non-human primate brain resources.
Annotated Behaviour and Observability Dataset (ABODe)
ABODe is a University of Edinburgh DataShare dataset for behavior classification in group-housed mice using home-cage video, identities, bounding boxes, ground-plate positions, and annotator labels.
DANDI Archive for NWB datasets
DANDI is a BRAIN Initiative archive for publishing and sharing neurophysiology data, including electrophysiology, optophysiology, and behavioral data packaged as NWB and related standards.
International Brain Laboratory public data
The International Brain Laboratory public data releases expose standardized mouse decision-making experiments, including Neuropixels recordings, widefield calcium imaging, behavior, and session metadata accessed through the ONE API.
OpenNeuro
OpenNeuro is a free, open platform for sharing neuroimaging datasets, with public search, dataset pages, and download paths for web, S3, DataLad, and the OpenNeuro CLI.