TARDIS RT Collaboration

Mentors: Student: Shreyans Saraf

Currently, TARDIS relies on IPyWidgets for its visualization modules. While effective within Jupyter environments, these widgets have limited compatibility with Sphinx, which is used to build and host the project’s documentation. In contrast, Panel provides significantly better integration with Sphinx, enabling seamless embedding of interactive components directly into static documentation. One of the key advantages of adopting Panel is the ability to deliver fully interactive visualizations within the documentation itself, without requiring a live Jupyter environment. This project aims to migrate TARDIS’s existing visualization tools from IPyWidgets to Panel and make them interactive in the documentation page itself. By doing so, users will be able to explore and interact with widgets directly on the documentation pages, leading to a more intuitive understanding of their functionality and usage. Additionally, this transition will establish a framework to allow future widgets to be easily integrated with interactivity in the documentation. Deliverables: - Custom Abundance Widget migrated to Panel - Grotrian Widget migrated to Panel - All widgets made interactive in the documentation.

Mentors: Student: Rishmita Rao

The plasma module is used to determine the ionization and excitation states of the supernova ejecta using the basic structure of the supernova (elemental abundances, densities, radiation temperature). As described in the project description in the GSOC project page, CodeCov does not accurately report coverage of the TARDIS plasma. This is because the plasma module is used as a parameter for models and simulations, and is therefore indirectly tested by the tests of the simulation and model functions. While there are parts of the plasma module that are tested directly, many aspects of the module have no easy to find direct tests. This project aims to increase the test coverage of the plasma module and make the tests of the plasma modules easy to find and read.

Mentors: Student: Haille Perkins

This project will result in functionality for both TARDIS and STARDIS to identify and display a user provided list of atomic and molecular lines to existing spectral visualizations. This will be done by leveraging information stored in the simulation's energy packets to identify source species. This is critical work as observed spectra often have blended line features due to the high ejecta speeds broadening neighboring lines into each other; However, in the simulated spectra, source packets are known and thus blended lines can be disentangled. This work will enable simple comparisons with published, labeled spectra; identification of unlabeled features in newly observed spectra; a physical understanding of new models; and development of publication-ready plots.

Mentors: Student: Riddhi Gangbhoj

TARDIS implements a regression testing framework which is used to compare the current output of TARDIS to a saved data repository to validate code. This data repository is modified at times when there are code/infrastructure changes in TARDIS, this could be environment updates, scientific code changes or more. However, the impact of smaller commits goes unnoticed. There is a comparison notebook implemented that can compare two different commits and spectra in a comprehensive manner but that does not provide a way to compare multiple commits at once. This project aims to build a system to compare the regression data produced by a range of TARDIS commits and will be able to find the commits which impact the regression data files. Also this project aims to enhance TARDIS HDF writing capabilities by adding a HDF writing system to most TARDIS objects and the simulation, so it is easy to reproduce TARDIS objects from stored HDF files.

Mentors: Student: Sumit_Gupta

TARDIS provides ways to simulate and analyze supernovae. Currently, as a visualization tool, we have the "Spectral element DEComposition (SDEC) Plot," which generates the output spectrum of the supernovae. However, there is a lot of other information a researcher might need, and this project aims to solve one, i.e., getting the interaction information. TARDIS already has a Tracker functionality which tracks all the interactions in the ejecta, which requires some optimizations and refactoring. I will also be introducing another Tracking Functionality, which will precisely track the last interaction. The Current Tracking functionality has no tests to check if the data generated by it is correct. So, I will also be writing tests. I will also be documenting the trackers.