Browse Categories

(10.4.1.9)
Changes to Batch Reference File Generator in PhotoRed that fixed issues with selecting catalogs other than MPOSC and added UCAC3 (NOT UCAC2).

(10.4.1.8)

Modified the Batch Import form in LAE to allow importing data for other than asteroids, e.g., variable stars.

If not working with asteroids, do not load a set of elements but do enter something in the "Name" field.

N.B.The RA/Dec fields for each session will be set to the defaults.
One you have created the export files and imported them into Canopus, you must edit each of the sessions so that the RA/Dev values are correct. Otherwise, the HJD (assuming you're doing variable star work) will be incorrect when doing period analysis.

(10.4.1.7)
Bug fixes for ALCDEF import into an empty export set

(10.4.1.6)
More fixes with indexing error with PhotoRed help where the wrong help was displayed for routines Second Order and beyond. The Reduce button was not being enabled when selecting "AAVSO Batch".

N.B.
The beta includes three FF2 files that reflect a change in the structure for importing ALCDEF files. These files MUST be copied to \MPO\COMMON, overwriting the existing files (make backups anyway).

(10.4.1.5)
Fixes indexing error with PhotoRed help where the wrong help was displayed for routines Second Order and beyond.

(10.4.1.3)
More changes to Batch Reference File Generator download of AAVSO star data. I can only hope that they limit "special" characters to space, plus, and minus.

October 8 bug fix: The x-axis label in the period spectrum when the period search was in days still had "hours".

(10.4.1.2)
AAVSO star names keep getting longer. Shoe size to be included next! The maximum size in the DB files and elsewhere has been expanded to 40 characters. This will be the last fix in this regard. If the names go longer, someone needs to talk some sense into the name-givers.

On first startup, the program will automatically restructure the AAVSO/AAVSO2 tables. You'll see a brief restructuring message (if the files are large enough for the message to appear and stay up).

(10.4.1.1)
When working with SBIG or FITS images that do not have header information that Canopus can read to know which asteroid was being worked, an error could appear during AutoMatch/AutoMeasure indicating that the asteroid could not be found in the asteroid database even though the number/name had been entered to generate the chart for the matching process.

(10.4.1.0)
At my request, the AAVSO made changes to the Get API for downloading data from the Variable Star Plotter. It now allows getting a delimited text file with the data and not having to go through the (many) machinations of parsing the HTML page that used to be downloaded.

The new process in Canopus also allows getting a chart in addition to the data text file and defining the chart orientation, e.g,. North Down.

The bug reported to the AAVSO regarding the "flip" keyword has been fixed and their documenation updated. The charts generated by this latest version now have the orientation per the settings on the new download form. The tutorial has been updated to reflect changes in the captions for two buttons on the Batch Reference File Generator form. The PDFs in the ZIP and Users Guide have been updated.

The bug regarding the Batch Definition form truncating the target and comp star names has been fixed. Old BFD files can still be loaded. They should be immediately saved so that they are written out to the new format, probably with a new name so that the old file is still around should there still be a problem.

(10.4.0.26)
When doing batch processing, the errors list was cleared at the start of processing each item in the list. This meant that the messages would appear only if there was an error processing the last item in the batch process list (Targets list).

(10.4.0.24)
When using the CompStarSelector, the first line of the memo field with the comp star data, which is used to transfer to the NOTES field or to an external text file, indicates the catalog from which the magnitudes were taken, e.g.

   Magnitudes from APASS

(10.4.0.21/10.4.0.22)
Address problem in Comp Star Selector that generates a "Unequal or bad counts of array elements" error. This is caused (usually) when filtering for solar color stars and there are less than 2 such stars available. The program presents a more friendly error message and recovery from the error but there is no cure if the image is dominated by non-solar color stars.

(10.4.0.20)
Fixes problem when generating an MPC astrometry report when the asteorid number > 100,000.

(10.4.0.19)
Fixes to ALCDEF reporting so that if multiple observers are in the Observers memo field on the custom output form, all observers are in the OBSERVERS= line of the ALCDEF report.

A "Use Observers" checkbox on that form, under the Observers memo field, forces this list to be used in lieu of the MPCINFO listing in the NOTES field of each session. With recent versions, when a session is created, the NOTES field includes information from the MPC tab in the configuration. This information is read when generating an ALCDEF report such that, for each session (lightcurve block), OBSERVERLONG/LAT and OBSERVERS line contains the data in the MPCINFO block in the NOTES field. By checking this box, you tell the program to force the OBSERVERS line in the ALCDEF report to the entry in the memo field on the custom output form. Note that the LONG/LAT are STILL taken from the MPCINFO block, if present.

The best way to understand the multiple interactions is to try various combinations of settings/options and see what is generated in the ALCDEF report.

The most direct, though not necessarily easiest, solution remains to generate a separate ALCDEF file for each observer and make sure that the settings are correct for that observer.

(10.4.0.18)
A new "Sessions Report" option is available under the "To File" button on the Sessions form. This creates a tab-delimited text file that can be sorted by session number, object name, or date. The output fields are limited to: session number, object name, mid-date time, filter, mag band, and date/time of first/last observation in the session. The file has a default name of MPO\UDATA\SessionsReport_[yyyymmmdd].txt but can be saved elsewhere under a different name.

N.B. The sessions form and some of its buttons are not disabled while the report is being generated. Do not click any buttons or close the form while the screen wait cursor is being displayed.

(10.4.0.17)
When filtering sessions (Ctrl+Shift+F on the Sessions form), the session that was selected before applying the filter is made the default. Before, the first session within the filtered set was the default.

(10.4.0.16)
Changed output of ALCDEF report so that, if available, the MPCINFO.Contact (name only) in the Sessions.NOTES field is entered for the OBSERVERS keyword and the COMMENT about the actual observer has been dropped.

(10.4.0.15)
Removed MagAdjust keyword output in ALCDEF files. The MPC rejects submissions using this proposed, but not yet adopted, keyword.

(10.4.0.13)
Fixes to H-G error calculations (envelope and header values) as implemented by Alan Harris.

(10.4.0.12)
Fixes to bugs part of 10.4.0.11 AAVSO changes

(10.4.0.11)
Changes to AAVSO Batch Processing. 1) Changed Batch Reference File Generator Import procedure to account for new format of data from AAVSO. 2) Import now saves chart (sequence) ID from AAVSO file. 3) In Batch Definition form, when specifying the Batch Reference file created with this version, the target name and chart ID are automatically entered into the appropriate fields.

Important! When generating the HTML file from the variable star plotter on the AAVSO web site, you must select the printable output option (bottom of the form) and then save the file as "Web page, HTML only, not as "Web page, complete" or "Web archive (single file)" with mht extension. These are the IE options; Firefox and other browsers may have differently-named options but the point is that the file must be simple, minimum HTML code.

(10.4.0.10)
Changed error bar widths to 1 pixel instead of 2 to make them less obtrusive. Also put cross-bar end caps on the error lines.

(10.4.0.7)
Fixed bug in ALCDEF output that would create a data line with 0.000 for a magnitude when all the comp mags were 99.99 (no entry). Not quite sure how this happens; it does so during image measuring.