To Report Bugs
While we have made every effort to ensure that SPICE runs smoothly on all operating systems, you may encounter some bugs that we have not yet found. In the event that bugs are encountered, please send an email to the Spitzer Helpdesk describing the problem, and include the following information:
- The platform that you are running SPICE on (e.g. Linux RedHat) and the version number of your operating system.
- The AORKEY of the dataset that was used, along with the specific filenames.
- The SPICE log - this can be found in /home/<user>/.spot/ and is named e.g. spice-aug03_14-56-23.log (the numbers give the date and time of the run).
Send your report via the
the Spitzer Science Center Helpdesk
List of known SPICE bugs
- PROBLEM:
In the previous version of SPICE, the bitmask could be overlaid on the 2D spectral image. This functionality is not yet available in the new SPICE. It will be added in a future upgrade.
SOLUTION:
Keep auto-update turned on....
- PROBLEM:
Clicking on the Profile plot will move the dotted line showing the peak, but it will not change the value in the manual Ridge setting.
SOLUTION:
Use the slider under the plot to move the peak (dotted line), or type the percentage directly into the Ridge input field.
- PROBLEM:
After using IRSCLEAN, SPICE does not automatically select the mask and uncertainty files when inputting the BCD files
SOLUTION:
Manually select the mask and uncertainty files or, alternatively, re-name them to remove the "clean" part of the filename, and SPICE will automatically select them for you.
- PROBLEM: (MAC ONLY)
The file chooser widget does not allow you to resize directory lists, so it is hard to see the entire name of Spitzer files.
SOLUTION:
If the cursor is hovered over a file name, a tooltip with the full name comes up. Clicking on a file once will open a file info window at the right of the widget.
- PROBLEM:
It is possible to set a manual
extraction width that is wider than the illuminated region of
the order. This can lead to the extraction including spurious flux
between the orders or even to including flux from another order.
SOLUTION:
Users should be very careful when selecting
manual extraction widths, and visually review the overlay of the
extraction window. In addition, inter-order pixels can be excluded
from the extraction by ensuring that bit 8 is set as fatal (this may
need to be done by hand).
- PROBLEM:
When first chosing a manual extraction width, the default numbers may be too large or too small to be sensible in some cases.
SOLUTION:
See the SSC website documentation for the correct default widths.
- PROBLEM:
Optimal extract will give an error if it is applied to a BCD with FOV=LL-Both or FOV=SL-Both and default order selection in Profile. Optimal was not designed to do multi-order low-res extraction, because the two low-res orders see different parts of the sky.
Bugs fixed in recent SPICE updates
Fixed 04/16/08
- PROBLEM:
The overlay of the extraction window on the FITS image is off by 0.5 or 1 pixels due to pixel indexing.
SOLUTION
If you need to know exactly which pixel is at the edge of the extraction, use the overlay.tbl file. In that file, the lower-left corner of the lower-left pixel is (0, 0) (e.g. the center of the lower-left pixel is at (0.5, 0.5)).
- PROBLEM:
The Select Fatal Bitmask Pattern pulldown menu in Extract does not update immediately when clicking on bits.
SOLUTION:
Close and reopen the menu to see the updated choice. Alternatively, enter the pattern as a number in the input field next to the menu.
- PROBLEM: (MAC ONLY)
A module window can be moved slightly out of the frame so that it cannot be recovered.
|
