LIST OF KNOWN ISSUES

Missing functionalities

For the current limitations of overlap analysis calculations see Introduction to overlap analysis
Tversky comparison metric is not supported by float vector descriptors.
Support of custom scaled float vector descriptors is not complete. Compressing sparse custom float vector descriptors is not supported.
Options -skip and -count fail in tool importStorage.
Command line scripts including self contained examples might fail currently when they are accessed through links.
Handling of missing additional data points (because of missing SDF property, failed Chemical Terms evaluation) and the handling of variable neighbor counts (resulting from a set dissimilarity threshold) in similarity based overlap analysis calculation and visualization is not implemented.

examples/benchmark.sh is improved in 0.1.4 but still under construction.
The following examples were present in previous releases, they are removed temporarily
- examples/realtime-example.sh
- examples/screen3d-workflow.sh
- examples/self-overlap-example.sh

Screenshots are not updated in the documentation.
Details on the visualization of profiling and execution statistics are not documented.
Java API documentation includes currently non functional, incomplete classes and also ones to be removed/refactored soon.
Rest API documentation includes currently non functional api endpoints.
Some of the public datasets introduced in the Prepare molecules documentation are not used in the examples.
Documentation compiled from Markdown sources are post processed on client side (TOC generation, syntax highlighting, some workarounds for styling).
Documentation of the API endpoint for showing available resources on the index page is missing.
Large images in the documentation are downscaled. A zoomed version is displayed on click, however it still is fitted to the screen. If the image is larger than the available screen currently they cannot be further zoomed in.
Documentation links non documentation files (scripts, data files, directories of distribution) which are not present on the product site.

Touch support of the WebUI provided by Jqurey UI touch punch is experimental and limited. (See https://github.com/furf/jquery-ui-touch-punch/issues/61.)
Web UI sources are now packaged and minified by webpack + babel. It is no longer recommended to modify the individual javascript files in the distribution. An experimental extension point is introduced in version 0.3.4, for details see Using MadFast Web UI JS library. Parts of the web ui frontend sources are expected to be available for modification in the future.
The current product icon of the MadFast tools (appearing in the documentation and in the Web UI) is expected to be reworked/changed in a subsequent release.
Issues of real time similarity search web UI
- Tooltip displayed for the disimilarity distribution zebra chart on molecule pick list component changed: descriptor reference is shown instead of proper descriptor name.
- No request prioritization/cancellation is implemented: when a long running (few secs) request (like dissimilarity distribution calculation on very large sets) is fired multiple times (for example during drawing) the previous requests are not cancelled. Also such requests are served concurrently.
- Dissimilarity distribution charts are showing dissimilarity range 0.0 - 1.0.
- Molecule pick list component is not responding to window/container resize events.
Issues of statistics visualization:
- Missing values of numeric dimensions are not handled on scatter plots.

Embedded server gui.sh prints WARNING level log messages (WARNING: Ignoring unknown format: png) when a molecule image conversion is requested.
A possible race condition in file IO might result in an Exception (Exception in thread "main" java.lang.IllegalArgumentException: java.lang.IllegalArgumentException: Empty stream cannot be read.) when reading files/standard input. This affects self contained examples.
In case of a malformed JSON POST request sent to the REST server occassionally a text/plain response (with HTTP status 400 - Bad request) is received. The expected behavior in such situation would be an application/json response with a proper error descriptor.
Request body encoding of the POST API endpoints are mixed; some of them accept only application/x-www-form-urlencoded bodies, some of them only application/json, some both. Consult REST API documentation.
When displaying command line help for tool searchStorage (by using option -h) a brief pause during printout happens.
On Windows + Cygwin passing a single * character as a command line argument might undergo wildcard expansion (globbing). This can be problematic when using tool gui.sh with -allowedOrigins "*" parameter specified. As a workaround use -allowedOrigins "*,*".