|
Size: 1050
Comment:
|
Size: 1980
Comment:
|
| 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 6: | Line 7: |
| . List inputs here |
. synoptic maps: . a) preliminary daily-updated map for daily model calculation . b) calibrated map |
| Line 9: | Line 11: |
| . List outputs here |
. 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: |
| . Indicate nominal cadence on which module is run |
. a) daily model : 1/day . b) high-res. model : 1 (or more ?) every 27.3-day Carrington Rotation period |
| Line 15: | Line 17: |
| . Indicate if/when products are archived |
. 3D volume data will be archived |
| Line 18: | Line 19: |
| . Indicate if there are any options when running the code |
. 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: |
| . Indicate estimate of percentage complete for the module ===== Status of Code ===== . Name heritage or percent complete for Basic Code |
. 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 27: | Line 28: |
| . Indicate status of DRMS module version of module |
. a) Remaining issues : define keyword . b) Remaining issues : define keyword |
| Line 30: | Line 31: |
* List issues that still need to be resolved * Describe as many as you like |
* b) Need drill test runs. |
| Line 35: | Line 33: |
| . Give name of local coordinator for development of this module | |
| Line 39: | Line 36: |
| Line 43: | Line 37: |
* Back to ["HMIModuleTable"] * Back to FrontPage |
* Back to ["HMIModuleTable"] * Back to FrontPage |
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 ([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)
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