NLFFF extrapolations of AR10978 — boundary data

NLFFF extrapolations of AR10978 — boundary data Brief description The results from a study to discern the dependence on spatial resolution by the various nonlinear force-free field (NLFFF) extrapolation methods are described in DeRosa et al. (2015). This dataset contains the boundary data used to constrain the NLFFF extrapolations. The data and metadata are stored in the nonproprietary HDF5 format, for which bindings exist in C, C++, Fortran90, IDL, Java, MATLAB, Python, R, and many other languages. Filename convention The filenames below use the following convention: binXX_BC.h5 : boundary data for bin level XX Data and metadata contained in each file As described in the ApJ article, the data have been interpolated onto a uniform grid, and projected to a helioplanar coordinate system so that the data appear as if AR10978 were at disk center. For each bin level, the data file contains the following arrays: I_CONT: continuum image BXH: Bx component, fill-fraction included, in G BYH: By component, fill-fraction included, in G BZH: Bz component, fill-fraction included, in G JZ: normal component Jz of the current density, in mA/m2 ALPHA: force-free parameter α, equivalent to Jz/Bz, in Mm−1 ERR_BXH: uncertainty in Bx component, propagated from the inversion output and not including disambiguation uncertainties ERR_BYH: uncertainty in By component, propagated from the inversion output and not including disambiguation uncertainties ERR_BZH: uncertainty in Bz component, propagated from the inversion output and not including disambiguation uncertainties ERR_JZ: uncertainty in Jz, propagated from the inversion output and not including disambiguation uncertainties ERR_ALPHA: uncertainty in α, propagated from the inversion output and not including disambiguation uncertainties ERR_BXH_WD: uncertainty in Bx component, as above but also including a penalization effect if AMBIG_CONF is less than 0.9 ERR_BYH_WD: uncertainty in By component, as above but also including a penalization effect if AMBIG_CONF is less than 0.9 ERR_BZH_WD: uncertainty in Bz component, as above but also including a penalization effect if AMBIG_CONF is less than 0.9 ERR_JZ_WD: uncertainty in Jz, as above but also including a penalization effect if AMBIG_CONF is less than 0.9 ERR_ALPHA_WD: uncertainty in α, as above but also including a penalization effect if AMBIG_CONF is less than 0.9 AMBIG_CONF: confidence level in ambiguity resolution (ranges from 0.5 to 1.0) ORIG_LATITUDE: original latitude of each observed point ORIG_CMD: original longitude (central meridian distance) of each observed point LOC_XY: location, relative to disk center, in Mm of each point for x and y OKDATA: mask showing where edges that have no data reside (residual from interpolation to regularly spaced grid) Each file also contains a POINT substructure that contains information about the remapping. The most useful quantities are probably XY_SIZE (the pixel size of the remapped data in Mm) and RADIUS (the radius of the sun in arcseconds as viewed from the Hinode spacecraft). In the uncertainties having the _WD suffix, note that disambiguation uncertainties were propagated as follows: where 100 trials (100 random number seeds) of the disambiguation did not agree 90% of the time, those azimuth errors were set to 180°, possibly resulting in apparently large spikes in uncertainties (as compared with more reasonable neighboring pixels). Most of these are in weak-signal areas, but not all. However, in strong-signal areas, these uncertainty spikes occur where, e.g., there's a divergence-point and the single Btrans vector in the middle of it is undetermined (that is, it could just really go either way).