Skip to content

Version 1.2.0

Compare
Choose a tag to compare
@mhucka mhucka released this 13 May 18:22
· 88 commits to master since this release

There are three important changes in release 1.2.0 of MOCCASIN. The first is a massive improvement to the speed of parsing MATLAB files compared to recent performance. The second is the elimination of the separate moccasin_CLI and moccasin_GUI entry points in favor of a single program, moccasin, that can be used either to start the GUI or perform actions via the command line. The third is corrections of errors in the installation scripts so that setup.py now correctly installs dependencies, thus making installation much easier than before for most users.

Enhancements:

  • New command-line driver interface called, simply, moccasin. It features a revised set of command-line options, snazzy colors, spinners and more!

  • A past enhancement to setup.py caused it to stop being able to install dependencies normally, with the consequence that users had to install dependent Python packages by hand. This was problematic in many cases because the packages were not always easily installed. The errors in setup.py have been corrected.

  • The installation instructions have been updated and improved.

  • The GUI interface has been enhanced. In addition, the GUI interface now provides (hopefully) more helpful dialogs in error situations.

  • Huge performance improvements.

Bug fixes:

  • #49 Fixed extreme slowness of MATLAB parser.

  • #46 Fix for moccasin GUI not launching.

  • #51 Fixed bugs in checking whether MATLAB input is translatable, and add support for use of element-wise operators such as .* when they are not actually being used on matrices.

  • #52 Fixed bug in writing out very large numbers. Thanks to user @willigott for reporting the issue.

  • #53 Biocham currently seems to mistranslate unary negation, at least in some situations. MOCCASIN now has a workaround that replaces expressions of the form -x with -1 * x, which works better when passed to Biocham. This is hopefully temporary, until Biocham has a chance to address whatever the underlying issue is. Many thanks to user @willigott for reporting the issue and suggesting the workaround.