[vsnet-alert 161] Re: on the format in which data are circulated by VSNET

[tkato@kusastro.kyoto-u.ac.jp]

Dear Dr. Munari and VSNET members,

    Since Nogami-san (the VSNET manager) will soon become absent in order to
attend a meeting (I am sending this from Mitaka NAOJ, Tokyo, though ...),
I would instead like to express our present situation on VSNET reporting
format of visual estimates. 

    We have once made a proposal on the reporting format just like what
Dr. Munari has mentioned.  However, we have not reached a good concensus
mainly because of two reasons.  One is that not all observers use computer
programs when preparing reports (and preparing a program for different
kinds of computers would be also a difficult task).  The other is that
some observers are already familiar with a specific program and already
storing their data in their formats.  In both cases, a strong and urgent
request about the data format in VSNET would require additional works
and time for the observers' side, which are especially difficult for
active observers working hours every night under the sky, or may cause
hesitation in posting their observations.

    Another reason is that VSNET does not belong to any pre-existing
variable star organizations.  So, the reports to VSNET should not be con-
sidered to be formal reports to the organizations like AAVSO, VSOLJ etc.,
but rather considered to be more alert-oriented (esp. this vsnet-alert).
From this reason, we have decided not to require observers to take
additional time in converting the data format, especially when the
converting procedure is not convenient for them.

    However, it would be helpful to show our "recommended" format for
those who start observing or reporting, or those who might prepare tools
or programs for the VSNET members (in this area, we may also work together;
for details please consult us using administrative mailing address:
vsnet-adm@kusastro.kyoto-u.ac.jp).

    Our recommended format was designed so that necessary data can be easily
extracted without serious programing.  The rule is just as ones which have
been used in observations issued by VSOLJ members.

  1) Each line has four fields separated by space characters.  The four
     fields represent the name of the object, the observed date in UT,
     the magnitude, and the observer's name or code.

  2) The name of the object should not be omitted, otherwise line-oriented
     tools like grep in UNIX would miss the observations.  The variable star
     name has the 3-letter constellation code in upper case letters, immedi-
     ately (without placing spaces) followed by its name in the constellation.
     The examples are:  DRAAG for AG Dra, CYGSS for SS Cyg, HERalpha for
     alpha Her, AQLnova1995 for Nova Aql 1995 etc.  Although the conventional
     names like AG Dra or Nova Aql 1995 are, of course, much more familiar
     to most observers, they have difficulties in that they have different
     number of space characters which have always posed a problem in auto-
     matic data selection.  From experiences in archiving the VSOLJ data,
     the name in the present rule has been found to work very well (placing
     the constellation at the beginning also enables simple sorting to get
     a order which are familiar to variable star observers; simple sorting
     of the data written in conventional names would result a notoriously
     unfamiliar order of objects).

  3) The observed time should be written in UT (UTC here).  This preference
     is because JD seems to be less familiar outside variable star specialist
     group, and because expression in UT would be more easily checked.
     We recommend observers to write the last two digits of the year, the
     month in two digits and the day and its fraction, like 950720.123
     which means 1995 July 20.123 UT.  Please write the year and month in
     each line of observations; otherwise they would become difficult to
     find in automatic selection.  Concerning the format of the year, we
     will reconsider if VSNET survives until 2000.

  4) The magnitudes and the observers' names or codes may not be as strict
     as the fields described above.

  The full lines would become like this:

CYGSS   990101.345  120  Xyz  /* not a real data */ 
CYGSS   990102.456  110  Xyz  /* write the name, yaer, month in every line */

     Please note that this rule would not be considered as requirements
but recommendation.  We would be grateful if any contributors are interested
in this scheme and may introduce this into their regular works.  And please
note that this format is for vsnet-obs for exchanging observations, and not
for usual text-based discussion.

     For less urgent data extraction, we have recently developed a system
of regular archiving the VSNET mails.  Anyone can access by anonymous ftp
(ftp.kusastro.kyoto-u.ac.jp, under /pub/vsnet/Mail).  This would reduce,
in some part, in extracting the necessary data.  The data reported in the
format above have been divided according to the star names and sorted in
the time sequence.  This has been done by a Perl script which has been
prepared by H. Baba, a member of the VSNET manager group.

     As a matter of fact, we have received a request from the CBAT of IAU
if the reporting format might be as in IAUCs.  We did not adopt this
because we thought this format would make future automatic extraction
more difficult.  If you find it necessary to direct your observations to
the CBAT, it would be advised to follow the CBAT's recommendation and
send the data directly to the CBAT.  When you send them as a carbon copy
of a mail to vsnet-obs, you may attach the data in the CBAT format to
the usual VSNET mails.

Regards,
Taichi Kato
(vsnet sub-manager)

PS. This "vsnet-alert" is not very suitable for discussing this sort of
    problem.  Please direct your opinions rather to vsnet-adm.  We will
    be able to make a small working group if necessary.

VSNET Home Page

Return to Daisaku Nogami

---

vsnet-adm@kusastro.kyoto-u.ac.jp