|
2 | 2 |
|
3 | 3 | See DataLab [roadmap page](https://datalab-platform.com/en/contributing/roadmap.html) for future and past milestones. |
4 | 4 |
|
| 5 | +## DataLab Version 0.18.0 ## |
| 6 | + |
| 7 | +ℹ️ General information: |
| 8 | + |
| 9 | +* PlotPy v2.7 is required for this release. |
| 10 | +* Dropped support for Python 3.8. |
| 11 | +* Python 3.13 is not supported yet, due to the fact that some dependencies are not compatible with this version. |
| 12 | + |
| 13 | +💥 New features and enhancements: |
| 14 | + |
| 15 | +* New operation mode feature: |
| 16 | + * Added "Operation mode" feature to the "Processing" tab in the "Settings" dialog box |
| 17 | + * This feature allows to choose between "single" and "pairwise" operation modes for all basic operations (addition, subtraction, multiplication, division, etc.): |
| 18 | + * "Single" mode: single operand mode (default mode: the operation is done on each object independently) |
| 19 | + * "Pairwise" mode: pairwise operand mode (the operation is done on each pair of objects) |
| 20 | + * This applies to both signals and images, and to computations taking *N* inputs |
| 21 | + * Computations taking *N* inputs are the ones where: |
| 22 | + * *N(>=2)* objects in give *N* objects out |
| 23 | + * *N(>=1)* object(s) + 1 object in give N objects out |
| 24 | + |
| 25 | +* New ROI (Region Of Interest) features: |
| 26 | + * New polygonal ROI feature |
| 27 | + * Complete redesign of the ROI editor user interfaces, improving ergonomics and consistency with the rest of the application |
| 28 | + * Major internal refactoring of the ROI system to make it more robust (more tests) and easier to maintain |
| 29 | + |
| 30 | +* Implemented [Issue #102](https://github.com/DataLab-Platform/DataLab/issues/102) - Launch DataLab using `datalab` instead of `cdl`. Note that the `cdl` command is still available for backward compatibility. |
| 31 | + |
| 32 | +* Implemented [Issue #101](https://github.com/DataLab-Platform/DataLab/issues/101) - Configuration: set default image interpolation to anti-aliasing (`5` instead of `0` for nearest). This change is motivated by the fact that a performance improvement was made in PlotPy v2.7 on Windows, which allows to use anti-aliasing interpolation by default without a significant performance impact. |
| 33 | + |
| 34 | +* Implemented [Issue #100](https://github.com/DataLab-Platform/DataLab/issues/100) - Use the same installer and executable on Windows 7 SP1, 8, 10, 11. Before this change, a specific installer was required for Windows 7 SP1, due to the fact that Python 3.9 and later versions are not supported on this platform. A workaround was implemented to make DataLab work on Windows 7 SP1 with Python 3.9. |
| 35 | + |
| 36 | +🛠️ Bug fixes: |
| 37 | + |
| 38 | +* Fixed [Issue #103](https://github.com/DataLab-Platform/DataLab/issues/103) - `proxy.add_annotations_from_items`: circle shape color seems to be ignored. |
| 39 | + |
5 | 40 | ## DataLab Version 0.17.1 ## |
6 | 41 |
|
7 | 42 | ℹ️ PlotPy v2.6.2 is required for this release. |
@@ -492,7 +527,7 @@ NumPy 2.0 support has been added with this release. |
492 | 527 | * Circle and ellipse results now also show area (A) |
493 | 528 | * Added "Plot results" entry in "Analysis" menu: |
494 | 529 | * This feature allows to plot analysis results (1D or 2D) |
495 | | - * It creates a new signal with X and Y axes corresponding to user-defined parameters (e.g. X = indexes and Y = radius for circle results) |
| 530 | + * It creates a new signal with X and Y axes corresponding to user-defined parameters (e.g. X = indices and Y = radius for circle results) |
496 | 531 | * Increased default width of the object selection dialog box: |
497 | 532 | * The object selection dialog box is now wider by default, so that the full signal/image/group titles may be more easily readable |
498 | 533 | * Delete metadata feature: |
@@ -544,9 +579,9 @@ NumPy 2.0 support has been added with this release. |
544 | 579 |
|
545 | 580 | * Fixed [Issue #29](https://github.com/DataLab-Platform/DataLab/issues/29) - Polynomial fit error: `QDialog [...] argument 1 has an unexpected type 'SignalProcessor'` |
546 | 581 | * Image ROI extraction feature: |
547 | | - * Before this release, when extracting a single circular ROI from an image with the "Extract all regions of interest into a single image object" option enabled, the result was a single image without the ROI mask (the ROI mask was only available when extracting ROI with the option disabled) |
| 582 | + * Before this release, when extracting a single circular ROI from an image with the "Extract all ROIs into a single image object" option enabled, the result was a single image without the ROI mask (the ROI mask was only available when extracting ROI with the option disabled) |
548 | 583 | * This was leading to an unexpected behavior, because one could interpret the result (a square image without the ROI mask) as the result of a single rectangular ROI |
549 | | - * Now, when extracting a single circular ROI from an image with the "Extract all regions of interest into a single image object" option enabled, the result is a single image with the ROI mask (as if the option was disabled) |
| 584 | + * Now, when extracting a single circular ROI from an image with the "Extract all ROIs into a single image object" option enabled, the result is a single image with the ROI mask (as if the option was disabled) |
550 | 585 | * This fixes [Issue #31](https://github.com/DataLab-Platform/DataLab/issues/31) - Single circular ROI extraction: automatically switch to `extract_single_roi` function |
551 | 586 | * Analysis on circular ROI: |
552 | 587 | * Before this release, when running computations on a circular ROI, the results were unexpected in terms of coordinates (results seemed to be computed in a region located above the actual ROI). |
@@ -640,7 +675,7 @@ NumPy 2.0 support has been added with this release. |
640 | 675 | 🛠️ Bug fixes: |
641 | 676 |
|
642 | 677 | * Region of interest (ROI) extraction feature for images: |
643 | | - * ROI extraction was not working properly when the "Extract all regions of interest into a single image object" option was enabled if there was only one defined ROI. The result was an image positioned at the origin (0, 0) instead of the expected position (x0, y0) and the ROI rectangle itself was not removed as expected. This is now fixed (see [Issue #6](https://github.com/DataLab-Platform/DataLab/issues/6) - 'Extract multiple ROI' feature: unexpected result for a single ROI) |
| 678 | + * ROI extraction was not working properly when the "Extract all ROIs into a single image object" option was enabled if there was only one defined ROI. The result was an image positioned at the origin (0, 0) instead of the expected position (x0, y0) and the ROI rectangle itself was not removed as expected. This is now fixed (see [Issue #6](https://github.com/DataLab-Platform/DataLab/issues/6) - 'Extract multiple ROI' feature: unexpected result for a single ROI) |
644 | 679 | * ROI rectangles with negative coordinates were not properly handled: ROI extraction was raising a `ValueError` exception, and the image mask was not displayed properly. This is now fixed (see [Issue #7](https://github.com/DataLab-Platform/DataLab/issues/7) - Image ROI extraction: `ValueError: zero-size array to reduction operation minimum which has no identity`) |
645 | 680 | * ROI extraction was not taking into account the pixel size (dx, dy) and the origin (x0, y0) of the image. This is now fixed (see [Issue #8](https://github.com/DataLab-Platform/DataLab/issues/8) - Image ROI extraction: take into account pixel size) |
646 | 681 | * Macro-command console is now read-only: |
|
0 commit comments