iDaVIE v1.0: A virtual reality tool for interactive analysis of astronomical data cubes

Abstract

As modern astronomy confronts unprecedented data volumes, automated pipelines and machine-learning techniques have become essential for processing and analysis. As these workflows grow more complex, astronomers also require input and inspection tools that can keep pace. To address challenges in navigating multidimensional datasets for quality control and scientific interpretation, we present the immersive Data Visualisation Interactive Explorer (iDaVIE), a virtual reality (VR) software suite developed in collaboration with the astronomy community. iDaVIE enables users to import and render large 3D data cubes within a VR environment, offering real-time tools for selection, cropping, catalogue overlays, and exporting results back into existing pipelines. Built on the Unity engine and SteamVR, the system uses custom plug-ins for efficient data parsing, downsampling, and statistical calculations. The software has already been integrated into workflows such as verifying HI data cubes from MeerKAT, ASKAP, and APERTIF, refining detection masks, and identifying new sources. Its intuitive interface aims to reduce the cognitive load associated with higher-dimensional data, allowing researchers to focus more directly on scientific goals. As an open-source, scalable, and adaptable platform, iDaVIE supports continued development and integration with other tools. Version 1.0 marks a significant milestone, with planned enhancements including subcube loading, advanced rendering modes, video-generation scripts, and collaborative capabilities. By pairing immersive visualisation with robust interaction tools, iDaVIE seeks to transform how researchers engage with complex datasets and enhance productivity in the era of big data.

Figures (13)

• Figure 1: This is a simplified high-level architecture of iDaVIE. The various classes and their interactions are shown. Classes are also grouped into different groups based on what component of the software they hold responsibility for.
• Figure 2: Example visualisations generated by iDaVIE in VR from the same data cube and mask: (a) the user’s 3D VR view (exportable as .png via voice command or the QuickMenu); (b) the floating Source Lists info window showing mask-derived statistics or imported VOTable columns; (c) and (d) realtime Moment 0 and Moment 1 maps for cropped regions (exportable as .png or .fits); (e) a spectral profile extracted from selected mask regions (exportable as .csv); and (f) a histogram of the dataset that updates with colourmap clamping.
• Figure 3: Sequence diagram of the file load process. The user selects a FITS file to load, which is then parsed by the FitsReader plug-in. The data is downsampled and loaded into a 3D texture, which is then rendered in the scene.
• Figure 4: The file tab of the desktop GUI. This is what the user first sees when loading iDaVIE. Browsing for a data or mask file opens the system default file browser and filters for FITS files. A scrollable text box gives a preview of the data file FITS header. The VR View box shows a duplicate of what the VR headset is currently rendering.
• Figure 5: Layout of the input buttons referenced in this paper for the Meta Quest 3 controllers. This layout is mapped to other VR controllers via the SteamVR action system, allowing custom button bindings across devices. Buttons are labelled once here but apply to both controllers. The primary controller is the user's dominant hand, set in the VR Settings menu.