Spitzer Science Center Leopard -- Archive Interface Software version 7.0 Known Bugs and Issues Last Updated: April 11, 2007 ----------------------------------------------------------------- Reporting Bugs ----------------------------------------------------------------- The known bugs in Leopard are listed here. If you think you have found a bug, before reporting it please check this list, read the Release Notes, and the applicable sections of the User's Guide. It may be a "feature" we already know about. If you have found a real bug then please do let us know by sending email to the Help Desk at help@spitzer.caltech.edu. Each time you run Leopard it creates a file called 'leopard-DATE_TIME.log'. When you run the Subscriber feature it also creates 'subscriber-DATE_TIME.log'. The log files are found in the default ~/.spot directory. If you report a bug to the Help Desk please include the log files as well as information about your hardware and operating system configuration. If you have found a bug then please do let us know by sending email to the Help Desk at help@spitzer.caltech.edu. You should turn on auto-update and wait a few minutes to ensure that you have the latest versions. ----------------------------------------------------------------- Known Bugs/Features ----------------------------------------------------------------- ----------------------------------------------------------------- 1. 11 April 2007 Known Bugs/Features in the Current Version ----------------------------------------------------------------- - Not a bug, but often a common pitfall: For Mac users, please be sure that your subscriber.app is in the same folder as leopard.app. If this is not the case, Leopard will not be able to find Subscriber, the latter will not open, and you will be unable to download data. - Show All Moving Targets at a Date overlay does not work for all moving targets, especially slow moving ones. - Spitzer Bright Objects for AOR overlay may not working for moving targets. - For the new BCD Preview feature in the Detail Information window, not all AORs will have BCD previews available, due to a known problem with our database. A warning will appear to this effect if this is the case for a given AOR. However, the BCD files themselves may still be available for download, even if the previews do not appear. - When selecting multiple AORs in the Archive Query Results window using Shift+Left_Mouse_button, the multi-select feature only works in descending order in the AOR list. - When selecting multiple AORs in the Archive Query Results window using Control+Left_Mouse_button, all of the additional AORs selected after the first selected AOR must be below the first selected AOR in the AOR list. - For Macs, the Command-X (or delete) key does not function, when trying to delete AORs. Use the Delete Selected AORs utility under the Edit menu. - As a feature of Leopard, for some programs you will see more observations (and possibly, available data) listed for a program than you would in Spot. This is most likely due to the fact that the program included Instrument Engineering Requests (IERs) or Spacecraft Engineering Requests (SERs) -- these involved non-standard observing modes. Under the Detail Information window, the Params tab will be blank for this reason. This is the main reason that Leopard should be used to search the Reserved Observations Catalog (ROC), rather than Spot. ----------------------------------------------------------------- 2. 19 December 2006 Java version for Intel Macs ----------------------------------------------------------------- With Software Updates, this may no longer be relevant. A user has informed us that the Java needed for non-Intel Macs at the website http://www.apple.com/support/downloads/java2se50release3.html is not appropriate for Intel Macs, when running Spot. The right Java can be found at http://www.apple.com/support/downloads/j2se50release4intel.html. ----------------------------------------------------------------- 3. 23 July 2004 Subscriber tool fails to open ----------------------------------------------------------------- This may no longer be a problem. On start-up, the subscriber fails to open properly and you see and error message that says: Unable to complete Subscriber : a network error occurred. java.io.IOException: subscriber start failed and then an empty subscriber dialog opens. Impact: Major Workaround: This happens if the subscriber doesn't get completely open in 30 seconds. Just close the subscriber and restart it again. ----------------------------------------------------------------- 4. 6 December 2004 Precession bug? ----------------------------------------------------------------- It looks like there a B1950 <--> J2000 precession bug is in Leopard. If you do a search for an object with J2000 coordinates using a certain search radius, e.g., 5", and if the object being sought is near, but not necessarily within, that search radius had its target coordinates entered into the original AOR in B1950, then Leopard cannot find the AORs corresponding to that object. Impact: Major Workaround: Actually, this is not a bug, it is a feature of Leopard. During S11 development, we found a bug that a radius search may miss some AORs, if the AORs have, e.g., cluster-type targets. We increased the search radius inside the code, to miss fewer sources. But, by doing so, we added some targets that otherwise would not be in the search radius. We are still trying to find ways to address this problem more thoroughly. Meanwhile, we feel it is better to retrieve extra AORs than fewer. ----------------------------------------------------------------- 5. 25 January 2005 Programs containing targets with non-standard emphemeris ----------------------------------------------------------------- When searching for data from a program which observed moving targets, any of which having a non-standard ephemeris, i.e., no NAIF ID, one is unable to obtain the data for the whole program. Impact: Minor. Workaround: The SSC will provide the user with the individual AOR IDs, to obtain the data associated with each of these separately. ----------------------------------------------------------------- 6. 1 August 2005 Network Problem with Fedora Core 4 ----------------------------------------------------------------- This may still be a problem. When installing Spitzer Pride on a Linux machine running Fedora Core 4, the package installs correctly, and both Leopard and Spot run OK. But, the network status is perpetually "Net Down." Impact: Major Workaround: Although we are not quite yet supporting Fedora Core 4, a user provided us with a possible workaround that could do the trick. Apparently there's a conflict between Java expecting IPv4 sockets for the network, while fC4 provides IPv6 sockets. Changing one line in the Leopard script (around line 17), from set jreJar = '-Dloader.jre.jarName=linux-jre.jar' to set jreJar = '-Dloader.jre.jarName=linux-jre.jar -Djava.net.preferIPv4Stack=true ' seems to solve the problem. This problem should have gone away with Java 1.5 (although this has not been tested). The same change obviously works for Spot, too. The suggestion was found at this site, http://www.jroller.com/page/dissonance/20050630#fedora_core_4_and_jdk . (The SSC does not endorse this solution, but if it works, go with it!) ----------------------------------------------------------------- 7. 19 September 2005 Leopard unable to access data ----------------------------------------------------------------- This problem may have gone away. Users may notice that they will be unable to access data for a very small number of sources (42). When you try to name resolve the source with SIMBAD or NED, or enter the coordinates manually, Leopard comes up with an error dialog, saying "Database Search has Problem." This is not a bug, it is a feature. Impact: Minor. Workaround: These sources are likely SERs, "Spacecraft Engineering Requests." The SERs do not have the RA and Dec field strings populated in the database, and this will cause the problem during the source search. If you encounter this problem, please email us at the Spitzer Helpdesk, help@spitzer.caltech.edu. ----------------------------------------------------------------- 8. 19 September 2005 Downloads with Mac OSX ----------------------------------------------------------------- Some users have noticed difficulty downloading data using Leopard running under Mac OSX. Often the download windows get hung or are unresponsive. Impact: Major. Workaround: One user found that pressing 'ctrl-click,' instead of plain 'click' (with the left mouse button), seems to be doing the job, at least for now. ----------------------------------------------------------------- 9. 19 September 2005 Installing Spot/Leopard under Fedora Core ----------------------------------------------------------------- This related to an older version of Spitzer Pride, but could still be a problem for Fedora Core. A user was having difficulty installing Spitzer Pride on a Linux machine, running under Fedora Core. The install script has a tar command in it, which seems to stymie the installation. You may see this error, for instance: ./Spitzer-pride15_0_5-linux.sh Unpacking... tail: cannot open `+25' for reading: No such file or directory Extracting... tar: This does not look like a tar archive tar: Skipping to next header tar: Error exit delayed from previous errors status from tar = 2 ABORTING INSTALLATION . Impact: Major. Workaround: This same user figured out the following workaround. Delete all the extra "echo" commands in the install script, in order to restore the original line numbering. The install script should then work. The key change was to line 8, where the "tail" command is: old version: tail +25 $0 > $outname_tar new version: tail -n +25 $0 > $outname_tar It's not really clear why the "echo" commands make a difference, since they occur before the point where the tar command begins, and "tail" should count from the end of the file. The SSC will look into a more robust solution. ----------------------------------------------------------------- 10. 4 October 2005 Installing Spot/Leopard under Mac OSX 10.4 (Tiger) ----------------------------------------------------------------- It is possible that, when one downloads the .dmg file for Spitzer Pride (i.e., Spitzer-pride16_0_3-mac.dmg), that the browser and/or download tool under 10.4 will attach a .txt suffix to the file, hence rendering it as an ascii file. This will make it impossible to unload the file and install Spitzer Pride. Impact: Major. Workaround: In a terminal window, under Mac Unix, "mv" or rename the file to exclude the .txt suffix, i.e., mv Spitzer-pride16_0_3-mac.dmg.txt Spitzer-pride16_0_3-mac.dmg. The file will then appear as a disk image file icon, which you can then click on and unpack. ----------------------------------------------------------------- 11. Old, old bugs that may have finally gone away.... ----------------------------------------------------------------- a) Too many Calibration files returned When you choose to download the calibration for IRAC data, we are currently sending you a whole lot more files than you probably need. Simply ignore any files that do not begin with "Spitzer_I?". Descriptions of the other files are in the IRAC Data Handbook. Again, this may no longer be an issue. b) Menu bar stops working on Mac Menu bar stops working in Leopard on Mac. Restarting Leopard is the only way around this at the moment. c) Query results still appear after Abort Leopard still displays query results (partial) after clicking Abort. This isn't catastrophic, but is confusing. d) Leopard won't execute from the command line When you try to run the Leopard executable (in Solaris) from the command line in a terminal window, by simply typing "leopard," you receive an error message, "Word too long." This can be fixed pretty easily. We've found that some machines have an older patch to Solaris that has limitations on the number of allowable characters in a string when using the c-shell. To work around this, open up the leopard script in your directory using your favorite editor. You should see a first line that reads "#!/bin/csh -f." If you modify the "csh" in that line to "tcsh," i.e., the t-shell (edit the line to read "#!/bin/tcsh -f"), leopard should be able to run from the command line. e) Quitting Leopard under MacOSX A user reports that he had to use the Force Quit option to exit Leopard under Mac OSX. We tried to replicate this on our own G4 and couldn't. This should have gone away with Tiger and Java 1.5. f) Leopard may not be able to open a linked directory (under Windows). This error was found when trying an AORID List Query. g) Default search radius for Fixed Target List Query When using the Fixed Target List Query utility (under the Query Menu), the assumed default search radius should be 1 arcminute, but in the past, it had assumed it was *zero* arcminutes. Thus, when either inputting actual coordinates or using object names to be resolved in a list, Leopard returned the erroneous result that no programs are found corresponding to any of your positions or objects. *This appears to have totally gone away.* However, generally to remedy this, you simply must include the desired search radius, keyword "RADIUS," at the top of the position/source list. See the Leopard User's Guide for the complete file syntax.