Work Description

Title: Stormtime energetics: Energy transport across the magnetopause in a global MHD simulation, simulation and analysis data Open Access Deposited

h
Attribute Value
Methodology
  • Simulation run using Space Weather Modeling Framework (SWMF) from University of Michigan Center for Space Environment Modeling (CSEM).

  • Data was processed using python plugin for Tecplot commercial visualization software. All analysis is automated with pytecplot scripts.

  • Observational data was downloaded from NASA Coordinated Data Analysis Web (CDAWeb) and processed in conjunction with pytecplot scripts.
Description
  • Coupling between the solar wind and magnetosphere can be expressed in terms of energy transfer through the separating boundary known as the magnetopause. Geospace simulation is performed using the Space Weather Modeling Framework (SWMF) of a multi-ICME impact event on February 18-20, 2014 in order to study the energy transfer through the magnetopause during storm conditions. The magnetopause boundary is identified using a modified plasma $\beta$ and fully closed field line criteria to a downstream distance of $-20R_{e}$. Observations from Geotail, Themis, and Cluster are used as well as the Shue 1998 model to verify the simulation field data results and magnetopause boundary location. Once the boundary is identified, energy transfer is calculated in terms of total energy flux \textbf{K}, Poynting flux \textbf{S}, and hydrodynamic flux \textbf{H}. Surface motion effects are considered and the regional distribution of energy transfer on the magnetopause surface is explored in terms of dayside $\left(X>0\right)$, flank $\left(X<0\right)$, and tail cross section $\left(X=X_{min}\right)$ regions. It is found that total integrated energy flux over the boundary is nearly balanced between injection and escape, and flank contributions dominate the Poynting flux injection. Poynting flux dominates net energy input, while hydrodynamic flux dominates energy output. Surface fluctuations contribute significantly to net energy transfer and comparison with the Shue model reveals varying levels of cylindrical asymmetry in the magnetopause flank throughout the event. Finally existing energy coupling proxies such as the Akasofu $\epsilon$ parameter and Newell coupling function are compared with the energy transfer results.
Creator
Depositor
  • aubr@umich.edu
Contact information
Discipline
Funding agency
  • National Science Foundation (NSF)
  • National Aeronautics and Space Administration (NASA)
Keyword
Date coverage
  • 2021-06-01 to 2021-09-30
Citations to related material
  • Brenner A, Pulkkinen TI, Al Shidi Q and Toth G (2021) Stormtime Energetics: Energy Transport Across the Magnetopause in a Global MHD Simulation. Front. Astron. Space Sci. 8:756732. doi: 10.3389/fspas.2021.756732
Resource type
Last modified
  • 11/22/2022
Published
  • 03/01/2022
Language
DOI
  • https://doi.org/10.7302/nxyj-7062
License
To Cite this Work:
Brenner, A. (2022). Stormtime energetics: Energy transport across the magnetopause in a global MHD simulation, simulation and analysis data [Data set], University of Michigan - Deep Blue Data. https://doi.org/10.7302/nxyj-7062

Relationships

This work is not a member of any user collections.

Files (Count: 33; Size: 358 GB)

#This repository contains data, processing, and analysis tools for

studying a geomagnetic storm event on Feb 18-20 2014, specifically

looking at the energy transfer occuring across the magnetopause

surface

#This work was done using anaconda environment/package manager tool

https://www.anaconda.com

#The primary tool used for analysis is Tecplot, specifically

Tecplot360ex2020r1 it is a licsenced software, details can be found

at https://www.tecplot.com/products/tecplot-360/

#Once tecplot is installed and the licsence is obtained, in order to

run pytecplot you will need to follow the installation procedure, a

hardcopy of the installation procedure is included here but the most

recent should be available at https://www.tecplot.com/docs/pytecplot/install.html

Note that pytecplot itself is simply installed with pip and is listed

in the included packages below

#Not all packages listed here are neccessarily used and alternate

versions were not tested since this is for archival purposes only

#pip was used to install all python packages, for details on what

specific packages are used see the import statements in the python

scripts

packages in environment:

#

Name Version Build Channel

_libgcc_mutex 0.1 conda_forge conda-forge
_openmp_mutex 4.5 1_gnu conda-forge
alabaster 0.7.12 pypi_0 pypi
babel 2.9.1 pypi_0 pypi
backcall 0.2.0 pypi_0 pypi
basesystem-amzn2-aarch64 10.0 5

binutils_impl_linux-64 2.36.1 h193b22a_2 conda-forge
bzip2 1.0.8 hb9a14ef_8 intel
ca-certificates 2021.5.30 ha878542_0 conda-forge
certifi 2021.5.30 py38h578d9bd_0 conda-forge
charset-normalizer 2.0.6 pypi_0 pypi
cycler 0.10.0 pypi_0 pypi
data 0.4 pypi_0 pypi
datetime 4.3 pypi_0 pypi
decorator 5.1.0 pypi_0 pypi
docutils 0.17.1 pypi_0 pypi
filesystem-amzn2-aarch64 3.2 5

flatbuffers 2.0 pypi_0 pypi
funcsigs 1.0.2 pypi_0 pypi
future 0.18.2 pypi_0 pypi
gcc 11.2.0 h702ea55_1 conda-forge
gcc_impl_linux-64 11.2.0 h82a94d6_9 conda-forge
glibc-amzn2-aarch64 2.26 5

glibc-common-amzn2-aarch64 2.26 5

glibc-minimal-langpack-amzn2-aarch64 2.26 5

h5py 3.4.0 pypi_0 pypi
imagesize 1.2.0 pypi_0 pypi
intelpython 2021.3.0 7 intel
ipython 7.28.0 pypi_0 pypi
jedi 0.18.0 pypi_0 pypi
jinja2 3.0.1 pypi_0 pypi
kernel-headers_linux-64 2.6.32 he073ed8_14 conda-forge
kiwisolver 1.3.2 pypi_0 pypi
latex 0.7.0 pypi_0 pypi
ld_impl_linux-64 2.36.1 hea4e1c9_2 conda-forge
libffi 3.3 13 intel
libgcc-devel_linux-64 11.2.0 h0952999_9 conda-forge
libgcc-ng 11.2.0 h1d223b6_9 conda-forge
libgomp 11.2.0 h1d223b6_9 conda-forge
libsanitizer 11.2.0 he4da1e4_9 conda-forge
libstdcxx-ng 11.2.0 he4da1e4_9 conda-forge
markupsafe 2.0.1 pypi_0 pypi
matplotlib 3.4.3 pypi_0 pypi
matplotlib-inline 0.1.3 pypi_0 pypi
matplotlib-label-lines 0.4.1 pypi_0 pypi
networkx 2.6.3 pypi_0 pypi
numexpr 2.7.3 pypi_0 pypi
numpydoc 1.1.0 pypi_0 pypi
openssl 1.1.1l h7f98852_0 conda-forge
packaging 21.0 pypi_0 pypi
parso 0.8.2 pypi_0 pypi
pexpect 4.8.0 pypi_0 pypi
pickleshare 0.7.5 pypi_0 pypi
pillow 8.3.2 pypi_0 pypi
pip 21.1.1 py38ha59826b_0 intel
progress 1.6 pypi_0 pypi
prompt-toolkit 3.0.20 pypi_0 pypi
protobuf 3.18.0 pypi_0 pypi
ptyprocess 0.7.0 pypi_0 pypi
pydash 5.0.2 pypi_0 pypi
pyforecasttools 1.1.1 pypi_0 pypi
pygments 2.10.0 pypi_0 pypi
pyparsing 2.4.7 pypi_0 pypi
pytecplot 1.4.0 pypi_0 pypi
python 3.8.11 ha27d850_1 intel
python-dateutil 2.8.2 pypi_0 pypi
python_abi 3.8 2_cp38 conda-forge
pyzmq 22.3.0 pypi_0 pypi
requests 2.26.0 pypi_0 pypi
scipy 1.7.1 pypi_0 pypi
setup-amzn2-aarch64 2.8.71 5

setuptools 52.0.0 py38h0d5a7d4_0 intel
shutilwhich 1.1.0 pypi_0 pypi
six 1.16.0 pypi_0 pypi
snowballstemmer 2.1.0 pypi_0 pypi
spacepy 0.2.2 pypi_0 pypi
sphinx 4.2.0 pypi_0 pypi
sphinxcontrib-applehelp 1.0.2 pypi_0 pypi
sphinxcontrib-devhelp 1.0.2 pypi_0 pypi
sphinxcontrib-htmlhelp 2.0.0 pypi_0 pypi
sphinxcontrib-jsmath 1.0.1 pypi_0 pypi
sphinxcontrib-qthelp 1.0.3 pypi_0 pypi
sphinxcontrib-serializinghtml 1.1.5 pypi_0 pypi
sqlite 3.35.5 hb9a14ef_1 intel
sysroot_linux-64 2.12 he073ed8_14 conda-forge
system-release-amzn2-aarch64 2 5

tables 3.6.1 pypi_0 pypi
tcl 8.6.10 1 intel
tempdir 0.7.1 pypi_0 pypi
tex 1.8 pypi_0 pypi
tk 8.6.10 h8e2d9d6_3 intel
traitlets 5.1.0 pypi_0 pypi
tzdata-amzn2-aarch64 2020d 5

urllib3 1.26.7 pypi_0 pypi
wcwidth 0.2.5 pypi_0 pypi
wheel 0.36.2 py38ha11c92b_0 intel
xz 5.2.5 h74280d8_2 intel
zlib 1.2.11.1 h047b5d8_3 intel
zope-interface 5.4.0 pypi_0 pypi

Download All Files (To download individual files, select them in the “Files” panel above)

Total work file size of 358 GB is too large to download directly. Consider using Globus (see below).



Best for data sets > 3 GB. Globus is the platform Deep Blue Data uses to make large data sets available.   More about Globus

Remediation of Harmful Language

The University of Michigan Library aims to describe library materials in a way that respects the people and communities who create, use, and are represented in our collections. Report harmful or offensive language in catalog records, finding aids, or elsewhere in our collections anonymously through our metadata feedback form. More information at Remediation of Harmful Language.