HIPE known issues for old versions

See this page for known issues on later HIPE versions.

Known issues in HIPE 7.3

None known in addition to those listed for HIPE 7.0.

Known issues in HIPE 7.2

None known in addition to those listed for HIPE 7.0.

Known issues in HIPE 7.1

None known in addition to those listed for HIPE 7.0.

Known issues in HIPE 7.0

• Cannot download data from the Herschel Archive due to corrupted cache.

Error messages about product cache corruption may vary. One example is the following:

herschel.share.util.ConfigurationException: Failed to locate product in cache

To solve the problem, try one or more of the following:

• Choose Edit --> Preferences and go to Data Access --> Storages & Pools. Select a pool in the Pools pane and click the Clear cache button. Note that this button will not be available if there are no pools listed in the Pools pane.
• If the above does not work, clear the HSA cache manually by deleting the home/.hcss/pal_cache/hsa directory, where home is your home directory.
• If the above does not work, clear all caches manually by deleting the home/.hcss/pal_cache directory.

• High disk activity with many local pools

If you have a high number of local pools on your disk (of the order of hundreds or more) you may experience noticeably high disk activity at HIPE startup.

• Step by step execution sometimes runs two statements at once

This happens when executing a compound statement, such as a for loop. The first command after the compound statement will be executed in the same step as the compound statement. Consider for example the following script:

for i in range(3):
  print i
print "Finished"

The line by line execution will run the for loop and the print "Finished' statement in the same step. A workaround for this behaviour is to add a pass command after the end of the compound statement. The pass command will be executed in the same step as the for loop, but without any effect:

for i in range(3):
  print i
pass
print "Finished"

Known issues in HIPE 6.1

None known in addition to those listed for HIPE 6.0.

Known issues in HIPE 6.0

Core

• Inverted sign in Observation Context radialVelocity metadata

Usually the velocity of a source with respect to the observer is positive if it results in an increase of the observed wavelength with respect to the rest value, and negative otherwise, according to the formula v = (lambda - lambda_rest) / lambda_rest. In the current implementation of the radialVelocity metadata into the ObservationContext product, this convention is inverted: the sign of the spacecraft velocity is positive when it is moving towards the target.

• Failure in mosaic task

The mosaic task fails if your default language uses a different delimiter for decimal numbers than English (for example, a comma rather than a dot).

A workaround is to add the following line to your hipe.props file:

java.vm.options = -Duser.language=en -Duser.region=en

The file should be in the .hcss subdirectory of your home directory. If the file does not exist, create it. If the file already contains a line defining the java.vm.options property, you can add the two values -Duser.language=en and -Duser.region=en at the end of the line, separated by a space from the other values.

• Wrong units and sign in Cube Spectrum Analysis Toolbox

The cursor readout from a velocity map created in the Cube Spectrum Analysis Toolbox indicates km/s, but the values are in m/s. Also, velocity maps created from a spectral cube with an upper sideband (USB) frequency scale have the wrong sign.

• Query with no results wrongly returns an empty product.

When using the Product Browser perspective, a query with no results creates an empty product called p in the Variables view.

Steps to reproduce:

1. In the Product Browser view, select a query source and search for an obsid that you know not to exist.
2. In the Variables view, variables QUERY_RESULT and p appear.
3. The QUERY_RESULT variable is correctly empty, as you can verify by issuing the command print QUERY_RESULT in the Console view.
4. The p variable should not have been returned. You can safely delete it.

See the Data Analysis Guide for more information on the Product Browser perspective.

• Slow startup due to error messages.

You may see many errors like the following in the command line window from which you are starting HIPE. These errors cause a considerable delay in HIPE startup:

31-Jan-11 10:00:17.797 WARNING NavigatorView: Error checking file /bin: java.util.concurrent.TimeoutException

Workaround: set the property hcss.hipe.refreshPeriod as follows:

hcss.hipe.refreshPeriod = 3600000

See the HIPE Owner's Guide for information on how to set properties.

Known issues in HIPE 5.3

None known in addition to those listed for previous 5.x versions.

Known issues in HIPE 5.2

None known in addition to those listed for previous 5.x versions.

Known issues in HIPE 5.1

Issues in previous 5.x versions may still apply to this version.

Core

• You may see many errors like the following in the command line window from which you are starting HIPE. These errors cause a considerable delay in HIPE startup:

31-Jan-11 10:00:17.797 WARNING NavigatorView: Error checking file /bin: java.util.concurrent.TimeoutException

Workaround: set the property hcss.hipe.refreshPeriod as follows:

hcss.hipe.refreshPeriod = 3600000

See the HIPE Owner's Guide for information on how to set properties.

• An error like the following can sometimes appear in the command line window from which you are starting HIPE. This error is harmless and can be ignored. May also affect older HIPE versions. Fixed in HIPE 6.0.
  

Exception in thread "AWT-EventQueue-0" java.util.ConcurrentModificationException
        at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372)
        at java.util.AbstractList$Itr.next(AbstractList.java:343)
        at herschel.ia.gui.kernel.parts.impl.AbstractSite.opened(AbstractSite.java:468)
        ...

• Caches of PAL pools (most often used for accessing the HSA) can be corrupted when switching back and forth between HIPE v5.1 and previous versions. The result of this corruption is that the cache can silently give you other data than the data you were asking for. If you are switching back and forth between 5.1 and previous versions, clear your caches in the Data Access Preferences panel: From the Edit menu, select Preferences. Under Data Access, locate the Pools and Storages section. In the bottom right section of the panel, select the pool that has a cache enabled and click "Clear cache". Fixed in HIPE 6.0 and 5.3.

Known issues in HIPE 5.0

Core

• The cursor readout from a velocity map created in the Cube Spectrum Analysis Toolbox indicates km/s, but the values are in m/s. Also, velocity maps created from a spectral cube with an upper sideband (USB) frequency scale have the wrong sign.
• HIPE does not start if there are too many local pools. This happens when the list of local pool names, separated by commas, exceeds 8096 characters.
• Zooming on an image may cause HIPE to hang. The zoom level at which this happens depends on the original size of the image.
• The saveObservation task with default settings fails to save an Observation Context to a pool.
  Workaround: delete the hsa_cache local pool directory and the $HOME/.hcss/pal_cache/hsa directory. Alternatively, move the hsa_cache local pool to $HOME/.hcss/pal_cache/hsa/pool/hsa_cache/. Note that you have to move the hsa_cache directory from your local pool directory into the above directory, so that you will have paths that have hsa_cache twice, for example: $HOME/.hcss/pal_cache/hsa/pool/hsa_cache/hsa_cache/herschel.ia.obs.ObservationContext.
• The ra and dec values in the metadata of an Observation Context (and hence the RA and DEC entries in the summary) can be significantly different from the target coordinates (raNominal and decNominal) entered in HSpot. This is caused from averaging the target and chop positions. Coordinates in the actual data are correct.
• The NearestNeighbourProjectionTask task, which creates a spectral cube from three-dimensional data, fails to create a target grid out of a set of target grids. A command such as targetGrid = nearestNeighbourProjection.targetGrid([tg1,tg2,tg3]) fails with an IllegalArgumentException.
  For more information on NearestNeighbourProjectionTask, see the HCSS User's Reference Manual in the HIPE Help System.
• In the LocalStoreWriter task, the default location of new local pools is $HOME/.hcss instead of the default $HOME/.hcss/lstore. This results in new pools being created in non-standard directories. Information about the locations of these pools is written in the $HOME/.hcss/hipe.props file.
  To remove a local pool in a non-standard location, delete the pool directory and the corresponding configuration line in hipe.props.
  To create local pools in the standard location, change the value in the Location field of the LocalStoreWriter task to $HOME/.hcss/lstore, where $HOME is your home directory (for example /home/mrbean/.hcss/lstore on Linux systems).
  Fixed in HIPE 5.1.
• A bug in Firefox may prevent the Help System from starting correctly (a browser window opens but nothing appears). This can be solved by deleting all the browser cookies, or just the cookies coming from 127.0.0.1 (the local system). See also General Help System issues on this page.
• Most entries in the User's Reference Manual have wrong or missing categories.
• The documentation shipped with HIPE still mentions JIDE in several places. JIDE was the data reduction application that came before HIPE and is no longer supported. With the exception of Appendix B of the Scripting and Data Mining guide, all references to JIDE can be applied to HIPE.
• The message INTERRUPTED while loading image can sometimes appear in the command line window from which you launched HIPE. This message is harmless and can be ignored.

HIFI

• Ra/Dec coordinates in data cube meta-data are incorrect.
• In CLASS files generated via the HiClass task, the source velocity is not included or applied (i.e. the frequency scale is wrong).
• When the frequency calibration of WBS is computed from the values of the HRS spectra, the coefficient of the polynomial to be used are function of the temperature. These are not available in the calibration tree.

PACS

• The following scripts in the Pipeline --> PACS menu in HIPE are known to crash: extended_pipeline.py, L1_smallSource.py, L2_scanMap.py. Other scripts may crash or not be applicable because they depend on the results of other non-working scripts. Many scripts are not adequately commented.
• The data/pcal/PCalSpectrometer_ArrayInstrument_FM_v5.fits calibration file, dealing with spectrometer spatial calibration, contains incorrect values. This results in offsets of the order of one arcsecond between reported coordinates and commanded positions.
• Some tasks may be holding data products in memory unnecessarily, thus slowing down HIPE and possibly causing out of memory errors.
• In the photProjectPointSource task, the calibration = false mode (no longer recommended) is not flux conserving.

SPIRE

• The signalJumpDetector task is not registered at HIPE startup.
  Workaround: import it manually with the following command:
  from herschel.spire.ia.pipeline.common.sigjump import SignalJumpDetectorTask?
• The AbstractMapperTask may treat incorrectly a Wcs provided as input. When the input Wcs is defined using the CDELTi keywords, the result is correct, but when the pixels are defined with the CDi_j keywords, these are translated into CDELTi and CROTA2 keywords. This is not equivalent, if not rectangular pixels are required.
• The AbstractMapperTask has a bug in the generation of tod files which can result in an ArrayIndexOutOfBoundsException at the map generation.
• The spireCal task outputs an empty calibration context if the input pool does not exist, instead of reporting the problem. This results in errors when user scripts attempt to access the calibration files.

---

blog comments powered by Disqus

---