Not sure what the protocol looks like in the near-term. In the long term, we'll need to handle the full 3D data cube. For the short term, it might be a python algorithm to pass in the appropriate numpy or x-array array.
Email from Leila Mays - Mon, Jun 10, 2019 at 1:31 PM
I happen to already have the entire run uploaded (358 GB) in case you want to see other timesteps. _{data has been downloaded to dakota:/d4/projects/MET_spaceweather}
Information on tim.0000.nc:
3D spherical grid in HEEQ coordinates +180 deg (Heliocentric Earth Equatorial, and then rotated 180 degrees.
X1, X2, X3 - grid information (r, theta (co latitude), phi)
TIME in seconds measured from rundate_mjd (so also add 2400000.5 to get to JD if needed)
V1, V2, V3 - velocity field (Vr, Vtheta, Vphi)
So for example, to recover graphics at latitude=0 (near the ecliptic plane) you would set the index for V2 (or X2) to 29.
TaraJensen
commented
5 years ago
Not sure what the protocol looks like in the near-term. In the long term, we'll need to handle the full 3D data cube. For the short term, it might be a python algorithm to pass in the appropriate numpy or x-array array.
Email from Leila Mays - Mon, Jun 10, 2019 at 1:31 PM
Here is a sample file from ENLIL - a heliosphere model. This run has a "high" spatial resolution setting, so the file size is about 2.5 GB, but at low resolution it's much smaller (around 50-100MB). If the file size is an issue I can send a different run. https://ccmc.gsfc.nasa.gov/RoR_WWW/output_files/leila/NCAR/Leila_Mays_101918_SH_3_sample/tim.0000.nc
I happen to already have the entire run uploaded (358 GB) in case you want to see other timesteps. _{data has been downloaded to dakota:/d4/projects/MET_spaceweather}
Simulation information: https://ccmc.gsfc.nasa.gov/database_SH/Leila_Mays_101918_SH_2.php
quicklook graphics: https://ccmc.gsfc.nasa.gov/RoR_WWW//raidya7/Leila_Mays_101918_SH_3/Leila_Mays_101918_SH_3_graphics.html
example: https://ccmc.gsfc.nasa.gov/RoR_WWW//raidya7/Leila_Mays_101918_SH_3/Leila_Mays_101918_SH_3_vel1o4-mars_high2syn_anim.gif
Information on tim.0000.nc: 3D spherical grid in HEEQ coordinates +180 deg (Heliocentric Earth Equatorial, and then rotated 180 degrees. X1, X2, X3 - grid information (r, theta (co latitude), phi) TIME in seconds measured from rundate_mjd (so also add 2400000.5 to get to JD if needed) V1, V2, V3 - velocity field (Vr, Vtheta, Vphi)
So for example, to recover graphics at latitude=0 (near the ecliptic plane) you would set the index for V2 (or X2) to 29.