SOFIA Known Bugs and Issues

Software version released: May 2023.

This list last updated: May 2023

Table of Contents

Reporting Bugs
Suggested Browsers
Known Major Bugs
Known Minor Bugs

Reporting Bugs

The known bugs and issues in this version of the SOFIA Science Archive service are listed here. If you think you have found a bug, before reporting it, please check this list, and read the online SOFIA Science Archive help. 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. Please include your operating system version and your browser software and version.

Suggested Browsers and Platforms

Older browser versions than these may work, but we may not be able to support bug fixes for them. We make no guarantees for anything on Solaris.

Known Major Bugs

  1. Level 0-1 data not always returned. If you ask for Level 0-1 data in your search and search by position, you may not get all of the available Level 0 or 1 data returned in your search.

    Workaround: Do the search by position. Make a note of the AOR ID for the observations you want. Return to the search screen. Change the search to "all-sky", limit it to the instrument you want, and ask for Level 0 and/or 1. In the results, go to the instrument tab, turn on the filters, and filter down to just include the AOR ID in question. The Level 0 and/or 1 data will appear in that list.

    Posted: 24 May 2023

Known Minor Bugs

  1. Level 1 data files have strange footprints that make them look like all-sky observations. If you turn on Level 1 data in your search and look at the coverage tab in the results, you will get an Aitoff projection image with boundaries all over the sky.

    Workaround: Turn off the Level 1 data until you know which observations to download.

    Posted: 16 Oct 2020

  2. Regions files saved from large catalogs do not include all the sources. If the file has >15,000 sources, it will make a heatmap plot and show only a fraction of the sources on the image, even if the image is zoomed in.

    Workaround: Filter down the catalog by position or SNR until you have <15,000 sources.

    Posted: 14 Oct 2020

Known Idiosyncracies

Many data caveats can be found in the online help.

Posted: December 2020

Large coverage footprints

In many cases among the higher level data, the valid data really is a small square embedded within a larger square of NaNs. The coverage software sees the larger pixel dimensions in the FITS headers and draws the larger square.

Posted: 5 December 2019

'Lost' Downloads

Depending on how your browser is configured, when you download data, your browser may save it in a counter-intuitive place. Under Safari (on the Mac), for small downloads, it might not appear to have done anything at all. It actually has; it's trying to be helpful by doing it quickly. To find where your browser has put your data, (a) search on your local disk for recently modified files; (b) look in the preferences for the browser configuration option of where to put downloaded files; or (c) look for a directory called "Downloads" or something similar.

Posted: December 2019

Searching in online help doesn't work

If you try to search the online help using the search box in the upper right, it will complain about security and not actually search.

Workaround: View the PDF and search within the PDF using your PDF viewer's search feature.

Posted: 6 December 2019

Strange behavior when requesting catalogs

Our catalog search options depend on other services, often other IRSA services, to search and display the catalogs. Sometimes these other services are down for maintenance or may be experiencing unusually heavy loads. On those occasions, the user may get an "Unresponsive script" error or a "Call failed on the server" error. Please do let us know if you continue to get these errors; we may not be aware of an overloaded or down server.

Posted: December 2019

Slow behavior when requesting large tables

When rendering long tables, the table can take several seconds to finish loading. For example, if you conduct a search returning 10000 entries, and change the page size from 50 to 2000, the browser will struggle for a few seconds trying to load the table. A red message appears to let you know that that is what is going on.

Posted: December 2019

Strange behavior, often transient

Sometimes there can be unusual behavior in the tool. If something isn't working (especially if it used to work), try opening a new window without cookies, e.g., a "private window" in Firefox, or an "incognito window" in Chrome) and start the tool there. This usually resolves most of the odd behavior.

Posted: 6 December 2019