What's new in MuniWin 2.1.32
Dec 12, 2021
- This release brings support for CR3 files.
New in MuniWin 2.1.31 (Feb 27, 2021)
- The new version 2.1.31 of the C-Munipack software is available for download. This release fixes a bug in the function that reads date & time from the FITS file
New in MuniWin 2.1.30 (Feb 1, 2021)
- This release add two new DSLR formats (Minolta DiMAGE A1 and Sony ILCE-7M2)
New in MuniWin 2.1.29 (May 31, 2020)
- This release fixes application crashes on Linux and other platforms that compile the software from the source code.
New in MuniWin 2.1.28 (May 22, 2020)
- This release adds two new date&time formats. There are also minor UI improvements.
New in MuniWin 2.1.26 (Apr 28, 2019)
- Bug fixes:
- This release contains minor fix in decoding declination in decimal format
- New features:
- Added an option to show variables from variable star catalogs (GCVS, VSX) as an overlay on fields (source files must contain WCS coordinates)
- New photometry method with manual object selection (detection) , the source frames must have been already aligned (e.g. me
New in MuniWin 2.1.25 (Oct 4, 2018)
- This release contains minor fix in the aperture photometry in large apertures.
New in MuniWin 2.1.23 (Dec 19, 2017)
- This release contains minor fixes in the user's manual, added new file format - Nikon D5500.
New in MuniWin 2.1.22 (Dec 8, 2017)
- This release contains minor fixes and improvements.
New in MuniWin 2.1.21 (Aug 11, 2017)
- This release fixes some minor issues in the Find variables tool and in processing DSLR frames with very short exposure time.
New in MuniWin 2.1.20 (Aug 11, 2017)
- There are only minor improvements in the Find variables tool and the Light curve tool.
New in MuniWin 2.1.17 (Aug 11, 2017)
- There are minor fixes + new date & time format.
New in MuniWin 2.1.16 (Aug 11, 2017)
- There is only one minor bug fix + new date & time format.
New in MuniWin 2.1.15 (Aug 11, 2017)
- The only change is a bugfix in BAA VSS export format.
New in MuniWin 2.1.14 (Aug 11, 2017)
- The only change is support for a new data & time format.
New in MuniWin 2.1.13 (Sep 19, 2016)
- The only change issupport for multiple comparison stars in the Find variables tool.
New in MuniWin 2.1.12 (Sep 19, 2016)
- The only change is a new date & time format - 'UTC' field.
New in MuniWin 2.1.11 (Sep 19, 2016)
- I have fixed a random crash in Find variables tool and there is also a new experimental matching algorithm which works much better for very dense fields then the standard matching algorithm.
New in MuniWin 2.1.10 (Sep 19, 2016)
- The only change is a new parameter in the 'munilist' command line tool that makes a table of objects out of a photometry file or a catalog file. If you just use Muniwin, you don't need to update.
New in MuniWin 2.1.9 (Sep 19, 2016)
- It fixed proram crashes made to the previous release. I apologize for inconvenience.
New in MuniWin 2.1.7 (Sep 19, 2016)
- There are two major improvements in branch 2.1 in comparison 2.0: the installer comes with 64-bit executables for Windows users and the software can be used for photometry of minor Solar System bodies.
New in MuniWin 2.1.4 (Jan 28, 2016)
- Bug Fix:
- Program crash in the photometry.
New in MuniWin 2.1.3 (Jan 28, 2016)
- Both 32-bit and 64-bit executables for MS Windows are provided in the installation package.
- Plot CCD temperature.
- Plot FWHM and other object properties.
New in MuniWin 2.0.21 (Jan 28, 2016)
- Fixed bug in creating a light curve with heliocentric correction
- Fixed bug in AAVSO export for the ensemble photometry.
- Added manual topic about creating an AAVSO report.
New in MuniWin 2.0.20 (Jan 28, 2016)
- Export a light curve in the AAVSO Extended format
- Fixed program crash in the Find variables tool.
New in MuniWin 2.0.19 (Jan 28, 2016)
- Added option in making a light curve - show all objects on the reference frame
- Maximizing the main window on startup is default, but it can be turned off in the Environment settings.
New in MuniWin 2.0.17 (Mar 24, 2015)
- There are no changes in this release, just a fix in saving CCD images.
New in MuniWin 2.0.14 (Jul 21, 2014)
- There are no major change in this release, just couple of fixes and one minor improvement in the Find variables tool.
New in MuniWin 2.0.13 (Jul 14, 2014)
- There are no major change in this release, just fix of program crash in the matching algorithm and selection of adaptive/fixed magnitude scale in the Find variables tool.
New in MuniWin 2.0.12 (Jul 7, 2014)
- There are no major change in this release, just fix of non-functional saving of a light curve to a file.
New in MuniWin 2.0.11 (Jun 20, 2014)
- Changed dialog for creating new project, loading and saving profiles.
- It is possible to save multiple selections of objects (multiple variable stars on one view field)
- Option if the first line in the FITS file is displayed at the top or the bottom of the window
New in MuniWin 2.0.10 (Jul 8, 2013)
- There are no major change in this release just couple of minor bug fixes and improvements.
New in MuniWin 2.0.9 (May 24, 2013)
- The major change in this release is that the graphs (light curve, for example) can alternatively show date and time and Julian date. There are also couple of minor fixes as well.
New in MuniWin 2.0.8 (May 24, 2013)
- This release fixes a critical bug - program crash in the dark correction procedure.
New in MuniWin 2.0.7 (May 24, 2013)
- This release fixes the following issues:
- When multiple bias/dark/flat correction frames was applied inside a single set of source frame, the corrections were not applied correctly. The first correction frame was applied always.
- Merge frames - correct handling of a case where the merged frames are rotated.
- Choose stars dialog - variable star was sometimes not displayed.
- Fixed master flat tool - failed in case where source frames were stored in signed 16-bit format.
- Other changes:
- Updated document `Theory of operation` - added detailed description of the matching algorithm.
- All dialog controls have tooltip texts.
New in MuniWin 1.2.32 (May 24, 2013)
- This release fixes a bug - when multiple bias/dark/flat correction frames was applied inside a single set of source frame, the corrections were not applied correctly. The first correction frame was applied always.