Differences between revisions 5 and 8 (spanning 3 versions)
Revision 5 as of 2009-09-15 07:03:10
Size: 1809
Editor: lilo
Comment:
Revision 8 as of 2012-03-16 07:51:46
Size: 1980
Editor: lilo
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
coronal/solar-wind MHD simulation(s) using Br data in synoptic map format: (a) low-resolution daily one by K.H., using updated map, and (b) high-resolution model at PSI, using calbrated map (conducted every 27~28 days) 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 15: Line 17:
 . Plots (images in format like gif or jpg) and
 . 2D cross-section data (sampled on selected quatorial/meridional plane and sphere) will be archived.
 . 3D volume data ? how to handle large files ?
 . 3D volume data will be archived
Line 19: Line 19:
 . a) daily MHD model will run on 8-CPU cluster machine, approximately 2~3 hours
 . b)
 . 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 22: Line 22:
 . a) Daily model : mostly ready as JSOC module: minor issue to handling data via JSOC/DRMS remaining
 . b) External model : the code is ready. the website for showing the results is well prepared by PSI.
 . 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.
Line 25: Line 25:
 . a) 90 %
 . b) ~100%
 . 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:
 . a) Need to define the keyword to specify the daily-updated synoptic maps, in the JSOC context.
 . b) N/A, the high-resolution MARS code will run on external super-computers. The cadence is about a month.
 . a) Remaining issues : define keyword
 . b) Remaining issues : define keyword
Line 31: Line 31:
 * there are no major issues.  * b) Need drill test runs.

HMI Pipeline Module - Module_Name_Here

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

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


  • Back to ["HMIModuleTable"]
  • Back to FrontPage

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