iraf.net

Firstly, thanks to Ivan for helping me! I have been trying to use the FXCOR package in IRAF to compute RV for an unknown object. With no tutorial I am not sure how to compute it. This is what I have done so far. Target A: unknown RV
Target B: known RV = also called the template I do the following: cl> fxcor
List of object spectra: Target A
List of Template Spectra: Target B Now I have a green window with split display. One showing the region chosen while the other is some Gaussian fitting. Next I type in the following:
:tempvel 30 (This sets the template velocity to 30 km/s)Next I hit "s" this takes me to spectrum mode where i see the unknown target and template spectrum.I use "b" to choose the areas of interest. Hit "q" to go back to the previous view. Here it says, "Pixel Correlation - No velocities will be computed"what do I do next to obtain radial velocity? Please help!

I'd have to see the image headers to be sure, but my guess is that one or both of your spectra are missing dispersion keywords. If there is no dispersion information at all a pixel-correlation is done so you can get a relative shift, if things like the RA/Dec or observatory are missing but you have a dispersion you can calculate a relative RV, but all of the keywords described in the help page are required for a heliocentric correction. You can use the SLIST task in the ONEDSPEC package to see whether the system recognizes your dispersion keywords, otherwise please post a header.Cheers,
-Mike

Thanks Fitz. I have also sent you the files by email as well. Sorry for such a long post!Because of the length I am only posting information about the template object. The unknown object would be similar. Here is the info from the raw file: jun25s0123.fits[1024,1024][int]: VB10
No bad pixels, min=0., max=0. (old)
Line storage mode, physdim [1024,1024], length of user area 4860 s.u.
Created Tue 14:07:50 02-Oct-2007, Last modified Mon 10:30:42 25-Jun-2007
Pixel file "jun25s0123.fits" [ok]
BSCALE = 1.00000 / Scaling factor
BZERO = 0.00000 / Scaling zero-point
TELESCOP= 'Keck II ' / Telescope
OBSERVER= 'xxxxxxxxxxxxxx' / Observer
OBJECT = ' VB10 ' / Object name
COMMENT = 'Obs # 1, Exp' / Comment
ROOTNAME= 'jun25s ' / File Root Name
FILENUM = 123 / Frame Number
FILENAME= 'jun25s0123.fits ' / Name of file
OUTDIR = '/sdata601/nirspec/2007jun25/spec/ ' / Data Directory
SCRIPTNA= 's25Jun0042.csh ' / Name of current script
FILNAME = 'NIRSPEC-3 ' / Filter Name
SLITNAME= '0.432x12 ' / Slit Name
SLITPA = 3.250 / Slit position angle
SLITX = 134.500 / X pixel of the center of the slit
SLITY = 125.500 / Y pixel of the center of the slit
SLITANG = 15.100 / Slit angle in the scam. CCW from hor.
SCAMPA = 78.150 / Scam position angle
ITIME = 120.000 / Integration time per coadd
COADDS = 1 / Number of coadds
SAMPMODE= 3 / 1=Single; 2=CDS; 3=MCDS
DETBIAS = 450 / Detector bias setting (0-4096)
MULTISPE= 16 / Number of multiple reads
SAMPRATE= 250 / Spec sampling rate in KHz
Q1OFFSET= 3240 / Aladdin Quadrant 1 preamp offset
Q2OFFSET= 3240 / Aladdin Quadrant 2 preamp offset
Q3OFFSET= 3240 / Aladdin Quadrant 3 preamp offset
Q4OFFSET= 3240 / Aladdin Quadrant 4 preamp offset
GAIN.SPE= 4 / Preamp gain setting 1-4
FREQ.SPE= 4 / Preamp filtering frequency setting 1-4
CRYOTEMP= 29.830 / Aladdin cold head temperature
FIL1POS = 11 / Filter 1 Position
FIL2POS = 14 / Filter 2 Position
SLITPOS = 2 / Slit Position
ECHLPOS = 63.000 / Echelle position
DISPPOS = 34.080 / Cross Disperser position
IROTLOC = 60291 / Step position of Image rotator
CALMPOS = 0 / Cal. Mirror Position, 0=out, 1=in
CALCPOS = 0 / Cal. Cover Position, 0=out, 1=in
CALPPOS = 0 / Cal. Pinhole Position, 0=out, 1=in
NEON = 0 / Neon lamp: 1=on, 0=off
ARGON = 0 / Argon lamp: 1=on, 0=off
KRYPTON = 0 / Krypton lamp: 1=on, 0=off
XENON = 0 / Xenon lamp: 1=on, 0=off
ETALON = 0 / Etalon lamp: 1=on, 0=off
FLAT = 0 / Flat lamp: 1=on, 0=off
UTC = '13:24:27.78 ' / coordinated universal time (h)
AIRMASS = 1.18242 / air mass (1.18)
AXESTAT = 'tracking ' / axes control status
AZ = -113.03175 / telescope azimuth (-113.03 deg
CALOCAL = 0.00767 / collimation azimuth local (27.
CELOCAL = -0.00986 / collimation elevation local (-
CURRINST= 'NIRSPEC ' / current instrument
DATE-OBS= '2007-06-25 ' / universal date of observation
DCSSTAT = 'standby ' / drive and control status
DCSVERS = '6-1-5 ' / drive and control version
DEC = 5.14856 / telescope declination (+05:08:
DOMEPOSN= 246.96000 / dome azimuth (246.96 deg)
DOMESTAT= 'tracking ' / dome status
EL = 57.71662 / telescope elevation (57.72 deg
EQUINOX = 2000.00000 / telescope equinox (2000.0)
FOCALSTN= 'rnas (right nasmyt' / focal station
HA = 29.61252 / telescope hour angle (+01:58:2
LST = '21:15:47.99 ' / local apparent sidereal time (
MJD-OBS = 54276.55865 / modified julian date of observ
PARANG = 60.42430 / parallactic angle astrometric
PARANTEL= 60.40758 / parallactic angle telescope (6
PONAME = 'REF ' / pointing origin name
POXOFF = 0.00000 / pointing origin x offset (0.00)
POYOFF = 0.00000 / pointing origin y offset (0.00
POXPOS = 0.00066 / pointing origin xposition (0.6
POYPOS = 0.00121 / pointing origin yposition (1.2
PONAME1 = 'REF ' / pointing origin name 1
POXPOS1 = 0.00066 / pointing origin xposition 1 (0
POYPOS1 = 0.00121 / pointing origin yposition 1 (1
PONAME2 = 'SLIT ' / pointing origin name 2
POXPOS2 = 0.00187 / pointing origin xposition 2 (1
POYPOS2 = 0.00006 / pointing origin yposition 2 (0
PONAME3 = 'REFA ' / pointing origin name 3
POXPOS3 = -0.00406 / pointing origin xposition 3 (-
POYPOS3 = 0.05239 / pointing origin yposition 3 (5
PONAME4 = 'DREF ' / pointing origin name 4
POXPOS4 = 0.00039 / pointing origin xposition 4 (0
POYPOS4 = -0.00090 / pointing origin yposition 4 (-
PONAME5 = 'DREFA ' / pointing origin name 5
POXPOS5 = -0.00057 / pointing origin xposition 5 (-
POYPOS5 = -0.05447 / pointing origin yposition 5 (-
PONAME6 = 'HNOD1 ' / pointing origin name 6
POXPOS6 = 0.00342 / pointing origin xposition 6 (3
POYPOS6 = 0.00057 / pointing origin yposition 6 (0
PONAME7 = 'HNOD2 ' / pointing origin name 7
POXPOS7 = -0.00318 / pointing origin xposition 7 (-
POYPOS7 = -0.00113 / pointing origin yposition 7 (-
PONAME8 = 'LNOD1 ' / pointing origin name 8
POXPOS8 = -0.00005 / pointing origin xposition 8 (-
POYPOS8 = 0.00536 / pointing origin yposition 8 (5
PONAME9 = 'LNOD2 ' / pointing origin name 9
RA = 289.23846 / telescope right ascension (19:
ROTCALAN= 0.00000 / rotator calibration angle (0.0
ROTMODE = 'position angle ' / rotator tracking mode
ROTPPOSN= -39.92635 / rotator physical position (-39
ROTPOSN = 78.19847 / rotator user position (78.20 d
ROTREFAN= 0.00000 / rotator reference angle (0.00
SECFOCUS= 0.00066 / secondary mirror focus raw (0.
SECTHETX= -0.00030 / secondary mirror thetax (-62.0
SECTHETY= -0.00104 / secondary mirror thetay (-215.
TARGDEC = 5.15028 / target declination (+05:09:01.
TARGEPOC= 2000.00000 / target epoch (2000.000000)
TARGEQUI= 2000.00000 / target equinox (2000.000000)
TARGFRAM= 'FK5 ' / target frame
TARGNAME= 'vB10 ' / target name
TARGPLAX= 0.00000 / target parallax (0.0 arcsec)
TARGPMDC= 0.00000 / target proper motion dec (0.00
TARGPMRA= 0.00000 / target proper motion ra (0.000
TARGRA = 289.24292 / target right ascension (19:16:
TARGRADV= 0.00000 / target radial velocity (0.0000
TELESCOP= 'Keck II ' / telescope name
TELFOCUS= 0.00137 / telescope focus compensated (1
TUBETEMP= 3.26569 / tube temperature (3.27 degC)
UTC = '13:24:27.78 ' / coordinated universal time (h)Below is the information from the processed file. I used REDSPEC package in IDL to process the file. The output file is vB1061.fits. ***something more but I cannot see in my xgterm window**** 939 939 0 -1 1. 1. 1024 VB10
940 940 0 -1 1. 1. 1024 VB10
941 941 0 -1 1. 1. 1024 VB10
942 942 0 -1 1. 1. 1024 VB10
943 943 0 -1 1. 1. 1024 VB10
944 944 0 -1 1. 1. 1024 VB10
945 945 0 -1 1. 1. 1024 VB10
946 946 0 -1 1. 1. 1024 VB10
947 947 0 -1 1. 1. 1024 VB10
948 948 0 -1 1. 1. 1024 VB10
949 949 0 -1 1. 1. 1024 VB10
950 950 0 -1 1. 1. 1024 VB10
951 951 0 -1 1. 1. 1024 VB10
jun25s0123.fits[1024,1024][int]: VB10
No bad pixels, min=0., max=0. (old)
Line storage mode, physdim [1024,1024], length of user area 4860 s.u.
Created Tue 14:07:50 02-Oct-2007, Last modified Mon 10:30:42 25-Jun-2007
Pixel file "jun25s0123.fits" [ok]
BSCALE = 1.00000 / Scaling factor
BZERO = 0.00000 / Scaling zero-point
TELESCOP= 'Keck II ' / Telescope
OBSERVER= 'Greene Zapatero Os' / Observer
OBJECT = ' VB10 ' / Object name
COMMENT = 'Obs # 1, Exp' / Comment
ROOTNAME= 'jun25s ' / File Root Name
FILENUM = 123 / Frame Number
FILENAME= 'jun25s0123.fits ' / Name of file
OUTDIR = '/sdata601/nirspec/2007jun25/spec/ ' / Data Directory
SCRIPTNA= 's25Jun0042.csh ' / Name of current script
FILNAME = 'NIRSPEC-3 ' / Filter Name
SLITNAME= '0.432x12 ' / Slit Name
SLITPA = 3.250 / Slit position angle
SLITX = 134.500 / X pixel of the center of the slit
SLITY = 125.500 / Y pixel of the center of the slit
SLITANG = 15.100 / Slit angle in the scam. CCW from hor.
SCAMPA = 78.150 / Scam position angle
ITIME = 120.000 / Integration time per coadd
COADDS = 1 / Number of coadds
vb1061.fits[1024,90][real]:
No bad pixels, min=0., max=0. (old)
Line storage mode, physdim [1024,90], length of user area 162 s.u.
Created Mon 11:25:03 01-Oct-2007, Last modified Sat 16:23:19 29-Sep-2007
Pixel file "vb1061.fits" [ok]
EXTEND = T / FITS data may contain extensions
DATE = '2007-09-29' / Creation UTC (CCCC-MM-DD) date of FITS heade
COMMENT FITS (Flexible Image Transport System) format is defined in 'Astronom
COMMENT and Astrophysics', volume 376, page 359; bibcode 2001A&A...376..359H
%%% Now if I do the "SLIST" task I have these columns...%%%%jun25s0123.fits 953 953 0 -1 1. 1. 1024 VB10
jun25s0123.fits 954 954 0 -1 1. 1. 1024 VB10
jun25s0123.fits 955 955 0 -1 1. 1. 1024 VB10
jun25s0123.fits 956 956 0 -1 1. 1. 1024 VB10
jun25s0123.fits 957 957 0 -1 1. 1. 1024 VB10
jun25s0123.fits 958 958 0 -1 1. 1. 1024 VB10
jun25s0123.fits 959 959 0 -1 1. 1. 1024 VB10
jun25s0123.fits 960 960 0 -1 1. 1. 1024 VB10
jun25s0123.fits 961 961 0 -1 1. 1. 1024 VB10
jun25s0123.fits 962 962 0 -1 1. 1. 1024 VB10
jun25s0123.fits 963 963 0 -1 1. 1. 1024 VB10
jun25s0123.fits 964 964 0 -1 1. 1. 1024 VB10
jun25s0123.fits 965 965 0 -1 1. 1. 1024 VB10
jun25s0123.fits 966 966 0 -1 1. 1. 1024 VB10
jun25s0123.fits 967 967 0 -1 1. 1. 1024 VB10
jun25s0123.fits 968 968 0 -1 1. 1. 1024 VB10
jun25s0123.fits 969 969 0 -1 1. 1. 1024 VB10
jun25s0123.fits 970 970 0 -1 1. 1. 1024 VB10
jun25s0123.fits 971 971 0 -1 1. 1. 1024 VB10
jun25s0123.fits 972 972 0 -1 1. 1. 1024 VB10
jun25s0123.fits 973 973 0 -1 1. 1. 1024 VB10
jun25s0123.fits 974 974 0 -1 1. 1. 1024 VB10
jun25s0123.fits 975 975 0 -1 1. 1. 1024 VB10
jun25s0123.fits 976 976 0 -1 1. 1. 1024 VB10
jun25s0123.fits 977 977 0 -1 1. 1. 1024 VB10
jun25s0123.fits 978 978 0 -1 1. 1. 1024 VB10
jun25s0123.fits 979 979 0 -1 1. 1. 1024 VB10
jun25s0123.fits 980 980 0 -1 1. 1. 1024 VB10
jun25s0123.fits 981 981 0 -1 1. 1. 1024 VB10
jun25s0123.fits 982 982 0 -1 1. 1. 1024 VB10
jun25s0123.fits 983 983 0 -1 1. 1. 1024 VB10
jun25s0123.fits 984 984 0 -1 1. 1. 1024 VB10
jun25s0123.fits 985 985 0 -1 1. 1. 1024 VB10
jun25s0123.fits 986 986 0 -1 1. 1. 1024 VB10
jun25s0123.fits 987 987 0 -1 1. 1. 1024 VB10
jun25s0123.fits 988 988 0 -1 1. 1. 1024 VB10
jun25s0123.fits 989 989 0 -1 1. 1. 1024 VB10
jun25s0123.fits 990 990 0 -1 1. 1. 1024 VB10
jun25s0123.fits 991 991 0 -1 1. 1. 1024 VB10
jun25s0123.fits 992 992 0 -1 1. 1. 1024 VB10
jun25s0123.fits 993 993 0 -1 1. 1. 1024 VB10
jun25s0123.fits 994 994 0 -1 1. 1. 1024 VB10
jun25s0123.fits 995 995 0 -1 1. 1. 1024 VB10
jun25s0123.fits 996 996 0 -1 1. 1. 1024 VB10
jun25s0123.fits 997 997 0 -1 1. 1. 1024 VB10
jun25s0123.fits 998 998 0 -1 1. 1. 1024 VB10
jun25s0123.fits 999 999 0 -1 1. 1. 1024 VB10
jun25s0123.fits 1000 1000 0 -1 1. 1. 1024 VB10
jun25s0123.fits 1001 1001 0 -1 1. 1. 1024 VB10
jun25s0123.fits 1002 1002 0 -1 1. 1. 1024 VB10
jun25s0123.fits 1003 1003 0 -1 1. 1. 1024 VB10
jun25s0123.fits 1004 1004 0 -1 1. 1. 1024 VB10
jun25s0123.fits 1005 1005 0 -1 1. 1. 1024 VB10
jun25s0123.fits 1006 1006 0 -1 1. 1. 1024 VB10
jun25s0123.fits 1007 1007 0 -1 1. 1. 1024 VB10
jun25s0123.fits 1008 1008 0 -1 1. 1. 1024 VB10
jun25s0123.fits 1009 1009 0 -1 1. 1. 1024 VB10
jun25s0123.fits 1010 1010 0 -1 1. 1. 1024 VB10
jun25s0123.fits 1011 1011 0 -1 1. 1. 1024 VB10
jun25s0123.fits 1012 1012 0 -1 1. 1. 1024 VB10
jun25s0123.fits 1013 1013 0 -1 1. 1. 1024 VB10
jun25s0123.fits 1014 1014 0 -1 1. 1. 1024 VB10
jun25s0123.fits 1015 1015 0 -1 1. 1. 1024 VB10
jun25s0123.fits 1016 1016 0 -1 1. 1. 1024 VB10
jun25s0123.fits 1017 1017 0 -1 1. 1. 1024 VB10
jun25s0123.fits 1018 1018 0 -1 1. 1. 1024 VB10
jun25s0123.fits 1019 1019 0 -1 1. 1. 1024 VB10
jun25s0123.fits 1020 1020 0 -1 1. 1. 1024 VB10
jun25s0123.fits 1021 1021 0 -1 1. 1. 1024 VB10
jun25s0123.fits 1022 1022 0 -1 1. 1. 1024 VB10
jun25s0123.fits 1023 1023 0 -1 1. 1. 1024 VB10
jun25s0123.fits 1024 1024 0 -1 1. 1. 1024 VB10
$$$$$$$$$THE same thing when I do SLIST on vB1061.fits $$$$$$$$$$vb1061.fits 15 15 0 -1 1. 1. 1024
vb1061.fits 16 16 0 -1 1. 1. 1024
vb1061.fits 17 17 0 -1 1. 1. 1024
vb1061.fits 18 18 0 -1 1. 1. 1024
vb1061.fits 19 19 0 -1 1. 1. 1024
vb1061.fits 20 20 0 -1 1. 1. 1024
vb1061.fits 21 21 0 -1 1. 1. 1024
vb1061.fits 22 22 0 -1 1. 1. 1024
vb1061.fits 23 23 0 -1 1. 1. 1024
vb1061.fits 24 24 0 -1 1. 1. 1024
vb1061.fits 25 25 0 -1 1. 1. 1024
vb1061.fits 26 26 0 -1 1. 1. 1024
vb1061.fits 27 27 0 -1 1. 1. 1024
vb1061.fits 28 28 0 -1 1. 1. 1024
vb1061.fits 29 29 0 -1 1. 1. 1024
vb1061.fits 30 30 0 -1 1. 1. 1024
vb1061.fits 31 31 0 -1 1. 1. 1024
vb1061.fits 32 32 0 -1 1. 1. 1024
vb1061.fits 33 33 0 -1 1. 1. 1024
vb1061.fits 34 34 0 -1 1. 1. 1024
vb1061.fits 35 35 0 -1 1. 1. 1024
vb1061.fits 36 36 0 -1 1. 1. 1024
vb1061.fits 37 37 0 -1 1. 1. 1024
vb1061.fits 38 38 0 -1 1. 1. 1024
vb1061.fits 39 39 0 -1 1. 1. 1024
vb1061.fits 40 40 0 -1 1. 1. 1024
vb1061.fits 41 41 0 -1 1. 1. 1024
vb1061.fits 42 42 0 -1 1. 1. 1024
vb1061.fits 43 43 0 -1 1. 1. 1024
vb1061.fits 44 44 0 -1 1. 1. 1024
vb1061.fits 45 45 0 -1 1. 1. 1024
vb1061.fits 46 46 0 -1 1. 1. 1024
vb1061.fits 47 47 0 -1 1. 1. 1024
vb1061.fits 48 48 0 -1 1. 1. 1024
vb1061.fits 49 49 0 -1 1. 1. 1024
vb1061.fits 50 50 0 -1 1. 1. 1024
vb1061.fits 51 51 0 -1 1. 1. 1024
vb1061.fits 52 52 0 -1 1. 1. 1024
vb1061.fits 53 53 0 -1 1. 1. 1024
vb1061.fits 54 54 0 -1 1. 1. 1024
vb1061.fits 55 55 0 -1 1. 1. 1024
vb1061.fits 56 56 0 -1 1. 1. 1024
vb1061.fits 57 57 0 -1 1. 1. 1024
vb1061.fits 58 58 0 -1 1. 1. 1024
vb1061.fits 59 59 0 -1 1. 1. 1024
vb1061.fits 60 60 0 -1 1. 1. 1024
vb1061.fits 61 61 0 -1 1. 1. 1024
vb1061.fits 62 62 0 -1 1. 1. 1024
vb1061.fits 63 63 0 -1 1. 1. 1024
vb1061.fits 64 64 0 -1 1. 1. 1024
vb1061.fits 65 65 0 -1 1. 1. 1024
vb1061.fits 66 66 0 -1 1. 1. 1024
vb1061.fits 67 67 0 -1 1. 1. 1024
vb1061.fits 68 68 0 -1 1. 1. 1024
vb1061.fits 69 69 0 -1 1. 1. 1024
vb1061.fits 70 70 0 -1 1. 1. 1024
vb1061.fits 71 71 0 -1 1. 1. 1024
vb1061.fits 72 72 0 -1 1. 1. 1024
vb1061.fits 73 73 0 -1 1. 1. 1024
vb1061.fits 74 74 0 -1 1. 1. 1024
vb1061.fits 75 75 0 -1 1. 1. 1024
vb1061.fits 76 76 0 -1 1. 1. 1024
vb1061.fits 77 77 0 -1 1. 1. 1024
vb1061.fits 78 78 0 -1 1. 1. 1024
vb1061.fits 79 79 0 -1 1. 1. 1024
vb1061.fits 80 80 0 -1 1. 1. 1024
vb1061.fits 81 81 0 -1 1. 1. 1024
vb1061.fits 82 82 0 -1 1. 1. 1024
vb1061.fits 83 83 0 -1 1. 1. 1024
vb1061.fits 84 84 0 -1 1. 1. 1024
vb1061.fits 85 85 0 -1 1. 1. 1024
vb1061.fits 86 86 0 -1 1. 1. 1024
vb1061.fits 87 87 0 -1 1. 1. 1024
vb1061.fits 88 88 0 -1 1. 1. 1024
vb1061.fits 89 89 0 -1 1. 1. 1024
vb1061.fits 90 90 0 -1 1. 1. 1024
onedspec>

Trillian,Thanks for the images. Neither of them have a spectral WCS (i.e. the CRVAL/CDELT keywords) and the processed images has most of the keywords removed. The FXCOR task is designed to only a 1-D correlation of extracted spectra; you can give it a 2-D image and step through the apertures/orders only if the spectra have been properly extracted to 1-D first.Unfortunately I have no idea how/what the MKTRACER task works and can't offer any advice on how to process the data to reduced spectra, but at the moment these images can't be used for velocity analysis. As you've seen, the task will treat the rows of the images as just plain pixels. You might contact Keck or the NIRSPEC documentation for further instructions.Cheers,
-Mike

The MKTRACER task is used from a package called wmkonspec. Usually this is package written for KECK observations, especially using NIRSPEC. It is used to straighten the spectra. Here is the link: http://www2.keck.hawaii.edu/inst/nirspec/wmkonspec/mktracer.html

Hello Mike, Getting back to your answer and continuing to work on this issue, I did the following:(1) Created DAT file containing two columns (Thanks to Ivan) ; Wavelength and Flux
(2) Read it in using rspec task and created FITS file out of a text file
This created a fits file with following infomation:
CRVAL1 = 1.24053
CRPIX1 = 1.
CDELT1 = 1.78543307E-5
CD1_1 = 1.78543307E-5But this header file does not have any information on obs-date, UT, RA, DEC, epoch etc..How do I get these in the header file? Or is there a way to specify them when I run the FXCOR task? I still get an INDEF when it comes to calculating the V_helio in FXCOR. Please let me know. Thanks!

Trillian,If your two columns of the DAT file are preceeded by a FITS header, the RSPEC task will read that in directly in addition to adding the new keywords. It sounds like you can get these keywords from the original image so it should just be a matter of how you prepare the DAT file.Otherwise, you would need to use HEDIT to add keywords to the header with the appropriate value (e.g. use HSELECT to pull them from the original image and HEDIT to add them to the new image). The task allows you to set the keyword to look for to find the needed value (i.e. KEYWPARS), but not the value itself.-Mike

Thanks for your quick reply. Yes, I have the keywords ( like UTC, RA, DEC,..) from the original image. I used the HEDIT command to add these keywords into the FITS file I created using RSPEC. My only concern was the following. (1) When adding the keywords using HEDIT, the task took the time in decimal format and not in HH:MM:SS format. But when looking into help under keywpars, I saw that the required format for RA, DEC, and UTC is HMS, which I guess means, I leave out the colons. Should this be the same format when using HEDIT? (2) The DC-FLAG parameter is set to zero, does this do wavelength correlation or just pixel? I am just trying to figure out how and why I get INDEF for Vhelio when I have given the files all that is required. Looking at the files may help you. Thanks a lot!

ok, answering my own question, the format as suggested ( i.e HHMMSS) does not work well. When you hit the "v" key while using FXCOR, it gives a report on the whole correlation and the errors involved. The errors were the following: Comments:
ERROR: Error getting '250607' from temp image header.
ERROR: Error getting '161425.20' from temp image header.
ERROR: Error getting '-025058' from temp image header.
ERROR: Missing EPOCH keyword.
ERROR: Missing exposure time keyword.So, how do I write times in HH:MM:SS format? HEDIT takes it in decimals? Also, I have EPOCH keyword in the header, why does it not recognize it? Please let me know. Thanks!

Once you've run the task and see the correlation plot, type 'v' to view the log file. You'll notice in the comments at the bottom that the image is missing a DATE-OBS keyword. The missing exposure time keyword can be cured by changing the KEYWPARS pset to use the 'itime' keyword in the image.Note that DATE-OBS must be in the proper format, e.g. [i:30d9eb66de]2007-01-01T00:00:00.0[/i:30d9eb66de]
-Mike