Differences between revisions 3 and 9 (spanning 6 versions)
⇤ ← Revision 3 as of 2009-05-19 01:46:58 →
Size: 1489
Editor: lilo
Comment:
← Revision 9 as of 2013-05-01 04:35:23 → ⇥
Size: 1982
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
Summarize the task performed by this module in a couple sentences coronal/solar-wind MHD simulation(s) using Br data in synoptic map format:
 . a) low-resolution daily, coronal MHD ([[http://sun.stanford.edu/~keiji/daily_mhd/daily_mhd.html|here]]) by K.H., using updated map
 . b) high-resolution model at PSI, using calibrated definitive map (every 27~28 days)
Line 7: Line 9:
 . b) calibrated  map for external model(s)  . b) calibrated map
Line 9: Line 11:
 . 1) Corona : field lines, synthetic LoS-integrated coronal density, temperature etc.
 . 2) Interplanetary (at 30Rs ?): solar wind parameters (B, V, N, T) map ?		  . 1) graphics and 3D data of solar corona and interplanetary space
 . 2) Interplanetary (at 30Rs): solar wind parameters (B, V, N, T) map
Line 12: Line 14:
 . daily model : 1/day
 . external, high-res. model : 1 (or mode ?) / one CR, where to run (a few days after one CR ends)?		  . a) daily model : 1/day
 . b) high-res. model : 1 (or more ?) every 27.3-day Carrington Rotation period
Line 15: Line 17:
 . Plots (images in format like gif or jpg) and
 . 2D data (sampled on selected quatorial/meridional plane and sphere) will be archived.
 . ? 3D volume data ? because of large file size etc.		  . 3D volume data will be archived
Line 19: Line 19:
 . one run will use 8 CPUs (or 16 on lws2?) or, outside Stanford  . a) KH's low-resolution daily MHD model will be run on an 8-CPU cluster machine, on daily basis.
 . b) High-resolution physics based coronal model by PSI (Predictive Science Inc.), on one-per-CR basis.
Line 21: Line 22:
 . 1) Daily model : mostly ready
 . 2) External model : to decide the spatial resolution, where to run, etc.
 . 3) Input data preparetion : may need to make new (c-)codes replacing exisiting IDL code and others so that
 . input data format match each developer's preference.
===== Status of Code =====
 . 70 %		  . a) Daily model, mostly finished :(1) take synotpic map through JSOC/DRMS, (2) prepare intiial values (3) do MHD simulation (4) save 3D data in JSOC database.
 . b) Interfaces with PSI model, mostly done : at Stanford JSOC site, (1) script to get PSI data via http protocol, (2) convert HDF4 to JSOC-favorite formats FITS (3) save the 3D data in JSOC database.
===== Code =====
 . a) 100 % of MHD part in Fortran, 90 % of JSOC interface codes and scripts.
 . b) 90 % of script (using wget) to fetch data via http, and 90% of JSOC interface codes and scripts.
Line 28: Line 28:
 . to do !  . a) Remaining issues : define keyword
 . b) Remaining issues : define keyword
Line 30: Line 31:
 * none  * b) Need drill test runs.
Line 36: Line 37:
 * Back to ["HMIModuleTable"]  * Back to [[HMIModuleTable]]

HMI Pipeline Module - Module_Name_Here

coronal/solar-wind MHD simulation(s) using Br data in synoptic map format:

  • a) low-resolution daily, coronal MHD (here) by K.H., using updated map

  • b) high-resolution model at PSI, using calibrated definitive map (every 27~28 days)

Module Inputs
  • synoptic maps:
  • a) preliminary daily-updated map for daily model calculation
  • b) calibrated map

Module Outputs
  • 1) graphics and 3D data of solar corona and interplanetary space
  • 2) Interplanetary (at 30Rs): solar wind parameters (B, V, N, T) map

Cadence
  • a) daily model : 1/day
  • b) high-res. model : 1 (or more ?) every 27.3-day Carrington Rotation period

Archive
  • 3D volume data will be archived

Options
  • a) KH's low-resolution daily MHD model will be run on an 8-CPU cluster machine, on daily basis.
  • b) High-resolution physics based coronal model by PSI (Predictive Science Inc.), on one-per-CR basis.

Overall Status of Module
  • a) Daily model, mostly finished :(1) take synotpic map through JSOC/DRMS, (2) prepare intiial values (3) do MHD simulation (4) save 3D data in JSOC database.
  • b) Interfaces with PSI model, mostly done : at Stanford JSOC site, (1) script to get PSI data via http protocol, (2) convert HDF4 to JSOC-favorite formats FITS (3) save the 3D data in JSOC database.

Code
  • a) 100 % of MHD part in Fortran, 90 % of JSOC interface codes and scripts.
  • b) 90 % of script (using wget) to fetch data via http, and 90% of JSOC interface codes and scripts.

Status of DRMS module
  • a) Remaining issues : define keyword
  • b) Remaining issues : define keyword

Issues needing resolution
  • b) Need drill test runs.

Responsible scientist

K. Hayashi

Remarks

JsocWiki: ModelDynamicCorona (last edited 2013-05-01 04:35:23 by localhost)