IRSA Viewer Known Bugs and Issues

version released January 2018.

Last Updated: January 2018

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 IRSA Viewer are listed here. If you think you have found a bug, before reporting it, please check this list, and read the online IRSA Viewer 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. Currently, the only Windows browser known to work is Firefox for Windows.

Known Major Bugs

none known.

Known Minor Bugs

  1. Flipping. If you load in images and do not insist on north-up, then the 'flip' tool in the image toolbox works as advertised, e.g., flips just the x-axis. If you rotate north up first, then flip instead flips both the x- and y-axes.

    Workaround: Leave it as not-north up.

    Posted: 14 December 2017

  2. WCS Match/Target Match. It used to be the case that the WCS match and the target match options did very different things. Now they are more or less interchangable. Big differences (and strange alignments) can occur, though, depending on which image you have selected when you tick these boxes.

    Workaround: Select the image that has your target best centered before ticking either box.

    Posted: 14 December 2017

  3. Plot options. When changing the plot options in some plots, the settings window that appears when selecting the gears does not have an 'x' to remove the window.

    Workaround: Click on the gears again to make the window go away.

    Posted: 30 August 2017

  4. SDE column isn't correct. When doing time series analysis, the returned table has a column, 'SDE', which is identical to the power; it should be the FAP.

    Workaround: none known.

    Posted: 30 August 2017

  5. LC phase-folded table doesn't get updated. If you filter the phase folded table, and then filter again, the table doesn't update the second time.

    Workaround: Reload the tool (and your data table) and filter only once.

    Posted: 30 August 2017

  6. Regions files saved from long catalogs do not include all the sources. 500 is the maximum number of regions that can be saved.

    Workaround: Overlay catalogs of less than 500 objects, or filter down the catalog.

    Posted: 30 August 2017

  7. Mouse-over popup on plots doesn't work. When making a plot of more than 5000 points, the plot is made as a density plot. When you mouse over a point, there is a pop-up that describes the contents of the point under your cursor. On Firefox, that pop-up is often white on white or black on black

    Workaround: Resize the plot, and then it works.

    Posted: 25 August 2017

  8. Pixel values. when IRSA Viewer displays an image that is an extension of a multi-extension fits file, in the upper right of the tool, it often displays the pixel value as NaN when the number is very, very small or very, very large.

    Workaround: None known.

    Posted: 30 August 2017

  9. Tables sometimes vanish. Occasionally, a mouse action will not be relayed properly, causing some table search results to disappear from the screen.

    Workaround: Click on another tab, and then go back to your catalog tab. This forces the browser to redraw it.

    Posted: 12 November 2013, updated 11 Dec 13

  10. Mouse control is sometimes lost when resizing a table column. When grabbing the boundary of a table column to resize it, occasionally the mouse action will not be relayed properly, and you lose control of the mouse use easily.

    Workaround: Click on another part of the IRSA Viewer screen, and then you should regain control of your mouse clicks.

    Posted: 11 December 13

  11. VO catalog results not displayed
  12. For VO catalog searches, the tool retrieves the catalog but is unable to display it.

    Workaround: Download the catalog yourself from another VO access point (see here) and upload it separately to the tool.

    Posted: March 23, 2016

Known Idiosyncracies

  1. 'Lost' targets

    In some cases, images will be returned for a search where the target is just off the edge of the viable data from the image. In this case, the requested target will not appear on your retrieved image, and it may not be immediately obvious that your target is not, in fact on the image. This most often happens for big and/or irregular mosaics.

    Posted: 12 November 2013

  2. '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: 12 November 2013

  3. Incorrect filters don't throw errors
  4. If you accidently type a character in where numbers were meant in a filter, such as ">f" or, worryingly, ">1-", it doesn't actually tell you that there is an error in what you have typed, and it may behave as if it has imposed a filter properly.

    Posted: 27 January 2015

  5. 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: 12 November 2013

  6. 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 1000 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: 12 November 2013

  7. Background monitor email notification

    When you send something to the background monitor, it always gives you the choice of sending email to you when the job is done. However, it only actually sends you email for packaging files, not catalog search results.

    Posted: 12 November 2013