|
Size: 1050
Comment:
|
Size: 1988
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 one by K.H., using updated map, and (b) high-resolution model at PSI, using calbrated map (conducted every 27~28 days) |
| Line 6: | Line 5: |
| . List inputs here |
. synoptic maps: . a) preliminary daily-updated map for daily model calculation . b) calibrated map for external model(s) |
| Line 9: | Line 9: |
| . List outputs here |
. 1) Corona : field lines, synthetic LoS-integrated coronal density, temperature etc. . 2) Interplanetary (at 30Rs ?): solar wind parameters (B, V, N, T) map ? |
| Line 12: | Line 12: |
| . 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 15: |
| . Indicate if/when products are archived |
. 3D volume data will be archived |
| Line 18: | Line 17: |
| . Indicate if there are any options when running the code |
. 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 |
| Line 21: | Line 20: |
| . 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) 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. ===== Code ===== . 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 |
| Line 27: | Line 26: |
| . Indicate status of DRMS module version of module |
. a) Remaining issues : define keyword. . b) Remaining issues : do define keyword other than physics unit and CR number. |
| Line 30: | Line 29: |
* List issues that still need to be resolved * Describe as many as you like |
* 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 |
| Line 35: | Line 31: |
| . Give name of local coordinator for development of this module | |
| Line 39: | Line 34: |
| Line 43: | Line 35: |
* 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 one by K.H., using updated map, and (b) high-resolution model at PSI, using calbrated map (conducted 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) Corona : field lines, synthetic LoS-integrated coronal density, temperature etc.
- 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) 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
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) 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.
Code
- 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
Status of DRMS module
- a) Remaining issues : define keyword.
- b) Remaining issues : do define keyword other than physics unit and CR number.
Issues needing resolution
- 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
Responsible scientist
K. Hayashi
Remarks
- Back to ["HMIModuleTable"]
Back to FrontPage