
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
<-- ANALYTICS CODE - DO NOT EDIT --> <-- Google Analytics script BEGIN --> <-- Google Analytics script END --> | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
<-- ANALYTICS CODE - DO NOT EDIT --> <-- Google Analytics script BEGIN --> <-- Google Analytics script END --> | ||||||||
| Line: 23 to 23 | ||||||||
| ||||||||
| Added: | ||||||||
| > > | Known issues in HIPE 10.1There are no changes with respect to the 10.0 issues detailed below. | |||||||
Known issues in HIPE 10.0Can't open plug-ins panel under KDE or Gnome 3 | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
<-- ANALYTICS CODE - DO NOT EDIT --> <-- Google Analytics script BEGIN --> <-- Google Analytics script END --> | ||||||||
| Line: 120 to 120 | ||||||||
| However, the target ephemeris inside HIPE doesn't get updated. I.e., doOffset uses the ephemeris current as of observation uplink to the spacecraft. Work is in progress to automatically update target ephemerids. If your target ephemeris was very uncertain at observation time (and if it has improved since), then you may be better off using a manual approach of downloading the Horizons ephemeris for each target. | ||||||||
| Added: | ||||||||
| > > | Printing a HIPE script to a file in Snowleopard sends the job to a printer insteadWhen a user tries to print a script to a file on disk, HIPE sends it to the printer instead. | |||||||
Known issues in HIPE 9.2 | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
<-- ANALYTICS CODE - DO NOT EDIT --> <-- Google Analytics script BEGIN --> <-- Google Analytics script END --> | ||||||||
| Line: 102 to 102 | ||||||||
| If you use HIPE 10, you should update to version 45 of the calibration tree to make use of several new calibration files. | ||||||||
| Added: | ||||||||
| > > | Generating a co-moving frame for HIFI mapping observations of solar system objectsThere is a task in HIPE that allows you to transform level-2 coordinates into a coordinate system co-moving with the target ephemeris. That task is called doOffset, http://herschel.esac.esa.int/hcss-doc-10.0/index.jsp#hifi_um:hdrg_offsetposn_use A typical code snippet would be: comet = getObservation(1342227173, useHsa=True) htp=comet.refs["level2"].product.refs["WBS-H-USB"].product # extract USB, pol H htp2=doOffset(htp=htp, overwrite=0, relative=1) # make coordinates relative to ephemeris HiClassTask?()(product=htp2, fileName='cometHUSB_relativeCoords.fits') # export in CLASS-readable format However, the target ephemeris inside HIPE doesn't get updated. I.e., doOffset uses the ephemeris current as of observation uplink to the spacecraft. Work is in progress to automatically update target ephemerids. If your target ephemeris was very uncertain at observation time (and if it has improved since), then you may be better off using a manual approach of downloading the Horizons ephemeris for each target. | |||||||
Known issues in HIPE 9.2 | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
<-- ANALYTICS CODE - DO NOT EDIT --> <-- Google Analytics script BEGIN --> <-- Google Analytics script END --> | ||||||||
| Line: 35 to 35 | ||||||||
| A patch is planned for this issue in HIPE 10.2. | ||||||||
| Added: | ||||||||
| > > | Clicking on the 'plug-in' button to add the cassis plugin, nothing happens and you see multiple java exceptionsThe "Desktop API", which is used to access the browser when you click "Find more.." button in the HIPE plugin dialogue, is not supported on KDE. It "was designed to work on Windows and Gnome". However, you can also open it directly by pointing your browser directly to http://herschel.esac.esa.int/twiki/bin/view/Public/DpHipePlugins, and copying the URL to the respective .jar files for the particular plugin you are interested in and pasting it in the HIPE plugins dialog to install it. If you would like to have the "Find more.." button working, all you need is to have the Gnome libraries installed. Some instructions: - To install Gnome 3 libraries on Ubuntu (http://www.filiwiese.com/installing-gnome-on-ubuntu-12-04-precise-pangolin/). Note that if you're using version 11.10 or later, you probably don't need the first command (sudo apt-add-repository ...). I would just skip it and if the last command does not complain about "package not found" or something similar, then all is well. - To install Gnome 2 libraries on Ubuntu: http://askubuntu.com/questions/123690/how-to-install-gnome2-on-ubuntu-11-10 A patch is planned for this issue in HIPE 10.2. | |||||||
Pools unreadable with Unknown format version: -11 errorIf you installed a developer build of HIPE 10 between 10.0.2069 and 10.0.2674 and modified any of your pools you will find those pools are no longer readable in any other HIPE version; when trying to load a pool withgetObservation you will get the following error message: | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
<-- ANALYTICS CODE - DO NOT EDIT --> <-- Google Analytics script BEGIN --> <-- Google Analytics script END --> | ||||||||
| Line: 11 to 11 | ||||||||
| Changed: | ||||||||
| < < | Installation and uninstallation issues | |||||||
| > > | Please note that some issues detected in previous versions may still be present in HIPE 10. Scroll down and check earlier versions if you do not see your particular issue listed for HIPE 10.
Installation and de-installation issues | |||||||
| ||||||||
| Line: 121 to 123 | ||||||||
Known issues in HIPE 9.0 | ||||||||
| Added: | ||||||||
| > > | Installation and de-installation issuesThere is a known problem with the InstallAnywhere? installer observed on a Linux 64 bits, Debian wheezy/sid, java 1.6.0_24 computer. Installation fails with the following error: "Configuring the installer for this system's environment... strings: '/lib/libc.so.6': No such file" Un-setting the PS1 envar solves the problem. Further details of the InstallAnywhere? issue can be found here: http://kb.flexerasoftware.com/selfservice/viewContent.do?externalID=Q112941 This issue is still present in HIPE 10.0. | |||||||
Performance issues of convolution task with NaN valuesThe performance of the imageConvolution task is severely degraded when NaN values are found in input data. HIPE 8.3 is not affected by this problem. Fixed in HIPE 9.1. | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
<-- ANALYTICS CODE - DO NOT EDIT --> <-- Google Analytics script BEGIN --> <-- Google Analytics script END --> | ||||||||
| Line: 23 to 23 | ||||||||
Known issues in HIPE 10.0 | ||||||||
| Added: | ||||||||
| > > | Can't open plug-ins panel under KDE or Gnome 3The Plug-ins panel cannot be opened (from the Tools menu) if you're working under Linux and you don't have the Gnome 2 library installed. Gnome 2 is a desktop environment, and typically if you use a different desktop environment (Gnome 3, KDE, Unity, etc), then you will not have this library. In both cases, the problem can be solved by installing the Gnome 2 library. For example on Ubuntu (or Kubuntu), the command is: sudo apt-get install libgnome2-0 A patch is planned for this issue in HIPE 10.2. | |||||||
Pools unreadable with Unknown format version: -11 errorIf you installed a developer build of HIPE 10 between 10.0.2069 and 10.0.2674 and modified any of your pools you will find those pools are no longer readable in any other HIPE version; when trying to load a pool withgetObservation you will get the following error message: | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
<-- ANALYTICS CODE - DO NOT EDIT --> <-- Google Analytics script BEGIN --> <-- Google Analytics script END --> | ||||||||
| Line: 68 to 68 | ||||||||
| If you have two or more separate Spectrum Explorer GUIs open and at least one is undocked, when using its Cube Toolbox the separate SE instances talk to each other--spectra or new cubes you create in one instance will also appear in the other one. | ||||||||
| Added: | ||||||||
| > > | New PACS calibration version 45 should not be used with HIPE 10In HIPE 10 a new spectroscopy telescope background calibration was introduced. This update is not compatible with the code in HIPE 9. You can alway check the calibration version that you are using with the following command:print getCalTree().version
If you use HIPE 10, you should update to version 45 of the calibration tree to make use of several new calibration files. | |||||||
Known issues in HIPE 9.2New PACS calibration version 45 should not be used with HIPE 9 | ||||||||
| Line: 490 to 501 | ||||||||
| ||||||||
| Added: | ||||||||
| > > |
| |||||||
| ||||||||
| Deleted: | ||||||||
| < < |
| |||||||
| ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
<-- ANALYTICS CODE - DO NOT EDIT --> <-- Google Analytics script BEGIN --> <-- Google Analytics script END --> | ||||||||
| Line: 19 to 19 | ||||||||
| ||||||||
| Added: | ||||||||
| > > |
| |||||||
Known issues in HIPE 10.0 | ||||||||
| Line: 489 to 490 | ||||||||
| ||||||||
| Deleted: | ||||||||
| < < |
| |||||||
| ||||||||
| Deleted: | ||||||||
| < < |
| |||||||
| ||||||||
| Added: | ||||||||
| > > |
| |||||||
| ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
<-- ANALYTICS CODE - DO NOT EDIT --> <-- Google Analytics script BEGIN --> <-- Google Analytics script END --> | ||||||||
| Line: 467 to 467 | ||||||||
| Added: | ||||||||
| > > | What are all the
You may find these pools in your local store directory (by default | |||||||
<-- COMMENT BOX CODE - DO NOT EDIT --> | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
<-- ANALYTICS CODE - DO NOT EDIT --> <-- Google Analytics script BEGIN --> <-- Google Analytics script END --> | ||||||||
| Line: 63 to 63 | ||||||||
| The solution is to send the data again without closing the external application. | ||||||||
| Added: | ||||||||
| > > | Separate, undocked instances Cube Toolbox talk to each otherIf you have two or more separate Spectrum Explorer GUIs open and at least one is undocked, when using its Cube Toolbox the separate SE instances talk to each other--spectra or new cubes you create in one instance will also appear in the other one. | |||||||
Known issues in HIPE 9.2New PACS calibration version 45 should not be used with HIPE 9 | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
<-- ANALYTICS CODE - DO NOT EDIT --> <-- Google Analytics script BEGIN --> <-- Google Analytics script END --> | ||||||||
| Line: 65 to 65 | ||||||||
Known issues in HIPE 9.2 | ||||||||
| Added: | ||||||||
| > > | New PACS calibration version 45 should not be used with HIPE 9In HIPE 10 a new spectroscopy telescope background calibration was introduced. This update is not compatible with the code in HIPE 9. If you use the background normalisation ipipe script for chopped spectroscopy in HIPE 9, you should not update the PACS calibration tree to version 45. You should keep using the calibration set 41 and cancel the update when the automatic calibration updater in HIPE asks to install set 45. If you have updated to set 45 and want to use the background normalisation in HIPE 9, you can switch back to version 41 in two ways:
print getCalTree().version
If you use HIPE 10, you should update to version 45 of the calibration tree to make use of several new calibration files. | |||||||
Issues with computePVMap taskThe computePVMap task has the following issues: | ||||||||
| Line: 463 to 480 | ||||||||
<-- END OF COMMENT BOX CODE --> | ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| ||||||||
| Deleted: | ||||||||
| < < |
| |||||||
| ||||||||
| Added: | ||||||||
| > > |
| |||||||
| ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| Line: 1 to 1 | |||||||||
|---|---|---|---|---|---|---|---|---|---|
<-- ANALYTICS CODE - DO NOT EDIT --> <-- Google Analytics script BEGIN --> <-- Google Analytics script END --> | |||||||||
| Line: 53 to 53 | |||||||||
| |||||||||
| Added: | |||||||||
| > > | HIPE cannot send data to an external application via SAMPWhen you try to send data to an external application via the SAMP Virtual Observatory protocol, the following window may appear:
The reason is that HIPE tries to send data before the external application has initialised properly. This issue seems to occur more frequently with VOSpec.
The solution is to send the data again without closing the external application. | ||||||||
Known issues in HIPE 9.2Issues with computePVMap task | |||||||||
| Line: 453 to 463 | |||||||||
<-- END OF COMMENT BOX CODE --> | |||||||||
| Added: | |||||||||
| > > |
| ||||||||
| |||||||||
| Changed: | |||||||||
| < < |
| ||||||||
| > > |
| ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
<-- ANALYTICS CODE - DO NOT EDIT --> <-- Google Analytics script BEGIN --> <-- Google Analytics script END --> | ||||||||
| Line: 330 to 330 | ||||||||
| HIPE should now be able to read the file. | ||||||||
| Changed: | ||||||||
| < < | Mac OS 10.8 Mountain Lion requires Java 7 to open WebStart applications | |||||||
| > > | Cannot run WebStart applications on Mac OS Lion or Mountain Lion because of security settings | |||||||
| Changed: | ||||||||
| < < | Mac OS 10.8 "Mountain Lion" requires Java Runtime Environment (JRE) 7 to open WebStart applications. WebStart applications that can be opened from within HIPE include the HSA User Interface, Aladin, VOSpec and so on. When a WebStart application is started and version 7 of the JRE is not installed, a warning with instructions is shown. Follow the instructions provided and try again. | |||||||
| > > | WebStart applications that can be opened from within HIPE include the HSA User Interface, Aladin, VOSpec and so on. When trying to open one of such applications, a window like the following may appear:
This is caused by the security settings of the Gatekeeper feature of Mac OS. For more information about Gatekeeper, see the Apple support website.
To allow a WebStart application that is blocked, change the Allow applications downloaded from option in Gatekeeper from Mac App Store to one of the two less restrictive options. If the application has a valid certificate, the Mac App Store and identified developers option will suffice. Otherwise you will need to select the Anywhere option. | |||||||
"Invalid context" errors on Mac OS X Lion | ||||||||
| Line: 449 to 455 | ||||||||
| ||||||||
| Added: | ||||||||
| > > |
| |||||||
| ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
<-- ANALYTICS CODE - DO NOT EDIT --> <-- Google Analytics script BEGIN --> <-- Google Analytics script END --> | ||||||||
| Line: 22 to 22 | ||||||||
Known issues in HIPE 10.0 | ||||||||
| Added: | ||||||||
| > > | Pools unreadable with Unknown format version: -11 errorIf you installed a developer build of HIPE 10 between 10.0.2069 and 10.0.2674 and modified any of your pools you will find those pools are no longer readable in any other HIPE version; when trying to load a pool withgetObservation you will get the following error message:
herschel.ia.task.TaskException: Error processing getObservation task: Unknown format version: -11See the Data Analysis Guide for a recovery procedure. You can download from this page the first and second script mentioned in the procedure. Change the extension from .py.txt to .py after downloading. | |||||||
The WCS explorer for cubes does not work with PACS and SPIRE cubesThe WCS explorer does not work on cubes for whichImageIndex is used to specify the wavescale axis. This is true for SPIRE and PACS cubes. If crpix3, crval3 and cdelt3 are used instead, the WCS explorer works. To be fixed in HIPE 11. | ||||||||
| Line: 439 to 449 | ||||||||
| ||||||||
| Added: | ||||||||
| > > |
| |||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
<-- ANALYTICS CODE - DO NOT EDIT --> <-- Google Analytics script BEGIN --> <-- Google Analytics script END --> | ||||||||
| Line: 22 to 22 | ||||||||
Known issues in HIPE 10.0 | ||||||||
| Added: | ||||||||
| > > | The WCS explorer for cubes does not work with PACS and SPIRE cubesThe WCS explorer does not work on cubes for whichImageIndex is used to specify the wavescale axis. This is true for SPIRE and PACS cubes. If crpix3, crval3 and cdelt3 are used instead, the WCS explorer works. To be fixed in HIPE 11. | |||||||
Issues with reading text files from SExtractor or TopcatWhile reading files from SExtractor or Topcat you may encounter the following issues: | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
<-- ANALYTICS CODE - DO NOT EDIT --> <-- Google Analytics script BEGIN --> <-- Google Analytics script END --> | ||||||||
| Line: 137 to 137 | ||||||||
| Fixed in HIPE 9.2. | ||||||||
| Deleted: | ||||||||
| < < | Known issues in HIPE 8.3None known in addition to those listed for HIPE 8.2.Known issues in HIPE 8.2
ScanSpeedMask = frames.getMask('ScanSpeedMask')[0,0,:]
indexSpeed = ScanSpeedMask.where(ScanSpeedMask==False)
map = photProject(frames.select(indexSpeed), calTree=calTree,calibration=True)
This bug shall be corrected in the next Hipe versions.
Known issues in HIPE 8.1None known in addition to those listed for HIPE 8.0.Known issues in HIPE 8.0
java.vm.options = -Dsun.java2d.opengl=true ![]() | |||||||
Older HIPE versionsKnown issues for older HIPE versions are listed in a separate page. | ||||||||
| Line: 379 to 316 | ||||||||
| HIPE should now be able to read the file. | ||||||||
| Added: | ||||||||
| > > | Mac OS 10.8 Mountain Lion requires Java 7 to open WebStart applicationsMac OS 10.8 "Mountain Lion" requires Java Runtime Environment (JRE) 7 to open WebStart applications. WebStart applications that can be opened from within HIPE include the HSA User Interface, Aladin, VOSpec and so on. When a WebStart application is started and version 7 of the JRE is not installed, a warning with instructions is shown. Follow the instructions provided and try again. | |||||||
"Invalid context" errors on Mac OS X LionWhen you start HIPE form a Terminal window on Mac OS X Lion, you may see errors such as these: | ||||||||
| Line: 492 to 433 | ||||||||
<-- END OF COMMENT BOX CODE --> | ||||||||
| Deleted: | ||||||||
| < < |
| |||||||
| ||||||||
| Deleted: | ||||||||
| < < |
| |||||||
| ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
<-- ANALYTICS CODE - DO NOT EDIT --> <-- Google Analytics script BEGIN --> <-- Google Analytics script END --> | ||||||||
| Line: 135 to 135 | ||||||||
| convertL1ToScanam(frames,assignRaDec=False) | ||||||||
| Added: | ||||||||
| > > | Fixed in HIPE 9.2. | |||||||
Known issues in HIPE 8.3None known in addition to those listed for HIPE 8.2. | ||||||||
| Line: 490 to 492 | ||||||||
<-- END OF COMMENT BOX CODE --> | ||||||||
| Deleted: | ||||||||
| < < |
| |||||||
| ||||||||
| Added: | ||||||||
| > > |
| |||||||
| ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
<-- ANALYTICS CODE - DO NOT EDIT --> <-- Google Analytics script BEGIN --> <-- Google Analytics script END --> | ||||||||
| Line: 39 to 39 | ||||||||
| ||||||||
| Added: | ||||||||
| > > | Known issues in HIPE 9.2Issues with computePVMap taskThe computePVMap task has the following issues:
| |||||||
Known issues in HIPE 9.1None known in addition to those listed for HIPE 9.0. | ||||||||
| Line: 481 to 490 | ||||||||
<-- END OF COMMENT BOX CODE --> | ||||||||
| Added: | ||||||||
| > > |
| |||||||
| ||||||||
| Deleted: | ||||||||
| < < |
| |||||||
| ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
<-- ANALYTICS CODE - DO NOT EDIT --> <-- Google Analytics script BEGIN --> <-- Google Analytics script END --> | ||||||||
| Line: 22 to 22 | ||||||||
Known issues in HIPE 10.0 | ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > | Issues with reading text files from SExtractor or TopcatWhile reading files from SExtractor or Topcat you may encounter the following issues:
Format change for exported variablesThe file format of variables exported with File --> Session --> Export has changed in HIPE 10. This means that HIPE 10 will not be able to read session variables exported with HIPE 9, and vice-versa.If you exported variables with HIPE 9 or a previous version, follow this workaround to read them in HIPE 10: | |||||||
| ||||||||
| Line: 36 to 45 | ||||||||
Known issues in HIPE 9.0 | ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > | Performance issues of convolution task with NaN valuesThe performance of the imageConvolution task is severely degraded when NaN values are found in input data. HIPE 8.3 is not affected by this problem. Fixed in HIPE 9.1. | |||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > | Performance issues with very large images | |||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > | Images larger than about 100 MB in FITS format can still take over a minute to load. During such time HIPE is unresponsive. Image analysis operations, such as cropping and adding contours, also take a long time on large images.
Problem with PACS background normalization scriptTheChopNodBackgroundNormalizationRange interactive pipeline script (Pipelines --> PACS --> Spectrometer --> Chopper large range scan SED --> Background Normalization) is missing a definition of the variable target. After loading the observation, assuming it is stored in a variable called obs, you can define the missing target variable as follows: | |||||||
target = obs.meta["object"].value.replace(" ","_")
| ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > | PACS task specFlatFieldLine problem with NaN valuesThespecFlatFieldLine task cannot handle NaNs in the fluxes of PacsCube products. This affected one observation as far as we tested. If you encounter this problem then you can mask the NaNs by running the function shown below. Copy and paste the function code in a new Jython script window in the Editor view of HIPE, then click the green double arrow icon in the HIPE toolbar to run the script. After that you can call the function from the Console view, passing the variable contaning your cube as argument: addInvalidMask(myCube). | |||||||
def addInvalidMask(slicedCube):
for i in range(0,slicedCube.numberOfSlices): | ||||||||
| Line: 57 to 74 | ||||||||
| slicedCube.replace(i,cube) | ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > | HIPE hangs when pressing the activate/deactivate button in the mask panel of the Spectrum Explorer PACS extensionsThis button is enabled only when you change the state of one or more masks. Fixed in HIPE 9.1.<-- PACS-4626 --> | |||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > | Image analysis tasks start only from Applicable sectionImage analysis tasks will open only from the Applicable folder of the Tasks view. These tasks will not open when selected from the All or By Category folders. Note that you must select an image variable in the Variables view for the Applicable folder to be filled with the available tasks. To be fixed in HIPE 10. The problem affects the following tasks: | |||||||
| ||||||||
| Line: 71 to 92 | ||||||||
| ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > | PV diagrams created with computePVMap on HIFI cubes cannot be easily viewedHIFI cubes have in general a small number of rows and columns, while the spectral dimension is rather large (thousands of channels). The PV map is very narrow in the x direction and really wide in the y-direction, so that it does not fit in the Spectrum panel. When displaying the y-axis values, at its smaller zoom, only a small number of channels can be seen. Workaround: open the variable created from the variables pane and use the full Display/Image Viewer. | |||||||
<-- use the old Cube Spectrum Analysis Toolbox, still available in HIPE 9. Legacy documentation is available in Appendix C of the Data Analysis Guide. For position-velocity diagrams, see subsection C.6.8.1.--> | ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > | HIPE crash linked to JAMA (Java Matrix) libraryHIPE may crash without warning when executing parts of the bundled JAMA library. If you experience a sudden crash when running a script, this may be the cause, even if there are no obvious references to matrices in the script. Take the following steps to prevent the crash from happening: | |||||||
| ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > | Problem with transpose taskIn some cases the transpose task does not convert correctly the WCS of the input image. This problem occurs only when the WCS of the image defines the rotation angle (CROTA2). When the transformation matrix (PCx_y or CDx_y) is used, the problem does not occur. To be fixed in HIPE 10.Velocity map creation in Legacy Cube Spectrum Analysis Toobox (CSAT) failsThe creation of velocity maps with the Legacy CSAT fails; the task will hang without an error message. CSAT is no longer supported and the new cube toolbox, which uses an improved algorithm for velocity map making, should be used instead. See 6.8.3 in the Herschel Data Analysis Guide for information about using the new cube toolbox.Flag set in HIFI's flagTool task do not appear to be used by the fitBaseline taskThis is a display issue only, the flags set by flagTool are, in fact, used. | |||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > | PACS specific: | |||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > | convertL1ToScanam fails because of a missing import for the calibration tree, when assignRaDec is set to True. The work around solution is : | |||||||
| Deleted: | ||||||||
| < < |
| |||||||
calTree = getCalTree(time=frames.startDate)
frames=photAssignRaDec(frames,calTree=calTree) | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
<-- ANALYTICS CODE - DO NOT EDIT --> <-- Google Analytics script BEGIN --> <-- Google Analytics script END --> | ||||||||
| Line: 335 to 335 | ||||||||
| HIPE should now be able to read the file. | ||||||||
| Added: | ||||||||
| > > | "Invalid context" errors on Mac OS X LionWhen you start HIPE form a Terminal window on Mac OS X Lion, you may see errors such as these:java[40745] <Error>: CGContextGetCTM: invalid contextThese errors are harmless and can be safely ignored. | |||||||
Jython bug when comparing NaN values with numbersJython behaves differently from Python when comparingNaN values with numbers. | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
<-- ANALYTICS CODE - DO NOT EDIT --> <-- Google Analytics script BEGIN --> <-- Google Analytics script END --> <-- END OF ANALYTICS CODE --> HIPE known issues | ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| ||||||||
| Changed: | ||||||||
| < < | Installation issues | |||||||
| > > | Installation and uninstallation issues | |||||||
| ||||||||
| Added: | ||||||||
| > > |
| |||||||
Known issues in HIPE 10.0 | ||||||||
| Line: 217 to 220 | ||||||||
| This error is probably due to a bug in the Java Virtual Machine, and has so far been found only on Windows XP 32 bit. | ||||||||
| Added: | ||||||||
| > > | I get startup messages about missing HIFI/PACS/SPIRE modules. Is that serious?You are probably referring to messages such as the following (for HIFI; messages for PACS and SPIRE are the same):
Import "from herschel.hifi.all import *" returns:
Import Error -> No module named hifi
Such messages are harmless and just reflect the fact that you have not installed the software related to the specified instruments. | |||||||
General Help System issuesThe help does not work anymore! What's wrong? | ||||||||
| Line: 239 to 253 | ||||||||
Yes, via the hipe_help command, which resides in the apps folder in your HIPE installation. The hipe_help command will start a standalone Help System in a window called Yet Another JAva Help System. Press the Display button to open the Help initial page in your default browser. | ||||||||
| Added: | ||||||||
| > > | The Help System opens in my web browser. Does it mean I need to be connected to the Internet?No, the Help System resides on your computer and does not need Internet connection, except of course for links to online resources, such as YouTube videos and pages hosted on the Herschel Wiki website, including the What's New and Known Issues documents. | |||||||
Why does searching the documentation take such a long time?When you execute the first search with a new HIPE version, HIPE has to index the contents of the documentation. This can take up to several minutes, depending on the performance of your system. Indexing of the documentation is only done for the first search. Subsequent searches will be much faster. We are investigating ways to include pre-built indexes in the documentation shipped with HIPE, so you will not have to wait for the results of your first search. | ||||||||
| Deleted: | ||||||||
| < < | The Help System opens in my web browser. Does it mean I need to be connected to the Internet?No, the Help System resides on your computer and does not need Internet connection, except for the What's New document, which is hosted on the Herschel Wiki website. | |||||||
Why is the HIPE Help System suddenly unable to connect to any help page?The Help System relies on a local web server to display help pages. If you close the application that started the web server, the server will shut down as well: | ||||||||
| Line: 280 to 294 | ||||||||
| ||||||||
| Added: | ||||||||
| > > | Herschel Science Archive issuesI have downloaded FITS files in a tar archive from the HSA, but they are corrupted. How can I fix them?You may have used WinZip under Windows. WinZip has an option called TAR file smart CR/LF conversion, in the Miscellaneous tab of the Configuration dialogue window (at least up to version 15.0), that is enabled by default and causes the corruption. Disable the option to solve this problem. You can also use other software such as 7-Zip.In the HSA user interface I can query and select observations, but I do not get the option in the HSA to pass the data to HIPE, or in HIPE to load the selected products. Why?If you are using Windows, the problem might be that you instructed your browser to auto-detect proxy settings. In Windows this is a system-wide setting which affects any application connecting to the Internet, including HIPE. You can change proxy settings for HIPE by following the instructions in the HIPE Owner's Guide.When I click Send to external Application in the HSA interface, nothing seems to happen. What is going on?The data is being transferred in the background. Clicking Send to external Application should bring to the front the main HIPE window, which will tell you that data is indeed being received. In some cases however the HIPE window does not appear. Bring it to the front manually to follow the progress of your action.When I try to retrieve data from the HSA I get an error message in the console about an invalid magic number for FITS file. What is going on?The reason is that the "data" being downloaded is in reality a small file containing an error message. Two issues have been shown to cause this problem:
| |||||||
Other issues | ||||||||
| Added: | ||||||||
| > > | HIPE crashed/froze! What do I do?If you cannot find a solution in this document, you may have found a bug in HIPE. Please report it by opening a Helpdesk ticket. If the system produced a dump file when the crash happened, make sure to include it in your ticket. For more information about dump files and where to look for them, see the HIPE Owner's Guide. | |||||||
Cannot open a FITS file created by HIPEIf you export a FITS file from HIPE and modify it with an external program, HIPE may not be able to import it anymore. If this happens, follow these steps: | ||||||||
| Line: 331 to 374 | ||||||||
hcss.ia.pal.pool.lstore.lock = simple | ||||||||
| Changed: | ||||||||
| < < | See the HIPE Owner's Guide for information on how to set properties. | |||||||
| > > | See the HIPE Owner's Guide for information on how to set properties. | |||||||
Why do I get a ClassCastException when trying to save an observation with the saveObservation command? | ||||||||
| Line: 345 to 388 | ||||||||
| ||||||||
| Added: | ||||||||
| > > | I get an
Add or edit the following property in your | |||||||
<-- COMMENT BOX CODE - DO NOT EDIT --> | ||||||||
| Line: 362 to 438 | ||||||||
<-- END OF COMMENT BOX CODE --> | ||||||||
| Deleted: | ||||||||
| < < |
| |||||||
| ||||||||
| Added: | ||||||||
| > > |
| |||||||
| ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
<-- ANALYTICS CODE - DO NOT EDIT --> <-- Google Analytics script BEGIN --> <-- Google Analytics script END --> | ||||||||
| Line: 27 to 27 | ||||||||
| ||||||||
| Added: | ||||||||
| > > | Known issues in HIPE 9.1None known in addition to those listed for HIPE 9.0. | |||||||
Known issues in HIPE 9.0 | ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| ||||||||
| Line: 50 to 54 | ||||||||
| slicedCube.replace(i,cube) | ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| ||||||||
| Line: 72 to 76 | ||||||||
| ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| ||||||||
| Line: 358 to 362 | ||||||||
<-- END OF COMMENT BOX CODE --> | ||||||||
| Added: | ||||||||
| > > |
| |||||||
| ||||||||
| Deleted: | ||||||||
| < < |
| |||||||
| ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
| Added: | ||||||||
| > > | <-- ANALYTICS CODE - DO NOT EDIT --> <-- Google Analytics script BEGIN --> <-- Google Analytics script END --> <-- END OF ANALYTICS CODE --> | |||||||
HIPE known issues
| ||||||||
| Line: 49 to 52 | ||||||||
| ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
<-- use the old Cube Spectrum Analysis Toolbox, still available in HIPE 9. Legacy documentation is available in Appendix C of the Data Analysis Guide. For position-velocity diagrams, see subsection C.6.8.1.--> | ||||||||
| Line: 348 to 361 | ||||||||
| ||||||||
| Added: | ||||||||
| > > |
| |||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 14 to 14 | ||||||||
| ||||||||
| Added: | ||||||||
| > > | Known issues in HIPE 10.0
| |||||||
Known issues in HIPE 9.0
| ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 255 to 255 | ||||||||
Other issues | ||||||||
| Added: | ||||||||
| > > | Cannot open a FITS file created by HIPEIf you export a FITS file from HIPE and modify it with an external program, HIPE may not be able to import it anymore. If this happens, follow these steps:
| |||||||
Jython bug when comparing NaN values with numbersJython behaves differently from Python when comparingNaN values with numbers. | ||||||||
| Line: 325 to 335 | ||||||||
<-- END OF COMMENT BOX CODE --> | ||||||||
| Deleted: | ||||||||
| < < |
| |||||||
| ||||||||
| Added: | ||||||||
| > > |
| |||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 6 to 6 | ||||||||
| ||||||||
| Deleted: | ||||||||
| < < |
| |||||||
Installation issues | ||||||||
| Line: 243 to 241 | ||||||||
How can I provide feedback/requests regarding HIPE documentation? | ||||||||
| Changed: | ||||||||
| < < | For informal feedback, click on the envelope icon on the top toolbar of any help page. This opens a new message in your email client, where you can add your feedback. If you want your issue to be officially tracked and supported, please raise a ticket with the Helpdesk of the Herschel Science Centre. | |||||||
| > > | You can leave a comment using the box at the bottom of any documentation page in the HIPE Help System. You must be connected to the Internet to view and submit comments.
Alternatively, you can click the envelope icon on the top toolbar of any help page. This opens a new message in your email client, where you can add your feedback.
If you want your issue to be officially tracked and supported, please raise a ticket with the Helpdesk of the Herschel Science Centre.
Other help issues
| |||||||
Other issues | ||||||||
| Line: 317 to 325 | ||||||||
<-- END OF COMMENT BOX CODE --> | ||||||||
| Added: | ||||||||
| > > |
| |||||||
| ||||||||
| Deleted: | ||||||||
| < < |
| |||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| ||||||||
| Line: 10 to 10 | ||||||||
| Added: | ||||||||
| > > | Installation issues
| |||||||
Known issues in HIPE 9.0
| ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 47 to 47 | ||||||||
| ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 12 to 12 | ||||||||
Known issues in HIPE 9.0 | ||||||||
| Added: | ||||||||
| > > |
| |||||||
| ||||||||
| Line: 309 to 311 | ||||||||
<-- END OF COMMENT BOX CODE --> | ||||||||
| Deleted: | ||||||||
| < < |
| |||||||
| ||||||||
| Added: | ||||||||
| > > |
| |||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 12 to 12 | ||||||||
Known issues in HIPE 9.0 | ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| ||||||||
| Line: 309 to 309 | ||||||||
<-- END OF COMMENT BOX CODE --> | ||||||||
| Added: | ||||||||
| > > |
| |||||||
| ||||||||
| Deleted: | ||||||||
| < < |
| |||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 12 to 12 | ||||||||
Known issues in HIPE 9.0 | ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 12 to 12 | ||||||||
Known issues in HIPE 9.0 | ||||||||
| Added: | ||||||||
| > > |
| |||||||
target = obs.meta["object"].value.replace(" ","_") | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 12 to 12 | ||||||||
Known issues in HIPE 9.0 | ||||||||
| Added: | ||||||||
| > > |
target = obs.meta["object"].value.replace(" ","_")
def addInvalidMask(slicedCube):
for i in range(0,slicedCube.numberOfSlices):
cube = slicedCube.get(i)
invalid = IS_NAN(cube.flux)
if not cube.containsMask("INVALID"):
cube.addMask("INVALID","Invalid signal values")
cube.setMask("INVALID",invalid)
slicedCube.replace(i,cube)
| |||||||
| ||||||||
| Line: 290 to 307 | ||||||||
<-- END OF COMMENT BOX CODE --> | ||||||||
| Deleted: | ||||||||
| < < |
| |||||||
| ||||||||
| Added: | ||||||||
| > > |
| |||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 32 to 32 | ||||||||
| ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
calTree = getCalTree(time=frames.startDate)
frames=photAssignRaDec(frames,calTree=calTree)
convertL1ToScanam(frames,assignRaDec=False)
| |||||||
Known issues in HIPE 8.3 | ||||||||
| Line: 45 to 47 | ||||||||
| ||||||||
| Changed: | ||||||||
| < < | == | |||||||
| > > | ||||||||
| ScanSpeedMask? = frames.getMask('ScanSpeedMask')[0,0,:] indexSpeed = ScanSpeedMask?.where(ScanSpeedMask?==False) map = photProject(frames.select(indexSpeed), calTree=calTree,calibration=True) | ||||||||
| Changed: | ||||||||
| < < | == | |||||||
| > > | ||||||||
This bug shall be corrected in the next Hipe versions.
Known issues in HIPE 8.1 | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 31 to 31 | ||||||||
| ||||||||
| Changed: | ||||||||
| < < |
from herschel.pacs.cal.all import getCalTree | |||||||
| > > |
| |||||||
Known issues in HIPE 8.3 | ||||||||
| Line: 45 to 45 | ||||||||
| ||||||||
| Changed: | ||||||||
| < < | ||||||||
| > > | == | |||||||
| ScanSpeedMask? = frames.getMask('ScanSpeedMask')[0,0,:] indexSpeed = ScanSpeedMask?.where(ScanSpeedMask?==False) map = photProject(frames.select(indexSpeed), calTree=calTree,calibration=True) | ||||||||
| Changed: | ||||||||
| < < | ||||||||
| > > | == | |||||||
This bug shall be corrected in the next Hipe versions.
Known issues in HIPE 8.1 | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 30 to 30 | ||||||||
| ||||||||
| Added: | ||||||||
| > > |
from herschel.pacs.cal.all import getCalTree | |||||||
Known issues in HIPE 8.3None known in addition to those listed for HIPE 8.2. | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 12 to 12 | ||||||||
Known issues in HIPE 9.0 | ||||||||
| Added: | ||||||||
| > > |
| |||||||
| ||||||||
| Line: 280 to 282 | ||||||||
<-- END OF COMMENT BOX CODE --> | ||||||||
| Deleted: | ||||||||
| < < |
| |||||||
| ||||||||
| Added: | ||||||||
| > > |
| |||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 14 to 14 | ||||||||
| ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
<-- use the old Cube Spectrum Analysis Toolbox, still available in HIPE 9. Legacy documentation is available in Appendix C of the Data Analysis Guide. For position-velocity diagrams, see subsection C.6.8.1.--> | |||||||
| ||||||||
| Line: 279 to 280 | ||||||||
<-- END OF COMMENT BOX CODE --> | ||||||||
| Deleted: | ||||||||
| < < |
| |||||||
| ||||||||
| Added: | ||||||||
| > > |
| |||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 23 to 23 | ||||||||
| ||||||||
| Added: | ||||||||
| > > |
| |||||||
Known issues in HIPE 8.3None known in addition to those listed for HIPE 8.2. | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 12 to 12 | ||||||||
Known issues in HIPE 9.0 | ||||||||
| Added: | ||||||||
| > > |
| |||||||
| ||||||||
| Line: 273 to 275 | ||||||||
<-- END OF COMMENT BOX CODE --> | ||||||||
| Added: | ||||||||
| > > |
| |||||||
| ||||||||
| Deleted: | ||||||||
| < < |
| |||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 21 to 21 | ||||||||
| ||||||||
| Added: | ||||||||
| > > | Known issues in HIPE 8.3None known in addition to those listed for HIPE 8.2. | |||||||
Known issues in HIPE 8.2
| ||||||||
| Line: 269 to 273 | ||||||||
<-- END OF COMMENT BOX CODE --> | ||||||||
| Deleted: | ||||||||
| < < |
| |||||||
| ||||||||
| Added: | ||||||||
| > > |
| |||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 12 to 12 | ||||||||
Known issues in HIPE 9.0 | ||||||||
| Added: | ||||||||
| > > |
| |||||||
| ||||||||
| Line: 267 to 269 | ||||||||
<-- END OF COMMENT BOX CODE --> | ||||||||
| Added: | ||||||||
| > > |
| |||||||
| ||||||||
| Deleted: | ||||||||
| < < |
| |||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 17 to 17 | ||||||||
| ||||||||
| Added: | ||||||||
| > > |
| |||||||
Known issues in HIPE 8.2
| ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 12 to 12 | ||||||||
Known issues in HIPE 9.0 | ||||||||
| Deleted: | ||||||||
| < < |
| |||||||
| ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 12 to 12 | ||||||||
Known issues in HIPE 9.0 | ||||||||
| Added: | ||||||||
| > > |
| |||||||
| ||||||||
| Line: 19 to 21 | ||||||||
Known issues in HIPE 8.2 | ||||||||
| Added: | ||||||||
| > > |
| |||||||
ScanSpeedMask = frames.getMask('ScanSpeedMask')[0,0,:] | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 33 to 33 | ||||||||
Known issues in HIPE 8.0 | ||||||||
| Added: | ||||||||
| > > |
| |||||||
| ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 10 to 10 | ||||||||
| Added: | ||||||||
| > > | Known issues in HIPE 9.0
| |||||||
Known issues in HIPE 8.2
| ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 237 to 237 | ||||||||
| ||||||||
| Added: | ||||||||
| > > | <-- COMMENT BOX CODE - DO NOT EDIT -->blog comments powered by Disqus <-- END OF COMMENT BOX CODE --> | |||||||
| ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 139 to 139 | ||||||||
| ||||||||
| Added: | ||||||||
| > > |
| |||||||
| ||||||||
| Line: 169 to 170 | ||||||||
| Note that when the Help System stops, any browser window or tab showing help pages will remain open, but links on them will not work anymore. | ||||||||
| Deleted: | ||||||||
| < < | Why are some code examples slightly different in the PDF and HTML versions of the documentation?Code examples and commands in the PDF versions of the manuals sometimes have extra dashes added (for instance,-XX:MaxPermSize=256m becomes --XX:MaxPermSize=256m). If an example or a command does not work as expected, try checking the HTML version of the documentation, which is not affected by this bug. | |||||||
Why are several important packages missing from the Javadoc?You are probably looking at the static Javadoc located in thedoc/api/ folder of your HIPE installation. The complete Javadoc can now be accessed from the HIPE Help System by clicking on HCSS Developer's Reference Manual (API) in the Developer Reference section. The plan is to remove the static version of the Javadoc completely. | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 12 to 12 | ||||||||
Known issues in HIPE 8.2 | ||||||||
| Changed: | ||||||||
| < < | None known in addition to those listed for HIPE 8.0. | |||||||
| > > |
ScanSpeedMask = frames.getMask('ScanSpeedMask')[0,0,:]
indexSpeed = ScanSpeedMask.where(ScanSpeedMask==False)
map = photProject(frames.select(indexSpeed), calTree=calTree,calibration=True)
This bug shall be corrected in the next Hipe versions. | |||||||
Known issues in HIPE 8.1 | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 10 to 10 | ||||||||
| Added: | ||||||||
| > > | Known issues in HIPE 8.2None known in addition to those listed for HIPE 8.0. | |||||||
Known issues in HIPE 8.1None known in addition to those listed for HIPE 8.0. | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 55 to 55 | ||||||||
![]() | ||||||||
| Deleted: | ||||||||
| < < | Known issues in HIPE 7.3None known in addition to those listed for HIPE 7.0.Known issues in HIPE 7.2None known in addition to those listed for HIPE 7.0.Known issues in HIPE 7.1None known in addition to those listed for HIPE 7.0.Known issues in HIPE 7.0
herschel.share.util.ConfigurationException: Failed to locate product in cacheTo solve the problem, try one or more of the following:
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" | |||||||
Older HIPE versionsKnown issues for older HIPE versions are listed in a separate page. | ||||||||
| Line: 227 to 177 | ||||||||
Other issues | ||||||||
| Added: | ||||||||
| > > | Jython bug when comparing NaN values with numbersJython behaves differently from Python when comparingNaN values with numbers.
In Python 2.4 or 2.5:
nan = float("nan")
print 0 < nan
# False
print 0 > nan
# False
In Jython 2.5.2:
nan = float("nan")
print 0 < nan
# False
print 0 > nan
# True
An issue has been opened on the Jython bug tracker. | |||||||
"Can't connect to X11" error when using the jylaunch commandExecuting a script outside HIPE with thejylaunch command may fail with a java.lang.InternalError: Can't connect to X11 window server error. This may happen even if the script does not open any graphical window, since it may indirectly call components that require an X11 server. The workaround is to run the script with the command jylaunch -Djava.awt.headless=true instead of just jylaunch. | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 10 to 10 | ||||||||
| Added: | ||||||||
| > > | Known issues in HIPE 8.1None known in addition to those listed for HIPE 8.0. | |||||||
Known issues in HIPE 8.0
| ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 12 to 12 | ||||||||
Known issues in HIPE 8.0 | ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 12 to 12 | ||||||||
Known issues in HIPE 8.0 | ||||||||
| Added: | ||||||||
| > > |
| |||||||
| ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 12 to 12 | ||||||||
Known issues in HIPE 8.0 | ||||||||
| Added: | ||||||||
| > > |
| |||||||
| ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| ||||||||
| Line: 247 to 249 | ||||||||
| ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 37 to 37 | ||||||||
| ||||||||
| Added: | ||||||||
| > > |
java.vm.options = -Dsun.java2d.opengl=true ![]() | |||||||
Known issues in HIPE 7.3None known in addition to those listed for HIPE 7.0. | ||||||||
| Line: 133 to 141 | ||||||||
| Try running HIPE after modifying the values until it successfully starts. | ||||||||
| Added: | ||||||||
| > > |
| |||||||
HIPE cannot start:
The terminal/command window from which you invoke HIPE shows a | ||||||||
| Line: 237 to 247 | ||||||||
| ||||||||
| Added: | ||||||||
| > > |
| |||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 12 to 12 | ||||||||
Known issues in HIPE 8.0 | ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 12 to 12 | ||||||||
Known issues in HIPE 8.0 | ||||||||
| Added: | ||||||||
| > > |
| |||||||
| ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 16 to 16 | ||||||||
| ||||||||
| Added: | ||||||||
| > > |
| |||||||
| ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 18 to 18 | ||||||||
| ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 162 to 162 | ||||||||
Is there a way to open the HIPE Help System without starting HIPE? | ||||||||
| Changed: | ||||||||
| < < | Yes, via the show_help command, which resides in the apps folder in your HIPE installation. The show_help command will start a standalone Help System in a window called Yet Another JAva Help System. Press the Display button to open the Help initial page in your default browser. | |||||||
| > > | Yes, via the hipe_help command, which resides in the apps folder in your HIPE installation. The hipe_help command will start a standalone Help System in a window called Yet Another JAva Help System. Press the Display button to open the Help initial page in your default browser.
Why does searching the documentation take such a long time?When you execute the first search with a new HIPE version, HIPE has to index the contents of the documentation. This can take up to several minutes, depending on the performance of your system. Indexing of the documentation is only done for the first search. Subsequent searches will be much faster. We are investigating ways to include pre-built indexes in the documentation shipped with HIPE, so you will not have to wait for the results of your first search. | |||||||
The Help System opens in my web browser. Does it mean I need to be connected to the Internet? | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 18 to 18 | ||||||||
| ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 16 to 16 | ||||||||
| ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| ||||||||
| Line: 27 to 27 | ||||||||
| ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
Known issues in HIPE 7.3 | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 12 to 12 | ||||||||
Known issues in HIPE 8.0 | ||||||||
| Added: | ||||||||
| > > |
| |||||||
| ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 25 to 25 | ||||||||
| ||||||||
| Added: | ||||||||
| > > |
| |||||||
Known issues in HIPE 7.3None known in addition to those listed for HIPE 7.0. | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 14 to 14 | ||||||||
| ||||||||
| Added: | ||||||||
| > > |
| |||||||
| ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 21 to 21 | ||||||||
![]() | ||||||||
| Added: | ||||||||
| > > |
| |||||||
Known issues in HIPE 7.3None known in addition to those listed for HIPE 7.0. | ||||||||
| Line: 52 to 54 | ||||||||
| 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. | ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
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: | ||||||||
| Line: 213 to 215 | ||||||||
| ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 12 to 12 | ||||||||
Known issues in HIPE 8.0 | ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
![]() | |||||||
Known issues in HIPE 7.3 | ||||||||
| Line: 207 to 214 | ||||||||
| ||||||||
| Added: | ||||||||
| > > |
| |||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 12 to 12 | ||||||||
Known issues in HIPE 8.0 | ||||||||
| Changed: | ||||||||
| < < | Upgrade to Jython 2.5: Starting from version 8.0, HIPE will include a new version of Jython. You may have to adapt your scripts for them to work with the new version. See this page for the details. | |||||||
| > > |
| |||||||
Known issues in HIPE 7.3 | ||||||||
| Line: 45 to 45 | ||||||||
| 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. | ||||||||
| Added: | ||||||||
| > > |
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" | |||||||
Older HIPE versionsKnown issues for older HIPE versions are listed in a separate page. | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 45 to 45 | ||||||||
| 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. | ||||||||
| Changed: | ||||||||
| < < | Known issues in HIPE 6.1 | |||||||
| > > | Older HIPE versions | |||||||
| Changed: | ||||||||
| < < | None known in addition to those listed for HIPE 6.0.
Known issues in HIPE 6.0Core
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.
hipe.props file:
java.vm.options = -Duser.language=en -Duser.region=enThe 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.
<-- HCSS-11540 -->
p in the Variables view.
Steps to reproduce:
31-Jan-11 10:00:17.797 WARNING NavigatorView: Error checking file /bin: java.util.concurrent.TimeoutExceptionWorkaround: set the property hcss.hipe.refreshPeriod as follows:
hcss.hipe.refreshPeriod = 3600000See the HIPE Owner's Guide for information on how to set properties. Known issues in HIPE 5.3None known in addition to those listed for previous 5.x versions.Known issues in HIPE 5.2None known in addition to those listed for previous 5.x versions.Known issues in HIPE 5.1Issues in previous 5.x versions may still apply to this version.Core
31-Jan-11 10:00:17.797 WARNING NavigatorView: Error checking file /bin: java.util.concurrent.TimeoutExceptionWorkaround: set the property hcss.hipe.refreshPeriod as follows:
hcss.hipe.refreshPeriod = 3600000See the HIPE Owner's Guide for information on how to set properties.
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)
...
Known issues in HIPE 5.0Core
HIFI
PACS
SPIRE
<-- | |||||||
| > > | Known issues for older HIPE versions are listed in a separate page. | |||||||
General HIPE startup issues | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 14 to 14 | ||||||||
| Upgrade to Jython 2.5: Starting from version 8.0, HIPE will include a new version of Jython. You may have to adapt your scripts for them to work with the new version. See this page for the details. | ||||||||
| Added: | ||||||||
| > > | Known issues in HIPE 7.3None known in addition to those listed for HIPE 7.0. | |||||||
Known issues in HIPE 7.2None known in addition to those listed for HIPE 7.0. | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 14 to 14 | ||||||||
| Upgrade to Jython 2.5: Starting from version 8.0, HIPE will include a new version of Jython. You may have to adapt your scripts for them to work with the new version. See this page for the details. | ||||||||
| Added: | ||||||||
| > > | Known issues in HIPE 7.2None known in addition to those listed for HIPE 7.0. | |||||||
Known issues in HIPE 7.1None known in addition to those listed for HIPE 7.0. | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 14 to 14 | ||||||||
| Upgrade to Jython 2.5: Starting from version 8.0, HIPE will include a new version of Jython. You may have to adapt your scripts for them to work with the new version. See this page for the details. | ||||||||
| Added: | ||||||||
| > > | Known issues in HIPE 7.1None known in addition to those listed for HIPE 7.0. | |||||||
Known issues in HIPE 7.0
| ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 29 to 29 | ||||||||
| ||||||||
| Added: | ||||||||
| > > |
| |||||||
Known issues in HIPE 6.1None known in addition to those listed for HIPE 6.0. | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 16 to 16 | ||||||||
Known issues in HIPE 7.0 | ||||||||
| Changed: | ||||||||
| < < | None known at the moment. | |||||||
| > > |
herschel.share.util.ConfigurationException: Failed to locate product in cacheTo solve the problem, try one or more of the following:
| |||||||
Known issues in HIPE 6.1 | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 141 to 141 | ||||||||
| ||||||||
| Changed: | ||||||||
| < < | Known issues in HIPE 4.0 | |||||||
| > > | ||||||||
General HIPE startup issues | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 16 to 16 | ||||||||
Known issues in HIPE 7.0 | ||||||||
| Changed: | ||||||||
| < < | In preparation. | |||||||
| > > | None known at the moment. | |||||||
Known issues in HIPE 6.1 | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
| Changed: | ||||||||
| < < | HIPE known issues | |||||||
| > > | HIPE known issues
| |||||||
| ||||||||
| Line: 22 to 24 | ||||||||
Known issues in HIPE 6.0 | ||||||||
| Changed: | ||||||||
| < < | Core | |||||||
| > > | Core | |||||||
| ||||||||
| Line: 80 to 82 | ||||||||
| Issues in previous 5.x versions may still apply to this version. | ||||||||
| Changed: | ||||||||
| < < | Core | |||||||
| > > | Core | |||||||
| ||||||||
| Line: 105 to 107 | ||||||||
Known issues in HIPE 5.0 | ||||||||
| Changed: | ||||||||
| < < | Core | |||||||
| > > | Core | |||||||
| ||||||||
| Line: 119 to 121 | ||||||||
| ||||||||
| Changed: | ||||||||
| < < | HIFI | |||||||
| > > | HIFI | |||||||
| ||||||||
| Changed: | ||||||||
| < < | PACS | |||||||
| > > | PACS | |||||||
| ||||||||
| Changed: | ||||||||
| < < | SPIRE | |||||||
| > > | SPIRE | |||||||
| ||||||||
| Line: 141 to 143 | ||||||||
Known issues in HIPE 4.0 | ||||||||
| Changed: | ||||||||
| < < | PAL Storage Manager: Can't add pools to storages | |||||||
| > > | PAL Storage Manager: Can't add pools to storages | |||||||
| After creating a new ProductStorage using the PAL Storage Manager, you have to specify the pools that should be added to the storage. After selecting them and clicking "OK" in the GUI, the application appears to hang. | ||||||||
| Line: 153 to 155 | ||||||||
General HIPE startup issues | ||||||||
| Changed: | ||||||||
| < < | HIPE does not start at all, without giving error messages. What's wrong? | |||||||
| > > | HIPE does not start at all, without giving error messages. What's wrong? | |||||||
| This can happen for different reasons, that are explored in the next entries. When you start HIPE by clicking on its icon and a problem occurs, you may only see a terminal/command window appear for a fraction of a second, leaving you without information on the error. | ||||||||
| Line: 161 to 163 | ||||||||
| The next entries list some common problems that prevent HIPE from starting. | ||||||||
| Changed: | ||||||||
| < < | HIPE cannot start: the JVM cannot reserve enough memory | |||||||
| > > | HIPE cannot start: the JVM cannot reserve enough memory | |||||||
| This only applies if you installed HIPE using the installer, and not downloading a developer build from the Continuous Integration System. | ||||||||
| Line: 193 to 195 | ||||||||
| Try running HIPE after modifying the values until it successfully starts. | ||||||||
| Changed: | ||||||||
| < < | HIPE cannot start: | |||||||
| > > | HIPE cannot start: | |||||||
The terminal/command window from which you invoke HIPE shows a SAXNotRecognizedException. | ||||||||
| Line: 201 to 203 | ||||||||
java.vm.options = -Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl | ||||||||
| Changed: | ||||||||
| < < | HIPE cannot start: exception access violation. | |||||||
| > > | HIPE cannot start: exception access violation. | |||||||
The terminal/command window from which you invoke HIPE shows an EXCEPTION_ACCESS_VIOLATION error related to a class in org.apache.xerces. | ||||||||
| Line: 211 to 213 | ||||||||
General Help System issues | ||||||||
| Changed: | ||||||||
| < < | The help does not work anymore! What's wrong? | |||||||
| > > | The help does not work anymore! What's wrong? | |||||||
First, check if your issue is that described below, in Why is the HIPE Help System suddenly unable to connect to any help page?
If not, you have probably encountered a bug. The following are known issues that can prevent you from viewing the documentation, resulting either in a blank page or an error message:
| ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| ||||||||
| Line: 226 to 228 | ||||||||
| ||||||||
| Changed: | ||||||||
| < < | Is there a way to open the HIPE Help System without starting HIPE? | |||||||
| > > | Is there a way to open the HIPE Help System without starting HIPE? | |||||||
Yes, via the show_help command, which resides in the apps folder in your HIPE installation. The show_help command will start a standalone Help System in a window called Yet Another JAva Help System. Press the Display button to open the Help initial page in your default browser. | ||||||||
| Changed: | ||||||||
| < < | The Help System opens in my web browser. Does it mean I need to be connected to the Internet? | |||||||
| > > | The Help System opens in my web browser. Does it mean I need to be connected to the Internet? | |||||||
| No, the Help System resides on your computer and does not need Internet connection, except for the What's New document, which is hosted on the Herschel Wiki website. | ||||||||
| Changed: | ||||||||
| < < | Why is the HIPE Help System suddenly unable to connect to any help page? | |||||||
| > > | Why is the HIPE Help System suddenly unable to connect to any help page? | |||||||
| The Help System relies on a local web server to display help pages. If you close the application that started the web server, the server will shut down as well: | ||||||||
| Line: 243 to 245 | ||||||||
| Note that when the Help System stops, any browser window or tab showing help pages will remain open, but links on them will not work anymore. | ||||||||
| Changed: | ||||||||
| < < | Why are some code examples slightly different in the PDF and HTML versions of the documentation? | |||||||
| > > | Why are some code examples slightly different in the PDF and HTML versions of the documentation? | |||||||
Code examples and commands in the PDF versions of the manuals sometimes have extra dashes added (for instance, -XX:MaxPermSize=256m becomes --XX:MaxPermSize=256m). If an example or a command does not work as expected, try checking the HTML version of the documentation, which is not affected by this bug. | ||||||||
| Changed: | ||||||||
| < < | Why are several important packages missing from the Javadoc? | |||||||
| > > | Why are several important packages missing from the Javadoc? | |||||||
You are probably looking at the static Javadoc located in the doc/api/ folder of your HIPE installation. The complete Javadoc can now be accessed from the HIPE Help System by clicking on HCSS Developer's Reference Manual (API) in the Developer Reference section. The plan is to remove the static version of the Javadoc completely. | ||||||||
| Changed: | ||||||||
| < < | Is it possible to have the traditional, frame-based Javadoc layout? | |||||||
| > > | Is it possible to have the traditional, frame-based Javadoc layout? | |||||||
| Javadoc pages appear within the HIPE Help System frame structure. If you click on the FRAME link on any Javadoc page, you will obtain the traditional Javadoc layout. To go back to the HIPE Help System layout you will have to use the Back button of your browser (clicking on the NO FRAMES link will not work). To avoid losing the HIPE Help System layout, you may want to right-click on the FRAMES link to open the traditional Javadoc layout into a new tab of your web browser. | ||||||||
| Changed: | ||||||||
| < < | How can I provide feedback/requests regarding HIPE documentation? | |||||||
| > > | How can I provide feedback/requests regarding HIPE documentation? | |||||||
For informal feedback, click on the envelope icon on the top toolbar of any help page. This opens a new message in your email client, where you can add your feedback. If you want your issue to be officially tracked and supported, please raise a ticket with the Helpdesk of the Herschel Science Centre.
Other issues | ||||||||
| Changed: | ||||||||
| < < | "Can't connect to X11" error when using the jylaunch command | |||||||
| > > | "Can't connect to X11" error when using the jylaunch command | |||||||
Executing a script outside HIPE with the jylaunch command may fail with a java.lang.InternalError: Can't connect to X11 window server error. This may happen even if the script does not open any graphical window, since it may indirectly call components that require an X11 server. The workaround is to run the script with the command jylaunch -Djava.awt.headless=true instead of just jylaunch. | ||||||||
| Changed: | ||||||||
| < < | Problems saving observations to NFS-mounted disks and FAT32 disks | |||||||
| > > | Problems saving observations to NFS-mounted disks and FAT32 disks | |||||||
When saving observation to your computer, you may experience problems in the following cases:
| ||||||||
| Line: 276 to 278 | ||||||||
| See the HIPE Owner's Guide for information on how to set properties. | ||||||||
| Changed: | ||||||||
| < < | Why do I get a ClassCastException when trying to save an observation with the saveObservation command? | |||||||
| > > | Why do I get a ClassCastException when trying to save an observation with the saveObservation command? | |||||||
| You probably retrieved the observation without having the corresponding instrument software installed (for instance, you retrieved a PACS observation without having the PACS modules in HIPE). | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 261 to 261 | ||||||||
Other issues | ||||||||
| Added: | ||||||||
| > > | "Can't connect to X11" error when using the jylaunch commandExecuting a script outside HIPE with thejylaunch command may fail with a java.lang.InternalError: Can't connect to X11 window server error. This may happen even if the script does not open any graphical window, since it may indirectly call components that require an X11 server. The workaround is to run the script with the command jylaunch -Djava.awt.headless=true instead of just jylaunch. | |||||||
Problems saving observations to NFS-mounted disks and FAT32 disksWhen saving observation to your computer, you may experience problems in the following cases: | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 8 to 8 | ||||||||
| Added: | ||||||||
| > > | Known issues in HIPE 8.0Upgrade to Jython 2.5: Starting from version 8.0, HIPE will include a new version of Jython. You may have to adapt your scripts for them to work with the new version. See this page for the details.Known issues in HIPE 7.0In preparation.Known issues in HIPE 6.1None known in addition to those listed for HIPE 6.0. | |||||||
Known issues in HIPE 6.0Core | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 12 to 12 | ||||||||
Core | ||||||||
| Added: | ||||||||
| > > |
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. | |||||||
| ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 12 to 12 | ||||||||
Core | ||||||||
| Added: | ||||||||
| > > |
hipe.props file:
java.vm.options = -Duser.language=en -Duser.region=enThe 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. | |||||||
<-- HCSS-11540 --> | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 215 to 215 | ||||||||
| Note that when the Help System stops, any browser window or tab showing help pages will remain open, but links on them will not work anymore. | ||||||||
| Added: | ||||||||
| > > | Why are some code examples slightly different in the PDF and HTML versions of the documentation?Code examples and commands in the PDF versions of the manuals sometimes have extra dashes added (for instance,-XX:MaxPermSize=256m becomes --XX:MaxPermSize=256m). If an example or a command does not work as expected, try checking the HTML version of the documentation, which is not affected by this bug. | |||||||
Why are several important packages missing from the Javadoc?You are probably looking at the static Javadoc located in thedoc/api/ folder of your HIPE installation. The complete Javadoc can now be accessed from the HIPE Help System by clicking on HCSS Developer's Reference Manual (API) in the Developer Reference section. The plan is to remove the static version of the Javadoc completely. | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 12 to 12 | ||||||||
Core | ||||||||
| Added: | ||||||||
| > > |
<-- HCSS-11540 --> | |||||||
p in the Variables view. | ||||||||
| Line: 75 to 79 | ||||||||
Core | ||||||||
| Added: | ||||||||
| > > |
| |||||||
| ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 36 to 36 | ||||||||
| See the HIPE Owner's Guide for information on how to set properties. | ||||||||
| Added: | ||||||||
| > > | Known issues in HIPE 5.3None known in addition to those listed for previous 5.x versions.Known issues in HIPE 5.2None known in addition to those listed for previous 5.x versions. | |||||||
Known issues in HIPE 5.1 | ||||||||
| Added: | ||||||||
| > > | Issues in previous 5.x versions may still apply to this version. | |||||||
Core
| ||||||||
| Line: 59 to 69 | ||||||||
| ... | ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
Known issues in HIPE 5.0 | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 12 to 12 | ||||||||
Core | ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
p in the Variables view.
Steps to reproduce:
| |||||||
31-Jan-11 10:00:17.797 WARNING NavigatorView: Error checking file /bin: java.util.concurrent.TimeoutException | ||||||||
| Line: 20 to 34 | ||||||||
hcss.hipe.refreshPeriod = 3600000 | ||||||||
| Changed: | ||||||||
| < < | See the HIPE Owner's Guide for information on how to set properties. | |||||||
| > > | See the HIPE Owner's Guide for information on how to set properties. | |||||||
Known issues in HIPE 5.1 | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 161 to 161 | ||||||||
| ||||||||
| Added: | ||||||||
| > > |
| |||||||
| ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 8 to 8 | ||||||||
| Added: | ||||||||
| > > | Known issues in HIPE 6.0Core
31-Jan-11 10:00:17.797 WARNING NavigatorView: Error checking file /bin: java.util.concurrent.TimeoutExceptionWorkaround: set the property hcss.hipe.refreshPeriod as follows:
hcss.hipe.refreshPeriod = 3600000See the HIPE Owner's Guide for information on how to set properties. | |||||||
Known issues in HIPE 5.1Core | ||||||||
| Added: | ||||||||
| > > |
31-Jan-11 10:00:17.797 WARNING NavigatorView: Error checking file /bin: java.util.concurrent.TimeoutExceptionWorkaround: set the property hcss.hipe.refreshPeriod as follows:
hcss.hipe.refreshPeriod = 3600000See the HIPE Owner's Guide for information on how to set properties. | |||||||
Exception in thread "AWT-EventQueue-0" java.util.ConcurrentModificationException | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 21 to 21 | ||||||||
| ... | ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
Known issues in HIPE 5.0 | ||||||||
| Line: 32 to 32 | ||||||||
| ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
* 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.
| ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Added: | ||||||||
| > > |
| |||||||
Known issues in HIPE 5.1 | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 17 to 17 | ||||||||
| ... | ||||||||
| Added: | ||||||||
| > > |
| |||||||
Known issues in HIPE 5.0Core | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 169 to 169 | ||||||||
Other issues | ||||||||
| Added: | ||||||||
| > > | Problems saving observations to NFS-mounted disks and FAT32 disksWhen saving observation to your computer, you may experience problems in the following cases:
hcss.ia.pal.pool.lstore.lock = simpleSee the HIPE Owner's Guide for information on how to set properties. | |||||||
Why do I get a ClassCastException when trying to save an observation with the saveObservation command?You probably retrieved the observation without having the corresponding instrument software installed (for instance, you retrieved a PACS observation without having the PACS modules in HIPE). | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Added: | ||||||||
| > > | Known issues in HIPE 5.1Core
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)
...
| |||||||
Known issues in HIPE 5.0Core | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 16 to 16 | ||||||||
| ||||||||
| Added: | ||||||||
| > > |
| |||||||
HIFI | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 16 to 16 | ||||||||
| ||||||||
| Added: | ||||||||
| > > |
| |||||||
HIFI | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 6 to 6 | ||||||||
Known issues in HIPE 5.0 | ||||||||
| Deleted: | ||||||||
| < < | All these issues are being addressed for HIPE 5.1. | |||||||
Core
| ||||||||
| Line: 27 to 25 | ||||||||
PACS | ||||||||
| Changed: | ||||||||
| < < | To be added. | |||||||
| > > |
| |||||||
SPIRE | ||||||||
| Changed: | ||||||||
| < < | To be added. | |||||||
| > > |
| |||||||
Known issues in HIPE 4.0 | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 6 to 6 | ||||||||
Known issues in HIPE 5.0 | ||||||||
| Added: | ||||||||
| > > | All these issues are being addressed for HIPE 5.1. | |||||||
Core | ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| ||||||||
| Changed: | ||||||||
| < < | Not complete yet. | |||||||
| > > |
| |||||||
HIFI | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 10 to 10 | ||||||||
| ||||||||
| Added: | ||||||||
| > > |
| |||||||
| Not complete yet. | ||||||||
| Line: 106 to 107 | ||||||||
| ||||||||
| Deleted: | ||||||||
| < < |
| |||||||
| ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Changed: | ||||||||
| < < | HIPE startup issues | |||||||
| > > | Known issues in HIPE 5.0Core
HIFI
PACSTo be added.SPIRETo be added.Known issues in HIPE 4.0PAL Storage Manager: Can't add pools to storagesAfter creating a new ProductStorage using the PAL Storage Manager, you have to specify the pools that should be added to the storage. After selecting them and clicking "OK" in the GUI, the application appears to hang.
The work-around is to click Cancel, after clicking OK. Clicking Cancel closes the panel, releases the deadlock, and allows the pools to be added to the storage, as was requested by the click on OK.
Fixed in HIPE 4.1.
General HIPE startup issues | |||||||
HIPE does not start at all, without giving error messages. What's wrong? | ||||||||
| Line: 62 to 97 | ||||||||
| This error is probably due to a bug in the Java Virtual Machine, and has so far been found only on Windows XP 32 bit. | ||||||||
| Changed: | ||||||||
| < < | Help System problems | |||||||
| > > | General Help System issues | |||||||
The help does not work anymore! What's wrong? | ||||||||
| Line: 108 to 143 | ||||||||
| For informal feedback, click on the envelope icon on the top toolbar of any help page. This opens a new message in your email client, where you can add your feedback. If you want your issue to be officially tracked and supported, please raise a ticket with the Helpdesk of the Herschel Science Centre. | ||||||||
| Changed: | ||||||||
| < < | Common problems | |||||||
| > > | Other issues | |||||||
Why do I get a ClassCastException when trying to save an observation with the saveObservation command? | ||||||||
| Line: 122 to 157 | ||||||||
| ||||||||
| Deleted: | ||||||||
| < < | PAL Storage Manager: Can't add pools to storages (HIPE 4.0)After creating a new ProductStorage using the PAL Storage Manager, one has to specify the pools that should be added to the storage. After selecting them and clicking "OK" in the GUI, the application appears to hang.
The work-around is to click Cancel, after clicking OK. Clicking Cancel will close the panel, release the deadlock, and allow the pools to be added to the storage, as was requested by the click on OK.
This has been originally report as HCSS-10745 and is due Java bug 6880336. A work-around has been implemented in HIPE 4.1 and the problem will disappear entirely when the Java version that comes with HIPE is upgraded to update 21 or higher. | |||||||
| ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 62 to 62 | ||||||||
| This error is probably due to a bug in the Java Virtual Machine, and has so far been found only on Windows XP 32 bit. | ||||||||
| Added: | ||||||||
| > > | Help System problemsThe help does not work anymore! What's wrong?First, check if your issue is that described below, in Why is the HIPE Help System suddenly unable to connect to any help page? If not, you have probably encountered a bug. The following are known issues that can prevent you from viewing the documentation, resulting either in a blank page or an error message:
Is there a way to open the HIPE Help System without starting HIPE?Yes, via theshow_help command, which resides in the apps folder in your HIPE installation. The show_help command will start a standalone Help System in a window called Yet Another JAva Help System. Press the Display button to open the Help initial page in your default browser.
The Help System opens in my web browser. Does it mean I need to be connected to the Internet?No, the Help System resides on your computer and does not need Internet connection, except for the What's New document, which is hosted on the Herschel Wiki website.Why is the HIPE Help System suddenly unable to connect to any help page?The Help System relies on a local web server to display help pages. If you close the application that started the web server, the server will shut down as well:
Why are several important packages missing from the Javadoc?You are probably looking at the static Javadoc located in thedoc/api/ folder of your HIPE installation. The complete Javadoc can now be accessed from the HIPE Help System by clicking on HCSS Developer's Reference Manual (API) in the Developer Reference section. The plan is to remove the static version of the Javadoc completely.
Is it possible to have the traditional, frame-based Javadoc layout?Javadoc pages appear within the HIPE Help System frame structure. If you click on the FRAME link on any Javadoc page, you will obtain the traditional Javadoc layout. To go back to the HIPE Help System layout you will have to use the Back button of your browser (clicking on the NO FRAMES link will not work). To avoid losing the HIPE Help System layout, you may want to right-click on the FRAMES link to open the traditional Javadoc layout into a new tab of your web browser.How can I provide feedback/requests regarding HIPE documentation?For informal feedback, click on the envelope icon on the top toolbar of any help page. This opens a new message in your email client, where you can add your feedback. If you want your issue to be officially tracked and supported, please raise a ticket with the Helpdesk of the Herschel Science Centre. | |||||||
Common problemsWhy do I get a ClassCastException when trying to save an observation with the saveObservation command? | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Line: 75 to 75 | ||||||||
| ||||||||
| Added: | ||||||||
| > > | PAL Storage Manager: Can't add pools to storages (HIPE 4.0)After creating a new ProductStorage using the PAL Storage Manager, one has to specify the pools that should be added to the storage. After selecting them and clicking "OK" in the GUI, the application appears to hang.
The work-around is to click Cancel, after clicking OK. Clicking Cancel will close the panel, release the deadlock, and allow the pools to be added to the storage, as was requested by the click on OK.
This has been originally report as HCSS-10745 and is due Java bug 6880336. A work-around has been implemented in HIPE 4.1 and the problem will disappear entirely when the Java version that comes with HIPE is upgraded to update 21 or higher.
| |||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Added: | ||||||||
| > > | ||||||||
HIPE startup issuesHIPE does not start at all, without giving error messages. What's wrong? | ||||||||
| Line: 59 to 61 | ||||||||
| Restart HIPE to resolve the issue. This error is probably due to a bug in the Java Virtual Machine, and has so far been found only on Windows XP 32 bit. \ No newline at end of file | ||||||||
| Added: | ||||||||
| > > | Common problemsWhy do I get a ClassCastException when trying to save an observation with the saveObservation command?You probably retrieved the observation without having the corresponding instrument software installed (for instance, you retrieved a PACS observation without having the PACS modules in HIPE). To solve this problem follow these steps:
| |||||||
| \ No newline at end of file | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
HIPE known issues | ||||||||
| Deleted: | ||||||||
| < < | Coming soon. | |||||||
| \ No newline at end of file | ||||||||
| Added: | ||||||||
| > > | HIPE startup issuesHIPE does not start at all, without giving error messages. What's wrong?This can happen for different reasons, that are explored in the next entries. When you start HIPE by clicking on its icon and a problem occurs, you may only see a terminal/command window appear for a fraction of a second, leaving you without information on the error. To obtain more information about the error, try invoking HIPE directly from a terminal/command window ([installation_dir]/apps/hipe) and examine the text output. Note that the output from some errors can be quite lengthy, so you may need to scroll up to discover the root cause.
The next entries list some common problems that prevent HIPE from starting.
HIPE cannot start: the JVM cannot reserve enough memoryThis only applies if you installed HIPE using the installer, and not downloading a developer build from the Continuous Integration System. The cause is that the Java virtual machine is unable to start with the designated amount of memory. The terminal/command window from which you invoke HIPE shows the following error message that indicates insufficient memory:Error occurred during initialization of VM Could not reserve enough space for object heap Could not create the Java virtual machine.To fix this error you have to modify two properties in the installed.properties file within your HIPE installation directory. There is no need to reinstall HIPE.
The properties you need to modify are the following. You have to lower the amount of allocated memory:
java.vm.memory.max java.vm.options=-XX:PermSizePossible values are the following: java.vm.memory.max=1024m java.vm.options=-XX:PermSize=128mTry running HIPE after modifying the values until it successfully starts. HIPE cannot start:
The terminal/command window from which you invoke HIPE shows a | |||||||
| \ No newline at end of file | ||||||||
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
| Added: | ||||||||
| > > |
HIPE known issuesComing soon. | |||||||