The-Info-We-Need-for-a-Run

From OpenGGCM
Jump to: navigation, search

If you request a simulation run from us (which we are happy to do) we need this information:

  • A brief paragraph of the objective and a description of the event. SW/IMF plots if available as well as data plots of in-situ measurements for comparisons. We need this info to make choices about the grid and other parameters.
  • UT start time YYYY:MM:DD:hh:mm:ss.sss (this time should be ~2-8h before the event, depending on IMF. For south IMF 2h are sufficient, for strong north IMF 8+ hours are needed).
  • UT end time YYYY:MM:DD:hh:mm:ss.sss of the run
  • UT dipole time YYYY:MM:DD:hh:mm:ss.sss of the run. The dipole will be fixed to its orientation at this time.
  • name of the SW monitor, 'fi' for made-up onditions
  • position of the SW monitor, X, Y, Z in RE/GSE
  • F107: 10.7 cm solar radio flux (one number, measured daily)
  • alphafak: 1+2*(fractio of alphas in SW) to account for mass of alpha particles in solar wind. Set to 1.1 if no alphas measurements.
  • SW/IMF data: one file each for, and with the following suffix: bx,by,bz,vx,vy,vz,rr,pp. All in GSE coordinates. bx,by,bz is magnetic field in nT. vx,vy,vz is velocity in km/s. rr is number density in 1/cc. pp is plasma pressure in pPa (10**-12 Pa, pp=n*k*T=rr*k*T). Files are ascii. Each line contains: 'YYYY MM DD hh mm ss.ssss value'. No fill values or zeroes for missing values. Times need not be synchronized between plasma and field. Make sure data are clean (no spikes, if in doubt eliminate values). Files can contain more data (earlier/later times) than needed. These data will be processed into a proper input file, with interpolation to common time base and gap filling by linear interpolation. Possibly minimum variance to find SW sheet structure and orientation.
  • Ionosphere model: CTIM (preferred), parameterized conductance model, or fixed conductance (specify Hall/Pedersen conductance in S).
  • Anomalous resistivity model: none, constant eta, or nonlinear model. In the latter case we need to talk about run objective and make a choice.
  • A set of 2d planes x=const, y=const, z=const for output and their output cadence. Output cadence (in seconds real time) for 3d data dumps. Cadences can be low for most of the run and cranked up for the 'event'. We will usually prouce standar movies at the cut planes and for ionosphere parameters.
  • A file with satellite orbit data pulled from 'SSCWEB/Locator tabular' [| (SSCWEB)]. Select GSE X Y Z with YYYY/MM/DD and HH:MM:SS formatting and 8 significant digits (important for LEO orbits). Download ALL satellites in one file by ctrl-clicking multiple satellites. Save as and provide to us as "sscweb.txt". Time series from the included satellites will be produced during the run. It is also possible to extract timeseries later from 2d/3d/io files but that is much more tedious.