 |
|
 |
Knowledgebase Categories |
|
|
| The knowledgebase is organized into different categories; please select a category that you are interested in. You can also search the entire knowledgebase by entering keywords in the navigation bar beside this text. |
|
| |
 | Articles |  |
|
 | I want to create an IRS spectral map using two different modules -- Why are the slits centered on different parts of the sky? |  |
| An example of the problem using the SH and LH slits is illustrated here.
The spectral map positions are in array coordinates, which have axes that are parallel and pe |
|
|
| What criteria should I follow to improve the probability that my peak-up will be successful? |  |
| Detailed information and procedures for configuring peak-ups can be found in the Spitzer Observer's Manual and the |
|
|
| I got my peak-up data and I want to double check that it was done right. What should I look for? | |
| An onboard peak-up algorithm measures the centroid of the brightest source in the peak-up field. It performs two measurements. First, the centroid of the brightest source in the peak-up array field-of-view is measured at an "acquisition" pointing (ACQ). N |
|
|
| I think my peak-up failed. How can I tell? | |
| There are two ways for the peak-up to "fail".
1. If the algorithm does not find a valid centroid, then it will report a failure. In the peak-up images, particularly the processed DCE (see above), there will be no visible source. You can also identify t |
|
|
| I didn't get a spectrum of my science target because there was a false positive. Was that exceptionally bad luck? | |
| The integrated number counts for sources with flux density of 1 mJy at 24 microns at high latitudes (see Marleau et al. 2004, ApJS, 154, 66) give 335 sources (both stars and galaxies) per square degree in a high galactic latitude field. That is one source |
|
|
| Are there IRS 'no observing zones'? | |
| We have received two queries regarding a rumor that the SSC is going to designate certain areas of the sky as off-limits to IRS. According to the rumor we are working on this now but aren't going to tell anyone which areas are banned until after the Cycle |
|
|
| I am having trouble installing SMART. What do I do? | |
| Read the SMART installation documentation carefully. In almost all cases, problems have been because of the order of directories in the IDL_PATH or a missing "+" sign |
|
|
| Does SMART work on Mac OSX ? | |
| Yes. However, many mac owners use the bash shell. In that case, you must edit one line in each of two files:
line 46 of /smart/utility/misc/sm_list_files.pro
line 81 of /smart/scripts/pro/sc_read_fits_bcd.pro
In each file, the line in question |
|
|
| In SMART, how do I calculate the coordinates of the source depending on where I do the extraction within the slit ? | |
| The values that are relevant are RA_SLT, DEC_SLT, PA_SLT. RA_SLT and DEC_SLT are different for different nod positions while RA_FOV and DEC_FOV remain the same between nods. So lets say your PA_SLT is 0 degrees (that means the long axis of the slit is rot |
|
|
| In SMART's interactive extraction mode, the size of the extraction window appears to be insensitive to the manually defined extraction width. | |
| This is a known problem and is being fixed.
It has been reported by a user that selecting 'fixed column' extraction in the 'interactive extraction' will perform a fixed column extraction and will use the user-defined extraction width if you manually se |
|
|
| How do I script the extraction of multiple sources in SMART ? | |
| Scripted autosky extraction hasn't yet been programmed into SMART and is on the to do list. However, you could look into the IDL source code to identify the subroutines which perform source extraction and write an IDL program which has just these routines |
|
|
| Is there a data reduction cookbook for SMART ? | |
| Yes, the developers of SMART have written a SMART cookbook.
Additional illustrations of data reduction with SMART can be found in |
|
|
| How do I bypass the usage of masks during extraction with SMART? | |
| To do it you need to make your own extraction mask. The simplest way to do this is to write an IDL routine which makes a 128X128 array, sets the array elements to the values you want them to be and then writes out to a file. Mask files can be either ".fit |
|
|
| In CUBISM, which calibration set should be used with which SSC IRS pipeline version? | |
| In order to understand the answer to this question, you need a little background on the SSC pipeline. Roughly every six months, the pipeline number (the "S-number") for all new Spitzer data (from all instruments) in the archive is incremented as a new so |
|
|
| When I try to run SMART, I get syntax errors involving 'sxpar'. What is the problem? | |
| You must add the astrolib library to your IDL path. Make sure that your IDL path includes SMART before astrolib. |
|
|
| I am trying to run SPICE in batch mode, but keep encountering the error "Failed during validation". What is going on? | |
| You may encounter the error "Failed during validation" if you have spaces in the path to your input files. To avoid this problem, you can:
- remove the space from your path
OR
- identify a directory with no spaces, and create a symbolic link to |
|
|
| How does CUBISM render slit sizes? | |
|
The aperture shown in CUBISM is data-driven, and does not intend to represent the full slit. The width in the CUBISM visualization reflects that of the 1 pixel width wavesamp, which is set that way on purpose, reflecting the fact that in the cross-slit |
|
|
| I am experiencing problems with colors in CUBISM. What do I do? | |
| You may experience inconsistencies between the colors indicated in the CUBISM documentation and what you see on your screen if you have chosen to install the full source distribution of CUBISM.
If you have trouble with the colors looking strange on a 1 |
|
|
| In Mac OSX, the SPICE GUI crashes when entering an input, uncertainty or mask image: the whole window disappears. How do I fix it? | |
| Open the "Java Preferences" application, found in Applications > Utilities > Java, and switch to Java 1.5 32-bit.
If this doesn't work, then close SPICE and open a Terminal window. Issue the following commands.
cd /Applications/spice/spice.app/Cont |
|
|
|
|
|
|
|
|
|
|
|
