iraf.net

Hi there,I'm presently trying to run the task onedspec.standard in my 2.13 beta installation of IRAF on my Mac intel system. (I have recently switched institutions and am running IRAF on a new platform compared to my old system, which was IRAF 2.12). I know I'm using the correct input parameters for standard, I successfully ran the task many times on my former computer.However, every time I try to run the task on my new system I get an error that says:gxtfbrsnN20070207S0059: Warning: Cannot open file (onedstds$blackboody/standards.men)
ERROR: Cannot open file (onedstds$blackboody/standards.men)I've looked at the standards.men file in question & it exists. It's 6 lines long with definitions of the blackbody wavelength bands for the calculation included in the task. It seems okay based on what the help file says, but I can't get the task to access it, though I've run the same task with success in the past. Thanks very much for your thoughts on this problem... I'd really appreciate any help you can give.tracy
beck

Tracy,You can eliminate any question of path permissions problems by seeing whether you can view the file from the CL directly, e.g.[code:1:9e4cfe8c7a]cl> type onedstds$blackbody/standards.men[/code:1:9e4cfe8c7a]If this fails then start checking individual paths, "cl> dir onedstds$" etc to see where the problem is.Are you running the STANDARD task directly from the CL prompt or from a script? If the latter then this could be a problem with running out of file descriptors. This can happen when e.g. a script opens a 'list' variable inside a loop but doesn't effectively close it with a[code:1:9e4cfe8c7a]list = ""[/code:1:9e4cfe8c7a]statement.We're not aware of any problems with the task or file permissions so something else must be going on. Hope this helps.Cheers,
-Mike

Hi,It looks to me like you have a typo:blackboody -> blackbody

Hello Mike,Thanks very much for your comments.I'm trying to run standard from the cl prompt on Gemini NIFS data. I'm sure something is funky with my new setup, but was just wondering if you'd seen this before...So, I've done as you suggest and got:
nifs> dir $onedstds
README ctiocal irscal redcal
blackbody ctioextinct.dat kpnoextinct.dat spec16cal
bstdscal ctionewcal names.men spec50cal
ctio iidscal oke1990 spechayescal
nifs> type $onedstds/blackbody/standards.men
Warning: Cannot open file ($onedstds/blackbody/standards.men)
nifs> dir $onedstds/blackbody/
no files foundSo, it looks like the onedstds directory is itself OK, but the blackbody directory within it is having access problems. I didn't think it was typical to have to define subdirectories? Thanks for any info... I'll continue to look into the directory definitions in my setup files...tracy

I think Frank has it nailed.BTW, '$onedstds' is a unix shell variable (and likely isn't set), 'onedstds$' is an iraf logical path and the value you should be using.-Mike

Hi Tracy,In you last message you have the $ in the wrong place (Unix rather than IRAF syntax). :wink:[code:1:26363bf809]
nifs> type $onedstds/blackbody/standards.men
[/code:1:26363bf809]should be[code:1:26363bf809]
type onedstds$blackbody/standards.men
[/code:1:26363bf809]Frank

Two replies in a minute. Hows that for service!

Thanks.I realized right as I hit 'post reply' on my last message that I had the $ in the wrong place. It's good to have a second (or third) pair of eyes instantly catch what I missed...Thanks very much, tracy
beck