|
Size: 1036
Comment:
|
Size: 1265
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 |
. time-sequence of local "patch" magnetogram maps at selected active regions |
| Line 9: | Line 7: |
| . List outputs here |
. Plots and 3-D volume data of MHD variables, field lines etc. above the active region |
| Line 12: | Line 9: |
| . Indicate nominal cadence on which module is run |
. on-demand. . SDO website will have links to guide users to point of contact to reach external developers |
| Line 15: | Line 12: |
| . Indicate if/when products are archived |
. Yes (?) |
| Line 18: | Line 14: |
| . Indicate if there are any options when running the code |
. the external developer |
| Line 21: | Line 16: |
| . Indicate estimate of percentage complete for the module |
. Agreements with the external developers, for us to introduce them. |
| Line 24: | Line 18: |
| . Name heritage or percent complete for Basic Code |
. MHD codes at UAH . RADMHD by UC Berkeley |
| Line 27: | Line 21: |
| . Indicate status of DRMS module version of module |
. Need to prepare the website, rather than the internal module process codes. |
| Line 30: | Line 23: |
* List issues that still need to be resolved * Describe as many as you like |
* Define the web-site forms assisting users to contact the developers. |
| Line 35: | Line 25: |
| . Give name of local coordinator for development of this module |
. K.Hayashi (point of contact at Stanford) |
| Line 38: | Line 27: |
| Line 42: | Line 28: |
* 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
- time-sequence of local "patch" magnetogram maps at selected active regions
Module Outputs
- Plots and 3-D volume data of MHD variables, field lines etc. above the active region
Cadence
- on-demand.
- SDO website will have links to guide users to point of contact to reach external developers
Archive
- Yes (?)
Options
- the external developer
Overall Status of Module
- Agreements with the external developers, for us to introduce them.
Status of Code
- MHD codes at UAH
- RADMHD by UC Berkeley
Status of DRMS module
- Need to prepare the website, rather than the internal module process codes.
Issues needing resolution
- Define the web-site forms assisting users to contact the developers.
Responsible scientist
- K.Hayashi (point of contact at Stanford)
Remarks
- Back to ["HMIModuleTable"]
Back to FrontPage