klabrie

Forum Replies Created

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • in reply to: Gsreduce MOS Science and Arc Exposures #2856

    klabrie
    Keymaster

    A long shot. From the logs you’ve sent, the last call to gsreduce is on a very, very long list of files. There’s an IRAF limit on the length of string, I wouldn’t be surprised if you were hitting that limit.

    Try using the “@” list format instead. List your input files in a normal text file, one file name per line, and feed that to gsreduce.

    For example:
    In “my_input_files.txt”:

    S20171220S0054
    S20171220S0055
    S20171220S0056
    S20171220S0057
    ....
    S20171220S0144

    Then call gsreduce as follow:

    gsreduce @my_input_files.txt ...the other params...

    Might help, might not, but it is certainly worth a try. Good luck!

    in reply to: Updated GNIRS reduction script #1535

    klabrie
    Keymaster

    I’m really happy to hear that you found a solution. Thank you for sharing it with the community.

    in reply to: Updated GNIRS reduction script #1533

    klabrie
    Keymaster

    Specifically regarding Anaconda and IRAF, I would like to make you aware that IRAF, and Gemini IRAF v1.13.1, have recently been added to the AstroConda channel. Maybe that will help. See the instructions at http://www.gemini.edu/node/12665

    Kathleen

    in reply to: Updated GNIRS reduction script #1518

    klabrie
    Keymaster

    Issue:
    Could not import aqutil, please see the online PyRAF FAQ
    http://www.stsci.edu/institute/software_hardware/pyraf/pyraf_faq#5.13

    Limited graphics available (aqutil not loaded)


    This problem occurs at Step 10, and it is related to the display. As stated in the XDGNIRS manual:

    “Most likely things to go wrong: This step is intended to help the Palomar XD group interpret the reduced data and may not work well on other data sets. If this step causes problems, simply run the code with “stop=9” and use your own routines to plot the .txt files output in the previous step. The total counts and FWHM recorded in the data sheet may not be correct for all data sets.”

    Therefore, Gemini recommend that you follow that advice and use your own plotting routines.

    Also, we would like to point out, also from that manual, Section 7:

    “XDGNIRS is not officially supported by Gemini. File a helpdesk request for general questions about GNIRS data and reduction. XDGNIRS-specific questions can be addressed to Rachel Mason, who will attempt to answer on a best-efforts basis, other commitments permitting.”

    This software is essentially a community-supported software, especially now that Rachel Mason has left Gemini, and the field. We recommend that you post your questions here on the DR Forum. Maybe someone in the community has solved this problem already and will be able to help.

    A colleague suggested that it might still be worth asking the question to help@stsci. While they are no longer supporting Ureka, they try to help with those things on a best effort basis. “aqutil” is a pyraf module, therefore belongs to STScI.

    I hope these clarifications help. If you do have a solution, please do post it here!

    in reply to: Updated GNIRS reduction script #1517

    klabrie
    Keymaster

    For reference, the original post is at http://drforum.gemini.edu/topic/gnirs-xd-reduction-script/

    in reply to: Installing Gemini IRAF version 1.13.1 #1258

    klabrie
    Keymaster

    I think I can put the following commands into my login.cl file:
    reset gemini = /Users/jwerk/Gemini/
    task gemini.pkg = gemini$gemini.cl

    You are correct. I prefer putting that stuff in my loginuser.cl but it should also work in the login.cl. You might want to add a “keep” after those lines just to be safe.

    You are also correct that the instructions distributed in the package are a bit old. It has been on my TODO list to update all that for the next release. (And add better instructions on the website too.) The instructions currently in the package were the standard installation instructions for external IRAF package way back then. What you propose is indeed a nicer, simpler way to do things.

    As for the helpdb… Er… I wasn’t sure but I just did a test. You should NOT have to do anything special. Just redefining the gemini package like you did above will pick up the help pages in that package. I just tried it and it was indeed picking up the new help pages. Give it a try, just edit one of the .hlp file with some bogus word added to the tile, launch cl/pyraf, load the gemini package and “help” the task associated to the .hlp you modified. You should see your bogus word, confirming that you are picking up the new .hlp files.

    Let me know how it turns out.

    Thanks for your post.

Viewing 6 posts - 1 through 6 (of 6 total)