Differences between revisions 2 and 3
Revision 2 as of 2009-04-11 00:52:09
Size: 1415
Editor: lilo
Comment:
Revision 3 as of 2009-05-19 01:46:58
Size: 1489
Editor: lilo
Comment:
Deletions are marked like this. Additions are marked like this.
Line 13: Line 13:
 . external, high-res. model : 1 (or mode ?) / one CR, where to run?  . external, high-res. model : 1 (or mode ?) / one CR, where to run (a few days after one CR ends)?
Line 19: Line 19:
 . one run will use 8 CPUs (or 16 on lws2?)  . one run will use 8 CPUs (or 16 on lws2?) or, outside Stanford
Line 21: Line 21:
 . daily model : mostly ready
 . external model : to decide the spatial resolution, where to run, etc.
 . input data preparetion : may need to make new c-codes or convert from IDL to make input data format for each developer's preference.
 . 1) Daily model : mostly ready
 . 2) External model : to decide the spatial resolution, where to run, etc.
 . 3) Input data preparetion : may need to make new (c-)codes replacing exisiting IDL code and others so that
 .
input data format match each developer's preference.
Line 29: Line 30:
 * test in HMI context  * none

HMI Pipeline Module - Module_Name_Here

Summarize the task performed by this module in a couple sentences

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
  • daily model : 1/day
  • external, high-res. model : 1 (or mode ?) / one CR, where to run (a few days after one CR ends)?

Archive
  • Plots (images in format like gif or jpg) and
  • 2D data (sampled on selected quatorial/meridional plane and sphere) will be archived.
  • ? 3D volume data ? because of large file size etc.

Options
  • one run will use 8 CPUs (or 16 on lws2?) or, outside Stanford

Overall Status of Module
  • 1) Daily model : mostly ready
  • 2) External model : to decide the spatial resolution, where to run, etc.
  • 3) Input data preparetion : may need to make new (c-)codes replacing exisiting IDL code and others so that
  • input data format match each developer's preference.

Status of Code
  • 70 %

Status of DRMS module
  • to do !

Issues needing resolution
  • none

Responsible scientist

K. Hayashi

Remarks


  • Back to ["HMIModuleTable"]
  • Back to FrontPage

JsocWiki: ModelDynamicCorona (last edited 2013-05-01 04:35:23 by localhost)