* DATA REQUESTS
1. Why do I get 2 IUESIPS MELO files for some low dispersion images but only 1 NEWSIPS MXLO file?
2. Can I request IUE data in ASCII format?
3. Why are some IUE NEWSIPS data not available? The IUESIPS version is available from the archive.
* READING FILES
4. How do I read NEWSIPS files into IRAF?
5. How do I read NEWSIPS files into IDL?
7. Can I use SAOimage to look at NEWSIPS files?
* NEWSIPS PROCESSING
8. What is the wavelength scale used for NEWSIPS? Is it heliocentric?
10. Why are there differences in IUESIPS and NEWSIPS wavelengths?
* ASCII LOGS
12. Are there ASCII files of the IUE Merged log?
* DATA ANALYSIS
13. When analyzing data, which of the data quality flags
should I use to throw out pixels?
15. Whew! Is there a simpler way of estimating noise?
16. Why do I see emission lines in NEWSIPS LO data that
seem too low?
1. Why do I get 2 IUESIPS MELO files for some low dispersion
images but only 1 NEWSIPS MXLO file?
2. Can I request IUE data in ASCII format?
3. Why are some IUE NEWSIPS data not available?
The IUESIPS version is available from the archive.
4. How do I read NEWSIPS files into IRAF?
5. How do I read NEWSIPS files into IDL?
6. Why are my RDAF-format IUESIPS files unreadable after I
transferred them from NDADS to my unix workstation?
7. Can I use SAOimage to look at NEWSIPS files?
8. What is the wavelength scale used for NEWSIPS? Is it
heliocentric?
9. I have a NEWSIPS image which may not have been
processed correctly (wrong dispersion, wrong exposure time). How can I
get a correct version?
10. The wavelengths for the Mg II h and k lines are very
different, by almost an Ångstrom, between my IUESIPS and NEWSIPS
high-dispersion data. Is this an error?
11. The wavelengths for my high-resolution NEWSIPS spectra
seem to be off by almost an Ånsgtrom. What happened?
12. Are there ASCII files containing the IUE Merged Log?
13. When analyzing data, which of the data quality flags
should I use to throw out pixels?
Users should also be aware that no attempt was made in NEWSIPS to eliminate
cosmic rays from the high-dispersion images, and the attempts made for low
dispersion probably err on the conservative side. The reason for this was a
concern that a provision for cosmic rays would lead NEWSIPS inadvertently
to remove actual emission lines. Users should especially be cautious about
the influence of oblique, diffuse cosmic rays, which can subtlely affect the
background surface by 150 pixels or more from the centroid of the "hit"
region and be responsible for less than optimal fits to the background surface.
We suggest that the SIHI or SILO images be first visually screened
before the extracted spectra are analyzed.
14. When coadding like spectra, should I weight the constituent
spectra by exposure time or the square root of exposure time?
For the coaddition of data, we recommend weighting individual spectra by
reciprocal of the means of their noise fluctuations. (But in computing such
a mean consider only those pixels with zero-value quality flags!) The
"sigma" vector is computed by NEWSIPS as an estimate of these fluctuations
as a by-product of the flux extraction process. For the extracted MXHI data
the estimate for each wavelength pixel is based on predicted fluctuations of
extraction slit pixels from the noise model
for the same region of the camera. The units of the sigma vector in high
dispersion are in "FNs" (Flux Numbers), the same as the net flux
vector. For MXLO data the sigma vector is derived from the noise model, but
it depends also upon the relative illuminations of pixels along the extraction
slit. In this case the result is also scaled to units of absolute flux.
15. Whew! Is there a simpler way of estimating noise?
Since "clean" continuum is not always easy to find, let's consider an
empirical procedure which works well even for a spectrum containing features.
As long as the flux errors are primarily gaussian- distributed, we can make
use of the fact that randomly drawn samples will differ from one another,
on average, by exactly one standard deviation. In the computing language IDL,
an estimate of the rms may be computed conveniently by a few steps.
Defining "f" as a spectral flux array
taken from pixels near the blaze maximum (so the noise will be approximately
uniform along the spectrum) and containing only zero-valued quality flags, we
compute the mean point to point fluctuation of two pixels separated by a short
distance n:
The distribution of noise fluctuations among
these pixels can be obtained from the computation:
rmsdist = abs( f - shift( f , n) ) .
The median of this distribution is computed by sorting the distribution
rmsdist and finding the middle element of the sorted rmsdist
array, which by definition is half the number of elements in the distribution.
Thus:
ntot = n_elements(rmsdist), so
ntot2 ,
= ntot/2 ,
Now we compute the sorted index distribution and take the value of
rmsdist we need:
isort = sort(rmsdist) ,
medrms = rmsdist( isort(ntot2) ) .
medrms is the our noise estimate using the median average.
The mean of the distribution can likewise easily be determined from:
meanrms = total( rmsdist )/ntot .
This value will be biased on the high side if there are outlying fluctuations
in the spectrum.
In practice the pixel separation distance n should be at least a spectral resolution
element (3 or more).
16. Why do I see emission lines in NEWSIPS LO data that
seem to be low