iraf.net

Dear IRAF support team,We have at my institute the V2.12.1 version of IRAF.
I do not manage to use the telluric command, I have the following warning
message:
"Environment variable not found or not integer (IMIO_BUFMAX)"
and I cannot go on with the telluric task.
This variable is not in the login.cl. I added it with a value of 32000000.
But I still get this warning.
Could you please tell me how to solve this problem?Best regards,
Jihane Moultaka.

Hi Jihane,
I'll send an earlier reply to another user with the same problem
that should answer your question. Let us know if you continue to have
problems.Cheers,
Mike Fitzpatrick--------------------------NOTE: As of Jan 1, 2006 NOAO will no longer be operating a HelpDesk for
IRAF at iraf@noao.edu. Support is being moved to a forum-based system
at https://iraf.net, please post future questions to that site. Thanks.---------------------------------> From: Frank Valdes <valdes@noao.edu>
> Date: Mon, 24 Feb 2003 12:27:39 -0700 (MST)
> To: stirpe@bo.astro.it
> Subject: Re: problem with "telluric"
> X-Sun-Charset: US-ASCII
>
> Hello Giovanna,
>
> All IRAF tasks actually check for this (and other) variable and it is
> normal for it to be absent. The problem with TELLURIC is that it gets
> confused by some other error and it then reports the wrong error
> message. This is a bug in the way the program deals with errors and it
> will be fixed.
>
> So the problem is to determine what the actual error is. It is most likely
> something simple with the parameters. The way you can get to the true
> error is by setting the variables.
>
> cl> set imio_bufmax = 16000000
> cl> set imio_bufsize = 260000
> cl> set imio_buffrac = 10
>
> These are the default values that the programs use when these variables are
> undefined so it will make no difference and you don't really need to know
> anything about these. They are used to optimize image access.
>
> After setting these values then you should get the correct error. If
> you get another misleading error like:
>
> Warning: Image header parameter not found (EXTVER)
>
> it probably means it could not open the calibration spectrum.
>
> I hope this helps and let us know if you still get errors which you don't
> understand with this task. If all else fails and you can figure out what
> is wrong you can send the parameter listing for telluric and I can provide
> a corrected binary executable that will then report the actual error.
>
> Yours,
> Frank Valdes
>
>
> NUMBER: 520
> MODULE: onedspec.telluric
> SYSTEM: -V2.12.2
> DATE: Mon Feb 24 12:18:04 MST 2003
> FROM: valdes
>
> BUG: When an error, such as invalid parameters or missing images, occurs
> the task first does some error clean up operations before reporting
> the error. The problem with this is that the actual error message
> can get lost and a misleading message, such as environment variable
> or image header parameter not found, will be given. Avoid this
> requires a code change. One way to sometimes get to the true error
> is to eliminate the misleading error by setting a value for the
> missing evironment or header parameter. Also check carefully all
> the task parameters since most error are the result of problems
> with them.
>
> STATUS: The error handling will be improved in the next release.

Hello Mike,thank you for your answer but it still doesn't work.
I got again the same warning message.I should tell you that the other error you talk about in your email:
"Warning: Image header parameter not found (EXTVER)",
I got it as well before the present error and I thougth it was because of
the fits files. So I added in the header of my two fits files the parameter
extver = 1
and then I got the present imio_bufmax error.I made a screen copy of what I just did.cl> set imio_bufmax = 16000000
cl> set imio_bufsize = 260000
cl> set imio_buffrac = 10
cl> telluric
List of input spectra to correct (2005FRI1N0ext2.fits):
List of output corrected spectra (ess2):
List of telluric calibration spectra (stand27T00.52ext2.fits):
2005FRI1N0ext2.fits: Airmass (1. (1.):
stand27T00.52ext2.fits: Airmass (1. (1.):
2005FRI1N0ext2.fits: Search interactively? (no|yes|NO|YES) (yes):
Warning: Environment variable not found or not integer (IMIO_BUFMAX)
cl>Hope there is a solution,
cheers,
Jihane.
On Thu, 8 Dec 2005, Mike Fitzpatrick wrote:>
> Hi Jihane,
> I'll send an earlier reply to another user with the same problem
> that should answer your question. Let us know if you continue to have
> problems.
>
> Cheers,
> Mike Fitzpatrick
>
>
>
> --------------------------
>
> NOTE: As of Jan 1, 2006 NOAO will no longer be operating a HelpDesk for
> IRAF at iraf@noao.edu. Support is being moved to a forum-based system
> at https://iraf.net, please post future questions to that site. Thanks.
>
>
>
> ---------------------------------
>
> > From: Frank Valdes <valdes@noao.edu>
> > Date: Mon, 24 Feb 2003 12:27:39 -0700 (MST)
> > To: stirpe@bo.astro.it
> > Subject: Re: problem with "telluric"
> > X-Sun-Charset: US-ASCII
> >
> > Hello Giovanna,
> >
> > All IRAF tasks actually check for this (and other) variable and it is
> > normal for it to be absent. The problem with TELLURIC is that it gets
> > confused by some other error and it then reports the wrong error
> > message. This is a bug in the way the program deals with errors and it
> > will be fixed.
> >
> > So the problem is to determine what the actual error is. It is most likely
> > something simple with the parameters. The way you can get to the true
> > error is by setting the variables.
> >
> > cl> set imio_bufmax = 16000000
> > cl> set imio_bufsize = 260000
> > cl> set imio_buffrac = 10
> >
> > These are the default values that the programs use when these variables are
> > undefined so it will make no difference and you don't really need to know
> > anything about these. They are used to optimize image access.
> >
> > After setting these values then you should get the correct error. If
> > you get another misleading error like:
> >
> > Warning: Image header parameter not found (EXTVER)
> >
> > it probably means it could not open the calibration spectrum.
> >
> > I hope this helps and let us know if you still get errors which you don't
> > understand with this task. If all else fails and you can figure out what
> > is wrong you can send the parameter listing for telluric and I can provide
> > a corrected binary executable that will then report the actual error.
> >
> > Yours,
> > Frank Valdes
> >
> >
> > NUMBER: 520
> > MODULE: onedspec.telluric
> > SYSTEM: -V2.12.2
> > DATE: Mon Feb 24 12:18:04 MST 2003
> > FROM: valdes
> >
> > BUG: When an error, such as invalid parameters or missing images, occurs
> > the task first does some error clean up operations before reporting
> > the error. The problem with this is that the actual error message
> > can get lost and a misleading message, such as environment variable
> > or image header parameter not found, will be given. Avoid this
> > requires a code change. One way to sometimes get to the true error
> > is to eliminate the misleading error by setting a value for the
> > missing evironment or header parameter. Also check carefully all
> > the task parameters since most error are the result of problems
> > with them.
> >
> > STATUS: The error handling will be improved in the next release.
>
>
>

Jihane,
Try using capitalized versions of the environment variables.-Mike