Skip to main content

Searching for Signals of Cosmic Anisotropy

Submission Number: 160
Submission ID: 2826
Submission UUID: 9b2959ad-74bc-4f05-ad69-9f6f98884559
Submission URI: /form/project

Created: Tue, 01/31/2023 - 12:28
Completed: Tue, 01/31/2023 - 12:32
Changed: Mon, 06/26/2023 - 17:54

Remote IP address: 76.152.53.161
Submitted by: Michael Seifert
Language: English

Is draft: No
Webform: Project
Searching for Signals of Cosmic Anisotropy
CAREERS
{Empty}
{Empty}
Finishing Up

Project Leader

Michael Seifert
{Empty}
{Empty}

Project Personnel

Thomas Langford
Wyatt Carbonell, Azade Modaressi
{Empty}

Project Information

In recent years, many physicists have begun to investigate the role of Lorentz symmetry in
physics and whether it could be broken. One mechanism by which this could be broken is with
a spacetime vector field; but the energy and pressure of this field would likely result in a slight
anisotropic expansion of the Universe, which could be observable through statistical analysis of
cosmological signals such as supernova data. However, allowing for this anisotropy also
increases the dimension of the parameter space involved.
In 2019, two students performed an initial analysis and found some intriguing results. Their
code involved running an MCMC code in Mathematica to sample a restricted parameter
subspace, and find the most likely values of various cosmological parameters in this restricted
space. Complicating matters, the objective function being optimized in this analysis was itself a
non-linear function of the parameters, and required the solution of numerical integrals at each
step.
I would like to extend this initial analysis to the full parameter space. This will require
optimization of code and porting to a language with less computational “overhead” (probably
Python, but other options might be viable as well.)

Project Information Subsection

The main deliverable for this project will be a computer code capable of performing MCMC
analysis for this problem on a larger parameter space, and which could be deployed on an HPC
cluster.
{Empty}
{Empty}
{Empty}
{Empty}
{Empty}
Connecticut College
{Empty}
CR-Yale
{Empty}
Yes
Already behind3Start date is flexible
3
{Empty}
{Empty}
{Empty}
{Empty}
  • Milestone Title: Milestone #1
    Milestone Description: Students are familiar with existing code base and with the physical
    problem being solved. Language for new code base has been chosen. (3 weeks after start)
  • Milestone Title: Milestone #2
    Milestone Description: New code has been developed to efficiently calculate
    luminosity-redshift relationship as function of cosmological parameters. (6 weeks after start)
  • Milestone Title: Milestone #3
    Milestone Description: New MCMC routines have been developed and are running
    efficiently. (8 weeks after start)
  • Milestone Title: Milestone #4
    Milestone Description: Code has been optimized and configured for possible deployment
    on HPC cluster. (12 weeks after start)
{Empty}
{Empty}
{Empty}
{Empty}
{Empty}
Ultimately this code would be deployed & run on an HPC cluster. Unfortunately, my institution
does not have such a facility. If time allows, this could be done as part of the 12-week
CAREERS project. If not, it may be possible to get internal funding from my institution and
apply for time via ACCESS or other programs.
[Note: They can use one of Yale's HPCs]
{Empty}

Final Report

{Empty}
{Empty}
{Empty}
{Empty}
{Empty}
{Empty}
{Empty}
{Empty}
{Empty}
{Empty}