|
Size: 1988
Comment:
|
Size: 1978
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 one by K.H., using updated map, and (b) high-resolution model at PSI, using calibrated definitive map (every 27~28 days) |
| Line 9: | Line 9: |
| . 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 by (b) high-resolution data by PSI (?) |
| Line 17: | Line 17: |
| . a) daily MHD model will run on 8-CPU cluster machine, approximately 2~3 hours . b) HDF file provided by PSI once a CR period will be first converted to FITS format then send to DRMS |
. 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 20: | Line 20: |
| . a) Daily model, mostly finished :(1) take synotpic map through JSOC/DRMS, (2) prepare intiial values (3) do MHD simulation (4) send 3D data to JSOC. . b) External PSI model : mostly done : (1) script to get PSI data at their website, (2) convert HDF4 to JSOC-favorite format (3) send the 3D data to JSOC. |
. 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) PSI model, mostly done : at Stanford JSOC site, (1) script to get PSI data via http protocol, (2) convert HDF4 to JSOC-favorite format, FITS (3) save the 3D data in JSOC. |
| Line 23: | Line 23: |
| . a) 100 % of MHD part in Fortran, 99 % of C-wrapper . b) 99 % of script (using wget) to fetch data via http, and 99% of C-code to push the 3D data to JSOC |
. 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 26: | Line 26: |
| . a) Remaining issues : define keyword. . b) Remaining issues : do define keyword other than physics unit and CR number. |
. a) Remaining issues : define keyword . b) Remaining issues : define keyword |
| Line 29: | Line 29: |
| * On j8.q and j.q, some code returns NaN even though the data is OK. o.q and o8.q do not have such problem.....unnnn | * Need drill tests, after the definitive synoptic maps ready. |
HMI Pipeline Module - Module_Name_Here
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 calibrated definitive map (every 27~28 days)
Module Inputs
- synoptic maps:
- a) preliminary daily-updated map for daily model calculation
- b) calibrated map for external model(s)
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 by (b) high-resolution data by PSI (?)
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) PSI model, mostly done : at Stanford JSOC site, (1) script to get PSI data via http protocol, (2) convert HDF4 to JSOC-favorite format, FITS (3) save the 3D data in JSOC.
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
- Need drill tests, after the definitive synoptic maps ready.
Responsible scientist
K. Hayashi
Remarks
- Back to ["HMIModuleTable"]
Back to FrontPage