Submit a Story  :  IRAF Links  :  Past Polls  :  Calendar  :  Advanced Search  
     iraf.net
  About iraf.net
Downloads
Docs
Projects
FAQ
Support
Forums
Links
Email Contact Us  
Privacy Policy
User Functions
Username:

Password:

Don't have an account yet? Sign up as a New User
What's New
STORIES
No new stories

COMMENTS last 48 hrs
No new comments
 Forum FAQForum FAQ   Forum SearchForum Search   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

IRAF 2.16 mscred ccdproc problem
Goto page Previous  1, 2
 
Post new topic   Reply to topic    iraf.net Forum Index -> General IRAF
View previous topic :: View next topic  
Author Message
rji
Active IRAF User


Joined: 21 Apr 2007
Posts: 87
PostPosted: Thu Mar 29, 2012 12:24 pm    Post subject: Reply with quote
The file
Code:
ftp://iraf.noao.edu/iraf/v216/README.VO

has no data.
Back to top
View user's profile Send private message
fitz
Site Admin


Joined: 30 Sep 2005
Posts: 3256
Location: Tucson
PostPosted: Thu Mar 29, 2012 5:21 pm    Post subject: Reply with quote
The README.VO file is still in preparation, I just tend to create empty files so people will notice and nag me until I actually write it Cool

Quote:

and found there "iraf.lnux.x86.tar.gz" (191660 KB, 03/23/2012, 01:25:00 AM) and "iraf.lnux.x86.gz" (195880 KB, 03/28/2012, 08:04:00 PM). I dowloaded the second one,


Ooops, the build script was still using the old naming scheme. Using the "second file" you mention is correct.

Quote:
The problem is with PyRAF:


I think the problem begin with the message about not finding the 'instrmsc' instrument setting, does defining this help? I think the rest of the trace is bogus since IMHEAD is never called directly from CCDPROC. I verified that the imaccess() function works properly without the ".fits" extension as well.

Some of the new v2.16 features certainly won't work under PyRAF unless/until it is updated, but otherwise things should generally be backwards compatible.
Back to top
View user's profile Send private message
rji
Active IRAF User


Joined: 21 Apr 2007
Posts: 87
PostPosted: Mon Apr 09, 2012 7:19 pm    Post subject: Reply with quote
Not exactly. The extern "mscred.ccdproc.cl" in line 103 has:
Code:
tmpfname = _ccdlist.ccdproc; _ccdlist.ccdproc="setinstrument"

really unexpected instruction here.
Back to top
View user's profile Send private message
rji
Active IRAF User


Joined: 21 Apr 2007
Posts: 87
PostPosted: Fri Apr 13, 2012 8:09 pm    Post subject: Reply with quote
The newest IRAF of today does not process MEF files:
Code:
j0062[im1]: Apr 13 22:03 Trim is [9:1016,9:2024]
j0062[im1]: Apr 13 22:03 Overscan is [1020:1035,9:2024], mean 1726.488
j0062[im2]: Apr 13 22:03 Trim is [9:1016,9:2024]
j0062[im2]: Apr 13 22:03 Overscan is [1020:1035,9:2024], mean 1748.158
j0062: Merge amplifiers
ERROR: segmentation violation
  "imdelete (mergeinput, verify-)"
     line 442: mscsrc$ccdproc.cl
     called as: `ccdproc (images=j0062, ccdtype=, overscan=yes, trim=yes, zerocor=no, darkcor=no, flatcor=no, merge=yes)'
     called as: `cl ()'
     called as: `cl ()'
     called as: `cl ()'
     called as: `cl ()'
     called as: `cl ()'
     called as: `cl ()'
     called as: `cl ()'
     called as: `cl ()'
  "clbye()"
     line 41: fitsutil$fitsutil.cl
     called as: `fitsutil ()'
  "fitsutil"
     line 5: mscred$mscred.cl
     called as: `mscred ()'
     called as: `cl ()'
  ""ccdproc(s1,ccdtype='',overs+,trim+,zeroc-,darkc-,flatc-,merge+)\n") ..."

The commands:
Code:
reset use_new_imt = no
flpr 0

do not help.
Back to top
View user's profile Send private message
fitz
Site Admin


Joined: 30 Sep 2005
Posts: 3256
Location: Tucson
PostPosted: Tue Apr 17, 2012 5:34 am    Post subject: Reply with quote
I verified that the files in the archive still process your test image from the earlier report, but I'm wondering whether the problems you had with the update might mean the files aren't installed correctly. Can you verify that binaries for the core system and the MSCRED package date from at least April 11 ??
Back to top
View user's profile Send private message
rji
Active IRAF User


Joined: 21 Apr 2007
Posts: 87
PostPosted: Tue Apr 17, 2012 12:39 pm    Post subject: Reply with quote
Today I did:
Code:
% cd $iraf
% make latest

and the output is:
Code:
Updating IRAF v2.16 to latest release.

Tue Apr 17 13:49:12 CEST 2012

(util/iraf_update -all)
Updating utility scripts ....Done
Updating IRAF system  ....
iraf_latest: cwd =  /iraf/iraf
Updating binaries:   linux
Downloading: patch-src.tar.gz Unpacking ... Done.
Downloading: patch.lnux.x86.tar.gz Unpacking ... Done.
Update all external packages ...
make[1]: Entering directory `/iraf/iraf/extern'
Initializing repository data ....
Creating system makefile ....
Setup Complete.
Updating repository data ....
Package adccdrom     is not installed ....
Package cfh12k       is not installed ....
Package ctio         is not installed ....
Package deitab       is not installed ....
Package esowfi       is not installed ....
Package fitsutil     is current ....
Package guiapps      is not installed ....
Package mem0         is not installed ....
Package mscdb        is not installed ....
Package mscred       is current ....
Package mtools       is not installed ....
Package nfextern     is not installed ....
Package optic        is not installed ....
Package patch        is not installed ....
Package rvsao        is not installed ....
Package song         is not installed ....
Package sqiid        is not installed ....
Package stsdas       is current ....
Package tables       is current ....
Package ucsclris     is not installed ....
Package upsqiid      is not installed ....
Package xdimsum      is not installed ....
Done
make[1]: Leaving directory `/iraf/iraf/extern'

Update Status:    Successful

Tue Apr 17 13:52:22 CEST 2012

Now I go to "cl" and make "setinstr" then:
Code:
mscred> ccdlist a
a[im1][1036,2032][ushort][][1][]:SYBIA_1
a[im2][1036,2032][ushort][][2][]:SYBIA_1
mscred> ccdproc a
a[im1]: Apr 17 13:55 Trim is [9:1016,9:2024]
a[im1]: Apr 17 13:55 Overscan is [1020:1035,9:2024], mean 1810.755
a[im2]: Apr 17 13:55 Trim is [9:1016,9:2024]
a[im2]: Apr 17 13:55 Overscan is [1020:1035,9:2024], mean 1807.158
a: Merge amplifiers
ERROR: segmentation violation
  "imdelete (mergeinput, verify-)"
     line 442: mscsrc$ccdproc.cl
     called as: `ccdproc (images=a)'

Then I make:
Code:
mscred> fcache list
mscred> tinfo ds9.xml
ERROR: Cannot open file (cache$.f775517028)
mscred> tinfo http://iraf.noao.edu/votest/usno-b.xml
ERROR: Cannot open file (cache$.f2018547945)

Then I made:
Code:
% cd iraf/extern
% pwd
/iraf/iraf/extern
% make mscred
Setting architecture: 'linux' ....
Adding dependency 'fitsutil' ....
Installing package 'fitsutil' ....  [OK]
Installing package 'mscred' ....  [OK]

Then "mkiraf", "cl", "mksred", "setinstr..." and I get again:
Code:
mscred> ccdlist a
a[im1][1036,2032][ushort][][1][]:SYBIA_1
a[im2][1036,2032][ushort][][2][]:SYBIA_1
mscred> ccdproc a
a[im1]: Apr 17 14:37 Trim is [9:1016,9:2024]
a[im1]: Apr 17 14:37 Overscan is [1020:1035,9:2024], mean 1810.755
a[im2]: Apr 17 14:37 Trim is [9:1016,9:2024]
a[im2]: Apr 17 14:37 Overscan is [1020:1035,9:2024], mean 1807.158
a: Merge amplifiers
ERROR: segmentation violation
  "imdelete (mergeinput, verify-)"
     line 442: mscsrc$ccdproc.cl
     called as: `ccdproc (images=a)'

So I did a step back installing the version 2.15.1a, then:
Code:
ccdlist a
a[im1][1036,2032][ushort][][1][]:SYBIA_1
a[im2][1036,2032][ushort][][2][]:SYBIA_1
mscred> ccdproc a
a[im1]: Apr 17 15:21 Trim is [9:1016,9:2024]
a[im1]: Apr 17 15:21 Overscan is [1020:1035,9:2024], mean 1810.751
a[im2]: Apr 17 15:21 Trim is [9:1016,9:2024]
a[im2]: Apr 17 15:21 Overscan is [1020:1035,9:2024], mean 1807.149
a: Merge amplifiers

So this version is correct.
Back to top
View user's profile Send private message
fitz
Site Admin


Joined: 30 Sep 2005
Posts: 3256
Location: Tucson
PostPosted: Fri Apr 20, 2012 9:11 pm    Post subject: Reply with quote
Would you mind posting the dates of the binaries or otherwise verify they are at least April 11 or later?? I've tried several machines and updated in the same way I posted, however it works just fine for me.
If you installed a distribution file with multiple binaries, could you also do a "show arch" at the CL prompt to verify the architecture being used (i.e. the updates were for 'linux', is there a chance something is running 'linux64'??).
Back to top
View user's profile Send private message
rji
Active IRAF User


Joined: 21 Apr 2007
Posts: 87
PostPosted: Sat Apr 21, 2012 8:10 am    Post subject: Reply with quote
I did the complete re-installation of the last binaries for 'linux32' and now it works fine with 'mscred' and 'ds9.xml' as well. Thank you.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    iraf.net Forum Index -> General IRAF All times are GMT
Goto page Previous  1, 2
Page 2 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2009 phpBB Group
 Copyright © 2005-2011 iraf.net
 All trademarks and copyrights on this page are owned by their respective owners.		 Powered By Geeklog 
Created this page in 0.12 seconds