Replies: 5 comments
-
There were no changes with the |
Beta Was this translation helpful? Give feedback.
-
I just tried to run the example locally, with IRAF 2.18 from Debian unstable, and python3-pyraf 2.2.1 from Debian testing, and it worked quite well (I got a Python tk/matplotlib exception at the very end indicaing a double destroy, but the pipeline passed). Therefore, I would assume some problems with your local setup. Specifically, |
Beta Was this translation helpful? Give feedback.
-
I am running on a Mac M1 with Sonoma 14.2, and I made a clean conda environment, then followed the installation instructions for 2.18. I think the double destroy occurs for me as well, @temuller tells me this is an unrelated problem. Here's a minimal example that throws the same error as above for me:
with the fits file in question attached here |
Beta Was this translation helpful? Give feedback.
-
I can't reproduce it. The code you mention works well for me and produces the ASCII file As I said, the error somehow mentions a file |
Beta Was this translation helpful? Give feedback.
-
As I am rather sure that this is not a bug, I will move this to the discussions. |
Beta Was this translation helpful? Give feedback.
-
Hello, I am trying to install iraf a few ways and I seem to be running into an issue with a variable called
uparm
.To Reproduce
Steps to reproduce the behavior.
iraf-2.18.tar.gz
and follow the installation steps.make test
passes all testsPESSTO
pipeline, using iraf 2.18 installation instructions instead of iraf 2.17and get the resulting error
Expected behavior
A clear and concise description of what you expected to happen.
System details:
Additional context
I figure one of the culprits is the version of iraf that the pipeline uses, is there something specific with the uparm directory / values that changed between the versions?
Beta Was this translation helpful? Give feedback.
All reactions