From fitsbits-request Wed May 4 21:12:32 1994 X-VM-Message-Order: (1 2 3 4 5 8 6 9 11 12 13 7 10 15 16 14 18 19 17) Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1081" "Tue" " 3" "May" "1994" "22:03:28" "-0800" "Mark Gaponoff" "gaponoff at halcyon.com" "" "22" "FITS on Mac via NIH Image Mods" "^From:" nil nil "5" "1994050406:03:28" "FITS on Mac via NIH Image Mods" (number " " mark " Mark Gaponoff May 3 22/1081 " thread-indent "\"FITS on Mac via NIH Image Mods\"\n") nil] nil) X-VM-Summary-Format: "%n %*%a %-17.17F %-3.3m %2d %4l/%-5c %I\"%s\"\n" X-VM-Labels: nil X-VM-VHeader: ("Resent-" "From:" "Sender:" "To:" "Apparently-To:" "Cc:" "Subject:" "Date:") nil X-VM-Bookmark: 19 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA01137; Wed, 4 May 94 21:12:32 EDT Return-Path: Message-Id: Organization: Northwest Nexus Inc. Path: saips.cv.nrao.edu!hearst.acc.Virginia.EDU!caen!math.ohio-state.edu!cyber2.cyberstore.ca!nwnexus!NewsWatcher!user From: gaponoff at halcyon.com (Mark Gaponoff) Sender: fitsbits-request at fits.CV.NRAO.EDU To: fitsbits at fits.CV.NRAO.EDU Subject: FITS on Mac via NIH Image Mods Date: Tue, 03 May 1994 22:03:28 -0800 I have been working with Dr. Balick at the University of Washington to develop a Mac based astronomical image processing program. We have based our work on modifying NIH Image, a source-code-in-public- domain medical image processing program. We have attained some success in this effort, and can read various FITS files fine, but it has been difficult to keep up with the changes in NIH Image and its platform, THINK PASCAL. NIH Image is a full-featured image processing program, but it does not read FITS. (A MACRO for FITS is in the NIH package, but it only works for a very limited fixed-format subset of FITS files.) Our modification of NIH Image, called "MyImage", reads arbitrary FITS headers, plus handles 16 or 32 bit pixels, plus does logarithmic interpolation. Our most recent version of Myimage (0.06) is a modification of NIH Image version 1.41. We would like to continue the effort, but could use some help, especially with testing and enthusiasm-generation. Anyone out there interested? Please reply to this newsgroup, or to "gaponoff at halcyon.com". From fitsbits-request Thu May 5 03:48:13 1994 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1033" "" " 4" "May" "1994" "09:19" "EDT" "BARRY M. SCHLESINGER" "bschlesinger at nssdca.gsfc.nasa.gov" "<4MAY199409193056 at nssdca.gsfc.nasa.gov>" "24" "Re: FITS on Mac via NIH Image Mods" "^From:" nil nil "5" "1994050413:19:00" "FITS on Mac via NIH Image Mods" (number " " mark " BARRY M. SCHLESIN May 4 24/1033 " thread-indent "\"Re: FITS on Mac via NIH Image Mods\"\n") ""] nil) Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA01303; Thu, 5 May 94 03:48:13 EDT Return-Path: Message-Id: <4MAY199409193056 at nssdca.gsfc.nasa.gov> Organization: NASA - Goddard Space Flight Center Path: saips.cv.nrao.edu!hearst.acc.Virginia.EDU!caen!math.ohio-state.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!ames!newsfeed.gsfc.nasa.gov!nssdca.gsfc.nasa.gov!bschlesinger References: From: bschlesinger at nssdca.gsfc.nasa.gov (BARRY M. SCHLESINGER) Sender: fitsbits-request at fits.CV.NRAO.EDU To: fitsbits at fits.CV.NRAO.EDU Subject: Re: FITS on Mac via NIH Image Mods Date: 4 May 1994 09:19 EDT In article , gaponoff at halcyon.com (Mark Gaponoff) writes... >I have been working with Dr. Balick at the University of Washington >to develop a Mac based astronomical image processing program. We >have based our work on modifying NIH Image.... We have attained some >success in this effort, and can read various FITS files... > >NIH Image is a full-featured image processing program, but it does >not read FITS. (A MACRO for FITS is in the NIH package, but it only >works for a very limited fixed-format subset of FITS files.) Our >modification of NIH Image, called "MyImage", reads arbitrary FITS >headers, plus handles 16 or 32 bit pixels, plus does logarithmic >interpolation. Our most recent version of Myimage (0.06) is a >modification of NIH Image version 1.41. > A couple of specific questions about your modified NIH image... Can it handle IEEE floating point in the data array? What values of NAXIS will it accept? Barry Schlesinger NSSDC/NOST FITS Support Office From fitsbits-request Mon May 9 04:41:30 1994 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1172" "Mon" " 9" "May" "1994" "00:01:54" "-0800" "Mark Gaponoff" "gaponoff at halcyon.com" "" "25" "FITS on MAC/NIH Image mods: Re-Post" "^From:" nil nil "5" "1994050908:01:54" "FITS on MAC/NIH Image mods: Re-Post" (number " " mark " Mark Gaponoff May 9 25/1172 " thread-indent "\"FITS on MAC/NIH Image mods: Re-Post\"\n") nil] nil) Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA00603; Mon, 9 May 94 04:41:30 EDT Return-Path: Message-Id: Organization: Northwest Nexus Inc. Path: saips.cv.nrao.edu!hearst.acc.Virginia.EDU!concert!news-feed-1.peachnet.edu!emory!europa.eng.gtefsd.com!howland.reston.ans.net!pipex!uknet!EU.net!uunet!nwnexus!NewsWatcher!user From: gaponoff at halcyon.com (Mark Gaponoff) Sender: fitsbits-request at fits.CV.NRAO.EDU To: fitsbits at fits.CV.NRAO.EDU Subject: FITS on MAC/NIH Image mods: Re-Post Date: Mon, 09 May 1994 00:01:54 -0800 I have been working with Dr. Balick at the University of Washington to develop a Mac based astronomical image processing program. We have based our work on modifying NIH Image, a source-code-in-public- domain medical image processing program. We have attained some success in this effort, and can read various FITS files fine, but it has been difficult to keep up with the changes in NIH Image and its platform, THINK PASCAL. NIH Image is a full-featured image processing program, but it does not read FITS. (A MACRO for FITS is in the NIH package, but it only works for a very limited fixed-format subset of FITS files.) Our modification of NIH Image, called "MyImage", reads arbitrary FITS headers, plus handles 16 or 32 bit pixels, plus does logarithmic interpolation. Our most recent version of Myimage (0.06) is a modification of NIH Image version 1.41. We would like to continue the effort, but could use some help, especially with testing and enthusiasm-generation. Anyone out there interested? Please reply to this newsgroup, or to "gaponoff at halcyon.com". To those that have replied, Thank you for your attention, and I hope this can be helpful. From fitsbits-request Thu May 12 01:18:21 1994 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1554" "Thu" "12" "May" "1994" "01:18:12" "-0400" "Ian M George, Code 668, NASA/GSFC, USA (Usque ad mortem bibendum)" "GEORGE at heagip.gsfc.nasa.gov" "<940512011812.20e0013b at heagip.gsfc.nasa.gov>" "38" "The OGIP data quality flag convention (OFWG prelim. recomm p20.3)" "^From:" nil nil "5" "1994051205:18:12" "The OGIP data quality flag convention (OFWG prelim. recomm p20.3)" (number " " mark " Ian M George, Cod May 12 38/1554 " thread-indent "\"The OGIP data quality flag convention (OFWG prelim. recomm p20.3)\"\n") nil] nil) Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA09610; Thu, 12 May 94 01:18:21 EDT Return-Path: Message-Id: <940512011812.20e0013b at heagip.gsfc.nasa.gov> From: "Ian M George, Code 668, NASA/GSFC, USA (Usque ad mortem bibendum)" Sender: fitsbits-request at fits.CV.NRAO.EDU To: fitsbits at fits.CV.NRAO.EDU Cc: GEORGE at heagip.gsfc.nasa.gov Subject: The OGIP data quality flag convention (OFWG prelim. recomm p20.3) Date: Thu, 12 May 1994 1:18:12 -0400 (EDT) THE OGIP DATA QUALITY FLAG CONVENTION ------------------------------------- At a meeting of the OGIP FITS Working Group (OFWG) on 1994 May 11, a convention was preliminarily approved regarding the values used to flag good & bad data within FITS datasets produced by the OGIP. Since this convention may be of interest to the general community it is being posted here. Comments from the rest of the community are invited. The OFWG plans to take a final vote on this proposal in a couple of weeks. Ian M George on behalf of the OFWG --------------------------------------------------------------------------- OFWG Prelim Recommendation p20.3 ----------------------------------------- | THE OGIP DATA QUALITY FLAG CONVENTION | ----------------------------------------- Version: 1994 May 11 The meaning and use of quality flags is often specific to a given instrument and/or data type. However, when devising quality flags for new FITS files, the OFWG recommends that the integer value 0 (zero) be used to indicate that the data to which the flag refers is of GOOD quality, and is to be automatically used by downstream software. An instrument/dataset/application-specific scale of non-zero quality flag values can be used to indicate why the data is considered of bad quality, the degree of 'badness', and data flagged to be ignored in downstream applications by the user. ----------------------------------- END ---------------------------------- Ian M George NASA/GSFC OFWG 1994 May 11 From fitsbits-request Mon May 16 19:55:17 1994 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["348" "Mon" "16" "May" "1994" "18:14:58" "GMT" "Dominique Beauchamp" "beaucham at phy.ulaval.ca" "" "16" "FITS viewer for OS/2 PM " "^From:" nil nil "5" "1994051618:14:58" "FITS viewer for OS/2 PM " (number " " mark " Dominique Beaucha May 16 16/348 " thread-indent "\"FITS viewer for OS/2 PM \"\n") nil] nil) Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA22173; Mon, 16 May 94 19:55:17 EDT Return-Path: Message-Id: Organization: CRAPUL Path: saips.cv.nrao.edu!hearst.acc.Virginia.EDU!concert!inxs.concert.net!taco.cc.ncsu.edu!gatech!news-feed-2.peachnet.edu!news-feed-1.peachnet.edu!news.duke.edu!MathWorks.Com!europa.eng.gtefsd.com!howland.reston.ans.net!cs.utexas.edu!utnut!utcsri!newsflash.concordia.ca!CC.UMontreal.CA!IRO.UMontreal.CA!clouso.crim.ca!athena.ulaval.ca!astro!beaucham Reply-To: beaucham at phy.ulaval.ca From: beaucham at phy.ulaval.ca (Dominique Beauchamp) Sender: fitsbits-request at fits.CV.NRAO.EDU To: fitsbits at fits.CV.NRAO.EDU Subject: FITS viewer for OS/2 PM Date: Mon, 16 May 1994 18:14:58 GMT Version 0.4, release 1 of ViewFITS, is _again_ on ftp.cdrom.com in directory os2/incoming under the name vf04r1.zip. Thanks. Dominique --- Dominique Beauchamp | Developer of ViewFITS, a FITS Labo. d'astrophysique, | viewer for OS/2 2.1 U. Laval, Ste-Foy, G1K7P4 | Last release: April 1994 beaucham at phy.ulaval.ca | ftp.cdrom.com From fitsbits-request Wed May 18 16:18:38 1994 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["601" "" "18" "May" "1994" "18:23:31" "GMT" "Patrick L. Nolan" "pln at egret0.Stanford.EDU" "<2rdmf3$j74 at nntp2.Stanford.EDU>" "13" "How many HISTORY lines?" "^From:" nil nil "5" "1994051818:23:31" "How many HISTORY lines?" (number " " mark " Patrick L. Nolan May 18 13/601 " thread-indent "\"How many HISTORY lines?\"\n") nil] nil) Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA27908; Wed, 18 May 94 16:18:38 EDT Return-Path: Message-Id: <2rdmf3$j74 at nntp2.Stanford.EDU> Organization: Stanford University Path: saips.cv.nrao.edu!hearst.acc.Virginia.EDU!concert!gatech!udel!MathWorks.Com!europa.eng.gtefsd.com!howland.reston.ans.net!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!lll-winken.llnl.gov!unixhub!headwall.Stanford.EDU!pln Reply-To: pln at egret0.Stanford.EDU From: pln at egret0.Stanford.EDU (Patrick L. Nolan) Sender: fitsbits-request at fits.CV.NRAO.EDU To: fitsbits at fits.CV.NRAO.EDU Subject: How many HISTORY lines? Date: 18 May 1994 18:23:31 GMT How can I tell when I have read all of the HISTORY lines in a file header? I'm working with FITSIO 3.31 (Fortran) on a Sun. I can use FTGKYS to read HISTORY lines one at a time, but when I get to the end of the list it just starts over from the beginning. Is there some way to tell how many there are, or when I have read the last one? -- * Patrick L. Nolan (415)723-0133 * * W. W. Hansen Experimental Physics Laboratory (HEPL) * * Stanford University * * Bitnet: PLN at SLACVM Internet: pln at egret0.stanford.edu * From fitsbits-request Wed May 18 16:39:32 1994 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["823" "Wed" "18" "May" "1994" "17:42:01" "GMT" "Jeffrey Oliver Breen" "job5g at algol.astro.Virginia.EDU" "" "20" "Compressed Data in FITS files?" "^From:" nil nil "5" "1994051817:42:01" "Compressed Data in FITS files?" (number " " mark " Jeffrey Oliver Br May 18 20/823 " thread-indent "\"Compressed Data in FITS files?\"\n") nil] nil) Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA27922; Wed, 18 May 94 16:39:32 EDT Return-Path: Message-Id: Organization: Department of Astronomy, University of Virginia Path: saips.cv.nrao.edu!hearst.acc.Virginia.EDU!murdoch!algol.astro.Virginia.EDU!job5g From: job5g at algol.astro.Virginia.EDU (Jeffrey Oliver Breen) Sender: fitsbits-request at fits.CV.NRAO.EDU To: fitsbits at fits.CV.NRAO.EDU Subject: Compressed Data in FITS files? Date: Wed, 18 May 1994 17:42:01 GMT Hi there, I recently had to deal with some large, sparse FITS arrays (i.e. many of the pixels were 0). These files turned out to be highly compressible -- up to 96% using GNU's gzip! Since one of the goals of the FITS format is long-term storage, I was wondering if there would be any interest in a new, compressed array extension. There are some great compression algorithms out there in the public domain nowadays so that shouldn't be a problem. Thanks, Jeffrey +---------- | Jeffrey Oliver Breen Ensure | Department of Astronomy "Even logic must give e-mail | University of Virginia way to physics." privacy: | Charlottesville, VA 22903 - Capt. Spock, encrypt | job5g at Virginia.edu Star Trek VI with PGP From fitsbits-request Thu May 19 00:46:53 1994 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1135" "Thu" "19" "May" "1994" "04:06:10" "GMT" "Greg Hennessy" "gsh7w at fermi.clas.Virginia.EDU" "" "23" "Re: Compressed Data in FITS files?" "^From:" nil nil "5" "1994051904:06:10" "Compressed Data in FITS files?" (number " " mark " Greg Hennessy May 19 23/1135 " thread-indent "\"Re: Compressed Data in FITS files?\"\n") ""] nil) Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA28215; Thu, 19 May 94 00:46:53 EDT Return-Path: Message-Id: Organization: University of Virginia Path: saips.cv.nrao.edu!hearst.acc.Virginia.EDU!murdoch!fermi.clas.Virginia.EDU!gsh7w References: From: gsh7w at fermi.clas.Virginia.EDU (Greg Hennessy) Sender: fitsbits-request at fits.CV.NRAO.EDU To: fitsbits at fits.CV.NRAO.EDU Subject: Re: Compressed Data in FITS files? Date: Thu, 19 May 1994 04:06:10 GMT Jeffrey Oliver Breen wrote: #Hi there, # #I recently had to deal with some large, sparse FITS arrays (i.e. many of the #pixels were 0). These files turned out to be highly compressible -- #up to 96% using GNU's gzip! Since one of the goals of the FITS format #is long-term storage, I was wondering if there would be any interest #in a new, compressed array extension. There has been one paper (at least) written on compressed FITS, written by ARchie Warnock, with Barb Pfarr and Bib Hill as co-authors in some permutation, but it is a difficult problem. IF you compress the header, a human has difficulty determining what is in the file, and just because a compression program exists on the hot unix box that WRITES the files, it does not mean that a decompression program exists on the IBM 650 that is trying to *READ* the file. It makes little use to write a tape that others can't read. I personally almost *always* compress my FITS disk files though, even though I find in many circumstances that compress gets better reduction, and works much faster than the GNU gzip program. Greg Hennessy From fitsbits-request Sat May 21 15:19:38 1994 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["75" "" "21" "May" "1994" "19:01:27" "GMT" "Matthias Cramer" "ASTRO_MGR at EZINFO.VMSMAIL.ETHZ.CH" nil "7" "FITS Viewer for VMS or DECWindows" "^From:" nil nil "5" nil nil (number " " mark " Matthias Cramer May 21 7/75 " thread-indent "\"FITS Viewer for VMS or DECWindows\"\n") nil] nil) Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA08933; Sat, 21 May 94 15:19:38 EDT Return-Path: Message-Id: <2rllq7$18n at elna.ethz.ch> Organization: ETH ZUERICH Path: saips.cv.nrao.edu!hearst.acc.Virginia.EDU!concert!news-feed-2.peachnet.edu!emory!europa.eng.gtefsd.com!howland.reston.ans.net!EU.net!chsun!elna.ethz.ch!usenet From: ASTRO_MGR at EZINFO.VMSMAIL.ETHZ.CH (Matthias Cramer) Sender: fitsbits-request at fits.CV.NRAO.EDU To: fitsbits at fits.CV.NRAO.EDU Subject: FITS Viewer for VMS or DECWindows Date: 21 May 1994 19:01:27 GMT Hello All Knows anyone of you a FITS-Viewer for VMS or DECWindows ??? From fitsbits-request Sat May 21 19:02:54 1994 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["0" "Sat" "21" "May" "1994" "22:33:09" "GMT" "Mike Fitzpatrick" "fitz at noao.edu" nil "0" "Re: FITS Viewer for VMS or DECWindows" "^From:" nil nil "5" nil nil (number " " mark " Mike Fitzpatrick May 21 0/0 " thread-indent "\"Re: FITS Viewer for VMS or DECWindows\"\n") nil] nil) Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA09029; Sat, 21 May 94 19:02:54 EDT Return-Path: Message-Id: <1994May21.223309.20530 at noao.edu> Organization: National Optical Astronomy Observatories, Tucson, AZ, USA Path: saips.cv.nrao.edu!hearst.acc.Virginia.EDU!darwin.sura.net!howland.reston.ans.net!pipex!swrinde!elroy.jpl.nasa.gov!ncar!noao!fitz References: <2rllq7$18n at elna.ethz.ch> From: fitz at noao.edu (Mike Fitzpatrick) Sender: fitsbits-request at fits.CV.NRAO.EDU To: fitsbits at fits.CV.NRAO.EDU Subject: Re: FITS Viewer for VMS or DECWindows Date: Sat, 21 May 1994 22:33:09 GMT >From article <2rllq7$18n at elna.ethz.ch>, by ASTRO_MGR at EZINFO.VMSMAIL.ETHZ.CH (Matthias Cramer): Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["438" "" " 7" "" "" "" "AST" "article" "article" nil "12" "" nil nil nil "" nil nil (number " " mark " article 7 12/438 " thread-indent "\"\"\n") nil] nil) > > Knows anyone of you a FITS-Viewer for VMS or DECWindows ??? Mathias, Check out SAOimage from iraf.noao.edu (140.252.1.1 or 5355::iraf) in the 'iraf.old' subdirectory as "saoimage.tar.Z". If you need an uncompressed version or something other than a tar file let me know and I can make it available. SAOimage will run standalone to display FITS images under both VMS and Unix. If you have any problems or questions with it send mail to iraf at noao.edu. Cheers, Mike Fitzpatrick NOAO/IRAF Group From fitsbits-request Sat May 21 21:33:10 1994 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["3436" "Sun" "22" "May" "1994" "01:16:15" "GMT" "Jeffrey Oliver Breen" "job5g at algol.astro.Virginia.EDU" nil "69" "Re: Compressed Data in FITS files?" "^From:" nil nil "5" nil nil (number " " mark " Jeffrey Oliver Br May 22 69/3436 " thread-indent "\"Re: Compressed Data in FITS files?\"\n") nil] nil) Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA09057; Sat, 21 May 94 21:33:10 EDT Return-Path: Message-Id: Organization: Department of Astronomy, University of Virginia Path: saips.cv.nrao.edu!hearst.acc.Virginia.EDU!murdoch!algol.astro.Virginia.EDU!job5g References: From: job5g at algol.astro.Virginia.EDU (Jeffrey Oliver Breen) Sender: fitsbits-request at fits.CV.NRAO.EDU To: fitsbits at fits.CV.NRAO.EDU Subject: Re: Compressed Data in FITS files? Date: Sun, 22 May 1994 01:16:15 GMT In article , Greg Hennessy wrote: >There has been one paper (at least) written on compressed FITS, >written by ARchie Warnock, with Barb Pfarr and Bib Hill as co-authors >in some permutation, but it is a difficult problem. Thanks for the pointer -- I'll take a look at their paper. >IF you compress >the header, a human has difficulty determining what is in the file, >and just because a compression program exists on the hot unix box that >WRITES the files, it does not mean that a decompression program exists >on the IBM 650 that is trying to *READ* the file. It makes little use >to write a tape that others can't read. Indeed. That's exactly why "new FITS extension" popped into my head. That way the header is left as is, and only the array would be compressed. Plus, since it could be part of the next FITS revision, it would have to be supported on any platform boasting FITS compatability. If the IBM 650 supports FITS, it would have to read compressed arrays just as it is now expected to read binary tables. It is precisely because slick compression programs probably won't be ported to older machines that incorporating compression into the FITS standard is an attractive solution. >I personally almost *always* >compress my FITS disk files though, even though I find in many >circumstances that compress gets better reduction, and works much >faster than the GNU gzip program. Well, my experience is just the reverse, but I brought up gzip not for its performance, but for its status as free, public domain code (unlike compress) which we could pilfer to our hearts' content. In the realm of "lossy compression", in which you are willing to sacrifice some information for smaller files ("quick look" images, digital sky surveys, etc.), it seems necessary for us to design our own algorithms anyway. Bill Press gave an interesting talk on wavelet-based compression algorithms a couple of years ago in which he made the case that astronomers will never be satisfied with "commercial" lossy compression standards like JPEG or MPEG. This is mostly due to the fact that astronomical images are unlike the "terrestrial" images for which these standards are being developed: most of the image is uninteresting (=sky background) and the brightest pixels are _not_ flukes but rather are often the focus of interest. While I don't propose settling on an absolute standard for all types of data compression in astronomy right now, it might be worth the effort to think about a framework which could be built upon later. We could start, for instance, with a new type "Z" for compressed data and a new FITS header like "ZTYPE". Start off with ZTYPE = 0 for gzip-like non-lossy compression and work from there. Then down the road, maybe add a ZTYPE = 1 for JPEG or 2 for FitsPress-like wavelet compression or whatever. Anyway, this is just a thought. I'd be curious to hear from anyone who's thought more about this. In the meantime, I'll find that paper and do some homework. Cheers, Jeffrey +---------- | Jeffrey Oliver Breen Ensure | Department of Astronomy "Even logic must give e-mail | University of Virginia way to physics." privacy: | Charlottesville, VA 22903 - Capt. Spock, encrypt | job5g at Virginia.edu Star Trek VI with PGP From fitsbits-request Sun May 22 07:34:55 1994 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["549" "Sun" "22" "May" "1994" "07:35:40" "-0400" "Selden E. Ball, Jr." "SEB at LNS62.LNS.CORNELL.EDU" nil "13" "Re: Compressed Data in FITS files?" "^From:" nil nil "5" nil nil (number " " mark " Selden E. Ball, J May 22 13/549 " thread-indent "\"Re: Compressed Data in FITS files?\"\n") nil] nil) Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA11320; Sun, 22 May 94 07:34:55 EDT Return-Path: Message-Id: <01HCMR87X0O2A74B5I at LNS62.LNS.CORNELL.EDU> X-Vms-To: IN%"job5g at algol.astro.Virginia.EDU" X-Vms-Cc: IN%"fitsbits at fits.cv.nrao.edu",SEB Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT From: "Selden E. Ball, Jr." Sender: fitsbits-request at fits.CV.NRAO.EDU To: job5g at algol.astro.Virginia.EDU Cc: fitsbits at fits.CV.NRAO.EDU Subject: Re: Compressed Data in FITS files? Date: Sun, 22 May 1994 07:35:40 -0400 (EDT) job5g at algol.astro.Virginia.EDU (Jeffrey Oliver Breen) wrote >Well, my experience is just the reverse, but I brought up gzip not for >its performance, but for its status as free, public domain code >(unlike compress) which we could pilfer to our hearts' content. Sorry, that is not the case. gzip is "Freely Redistributable," not "Public Domain." Since it is covered by the Free Software Foundation's "CopyLeft" license, many companies selling commercial imaging products that include Fits support would be extremely reluctant to use it. Selden From fitsbits-request Sun May 22 22:20:58 1994 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1204" "" "23" "May" "1994" "02:05:38" "GMT" "Allen S. Rout" "asr at beach.cis.ufl.edu" "" "31" "Re: Compressed Data in FITS files?" "^From:" nil nil "5" "1994052302:05:38" "Compressed Data in FITS files?" (number " " mark " Allen S. Rout May 23 31/1204 " thread-indent "\"Re: Compressed Data in FITS files?\"\n") ""] nil) Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA11845; Sun, 22 May 94 22:20:58 EDT Return-Path: Message-Id: Organization: University of Florida, Dept of CIS Path: saips.cv.nrao.edu!hearst.acc.Virginia.EDU!concert!gatech!usenet.ufl.edu!usenet.cis.ufl.edu!usenet.cis.ufl.edu!asr References: From: asr at beach.cis.ufl.edu (Allen S. Rout) Sender: fitsbits-request at fits.CV.NRAO.EDU To: fitsbits at fits.CV.NRAO.EDU Subject: Re: Compressed Data in FITS files? Date: 23 May 1994 02:05:38 GMT -=> Regarding: Re: Compressed Data in FITS files?: -=> gsh7w at fermi.clas.Virginia.EDU (Greg Hennessy) sez: > Jeffrey Oliver Breen wrote: > #Hi there, > # [ compress FITS files! gzip does wonders! ] > > [ ... ] just because a compression program exists on the hot unix box that > WRITES the files, it does not mean that a decompression program exists > on the IBM 650 that is trying to *READ* the file. Umm.. Call me a Unix geek, but... If you can find an architecture on which gzip will not compile succsessfully, you'll shortly have a great deal of attention from a lot of people trying to fix it. In general, the FSF and the GNU project are very, very, VERY quick to respond. Worrying about avaliability of gzip on should be, I contest, way down on your list of worries. -- < asr at cis.ufl.edu >| Please feel free to respond to anything I < (904)373-0906 >| say: I have strong opinions, but a wide-open < 1936 N.W. 2nd Avenue >| mind. < Gainesville, FL 32603 >| BUT KEEP THE FLAMES TO E-MAIL! (geez!) -"My marriage is on the rocks, but only because we can't find a blanket." My Home Page From fitsbits-request Sun May 22 22:34:08 1994 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1444" "Mon" "23" "May" "1994" "02:17:48" "GMT" "Jeffrey Oliver Breen" "job5g at algol.astro.Virginia.EDU" "" "33" "Re: Compressed Data in FITS files?" "^From:" nil nil "5" "1994052302:17:48" "Compressed Data in FITS files?" (number " " mark " Jeffrey Oliver Br May 23 33/1444 " thread-indent "\"Re: Compressed Data in FITS files?\"\n") "<01HCMR87X0O2A74B5I at lns62.lns.cornell.edu>"] nil) Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA11879; Sun, 22 May 94 22:34:08 EDT Return-Path: Message-Id: Organization: Department of Astronomy, University of Virginia Path: saips.cv.nrao.edu!hearst.acc.Virginia.EDU!murdoch!algol.astro.Virginia.EDU!job5g References: <01HCMR87X0O2A74B5I at lns62.lns.cornell.edu> From: job5g at algol.astro.Virginia.EDU (Jeffrey Oliver Breen) Sender: fitsbits-request at fits.CV.NRAO.EDU To: fitsbits at fits.CV.NRAO.EDU Subject: Re: Compressed Data in FITS files? Date: Mon, 23 May 1994 02:17:48 GMT In article <01HCMR87X0O2A74B5I at lns62.lns.cornell.edu>, Selden E. Ball, Jr. wrote: >job5g at algol.astro.Virginia.EDU (Jeffrey Oliver Breen) wrote > >>Well, my experience is just the reverse, but I brought up gzip not for >>its performance, but for its status as free, public domain code >>(unlike compress) which we could pilfer to our hearts' content. > >Sorry, that is not the case. gzip is "Freely Redistributable," >not "Public Domain." Since it is covered by the Free Software Foundation's >"CopyLeft" license, many companies selling commercial imaging products >that include Fits support would be extremely reluctant to use it. Thanks for pointing out my error (and thanks to those who sent me e-mail, too). While the gzip source code is copyrighted (or copylefted), its compression algorithms are not patented, and that's what really matters. If a compressed data extension were adopted into FITS, there wouldn't be any reason to even mention gzip in the specs. It's the algorithms which matter, not a specific implementation of them. Cheers, Jeffrey +---------- | Jeffrey Oliver Breen Ensure | Department of Astronomy "Even logic must give e-mail | University of Virginia way to physics." privacy: | Charlottesville, VA 22903 - Capt. Spock, encrypt | job5g at Virginia.edu Star Trek VI with PGP From fitsbits-request Mon May 23 12:01:10 1994 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["2159" "" "23" "May" "1994" "11:42" "EDT" "BARRY M. SCHLESINGER" "bschlesinger at nssdca.gsfc.nasa.gov" "<23MAY199411421102 at nssdca.gsfc.nasa.gov>" "43" "New NOST User's Guide, version 3.1, LaTeX and PostScript" "^From:" nil nil "5" "1994052315:42:00" "New NOST User's Guide, version 3.1, LaTeX and PostScript" (number " " mark " BARRY M. SCHLESIN May 23 43/2159 " thread-indent "\"New NOST User's Guide, version 3.1, LaTeX and PostScript\"\n") nil] nil) Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA13749; Mon, 23 May 94 12:01:10 EDT Return-Path: Message-Id: <23MAY199411421102 at nssdca.gsfc.nasa.gov> Organization: NASA - Goddard Space Flight Center Path: saips.cv.nrao.edu!hearst.acc.Virginia.EDU!concert!gatech!udel!MathWorks.Com!europa.eng.gtefsd.com!news.umbc.edu!haven.umd.edu!ames!newsfeed.gsfc.nasa.gov!nssdca.gsfc.nasa.gov!bschlesinger From: bschlesinger at nssdca.gsfc.nasa.gov (BARRY M. SCHLESINGER) Sender: fitsbits-request at fits.CV.NRAO.EDU To: fitsbits at fits.CV.NRAO.EDU Subject: New NOST User's Guide, version 3.1, LaTeX and PostScript Date: 23 May 1994 11:42 EDT Version 3.1 of the NASA/Science Office of Standards and Technology (NOST) User's Guide to the Flexible Image Transport System (FITS) is now available. For the first time, the User's Guide can be obtained electronically in LaTeX format. A PostScript version of the User's Guide, produced from the LaTeX form, is also available. This PostScript version is quite large, 1150 VAX blocks, or about 600 Kbytes. Methods for generating a compressed version are being investigated. Printed copies are also available. While version 3.1 is not a full revision, there have been some changes from version 3.0. Progress of the BINTABLE and IMAGE extensions through the International Astronomical Union approval process has been noted. A discussion of the proposed convention for arrays of substrings in binary table fields has been added. The section on World Coordinates has been revised in light of the Greisen and Calabretta proposal and the discussion contained therein, and some of the issues that remain unresolved are noted. The discussion of IEEE floating point has been amplified, and the appendix on special values expanded to include all permitted special values. A number of additional updates and corrections have been made. The electronic copies of the User's Guide are available from ftp://nssdca.gsfc.nasa.gov/fits or by DECnet copy from NSSDCA, in the directory FITS. The LaTeX version is in the file USERS_GUIDE.TEX, while USERS_GUIDE.PS holds the new PostScript version. The LaTeX version requires the accompanying GUIDE.STY style file. Printed copies of the User's Guide can be obtained from the NOST Librarian. If you request a printed copy, provide a complete mailing address. The Librarian can also provide electronic copies of the User's Guide by mail to those without ftp access. The NOST Librarian can be reached as follows: (Postal) NASA/Science Office of Standards and Technology Code 633.2 Goddard Space Flight Center Greenbelt MD 20771 USA (Internet) nost at nssdca.gsfc.nasa.gov (DECnet) NCF::NOST Telephone: +1-301-286-3575 If the Librarian is unavailable, a phone mail system takes the call after four rings. From fitsbits-request Tue May 24 11:19:48 1994 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1482" "" "24" "May" "1994" "01:07:22" "GMT" "Allyn Tennant" "tennant at alph.msfc.nasa.gov" "<2rrk0a$bra at hammer.msfc.nasa.gov>" "30" "Re: Compressed Data in FITS files?" "^From:" nil nil "5" "1994052401:07:22" "Compressed Data in FITS files?" (number " " mark " Allyn Tennant May 24 30/1482 " thread-indent "\"Re: Compressed Data in FITS files?\"\n") ""] nil) Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA24418; Tue, 24 May 94 11:19:48 EDT Return-Path: Message-Id: <2rrk0a$bra at hammer.msfc.nasa.gov> Organization: NASA/MSFC Path: saips.cv.nrao.edu!hearst.acc.Virginia.EDU!concert!news-feed-1.peachnet.edu!emory!sol.ctr.columbia.edu!news.msfc.nasa.gov!usenet References: Reply-To: tennant at alph.msfc.nasa.gov From: tennant at alph.msfc.nasa.gov (Allyn Tennant) Sender: fitsbits-request at fits.CV.NRAO.EDU To: fitsbits at fits.CV.NRAO.EDU Subject: Re: Compressed Data in FITS files? Date: 24 May 1994 01:07:22 GMT In article > While I don't propose settling on an absolute standard for all > types of data compression in astronomy right now, it might be worth > the effort to think about a framework which could be built upon later. > We could start, for instance, with a new type "Z" for compressed data > and a new FITS header like "ZTYPE". Start off with ZTYPE = 0 for > gzip-like non-lossy compression and work from there. Then down the > road, maybe add a ZTYPE = 1 for JPEG or 2 for FitsPress-like wavelet > compression or whatever. > Aaargh! Since FITS forces you to use 80 columns to describe a single parameter, there is no advantage to numbers as parameter values. Thus it would be much better to use ZTYPE='GZIP' for gzip and ZTYPE='JPEG' for... Since I've felt it necessary to comment on this, let me point out that I do *not* endorse adding such compression standards to FITS. First, anyone can use gzip (or compress) to compress files, and likewise use zcat to view the header. Thus the existing use of gzip/zcat is a standard in that someone who has never heard of FITS would be able to compress/uncompress the file. Likewise if you want to jpeg compress an image, you should write a *.jpg file and there are lots of existing tools that can manipulate *.jpg files and zero tools (to my knowledge at least :-) that can manipulate JPEG data inside a FITS file. There is no reason for FITS users to reinvent these tools. Allyn From fitsbits-request Fri May 27 13:40:08 1994 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["497" "Fri" "27" "May" "1994" "13:40:01" "-0400" "RANDY THOMPSON (301) 286-8800" "RTHOMPSON at iuedac.gsfc.nasa.gov" "<940527134001.27603d1f at iuedac.gsfc.nasa.gov>" "11" "FITS Image Extension" "^From:" nil nil "5" "1994052717:40:01" "FITS Image Extension" (number " " mark " RANDY THOMPSON (3 May 27 11/497 " thread-indent "\"FITS Image Extension\"\n") nil] nil) Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA02554; Fri, 27 May 94 13:40:08 EDT Return-Path: Message-Id: <940527134001.27603d1f at iuedac.gsfc.nasa.gov> From: RANDY THOMPSON (301) 286-8800 Sender: fitsbits-request at fits.CV.NRAO.EDU To: fitsbits at fits.CV.NRAO.EDU Cc: RTHOMPSON at iuedac.gsfc.nasa.gov Subject: FITS Image Extension Date: Fri, 27 May 1994 13:40:01 -0400 (EDT) A paper describing the FITS image extension has been published in the Astronomy and Astrophysics Supplements. The reference is Astron. Astrophys. Suppl. Ser. 105, 53-55 (1994). The image extension, as recently approved by the European, WGAS, and Japanese FITS committees, is basically a replication of the primary header and data unit following the guidelines and rules for FITS extensions. A limited number of reprints will be available soon. Randy Thompson IUE Data Analysis Center From fitsbits-request Fri May 27 16:30:19 1994 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["251" "Fri" "27" "May" "1994" "16:30:09" "-0400" "RANDY THOMPSON (301) 286-8800" "RTHOMPSON at iuedac.gsfc.nasa.gov" "<940527163009.27603d1f at iuedac.gsfc.nasa.gov>" "10" "RE: Image Extension Paper" "^From:" nil nil "5" "1994052720:30:09" "Image Extension Paper" (number " " mark " RANDY THOMPSON (3 May 27 10/251 " thread-indent "\"RE: Image Extension Paper\"\n") nil] nil) Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA02811; Fri, 27 May 94 16:30:19 EDT Return-Path: Message-Id: <940527163009.27603d1f at iuedac.gsfc.nasa.gov> From: RANDY THOMPSON (301) 286-8800 Sender: fitsbits-request at fits.CV.NRAO.EDU To: fitsbits at fits.CV.NRAO.EDU Cc: RTHOMPSON at iuedac.gsfc.nasa.gov Subject: RE: Image Extension Paper Date: Fri, 27 May 1994 16:30:09 -0400 (EDT) I inadvertently left out the title and authors of the FITS image extension paper mentioned in the previous e-mail. The full reference would be: "The FITS image extension", Ponz J.D., Thompson R.W., Munoz J.R., 1994, A&AS 105, 53-55 From fitsbits-request Fri May 27 20:53:29 1994 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["2660" "" "25" "May" "1994" "15:01:10" "GMT" "Mike Hayden" "mhayden at cc.gettysburg.edu" "<2rvp7m$d48 at jupiter.cc.gettysburg.edu>" "56" "Correction to FITS Header editor notice" "^From:" nil nil "5" "1994052515:01:10" "Correction to FITS Header editor notice" (number " " mark " Mike Hayden May 25 56/2660 " thread-indent "\"Correction to FITS Header editor notice\"\n") nil] nil) Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA03034; Fri, 27 May 94 20:53:29 EDT Return-Path: Message-Id: <2rvp7m$d48 at jupiter.cc.gettysburg.edu> Organization: Gettysburg College Physics Department Path: saips.cv.nrao.edu!hearst.acc.Virginia.EDU!concert!gatech!psuvax1!news.pop.psu.edu!news.cac.psu.edu!jupiter.cc.gettysburg.edu!io!marschal Reply-To: mhayden at cc.gettysburg.edu From: mhayden at cc.gettysburg.edu (Mike Hayden) Sender: fitsbits-request at fits.CV.NRAO.EDU To: fitsbits at fits.CV.NRAO.EDU Subject: Correction to FITS Header editor notice Date: 25 May 1994 15:01:10 GMT The Fits Header Editor This is a corrected announcement of a new tool that enables users of Windows to edit FITS headers conveniently. For those who have been troubled by incompatibility betewen the FITS files their cameras produce and the FITS files their image processing programs require, this is the ticket. An earlier announcement had an ambiguous internet address. The Fits Header Editor (FHE) provides a useful tool to directly edit the basic FITS header without corrupting the attached data array. Using FHE it is possible to change the value of any keyword in a FITS header, add new keywords and values or delete lines of the header. FHE can import a pre-formatted text file directly into an existing HDU, and features a logging function which permits selected keywords and their values to be defined and then written to a disk file for logging or administrative purposes. Some of these features are available in IRAF for systems that will support it, but FHE is PC based and runs under Windows. With FHE, the ability to edit and manipulate the header of FITS files of any arbitrary size has been extended to the PC environment. FHE uses a graphical user interface, is mouse driven and intuitive in use. FHE takes only minutes to learn and is far easier to master than a command line oriented system. Simple online help is available to guide the new user through the basics. A brief documentation file is provided and explains important details regarding the FHE files and their formats and supplemental information. Written as a true Windows application, the look and feel of FHE provides users with a familiar and comfortable operating environment. Its various screens are visually appealing and use a convenient combination of buttons and menu bars. FHE should run on any machine capable of running Windows 3.1 or better. A VGA card is sufficient, but SVGA or better is preferred, particularly for the spectacular sign-on image which features the post servicing Space Telescope image of the core of M100. Installation is simple and swift using a setup routine provided with the software. FHE is distributed freely as shareware, with a very modest $10 registration fee for single users. FHE is available via anonymous ftp at io.cc.gettysburg.edu in the directory /pub/misc/pc. Alternatively, the editor can be loaded via The Gettysburg Gazette BBS at 717-334-0736 (8N1, up to 19.2K) and will be distributed to other popular Internet sites throughout the summer. Inquiries can be directed to mhayden at gettyburg.edu or to M. B. Hayden, P.O. Box 3573, Gettysburg. PA 17325.