c:\temp\temp\convdoc.txt INSTRUCTIONS FOR CONVERTING VSNET FORMAT TO AAVSO FORMAT USING CONVERTV (2/2001) You only need to run one program, CONVERTV, to format your VSNET files to AAVSO format. Download CONVERTV from the AAVSO website or contact AAVSO Headquarters. Notes: a) You will need the AAVSO starname/designation list VALID.AAV to run this program. Download VALID.AAV from the AAVSO website, or contact AAVSO Headquarters. b) You also need to know your AAVSO Observer Initials. If you do not know them, please contact AAVSO Headquarters. 1. Put the AAVSO program CONVERTV.EXE in the same directory (folder) as your other AAVSO programs. Make sure the file VALID.AAV is there, too. 2. Have your data in VSNET format in one or more ASCII (plain text) files. The files may have any name, but should be in the format "filename.xxx" and "filename" must not be more than 8 characters in length. Example: DATA1.DAT Note on VSNET input format: a) VSNET format allows any number of blank spaces between the various data columns, but it does NOT allow embedded blanks in the star name, nor does it allow a decimal point in the magnitude. b) VSNET format fields are: starname utdecimal mag obs comments (including compstars/charts used) for example: CYGSS 990821.1834 <140 WEO OUTBURST HAZE 97,101 SCO796 NOTE: IT IS IMPORTANT THAT THE STARNAME, UT, MAGNITUDE, AND OBSERVER I.D. FIELDS CONTAIN NO BLANK CHARACTERS. Starnames such as "NSV 3456" should be entered as "NSV3456". Use of blank characters within these fields will result in data that will not convert. The Comments field (after the observer i.d.) is a free-form area, with no format restrictions. 3. Run CONVERTV (type "convertv") on each file, answering the prompts for your AAVSO Observer Initials and input and output file names. The output file must also be in the format "filename.xxx". Example: DATA1.OUT If the output file already exists, you may either append the converted data to the end of the existing output file or abort the program. 4. As CONVERTV runs, it displays all records found to be NOT in VSNET format. At the end of the run, the total number of legitimate VSNET format records found and written to the output file is displayed. 5. Because the VSNET Comments field is free-form, it may be impossible for CONVERTV to convert everything in this field to the corresponding AAVSO fields. You may need to edit DATA1.OUT to add or move comment codes, chart/compstar information, etc. CONVERTV automatically does the following: - looks for comment phrases (active, outburst, moon, clouds, fatigue, etc.) and inserts the corresponding AAVSO one-letter comment code after the magnitude. A complete list of AAVSO one-letter comment codes is given at the end of this file. - looks for instrumentation comment (PEP, PTG, PV, CCD, CCDV, CCDB, CCDR, CCDI) and inserts this comment after the magnitude. - looks for chart source phrases (such as BAA, GSC, Guide, Henden, Hipparcos, RASNZ, TA, Tycho, USNO, VSNET), inserts the the corresponding AAVSO one-letter chart code after the magnitude, and puts the chart source phrase in the correct place. It will not put anything if the chart is from AAVSO. If it doesn't recognize your chart source it will not add a chart code or keep the chart source. (Please add a "K" comment and move the chart source into the correct place - this information is extremely important!) Comment codes go in columns 37-43. Comparison star magnitudes go in columns 44-54. Chart information goes in columns 55-61. ============================================================================== Example of AAVSO format Column # 00000000011111111112222222222333333333344444444445555555555666666666677777777778 12345678901234567890123456789012345678901234567890123456789012345678901234567890 Design. Name Julian Date Magn. CommentStep Mag Charts Init.Remarks Codes or Comp Stars xxxx+xxxnnnnnnnnnnxxxxxxx.xxxx