SIG x Set ’multiple of sigma’ continuum rejection parameter to x. DEG n Set polynomial degree for continuum fit to n (1..7). ITN n Set ’number of iterations’ continuum rejection parameter to n. LIMIT Line will be delimited by the cursor positions indicated. NOLIM Line delimited by points where data becomes < continuum. WIDTH x Set wavelength range displayed to x. CONT Determine continuum, starting with subsegment selection by cursor. RECONT Repeat continuum fit, using same segments as last time. FIT Analyse a line, delimiting it using the cursor. HELP (or ?) Output this information. QUIT Exit ABLINE.
Commands may be abbreviated. Omitted numeric parameters are prompted for.
Generally, the sequence is: 1) Select center wavelength, 2) CONTinuum, 3) FIT one or more lines. To change degree of continuum fit, use DEG followed by RECONT. Similarly for other continuum parameters.
More details should be available from the printed documentation.
This routine does interactive analysis of absorption lines in spectra.
The user designates a segment of the input spectrum to be analysed in each pass. First a continuum is fitted to this region, using only wavelength subsegments selected graphically by the user (i.e. ignoring the absorption line in question and any other nearby lines or spikes). In addition to this selection, iterative rejection of discrepant points is performed. The functional form of the continuum is a polynomial of degree specified by the user (0 - 7). Alternatively, if a precomputed continuum spectrum is available, it can be used instead.
The user specifies the wavelength limits of the interval containing the line itself: the median wavelength and equivalent width of the absorption line are calculated.
The routine finishes up each segment with a hard copy plot showing the data, continuum and wavelength limits of the line, with a printout of results.
Command line parameters -
SPECTRUM Name of the file containing the spectrum with lines to be fitted CONTIN File containing precomputed continuum, if one is to be used. SIG Multiple of sigma for continuum point rejection ITN Number of iterations for continuum point rejection DEG Degree of polynomial for continuum fit WIDTH Wavelength range to display at one time CONTOUT Output continuum file name, if one is written. If CONTOUT is the same as CONTIN, the new continuum overwrites the old. Otherwise, a new file, the same as SPECTRUM except for the data, is created. CMD The command in the main menu. LINENAME The name of a line to be fitted. COMMENT A comment for a hardcopy
Command keywords -
OLDCONT Set if a precomputed continuum is to be used. LIMIT LIMIT is set if the limits of a line are to be taken as the limits indicated with the cursor. Otherwise, the program will look for the points within the indicated limits where the data drops below the continuum. NEWCONT Set if the continuum constructed during the run is to be written to a file. HARDCOPY Yes if hardcopy of soft plot to be made.
User variables - (">" input, "<" output)
(>) SOFT (Character) Device/type for soft plots (>) HARD (Character) " " " hard " (<) TVXST (Numeric) ) (<) TVXEN (Numeric) ) Used to set the soft plot (<) TVHIGH (Numeric) ) parameters so that (<) TVLOW (Numeric) ) routines such as CCUR (<) XSTART (Numeric) ) know what the display (<) XEND (Numeric) ) limits for the currently (<) HIGH (Numeric) ) displayed plot have (<) LOW (Numeric) ) been set to. (<) TVFILE (Character)) (<) TVCOLOR (Numeric) ) JGR Jan 1985
In detail, ADJOIN is a little more complex, since it produces a spectrum in which the X data increase. This may involve the sorting of the various arrays, so ADJOIN can be regarded as a program that merges two spectra into increasing X order.
If neither spectrum has any X information (i.e. no wavelength array), the sort order will be first and then second. If one or both have X data, the resulting spectrum will be in order of X value.
Each invocation of ARC produces a file arlines.lis in the working directory. This file must be renamed or deleted before re-invoking ARC.
Fit - Repeat the fit. Disp - Display the deviation of the fit from a linear fit. This shows the trend of the fit, and the errors in each line. Order - Change the order of the fit. Edit - Delete or change the wavelength of one or more of the selected lines, without returning to the cursor selection. Reselect - Return to selection using the cursor. Print - Prints a copy of the fit (what ARLINES.LIS would look like if you were to exit now). Auto - Starting from your current fit and arc line list, ARC looks for additional line in the arc at wavelengths given in the line list and adds any it finds to the identified line tables. Xauto - Deletes all the lines found by ’Auto’. Modify - Allows you some control over the Autofit parameters. Quit - Start to exit ARC. Help - (or ?) Display this information.
The first letter of each command is sufficient.
It takes each pixel in turn. If that pixel is more than CHFACT times the current sigma value from any line already found, it uses that pixel as the starting point for a line search. If anything resembling a line can be found, it calculates its wavelength and looks in the line tables for a line close to that wavelength.
A line is accepted if the discrepancy between calculated and tabulated wavelength is less than SIGFACT times the current RMS value. This means that the criterion for accepting new lines is based on how their wavelength discrepancies compare with those for the lines that have already been accepted.
SIGFACT is the more important parameter.
It takes each pixel in turn. If that pixel is more than CHFACT times the current sigma value from any line already found, it uses that pixel as the starting point for a line search. If anything resembling a line can be found, it calculates its wavelength and looks in the line tables for a line close to that wavelength.
A line is accepted if the discrepancy between calculated and tabulated wavelength is less than SIGFACT times the current RMS value. This means that the criterion for accepting new lines is based on how their wavelength discrepancies compare with those for the lines that have already been accepted.
SIGFACT is the more important parameter.
arcdisp in order
This routine works in situ and modifies the input file.
arcgendb in fdb
arcident in out fdb wrange=?
arclocat in fwhm thresh
This routine works in situ and modifies the input file.
ascin in lines colaxes=? coldata=? [start=? step=? end=?] out=?
ascout in out
This routine is available in the Specdre graphical user interface.
bbody temp in=? xstart=? xstep=? xend=? xlabel=? xunit=? out=?
This routine calculates for a given (vacuum) wavelength or frequency axis the intensity of a black body at given temperature. The intensity is the energy per unit time, per unit area, per unit solid angle, and per unit frequency (and for all polarisations):
where c is the velocity of light, and h and k are the Planck and Boltzmann constants.
WARNING - you should examine the output from BCLEAN carefully to ensure that the parameters that you have chosen are appropriate. FIX=NO and TEXTFILE are useful here.
The data may be multi-dimensional; if it is, a multi-dimensional FFT is performed. Note that the Figaro routine R2CMPLX will turn an existing real data structure into a complex one acceptable to this routine. FFT does not perform any cosine belling or other tapering of the data, nor does it reduce it to a zero mean.
jm: Jo Murray (RAL, Starlink)
jms: ??? (AAO)
hme: Horst Meyerdierks (UoE, Starlink)
OUTPUT=SPECTRUM*(BSTAR**(SSECZ/BSECZ)**BETA))
where SSECZ and BSECZ are the air masses for the spectrum and the B star respectively. BETA should be 0.5 for saturated lines, 1.0 for unsaturated lines, and the generally accepted best compromise value for all lines (determined by P.J. Young) is 0.55.
M=C*(1+alpha*C)
where M and C are the measured and corrected intensities (after bias subtraction) respectively. John Barton’s memo gives a value of alpha=3.16E-6, and this is the reset value.
The approximate positions input are obtained from environment variables. These variables should be set up prior to running CENTERS, usually by using Figaro functions IGCUR or ICUR. Alternatively, you may enter the positions into a text file and use IMPOS to read this file and copy the values into the environment variables required by CENTERS.
The computed centroids are output to a new file called center.dat.
hme: Horst Meyerdierks (UoE, Starlink)
HME: Horst Meyerdierks (UoE, Starlink)
JFL: John Lightfoot (ROE)
correl inlist out logfil
This routine correlates two or three data sets. Either pair is subjected to a linear fit and the third data set is subjected to a two-parameter linear fit (i.e. regarded as a linear function of the first and second data sets). Each data set may be an NDF section. All must have the same dimensions.
This example NDF group specification consists of
HME: Horst Meyerdierks (UoE, Starlink)
HME: Horst Meyerdierks (UoE, Starlink)
The Y value for each point is the pixel value from IMAGE and the X value is the value of the corresponding value from IMAGE2.
The images must have identical dimensions.
Continue - go to the next order to be fitted interactively. Repeat - return to working on the order just completed. Start - back to square one. Quit - quit prematurely.
Fit - Repeat the fit. O_fit - Change the order of the fit. Disp - Display the deviation of the fit from a linear fit. This shows the trend of the fit, and the errors in each line. Edit - Delete or change the wavelength of one or more of the selected lines, without returning to the cursor selection. Reselect - Return to selection using the cursor. Continue - Start to quit this order. Print - Prints a copy of the fit (what ARLINES.LIS would look like if you were to exit now). Auto - Starting from your current fit and arc line list, ECHARC looks for additional line in the arc at wavelengths given in the line list and adds any it finds to the identified line tables. Xauto - Deletes all the lines found by ’Auto’. Modify - Allows you some control over the Autofit parameters. Help - (or ?) Display this information.
The first letter of each command is sufficient.
It takes each pixel in turn. If that pixel is more than CHFACT times the current sigma value from any line already found, it uses that pixel as the starting point for a line search. If anything resembling a line can be found, it calculates its wavelength and looks in the line tables for a line close to that wavelength.
A line is accepted if the discrepancy between calculated and tabulated wavelength is less than SIGFACT times the current RMS value. This means that the criterion for accepting new lines is based on how their wavelength discrepancies compare with those for the lines that have already been accepted.
SIGFACT is the more important parameter.
It takes each pixel in turn. If that pixel is more than CHFACT times the current sigma value from any line already found, it uses that pixel as the starting point for a line search. If anything resembling a line can be found, it calculates its wavelength and looks in the line tables for a line close to that wavelength.
A line is accepted if the discrepancy between calculated and tabulated wavelength is less than SIGFACT times the current RMS value. This means that the criterion for accepting new lines is based on how their wavelength discrepancies compare with those for the lines that have already been accepted.
SIGFACT is the more important parameter.
The coefficient file will normally have been written by SDIST and if so must have been written by the version of SDIST that was modified to support ECHMASK.
The PERISCOPE keyword (see below) determines whether each order has two separate parts (corresponding to object and sky and due to the special periscope that samples object and sky at a wide spacing and brings them together on the slit) or one part corresponding simply to the slit). The data values in the mask are 10 * (true order number) + (sub-order number) where the sub-order number is 0 if there is no periscope fitted, 1 if this is the first part of an order and 2 if this is the second part of the order. The "first" and "second" parts of an order are defined so that the actual data values in the mask are monotonic along a vertical slice through it, i.e. they might go 412, 411, 402, 401 if the periscope is fitted and they might go 410, 400 if it is not fitted.
If PERISCOPE is NO then the user has the option of splitting the data in an order into object and up to two separate regions of sky. The object is assigned sub-order 1 and the sky is assigned sub-order 2. Note that this assignment may differ from when PERISCOPE is yes, since in that case there is no guarantee that sub-order 1 is object - it may be sky! There may be room for enhancement here.
It creates a 1-D output file which consists of all the orders from the input files. Where orders overlap a weighted sum of the overlapping orders is used. The formula used is:
in1weight(i) * in1(i) + in2weight(i) * in2(i) in1weight(i) + in2weight(i)
and the weights are simply the result of median smoothing the data that they weight. This means that more weight is given to stronger signal data, that data where one of the inputs is zero is set to the other of the inputs and that data where both of the inputs are equal is left unaltered. All of these are desirable qualities. There may be less desirable statistical consequences and it is not obvious that signal to noise ratio cannot be degraded although intuitively it will not be since on the assumption of Poisson statistics the weights are essentially just the inverse variances. At low signal, a cutoff applies since the major noise contribution will no longer be Poisson.
The output file can be the same as either of the two input files and the second input file can be given a blank name, in which case it is not required. Often the first run will use a single input file to create the output file and subsequent runs will add in more input files to the existing output file.
editext request in
This routine allows the user to modify the Specdre Extension. See the topic "Requests" for details. Users should also consult the description of the Specdre Extension in SUN/140.
- LIST - CREATE - CREATE RESULTS type1 type2 type3 int1 int2 - DELETE - DELETE struct - SET ndf-struct - SET SPECVALS.comp value - SET COORD1.comp value - SET COORD2.comp value - SET scalar value - SET vector element value - TYPE scalar type - TYPE ndf-struct type - TYPE RESULTS type1 type2 type3 - SHAPE RESULTS int1 int2
This routine works in situ and modifies the input file.
There may or may not follow a second word specifying the structure affected. This can be any of the scalar structures in the Specdre Extension, i.e. SPECAXIS, RESTFRAME, INDEXREFR, FREQREF, FREQUNIT. It can also be any of the NDF-type structures in the Specdre Extension, i.e. SPECVALS, SPECWIDS, COVRS, RESULTS. Finally it can be any structure which is an extension to the (NDF-)structure RESULTS. These latter structures are all HDS vectors, their names are LINENAME, LABFREQ, COMPTYPE, NPARA, MASKL, MASKR, PARATYPE. The structure specification is case-insensitive.
Further words contain parameter values, usually one word per parameter. But if the last parameter is a string, it may consist of several words. No quotes are necessary.
There is only one LIST request, namely the sole word LIST. This will cause the complete Specdre Extension - except the contents of NDF arrays - to be listed to the log file or to the screen.
There are two possible CREATE requests.
- "CREATE" on its own will create an empty Specdre Extension, or fail if a Specdre Extension already exists.
- "CREATE RESULTS type1 type2 type3 int1 int2" needs five parameters. Three parameters are case-insensitive HDS data types. These are either _DOUBLE or assumed to be _REAL. The result structure is an NDF-type structure and the different type specifications apply to (i) the data and variance structures of the NDF, (ii) the laboratory frequency extension to the result NDF, (iii) the left and right mask extensions to the result NDF. All extensions to the result NDF are HDS vectors. Some of these have one element for each spectral component, their created length is specified by the fourth (last but one) request parameter, i.e. the sixth word. This word must convert to an integer greater than zero. Other HDS vectors in the extension to the result NDF have one element for each result parameter, their created length is specified by the fifth (last) request parameter, i.e. the seventh word. This word must convert to an integer greater than zero. "CREATE RESULTS" fails if the result NDF already exists.
"DELETE" on its own will delete the whole Specdre Extension. "DELETE struct" will delete the specified structure. This can be any of the NDF-type structures SPECVALS, SPECWIDS, COORD, COVRS, RESULTS. Deleting a structure does not include deleting the whole Extension, even if it becomes empty.
All SET request will create the Specdre Extension, even if the request is not recognised as a valid one.
"SET ndf-struct", where the second word specifies an NDF-type structure, will set the values of the specified structure to the default values. This does not work for COVRS, since it defaults to non-existence. The structure is created if it does not already exist. For SPECVALS and SPECWIDS only the NDF’s data structure is affected. For RESULTS the NDF’s data and variance structures are set to bad values, but all the vectors in the result NDF’s extension remain unchanged.
- "SET SPECVALS" will set the values in the data array of spectroscopic values to the default values. These are copies of the spectroscopic axis centres in the main NDF.
- "SET SPECWIDS" will set the values in the data array of spectroscopic widths to the default values. These are copies of the spectroscopic axis widths in the main NDF.
- "SET COORD" will set the values in the data array of COORD1 and COORD2 to the default values. These are copies axis centres for the first and second non-spectroscopic axes in the main NDF.
- "SET RESULTS" will set the values in the data and variance arrays of the result NDF to bad values.
"SET SPECVALS.comp value" can be used to set the label and unit components of the spectroscopic values’ NDF.
- "SET SPECVALS.LABEL label" will set the value of the label of the spectroscopic values’ NDF.
- "SET SPECVALS.UNITS unit" will set the value of the unit of the spectroscopic values’ NDF.
- "SET COORD1.LABEL label1" will set the value of the label of the COORD1 NDF. Similarly for COORD2.
- "SET COORD1.UNITS unit1" will set the value of the units of the COORD1 NDF. Similarly for COORD2.
"SET scalar value" will convert the third word to a value and put it in the scalar structure specified by the second word.
- "SET SPECAXIS int" will try to convert the third word into an integer. It must be between 1 and the number of axes in the NDF to which this Specdre Extension is an extension. If the value is actually changed, then this command will also delete the NDF-type structures SPECVALS, COVRS and RESULTS. This is because the contents of those structures depends on the choice of spectroscopic axis and become invalid when the value is changed. This command will also create the Specdre Extension and spectroscopic axis structure if they do not yet exist.
- "SET RESTFRAME more words" will put the third and following words (case-sensitive) into the reference frame structure. This command will also create the Specdre Extension and reference frame structure if they do not yet exist.
- "SET INDEXREFR value" will try to convert the third word into a real or double value, depending on the current type of the refractive index structure. This command will also create the Specdre Extension and refractive index structure if they do not yet exist.
- "SET FREQREF value" will try to convert the third word into a real or double value, depending on the current type of the reference frequency structure. This command will also create the Specdre Extension and reference frequency structure if they do not yet exist.
- "SET FREQUNIT int" will try to convert the third word into an integer. This command will also create the Specdre Extension and frequency unit structure if they do not yet exist.
"SET vector element value" will change the value of the specified element in the specified vector. The vector must be one of the extensions of the result NDF. The result NDF must exist beforehand, which implies the existence of the vector. The vector must also be long enough to contain the element specified and the element number must be integer and greater than zero. There are two kinds of vectors, those indexed by spectral component and those indexed by result parameter.
- "SET LINENAME comp more words" will put the forth and following words (case-sensitive) into the comp-th element of the line name structure.
- "SET LABFREQ comp value" will try to convert the fourth word into a real or double value, depending on the current type of the laboratory frequency structure. It will then put the value into the comp-th element of the laboratory frequency structure.
- "SET COMPTYPE comp more words" will put the forth and following words (case-sensitive) into the comp-th element of the component type structure.
- "SET NPARA comp npara" will try to convert the fourth word into an integer greater than or equal to zero. This is the new number of parameters allocated to the comp-th component. Changing this value will affect several parts of the result structure both in their shapes and values. If the comp-th spectral component is allocated more parameters than before, then it may be necessary to provide for a higher total number of parameters, which implies increasing the size of .MORE.SPECDRE.RESULTS.DATA_ARRAY and VARIANCE and of .MORE.SPECDRE.RESULTS.MORE.PARATYPE. At any rate, the information about spectral components with indices higher than comp must be relocated within those arrays.
- "SET MASKL comp value" and "SET MASKR comp value" will try to convert the fourth word into a real or double value, depending on the current type of the mask structures. It will then put the value into the comp-th element of the relevant mask structure.
- "SET PARATYPE para more words" will put the forth and following words (case-sensitive) into the para-th element of the parameter type structure.
A TYPE request can be applied to _REAL or _DOUBLE structures, and of these to scalars and NDF-type structures. Changing the type(s) of the result NDF needs specification of three separate types.
- "TYPE scalar type" can be applied to INDEXREFR and FREQREF. The type specification is case-insensitive. If it is not _DOUBLE, then _REAL is assumed.
- "TYPE ndf-struct type", will change the type of the specified NDF. The type specification is case-insensitive. It must be _DOUBLE or is assumed to be _REAL. This command can be applied to SPECVALS, SPECWIDS, COORD, and COVRS. SPECVALS, SPECWIDS, COORD1 and COORD2 will be created if necessary, COVRS will not be created.
- "TYPE RESULTS type1 type2 type3" will change the types of (i) the NDF’s data and variance, (ii) the NDF’s laboratory frequency extension, (iii) the NDF’s mask extensions. the parameters are case-insensitive. They must be _DOUBLE or are assumed to be _REAL. This command includes creation of the result structure if necessary.
"SHAPE RESULTS int1 int2" will change the shape of the result structure. The two command parameters must convert to integers greater than zero. The first is the number of spectral components to be provided for, the second is the total number of parameters. If the result structure does not exist, then it is created. If it exists, then existing values are retained unless they were stored outside the new bounds.
evalfit in out comp=?
% hdstrace datafile full
The data may be multi-dimensional; if it is, a multi-dimensional FFT is performed. Note that the Figaro routine R2CMPLX will turn an existing real data structure into a complex one acceptable to this routine. FFT does not perform any cosine belling or other tapering of the data, nor does it reduce it to a zero mean.
jm: Jo Murray (RAL, Starlink)
jms: ??? (AAO)
hme: Horst Meyerdierks (UoE, Starlink)
- A blank response gets you one level up in the topic hierarchy.
- A question mark (?) re-displays the current topic.
- An end-of-file character exits fighelp. Note that this is Ctrl-z under VMS but usually Ctrl-d under Unix.
- Any normal text specifies (sub-) topics to look for.
- Each blank-separated word stands for one topic in the hierarchy. E.g. three blank-separated words go down three levels in the hierarchy.
- Each underscore-separated word stands for an underscore-separated word in a single topic
- Words (whether separated by blanks or underscores) that are not unique topics or include wild card characters are expanded and help is given on all matching topics. Wild card characters are % for a single character and * for any number of characters including none. In the word expansion A_G_N would match active_galactic_nuclei, which is one topic. The same is true for A*_G*_N* or active or active*.
When the help text to be printed is longer than the terminal page, then the user is asked to press the Return key before proceeding with output. At this point, too, can an end-of-file character be given to exit fighelp immediately.
fillcube in out
This routine works in situ on an existing output file.
Spectroscopic values must not exist in the Extension of either the input or the output NDF: A unique coordinate axis is required for all axes, including the spectroscopic one, in order to locate the target pixels by matching coordinates between input and output. If this is inconvenient, GROW may be a more suitable application for your purpose.
Spectroscopic widths must not exist in the Extension of the output NDF and are ignored in the input NDF: This information is likely to be present only when spectroscopic values are present as well.
Covariance row sums must not exist in the Extension of the output NDF: The validity of this information is difficult to assess when only parts of spectra might be copied from one cube to another, and when these parts are contiguous in the input but might not be in the output. Input covariance row sums are ignored.
The results in the input Extension are ignored, and results must not exist in the output Extension.
The technique of this routine is to
1 Compress the data array, 2 Follow ridges from start positions by centroiding, 3 Fit a polynomial Y(X) to the centroids, 4 Write the polynomial coefficients to a text file.
The text file can be read by the applications OVERPF and POLEXT. Those applications will also be able to read text files in version 1 format.
hme: Horst Meyerdierks (UoE, Starlink)
fitbb in device=? mask1=? mask2=? ncomp=? theta=? alpha=? lgtemp=? sf=? af=? tf=? comp=? logfil=?
mask = [MASK1(1);MASK2(1)] U [MASK1(2);MASK1(2)] U ... U [MASK1(MSKUSE);MASK2(MSKUSE)].
The elements of the MASK parameters are not checked for monotony. Thus intervals may be empty or overlapping. The number of intervals to be used is derived from the number of lower/upper bounds entered. Either MASK1 or MASK2 should be entered with not more numbers than mask intervals required.
This routine works in situ and modifies the input file.
Meyerdierks, H., 1992b, Fitting resampled spectra, in P.J. Grosbol, R.C.E. de Ruijsscher (eds), 4th ESO/ST-ECF Data Analysis Workshop, Garching, 13 - 14 May 1992, ESO Conference and Workshop Proceedings No. 41, Garching bei Muenchen, 1992
fitgauss in device=? mask1=? mask2=? ncomp=? cont=? centre=? peak=? fwhm=? cf=? pf=? wf=? comp=? logfil=?
mask = [MASK1(1);MASK2(1)] U [MASK1(2);MASK1(2)] U ... U [MASK1(MSKUSE);MASK2(MSKUSE)].
The elements of the MASK parameters are not checked for monotony. Thus intervals may be empty or overlapping. The number of intervals to be used is derived from the number of lower/upper bounds entered. Either MASK1 or MASK2 should be entered with not more numbers than mask intervals required.
This routine works in situ and modifies the input file.
Meyerdierks, H., 1992b, Fitting resampled spectra, in P.J. Grosbol, R.C.E. de Ruijsscher (eds), 4th ESO/ST-ECF Data Analysis Workshop, Garching, 13 - 14 May 1992, ESO Conference and Workshop Proceedings No. 41, Garching bei Muenchen, 1992
fitpoly in device=? mask1=? mask2=? order=? comp=? logfil=?
This routine fits a polynomial to a one-dimensional data set. This can be specified as an NDF section. The data set must extend along the spectroscopic axis.
mask = [MASK1(1);MASK2(1)] U [MASK1(2);MASK1(2)] U ... U [MASK1(MSKUSE);MASK2(MSKUSE)].
The elements of the MASK parameters are not checked for monotony. Thus intervals may be empty or overlapping. The number of intervals to be used is derived from the number of lower/upper bounds entered. Either MASK1 or MASK2 should be entered with not more numbers than mask intervals required.
This routine works in situ and modifies the input file.
fittri in device=? mask1=? mask2=? ncomp=? cont=? centre=? peak=? fwhm=? cf=? pf=? wf=? comp=? logfil=?
This routine fits up to six triangular profiles at a time to a one-dimensional data set. This can be specified as an NDF section. The data set must extend along the spectroscopic axis.
mask = [MASK1(1);MASK2(1)] U [MASK1(2);MASK1(2)] U ... U [MASK1(MSKUSE);MASK2(MSKUSE)].
The elements of the MASK parameters are not checked for monotony. Thus intervals may be empty or overlapping. The number of intervals to be used is derived from the number of lower/upper bounds entered. Either MASK1 or MASK2 should be entered with not more numbers than mask intervals required.
This routine works in situ and modifies the input file.
Meyerdierks, H., 1992b, Fitting resampled spectra, in P.J. Grosbol, R.C.E. de Ruijsscher (eds), 4th ESO/ST-ECF Data Analysis Workshop, Garching, 13 - 14 May 1992, ESO Conference and Workshop Proceedings No. 41, Garching bei Muenchen, 1992
This assumes stability (x positions of the fibres do not move), and vertical orientation of the fibres. These are satisfied by FLAIR (Parker, private communication).
This assumes stability (x positions of the fibres do not move), and vertical orientation of the fibres. These are satisfied by FLAIR (Parker, private communication).