From dwells at fits.cx.nrao.edu Tue Feb 4 10:22:51 1992 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: 1 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1048" "Tue" "4" "February" "1992" "15:20:02" "GMT" "Don Wells" "dwells at fits.cx.nrao.edu " nil "20" "SI-units discussion available" "^From:" nil nil "2" nil nil (number " " mark " Don Wells Feb 4 20/1048 " thread-indent "\"SI-units discussion available\"\n") nil] nil) Newsgroups: sci.astro,alt.sci.astro.fits Organization: National Radio Astronomy Observatory, Charlottesville, VA Distribution: sci From: dwells at fits.cx.nrao.edu (Don Wells) Subject: SI-units discussion available Date: Tue, 4 Feb 1992 15:20:02 GMT I have concatenated most of the recent sci.astro SI units discussion into a file which is available via anonymous FTP on fits.cx.nrao.edu [192.33.115.8] in directory FITS/fitsbits as the file: -rw-r--r-- 1 dwells 74858 Feb 3 09:57 sci.astro.9201.SI The messages are ordered in the file mostly by subject threads, not by time, due to the way my current newsreader (GNUS) operates. I expect that some parts of this discussion will prove to be useful to the FITS community in the future in formulating recommended practices for the units which are used in astronomical datasets. I want to thank all of you who participated; I was impressed with the general high quality and good spirit of the discussion which I started with my two initial postings. -- Donald C. Wells Associate Scientist dwells at nrao.edu National Radio Astronomy Observatory +1-804-296-0277 520 Edgemont Road Fax= +1-804-296-0278 Charlottesville, Virginia 22903-2475 USA 78:31.1W, 38:02.2N From EXOSAT at IMISIAM.MI.CNR.IT Sun Feb 16 22:26:55 1992 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1157" "Tue" "4" "February" "1992" "21:50:18" "GMT" "Lucio Chiappetti - IFC Milano" "EXOSAT at IMISIAM.MI.CNR.IT" nil "27" "Format of TFORMnnn keywords" "^From:" nil nil "2" nil nil (number " " mark " Lucio Chiappetti Feb 4 27/1157 " thread-indent "\"Format of TFORMnnn keywords\"\n") nil] nil) Newsgroups: alt.sci.astro.fits Organization: National Radio Astronomy Observatory From: Lucio Chiappetti - IFC Milano Subject: Format of TFORMnnn keywords Date: Tue, 4 Feb 1992 21:50:18 GMT Is there some specification more restrictive than the one stated at pag. 42 of NOST 100-0.3b FITS implementation standard concerning the content of TFORMnnn keywords ? Or some rule which may be adopted for analogy with other keywords ? What I am concerned with is the presence of leading blanks. If a TFORMnnn keyword might have values say from 1E to 999E, is it allowed to code it ' 1E', ' 10E' etc. (from '100E' it is OK), or shall it be flush left '1E' '10E' etc. ? \ Lucio Chiappetti ----------------------------------------------------------------------------- Lucio Chiappetti Istituto di Fisica Cosmica e Tecnologie Relative - CNR via Bassini 15 - I-20133 Milano - Italy Phone : +39 2 2363542 / 2665237 / 2665753 Telex : 313839 MUACNR I Fax : +39 2 2362946 E-mail: EXOSAT at IMISIAM (Bitnet) EXOSAT at IMISIAM.MI.CNR.IT (Internet) IFCTR::LUCIO (SPAN/DECNET) Bitnet node IMISIAM is Internet node (IMI)SIAM.MI.CNR.IT alias 192.65.131.1 Decnet node IFCTR is 38.698 (39610) and Internet node IFCTR.MI.CNR.IT alias 192.65.131.40. Acknowledge-To: From bschlesinger at nssdca.gsfc.nasa.gov Sun Feb 16 22:27:03 1992 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1663" "" "4" "February" "92" "19:33:00" "GMT" "Barry Schlesinger" "bschlesinger at nssdca.gsfc.nasa.gov " nil "32" "Re: Format of TFORMnnn keywords" "^From:" nil nil "2" nil nil (number " " mark " Barry Schlesinger Feb 4 32/1663 " thread-indent "\"Re: Format of TFORMnnn keywords\"\n") nil] nil) Newsgroups: alt.sci.astro.fits Summary: Fixed format Keywords: FITS, keywords Organization: NASA - Goddard Space Flight Center News-Software: VAX/VMS VNEWS 1.41 Nntp-Posting-Host: nssdca.gsfc.nasa.gov From: bschlesinger at nssdca.gsfc.nasa.gov (Barry Schlesinger) Subject: Re: Format of TFORMnnn keywords Date: 4 Feb 92 19:33:00 GMT In article <9202041554.AA26285 at fits.cx.nrao.edu>, Lucio Chiappetti - IFC Milano writes... >Is there some specification more restrictive than the one stated at pag. >42 of NOST 100-0.3b FITS implementation standard concerning the content >of TFORMnnn keywords ? >Or some rule which may be adopted for analogy with other keywords ? > >What I am concerned with is the presence of leading blanks. >If a TFORMnnn keyword might have values say from 1E to 999E, is it >allowed to code it ' 1E', ' 10E' etc. (from '100E' it is OK), or shall >it be flush left '1E' '10E' etc. ? The general rule governing value fields appears in FITS Paper I, "the value field will be written following the rules of ANSI FORTRAN 77 for list-directed input." The TFORMn keyword is required for the binary tables extension. Its value must therefore appear in the fixed format. (FITS Paper I: "use of a fixed format for the most essential parameters is required," interpreted by the NOST Panel to refer to required keywords.) Also note the interpretation from the NOST document, "Leading blanks are significant; trailing blanks are not." Because the allowed value is described as "rE", not " rE", that is, no leading blank specifically prescribed, the wording would appear to imply that leading blanks as not being allowed. Incidentally, note that the binary tables appendix of the NOST standard is simply the Cotton and Tody 'BINTABLE' proposal, changed only to fit the format of the NOST standard. It appears for reader information but should not be considered part of the NOST standard. Barry Schlesinger NSSDC/NOST FITS Support Office From thompson at stars.gsfc.nasa.gov Sun Feb 16 22:27:08 1992 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1423" "Tue" "4" "February" "1992" "21:38:00" "GMT" "William Thompson, code 682.1, x2040" "thompson at stars.gsfc.nasa.gov " nil "30" "Re: Format of TFORMnnn keywords" "^From:" nil nil "2" nil nil (number " " mark " William Thompson, Feb 4 30/1423 " thread-indent "\"Re: Format of TFORMnnn keywords\"\n") nil] nil) Newsgroups: alt.sci.astro.fits News-Software: VAX/VMS VNEWS 1.4-b1 Nntp-Posting-Host: stars.gsfc.nasa.gov Organization: NASA/GSFC-Laboratory for Astronomy and Solar Physics From: thompson at stars.gsfc.nasa.gov (William Thompson, code 682.1, x2040) Subject: Re: Format of TFORMnnn keywords Date: Tue, 4 Feb 1992 21:38:00 GMT In article <9202041554.AA26285 at fits.cx.nrao.edu>, Lucio Chiappetti - IFC Milano writes... >Is there some specification more restrictive than the one stated at pag. >42 of NOST 100-0.3b FITS implementation standard concerning the content >of TFORMnnn keywords ? >Or some rule which may be adopted for analogy with other keywords ? > >What I am concerned with is the presence of leading blanks. >If a TFORMnnn keyword might have values say from 1E to 999E, is it >allowed to code it ' 1E', ' 10E' etc. (from '100E' it is OK), or shall >it be flush left '1E' '10E' etc. ? > I may be misreading you, but you seem to imply that the number of elements in a binary table can only be up to 999. We are planning to store images in binary tables (using the TDIM convention) which are going to be much larger than 999 elements. On your main question, although it may not be in the section on binary tables, it is mentioned (somewhere) in the NOST document that leading blanks in string values are significant, while trailing blanks are not. I would interpret that to mean that the values of TFORM should be flush left. Also, it should be '10Ebbbbb' (where "b" stands for blank) and not '10E', since character string values are required to be at least eight characters long. I'm not the authority on this, you understand. I'm just presenting how I interpret the proposed standard. Bill Thompson From bschlesinger at nssdca.gsfc.nasa.gov Sun Feb 16 22:27:12 1992 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["621" "Thu" "6" "February" "1992" "14:10:47" "GMT" "Barry Schlesinger" "bschlesinger at nssdca.gsfc.nasa.gov " nil "16" "Re: Format of TFORMnnn keywords" "^From:" nil nil "2" nil nil (number " " mark " Barry Schlesinger Feb 6 16/621 " thread-indent "\"Re: Format of TFORMnnn keywords\"\n") nil] nil) Newsgroups: alt.sci.astro.fits Nntp-Posting-Host: nssdca.gsfc.nasa.gov Organization: Goddard Space Flight Center From: bschlesinger at nssdca.gsfc.nasa.gov (Barry Schlesinger) Subject: Re: Format of TFORMnnn keywords Date: Thu, 6 Feb 1992 14:10:47 GMT In article <4FEB199217382187 at stars.gsfc.nasa.gov>, thompson at stars.gsfc.nasa.gov (William Thompson, code 682.1, x2040) writes... > Also, it should be >'10Ebbbbb' (where "b" stands for blank) and not '10E', since character string >values are required to be at least eight characters long. > Yes. FITS Paper I specifies the fixed format for character strings as follows, "normally 8 characters in length although longer values are allowed; represented by a ' in column 11, followed by the string, followed by a close ' that cannot occur before column 20." Barry Schlesinger NSSDC/NOST FITS Support Office From eso!pgrosbol at fits.cx.nrao.edu Sun Feb 16 22:27:32 1992 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1231" "Fri" "7" "February" "1992" "11:29:21" "GMT" "eso!pgrosbol at fits.cx.nrao.edu" "eso!pgrosbol at fits.cx.nrao.edu" nil "26" "On RFD: sci.astro.fits" "^From:" nil nil "2" nil nil (number " " mark " eso!pgrosbol at fits Feb 7 26/1231 " thread-indent "\"On RFD: sci.astro.fits\"\n") nil] nil) Newsgroups: alt.sci.astro.fits Organization: National Radio Astronomy Observatory From: Subject: On RFD: sci.astro.fits Date: Fri, 7 Feb 1992 11:29:21 GMT Garching, Feb. 7, 1992 The FITS data format is used widely in the astronomical community and is essential for the exchange of data between institutes. Thus, it is important that questions, comments and information on the standard easily can be circulated in the community. This not only to clarify possible ambiguities and implementation issues but also to discuss future extensions to it. The FITS community was using normal or electronic mail for these purposes until last year when an 'alt' news group was created. Although e-mail can be used, it has two major disadvantages: a) it limits discussion to a predefined group, and b) broadcast of questions is not effective. These issues are solved by using the USEnet News. I believe it is very important to have an open discussion on widely used, common matters like FITS. Although the astronomical community only is counted in thousands, the availability of CD-ROM's with astronomical images and tables in FITS format will open the discussion among a large number of other users with general interest in astronomy. Thus, I strongly support the creating of a 'sci.astro.fits' News group. Preben Grosbol Chairman, IAU FITS WG From sla at helios.ucsc.edu Sun Feb 16 22:27:46 1992 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1418" "" "8" "February" "92" "22:46:34" "GMT" "Steve Allen" "sla at helios.ucsc.edu " nil "23" "RFD: sci.astro.fits" "^From:" nil nil "2" nil nil (number " " mark " Steve Allen Feb 8 23/1418 " thread-indent "\"RFD: sci.astro.fits\"\n") nil] nil) Newsgroups: alt.sci.astro.fits,news.groups Summary: enthsiastic support for creation Followup-To: news.groups Organization: UCO/Lick Observatory From: sla at helios.ucsc.edu (Steve Allen) Subject: RFD: sci.astro.fits Date: 8 Feb 92 22:46:34 GMT I support the creation of the new newsgroup sci.astro.fits The FITS standard is becoming more important for people both inside and outside the professional astronomical community. NASA is greatly accelerating the production of CD-ROMs containing astronomical data from many space missions. Much of these data is being written using FITS format. These data are of interest not only to researchers, but also to the general public. Furthermore, the existence of high-bandwidth networks has resulted in the routine shipment of newly acquired astronomical data >from site to site. New instruments and new demands for systematic archiving of data require discussion to allow evolution of the standard. The creation of the group alt.sci.astro.fits has allowed UCO/Lick Observatory to observe and participate in discussions about the evolution of the FITS standard. This was not possible before the advent of a.s.a.f, because limited travel funds prevented contact between the appropriate and interested parties. The creation of sci.astro.fits will make these discussions available to even more sites. _______________________________________________________________________________ Steve Allen | That was the equation! | sla at helios.ucsc.edu UCO/Lick Observatory | Existence!...Survival must | If the UC were opining, Santa Cruz, CA 95064 | cancel out programming! -- Ruk | it wouldn't tell me. From thompson at stars.gsfc.nasa.gov Sun Feb 16 22:29:42 1992 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1659" "" "10" "February" "92" "17:20:00" "GMT" "William Thompson, code 682.1, x2040" "thompson at stars.gsfc.nasa.gov " nil "33" "FITS binary tables" "^From:" nil nil "2" nil nil (number " " mark " William Thompson, Feb 10 33/1659 " thread-indent "\"FITS binary tables\"\n") nil] nil) Newsgroups: alt.sci.astro.fits Organization: NASA/GSFC-Laboratory for Astronomy and Solar Physics News-Software: VAX/VMS VNEWS 1.4-b1 Nntp-Posting-Host: stars.gsfc.nasa.gov From: thompson at stars.gsfc.nasa.gov (William Thompson, code 682.1, x2040) Subject: FITS binary tables Date: 10 Feb 92 17:20:00 GMT I am currently engaged in writing IDL-based I/O software for FITS binary tables. I want to get some clarification on one point. I'm not entirely clear about how bit arrays (denoted as 'X' in the TFORM keyword) are treated. Does the repeat parameter give the number of bits, or the number of bytes contained within the bit array? I.e., if TFORM1 = '100X ' then does this column contain 100 bits (rounded off to 13 bytes) or 800 bits within 100 bytes? On another topic, I've run into some problems with complex arrays in both primary FITS data units, and in binary tables, and I thought I'd air the techniques I'm using to get around them, to see if anybody had a different way to handle it. In standard FITS files, the BITPIX keyword has no way of marking an array as complex. Therefore, I decided to write complex arrays as floating point, with the first dimension (NAXIS1) being 2, and the remaining dimensions being the dimensions of the array. The comment attached to the NAXIS1 header record says that these are the real and imaginary parts of a complex number. No such problem occurs in FITS binary tables. However, IDL does not currently support a data type corresponding to 'M' (double-precision complex). Therefore, I am defining the reader software to treat such arrays as double-precision, with twice as many elements, and formatted such that the first dimension of the array is 2 (real and complex parts). The writing software will also be able to write double-precision arrays as type 'M' if the user tells it to, and if the first dimension of the array is 2. Does anyone envision any problems with that approach? Bill Thompson From bcotton at gorilla.CV.NRAO.EDU Sun Feb 16 22:29:48 1992 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["745" "Thu" "13" "February" "1992" "12:10:23" "GMT" "Bill Cotton" "bcotton at gorilla.CV.NRAO.EDU " nil "15" "Re: FITS binary tables" "^From:" nil nil "2" nil nil (number " " mark " Bill Cotton Feb 13 15/745 " thread-indent "\"Re: FITS binary tables\"\n") nil] nil) Newsgroups: alt.sci.astro.fits Organization: National Radio Astronomy Observatory From: bcotton at gorilla.CV.NRAO.EDU (Bill Cotton) Subject: Re: FITS binary tables Date: Thu, 13 Feb 1992 12:10:23 GMT William Thompson, code 682.1, x2040 writes: > I am currently engaged in writing IDL-based I/O software for FITS binary > tables. I want to get some clarification on one point. I'm not entirely clear > about how bit arrays (denoted as 'X' in the TFORM keyword) are treated. Does > the repeat parameter give the number of bits, or the number of bytes contained > within the bit array? I.e., if > > TFORM1 = '100X ' > > then does this column contain 100 bits (rounded off to 13 bytes) or 800 bits > within 100 bytes? The repeat count is the number of elements of the given type. Your example, TFORM1= '100X ', means an array of 100 bits occupying 13 bytes. The trailing bits of the final byte are undefined. -Bill Cotton From CUR%STARLINK.RUTHERFORD.AC.UK at VTVM2.CC.VT.EDU Sun Feb 16 22:30:07 1992 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1012" "Thu" "13" "February" "1992" "17:29:00" "GMT" "\"Malcolm J. Currie\"" "CUR%STARLINK.RUTHERFORD.AC.UK at VTVM2.CC.VT.EDU" nil "18" "(IUE)IMAGE extension" "^From:" nil nil "2" nil nil (number " " mark " \"Malcolm J. Curri Feb 13 18/1012 " thread-indent "\"(IUE)IMAGE extension\"\n") nil] nil) Newsgroups: alt.sci.astro.fits Organization: National Radio Astronomy Observatory From: "Malcolm J. Currie" Subject: (IUE)IMAGE extension Date: Thu, 13 Feb 1992 17:29:00 GMT Please can someone confirm that the only difference between the IMAGE and IUEIMAGE extensions a question of name, because "IMAGE", being generic, is reserved until or if the extension is approved by the FITS committees. In other words does the IUEIMAGE extension assume knowledge of IUE-specific keywords? Until the binary-table conventions for handling arrays become established I am planning to use the (IUE)IMAGE extension for the export of hierarchical datasets containing quality and/or variance data in addition to the main data array. Generally, for our datasets there is little wastage of space since the main headers will apply globally, save the mandatory headers, BSCALE, BZERO, EXTLEVEL and EXTNAME. ----------------------------------------------------------------------- Malcolm J. Currie | Span: RLVAD::CUR Starlink Project | Janet: CUR at UK.AC.RUTHERFORD.STARLINK | +44-235-21900 x6735 ----------------------------------------------------------------------- From dwells at fits.cx.nrao.edu Sun Feb 16 22:30:10 1992 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["2072" "Fri" "14" "February" "1992" "17:08:06" "GMT" "Don Wells" "dwells at fits.cx.nrao.edu " nil "48" "Re: (IUE)IMAGE extension" "^From:" nil nil "2" nil nil (number " " mark " Don Wells Feb 14 48/2072 " thread-indent "\"Re: (IUE)IMAGE extension\"\n") nil] nil) Newsgroups: alt.sci.astro.fits In-Reply-To: "Malcolm J. Currie"'s message of Thu, 13 Feb 1992 17: 29:00 GMT Organization: National Radio Astronomy Observatory, Charlottesville, VA From: dwells at fits.cx.nrao.edu (Don Wells) Subject: Re: (IUE)IMAGE extension Date: Fri, 14 Feb 1992 17:08:06 GMT [The following message arrived at my mailbox, probably in my guise as "fitsbits-request at fits.cx.nrao.edu", to which it may have been addressed (rather than to "fitsbits at fits.cx.nrao.edu"); the header is confusing, and I am unsure what happened. -Don] From: jmunoz at estsaa.DNET.NASA.GOV (J. R. Munoz_Peiro, SSD/SA/ISO (ESTEC), Ext. 3564) To: "fitsbits-request at fits.cx.nrao.edu" at EAST.DNET.NASA.GOV Subject: RE: (IUE)IMAGE extension Date: Fri, 14 Feb 92 10:50:32 -0500 From: EAST::"fitsbits-request at fits.cx.nrao.edu" 13-FEB-1992 20:28:30.62 To: FITSBITS at FITS.CX.NRAO.EDU CC: Subj: (IUE)IMAGE extension >Please can someone confirm that the only difference between the IMAGE >and IUEIMAGE extensions a question of name, because "IMAGE", being >generic, is reserved until or if the extension is approved by the FITS >committees. In other words does the IUEIMAGE extension assume knowledge >of IUE-specific keywords? > >Until the binary-table conventions for handling arrays become established I am planning to use the (IUE)IMAGE extension for the export >of hierarchical datasets containing quality and/or variance data in >addition to the main data array. Generally, for our datasets there is >little wastage of space since the main headers will apply globally, save >the mandatory headers, BSCALE, BZERO, EXTLEVEL and EXTNAME. You are right, IUEIMAGE is just a temporary extension name till it is approved by the FITS committees. I originally intended to call it just IMAGE but the European FITS committee recomended me to attach the 'IUE' part because it was initially born to accomodate IUE data (till wider usage could be found). As you may check, the extension doesn't contain any specific IUE keywords. Regards J.R. Munoz Peiro ESA/ESTEC/SAI -- Donald C. Wells Associate Scientist dwells at nrao.edu National Radio Astronomy Observatory +1-804-296-0277 520 Edgemont Road Fax= +1-804-296-0278 Charlottesville, Virginia 22903-2475 USA 78:31.1W, 38:02.2N From jdp at vilspa.DNET.NASA.GOV Sun Feb 16 22:30:33 1992 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1095" "Fri" "14" "February" "1992" "15:41:38" "GMT" "Jose Daniel Ponz VILSPA/VCS" "jdp at vilspa.DNET.NASA.GOV " nil "26" "RE: (IUE) Image Extension" "^From:" nil nil "2" nil nil (number " " mark " Jose Daniel Ponz Feb 14 26/1095 " thread-indent "\"RE: (IUE) Image Extension\"\n") nil] nil) Newsgroups: alt.sci.astro.fits Organization: National Radio Astronomy Observatory From: jdp at vilspa.DNET.NASA.GOV (Jose Daniel Ponz VILSPA/VCS) Subject: RE: (IUE) Image Extension Date: Fri, 14 Feb 1992 15:41:38 GMT RLVAD::CUR (Malcom J. Currie) asks the question: MC> Please can someone confirm that the only difference between the IMAGE MC> and IUEIMAGE extensions a question of name, because "IMAGE", being MC> generic, is reserved until or if the extension is approved by the FITS MC> committees. In other words does the IUEIMAGE extension assume knowledge MC> of IUE-specific keywords? The IUEIMAGE extension has been reserved for temporary use inside the IUE project until the generic IMAGE extension is approved by the FITS committees. IUEIMAGE does not assume knowledge on IUE specific keywords. The draft proposal for the IMAGE extension was submitted on 1992.2.7 to the Chairman of the FITS Committee for review. The proposal will be discussed during the European FITS Committee meeting in Munich (1992.5.15). Daniel Ponz -------------------------------- J.D.Ponz vilspa::jdp ESA/ECNOD European Space Agency Villafranca Satellite Tracking Station 34-1-8131183 P.O.Box 50727 28080 Madrid, SPAIN From dwells at fits.cx.nrao.edu Wed Feb 19 09:56:36 1992 Status: RO X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["14970" "Wed" "19" "February" "1992" "06:20:40" "GMT" "Don Wells" "dwells at fits.cx.nrao.edu" nil "270" "2nd CFV and VOTE ACK: sci.astro.fits" "^From:" nil nil "2" nil nil nil nil] nil) Newsgroups: news.announce.newgroups,news.groups,sci.astro,sci.astro.hubble,sci.space,alt.sci.astro.fits Followup-To: poster Nntp-Posting-Host: cs.rpi.edu Organization: National Radio Astronomy Observatory, Charlottesville, VA From: dwells at fits.cx.nrao.edu (Don Wells) Subject: 2nd CFV and VOTE ACK: sci.astro.fits Date: Wed, 19 Feb 1992 06:20:40 GMT This is the second Call For Votes on the creation of the unmoderated newsgroup sci.astro.fits. Name: sci.astro.fits Status: Unmoderated Charter: This newsgroup will provide a forum for the discussion of all topics concerning the FITS [Flexible Image Transport System] data format. The newsgroup will be interfaced to the Email exploder fitsbits at fits.cx.nrao.edu so that traffic originating on either the newsgroup on the exploder will be automatically transmitted to the other. This new newsgroup will replace existing newsgroup alt.sci.astro.fits. Reference Entry: sci.astro.fits Issues related to FITS [Flexible Image Transport System] How to Vote: Send Email to "dwells at fits.cx.nrao.edu" (or "dwells at nrao.edu") with the Subject line containing either "I vote YES on sci.astro.fits" or "I vote NO on sci.astro.fits". If you are unable to generate/edit a Subject line then insert the YES/NO statement into the body of your message. The votes must be an explicit YES or NO; conditional votes will not be accepted. Only votes mailed to the above addresses will count; votes posted to the net for any reason and proxy votes (such as mailing list maintainers claiming a vote for each member of the list) will not be counted. Each vote will be acknowledged by Email, and at least one more mass acknowledgement will be posted to various newsgroups. Period: This vote will end at 23:59 Eastern time on Monday 2 March 1992. =-=-=-=-= At 15:00 EST (20:00 GMT) Tuesday February 18, votes had been received >from 218 people, and acknowledgements sent, with the exception of one address which bounces due to its mailer being mis-configured. To all of you who have voted so far I say: "Thank You!". adelmans at citadel.bitnet anderson at atnf.csiro.au anw at anwsun.phya.utoledo.edu bob at ipac.caltech.edu bpirenne at eso.org bschlesinger at nssdca.gsfc.nasa.gov c1796 at slvaxa.umsl.edu cbiemes at noao.edu cguirao at eso.org colorado at stars.gsfc.nasa.gov dreher at bkyast.berkeley.edu ed at astro.umd.edu fmurtagh at eso.org gondwana at athena.mit.edu hmadorf at eso.org howard at ssl.msfc.nasa.gov jmcgaha at pimacc.pima.edu kemper at nssdca.gsfc.nasa.gov mary at jach.hawaii.edu neff at stars.gsfc.nasa.gov pdierckx at eso.org pgrosbol at eso.org pwb at isaac.phys.unsw.oz.au ralbrech at eso.org rick at ipac.caltech.edu sysevm%nsrvan.uucp%clark.uucp at clark.edu w3whw at scfmvs.bitnet weiland at aruba.gsfc.nasa.gov whb at hoh-2.att.com wls at astro.umd.edu Lenny Abbey labbey at gtri01.gatech.edu David Adler dadler at negra.aoc.nrao.edu Miguel Albrecht malbrech at eso.org Michael Albrow phys170 at csc.canterbury.ac.nz Bruce Balick balick at tahoma.phys.washington.edu Tom Bania bania at buast4.bu.edu Timothy Banks bankst at kauri.vuw.ac.nz Klaus Banse kbanse at eso.org Jeannette Barnes jbarnes at noao.edu Fritz Benedict fritz at dorrit.as.utexas.edu Jeff Bloch 103283 at sstdp1.lanl.gov Michael Eric Boschat andromed at atm.dal.ca P.J. Boulay pjb4288 at ultb.isc.rit.edu Jeffrey Oliver Breen job at cfa236.harvard.edu Daniel Briggs dbriggs at zia.aoc.nrao.edu Lawrence E. Brown elwin at gamma.phys.clemson.edu Liz Bryson bryson at cfht.hawaii.edu Markus Buchhorn markus at merlin.anu.edu.au Sinclair Budd cmaae50 at cc.ic.ac.uk Frank Bull bull%pyrrus.uucp at noao.edu Ann Burgess aburgess at atnf.csiro.au Bob Burns bburns at polaris.cv.nrao.edu Howard Bushouse bushouse at iuegtc.dnet.nasa.gov Mark Calabretta mcalabre at macabre.cv.nrao.edu Hulya CalIskan jk017 at triuvm11.bitnet Bill Carson brighton%phuket.uucp%pixar.uucp at next.com Carol Christian carolc at ssl.berkeley.edu Chris Clark chris at cfht.hawaii.edu Rick Coates rick at ateq.com Bruce C Cogan bcc900 at cscgpo.anu.edu.au Judith Cohen jlc at deimos.caltech.edu Mike Collins mcollins at phx.mcd.mot.com Mark E. Cornell cornell at puck.as.utexas.edu Paulo da Costa dacosta at prl.philips.nl Bill Cotton bcotton at gorilla.cv.nrao.edu Dennis Crabtree crabtree at dao.nrc.ca Malcolm J. Currie cur at starlink.rutherford.ac.uk Chris J. Davis chris at airdata.socal.com Mike Davis davis at naic.edu Carl A. Dobson cad at ssl.berkeley.edu Elwood C. Downey e_downey at hwking.cca.cr.rockwell.com Frank Drake drake at dragon.ulowell.edu Chris Dudley dudley at galileo.ifa.hawaii.edu Ron Ekers rekers at atnf.csiro.au Rick Ellis rick at ofa123.fidonet.org Martin Ewing ewing-martin at cs.yale.edu Allen Farris farris at stsci.edu Eric D. Feigelson edf at astro.psu.edu Tony Ferro tony at quasar.la.asu.edu david fisher fish at helios.ucsc.edu Chris Flatters cflatter at greystoke.cv.nrao.edu Murray Forbes forbesmc at matai.vuw.ac.nz Thierry Forveille forveill at gag.observ-gr.fr Priscilla Frisch frisch at galadriel.uchicago.edu Terry Gaetz gaetz at julian.uwo.ca Bob Garwood bgarwood at sngldsh.cv.nrao.edu FRANK GHIGO fghigo at lodestar.gb.nrao.edu John Glaspey glaspey at cfht.hawaii.edu Brian Glendenning bglenden at colobus.cv.nrao.edu Orhan GOKCOL ucgokcol at tritu.bitnet Daniel Golombek golombek at stsci.edu James P. Goltz frost at helix.nih.gov Steve Grandi grandi at noao.edu Andrew Gray agray at atnf.csiro.au Eric Greisen egreisen at polaris.cv.nrao.edu Gerry Grieve grieve at geop.ubc.ca Gaston Groisman gaston at cpsc.ucalgary.ca Edward J. Groth groth at pupgg.princeton.edu Bob Hanisch hanisch at stsci.edu Wendy Harrison harrison at cfht.hawaii.edu Booth Hartley booth at ipac.caltech.edu Helge Hauglin helgeha at ifi.uio.no Jeff Hayes hayes at stsci.edu Greg Hennessy gsh7w at fermi.clas.virginia.edu Tony Hewitt hewitt at aslpet.med.ge.com Mike Hicks hicksm at lpl.arizona.edu Phil Hodge hodge at stsci.edu John Horne horne at cfht.hawaii.edu Victor Hughes hughesv at qucdn.queensu.ca Gareth Hunt ghunt at nrao.edu Dr. Albert Hybl hybl at umbc4.umbc.edu Peter D. Jackson jackson at cobecl.dnet.nasa.gov Dave Jenner davej at phast.phys.washington.edu Diab Jerius dj at pelf.harvard.edu Justin Jonas phjj at ruchem.ru.ac.za Dean C Josephson dean at cfht.hawaii.edu Joel C. Justen joel%crpi.uucp at uunet.uu.net Markus G. Kempf kempf at rhrk.uni-kl.de John Kerr john at cfht.hawaii.edu james kiley jkiley at andy.bgsu.edu Edward King eking at herca.jpl.nasa.gov Quincey Koziol koziol at ncsa.uiuc.edu N PAUL KUIN kuin at nssdca.gsfc.nasa.gov Tom Kuiper kuiper at kuiper.jpl.nasa.gov Krishna Kunchithapadam krisna at cs.wisc.edu Glen Langston glangsto at saips.cv.nrao.edu MICHAEL CHRISTOPHER LAPAGLIA m953618 at mcdonald.nadn.navy.mil Charles Lawrence crl at eccles.caltech.edu D.A. Leahy leahy at iras.ucalgary.ca Zoltan Levay levay at stsci.edu Greg Lindahl gl8f at fermi.clas.virginia.edu Peter Linde peter at astro.lu.se Bob Link link at cfht.hawaii.edu Joseph St. Lucas stlucas at gdwest.gd.com Lars Lundahl lundahl at oso.chalmers.se Dyer Lytle lytle at noao.edu Barney Magrath magrath at cfht.hawaii.edu George Martin gmartin at zia.aoc.nrao.edu Rick McGonegal mcgonegr at noao.edu Ed McGuire emcguire at ccad.uiowa.edu David Mehringer dmehring at zia.aoc.nrao.edu Ken Mighell mighell at merlin.anu.edu.au Stefan Mochnacki stefan at vela.astro.utoronto.ca David Moffett dpm at cs.purdue.edu Christopher B. Moore cmoore at alioth.mit.edu J. R. Munoz_Peiro jmunoz at estsaa.dnet.nasa.gov KAYLENE MURDOCH phys166 at csc.canterbury.ac.nz Pat Murphy pmurphy at nrao.edu Steve Murray ssm at cfa244.harvard.edu Robert Mutel rlm at sunlight.physics.uiowa.edu Matthew J. Nelson nelson at larry.sal.wisc.edu Mike Newberry newberry at as.arizona.edu Patrick L. Nolan pln at egret1.stanford.edu Ray Norris rnorris at atnf.csiro.au Michael Olberg olberg at oso.chalmers.se Nancy Oliversen noliversen at iuegtc.dnet.nasa.gov Eric C. Olson ericco at ssl.berkeley.edu Bruce Oneel oneel at arupa.gsfc.nasa.gov Patricio Ortiz ortiz at vela.astro.utoronto.ca Paul Palmer palmerp at math.orst.edu Aliza R. Panitz buglady at silver.lcs.mit.edu Tim Pearson tjp at eccles.caltech.edu Jeffrey A. Pedelty pedelty at jansky.gsfc.nasa.gov George D. Phillies phillies at wpi.wpi.edu The Daft Pict mclean at shadow.stsci.edu Phil Plait pcp2g at karma.astro.virginia.edu Joe Plassmann joep at asgard.lpl.arizona.edu Jose Daniel Ponz jdp at vilspa.dnet.nasa.gov Tony Putman tonyp at ucthpx.uct.ac.za Ernst Raimond exr at nfra.nl Kavan Ratnatunga kavan at merlin.anu.edu.au Somak Raychaudhury somak at cfa203.harvard.edu Gail Reichert reichert at rosgip.gsfc.nasa.gov Brian Reynolds reynolds at fsg.com Greg N. Roberts roberts at orion.arc.nasa.gov Andreas Roemer andi at comet.gold.sub.org Chris Rogers crogers at drao.nrc.ca Steve Rooke rooke at noao.edu a. m. rushton rushton at stsci.edu Robert Rutledge rutledge at space.mit.edu Gustaf Rydbeck gustaf at oso.chalmers.se Paul J. Schinder schinder at leprss.gsfc.nasa.gov Rob Seaman seaman at noao.edu Nigel Sharp sharp at vela.tuc.noao.edu Steinn Sigurdsson steinly at topaz.ucsc.edu Michal Simon msimon at ccmail.sunysb.edu Jhs John Simonetti jhs at astro.phys.vt.edu Robert W. Spiker rws3n at astsun9.astro.virginia.edu Ralf Stephan hagbard at ark.abg.sub.org Carolyn Stern stern at jasra.harvard.edu Peter B. Stetson stetson at dao.nrc.ca Mark Stevens stevens at stsci.edu Thomas Stingl stingl at gate.fzi.de Jose Suarez suarez at as.arizona.edu Denis Sullivan sullivan at emf.vuw.ac.nz William Thompson thompson at serts.gsfc.nasa.gov Rich Thomson rthomson at dsd.es.com Michael H. Tipping greywolf at vesta.unm.edu Doug Tody tody at noao.edu Tasso Tzioumis atzioumi at atnf.csiro.au Frank Valdes valdes at noao.edu Dirk Valk dirk at spacsun.rice.edu Edward Vielmetti emv at msen.com Stephen Walton swalton at solaria.csun.edu George M. Weaver weaver at astro.psu.edu Don Wells dwells at fits.cx.nrao.edu Mark Wieringa mwiering at atnf.csiro.au Dan Wilcox wilcox at cfht.hawaii.edu Tony Willis twillis at drao.nrc.ca rob woiccak rewoicc at erenj.bitnet Donna Womble womble at cass05.dnet.nasa.gov Al Wootten awootten at polaris.cv.nrao.edu Jim Wright jwright at cfht.hawaii.edu Bill Wyatt wyatt at cfa214.harvard.edu Peter Yee yee at spectre.arc.nasa.gov A. Young ayoung at eso.org Nelson Zarate nelson at stsci.edu Yun Fei Zhang zhang at buast0.bu.edu -- Donald C. Wells Associate Scientist dwells at nrao.edu National Radio Astronomy Observatory +1-804-296-0277 520 Edgemont Road Fax= +1-804-296-0278 Charlottesville, Virginia 22903-2475 USA 78:31.1W, 38:02.2N