There are no known issues with APALL and no recent changes to indicate something was fixed, so we'll need more information in order to be able to reproduce the problem. Could you upload the data files used as well as the parameter setting (e.g. "dpar apall") to the anonftp at ftp://iraf.noao.edu/pub so we can have a look?
I was able to reproduce this and track the source down. Below is the bug report. So it will be fixed in the next release. If you need something sooner let us know and we can provide a special patch to you.
DATE: Mon Mar 5 08:51:03 MST 2012
BUG: The optimal extraction for significantly tilted spectra, the Marsh
algorithm, has bug which manifests only under 64-bit architectures.
The symptom is a crash, usually a memory or segmentation panic.
The only workarounds are 1) go to an 32-bit system or 2) don't
use the optimal extraction option.
Thanks Mike - I've put in the new binary, but there is now another problem
List of input images: WUma-010.fit
Find apertures for WUma-010? (yes):
Number of apertures to be found automatically: 1
Resize apertures for WUma-010? (yes):
Edit apertures for WUma-010? (yes):
ERROR: segmentation violation
called as: `apall ()'
at which point the graphics window should appear and doesn't and then I get kicked back to the "apextract>" prompt. It doesn't seem to make any difference if I change any apall parameters or if I run from a clean directory.
and install it the usual place renaming it to the usual name (i.e. x_apextract.e). This binary is the one I built on a different linux64 platform and have not had a problem. Please let us know whether it works or not. If not, just to be sure, return the result of
cl> dir noaobin$x_apextract.e l+
to double check the binary that is actually being run.
Posted: Mon Jun 11, 2012 11:45 am Post subject: Segmentation violation when using sections
I updated from V2.15 to V2.16 last week. Since then I get the same kind of error as described below for my x64 system. Sometimes the PANIC turns up, but mostly it only gives the segmentation violation. The few times that the PANIC protocol did show and displayed a back-trace, it seemed that it originates in x_images.e.... ....which seems right because sections is a subtask of images->imutil->sections.
Could you please have a look, because I use the sections task in a lot of in-house scripts.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum