Size: 1036
Comment:
|
Size: 1222
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 |
The products will be in on-request category. We propose to have external modules to do it. will discuss how to make it happen. The target modules are from STWu at Alabama, and (perhaps) from Abbit at Berkeley. |
Line 6: | Line 5: |
. List inputs here |
. (may be) time-sequence of local patch (at selected active regions) , in format preferred by external developers |
Line 9: | Line 7: |
. List outputs here |
. (?) 3D data of MHD variables, field lines etc. |
Line 12: | Line 9: |
. Indicate nominal cadence on which module is run |
. on-demand. |
Line 15: | Line 11: |
. Indicate if/when products are archived |
. Yes. |
Line 18: | Line 13: |
. Indicate if there are any options when running the code |
. SDO website will have webpage to guide users to appropriate points of contact where options be discussed. |
Line 22: | Line 16: |
Line 25: | Line 18: |
Line 28: | Line 20: |
Line 30: | Line 21: |
* List issues that still need to be resolved * Describe as many as you like |
* List issues that still need to be resolved * Describe as many as you like |
Line 35: | Line 24: |
. Give name of local coordinator for development of this module |
. K.Hayashi (point of contact at Stanford) |
Line 38: | Line 26: |
Line 42: | Line 27: |
* Back to ["HMIModuleTable"] * Back to FrontPage |
* Back to ["HMIModuleTable"] * Back to FrontPage |
HMI Pipeline Module - Model3DARField
The products will be in on-request category. We propose to have external modules to do it. will discuss how to make it happen. The target modules are from STWu at Alabama, and (perhaps) from Abbit at Berkeley.
Module Inputs
- (may be) time-sequence of local patch (at selected active regions) , in format preferred by external developers
Module Outputs
- (?) 3D data of MHD variables, field lines etc.
Cadence
- on-demand.
Archive
- Yes.
Options
- SDO website will have webpage to guide users to appropriate points of contact where options be discussed.
Overall Status of Module
- Indicate estimate of percentage complete for the module
Status of Code
- Name heritage or percent complete for Basic Code
Status of DRMS module
- Indicate status of DRMS module version of module
Issues needing resolution
- List issues that still need to be resolved
- Describe as many as you like
Responsible scientist
- K.Hayashi (point of contact at Stanford)
Remarks
- Back to ["HMIModuleTable"]
Back to FrontPage