bug in gscut

Home › Forums › Gemini Data Reduction › bug in gscut

Tagged: , , ,

This topic contains 1 reply, has 2 voices, and was last updated by  Mark 8 years, 4 months ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • October 25, 2014 at 1:04 am #711

    phibon
    Participant

    Liz Buckley-Geer have found a bug in GSCUT. The problem arises if the last slit of an MDF file contains an acquisition object. This means that the EXTVER for that slit to be zero because these objects are ignored. The value contained in EXTVER is read into the n_j variable in GSCUT using scan and so it gets set to zero. So when the code comes to insert n_j into the NSCIEXT keyword it finds a value of zero and exits with an error. She worked around it by setting the priority of the acquisition object to 3 so that it wouldn’t ignore it.

    November 25, 2014 at 7:02 pm #742

    Mark
    Participant

    Just to follow up on this, the bug fix has been made and will officially go out in the next release. However, I’ll post it here for users to test sooner rather than later.

    Thanks,

    Mark

    Instructions:

    Unzip the file.

    Either overwrite the original file in your current installation in the directory defined by ‘gmos$’ or in your IRAF / PyRAF session define it:

    task gscut=/path/to/unzipped/file/gscut.cl

    • This reply was modified 8 years, 4 months ago by  Mark. Reason: added more tags
    Attachments:
    1. gscut.cl.gz
  • Author
    Posts
Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.