ALO Release Notes
v3.0.2 (February 26, 2025)
Update
- UI Arguments (ui_args) Support
- Added support for ui_args that can be used for customizing the UI.
Supported version
- AI Conductor: v2.0.1
- Edge App: v3.2.0
v3.0.1 (February 19, 2025)
Features
- Added AloSolutionStreamError
- New error classes with codes ALO-SSA-015, ALO-SSA-016, and ALO-SSA-017 introduced.
- These errors handle cleanup issues during solution registration.
Bug Fixed
- Changed return type in the cleanup method to handle errors more effectively.
Supported version
- AI Conductor: v2.0.1
- Edge App: v3.2.0
v3.0.0 (February 12, 2025)
Features
- Installation via PyPI
- ALO can now be installed simply using pip install mellerikat-alo, making it more accessible and easier to manage.
- Introduction of ALO CLI
- New command-line interface (CLI) for ALO to enhance user interaction and simplify management tasks.
- Usage examples and documentation are available to guide users through the new interface.
- Expanded Operational Environment
- ALO now supports execution in any environment where Python is available.
- AI Solution registration through ALO is now possible in any environment capable of building Docker images.
- Removal of ALO API
- The internal ALO API has been removed to streamline the architecture and simplify maintenance.
- Improved YAML Structure
- Enhancements to the YAML configuration structure for better readability and manageability.
- The new structure is designed to be more intuitive and easier to use, reducing the potential for errors.
Supported version
- AI Conductor: v2.1.0
- Edge App: v3.2.0
v2.8.0 (February 12, 2025)
Updates
- support for operating with AI Conductor 2.1.0 on Sagemaker.
Supported version
- AI Conductor: v2.1.0
- Edge App: v3.4.1
v2.7.0 (December 11, 2024)
Features
- Train gpu docker is supported
- (usage) 'train_gpu': True in register-ai-solution.ipynb
- (version limitation) tensorflow >= v2.14.0, torch >= 2.0.1
- A function for data in/out with GCP's GCS has been added.
Supported version
- AI Conductor: v2.0.1
- Edge App: v3.2.0
v2.6.0 (September 30, 2024)
Features
- Add 'overview' and 'detail' fields to 'solution_info' entry in register-ai-solution.ipynb.
- Delete 'solution_type' (private, public) field from 'solution_info' entry in register-ai-solution.ipynb.
- Only 'private' is supported from AIC v2.0.0
Updates
- Update the backend to be compatible with AIC v2.0.0 REST API during the solution register process.
- Change format to solution metadata v1.2
Bug Fixed
- Fixed a bug where during the inference process, after success - fail, if success is achieved again during the next inference, the changed setting of UI args is initialized to the original solution.
- Fixed bug where redis publish message other than 'booting' occurred during ALO booting while interfacing with EdgeApp.
Supported version
- AI Conductor: v2.0.0
- Edge App: v3.2.0
v2.5.2 (July 16, 2024)
Updates
- For Edgeapp interface, when the status of Redis publish is in 'loop and boot' mode, it is fixed as 'booting'.
Bug Fixed
- Create a solution_meta.yaml under the ALO project home when registering solution.
- Fix the bug in S3 data download where the sub-directory structure was not maintained.
- Add defensive code to handle cases where the 'args' in experimental_plan.yaml are provided as an empty list.
Supported version
- AI Conductor: v1.7.0
- Edge App: v3.1.0
v2.5.1 (June 13, 2024)
Bug Fixed
- Skip when ui_args is written as null in experimental_plan.yaml
Supported version
- AI Conductor: v1.7.0
- Edge App: v3.1.0
v2.5.0 (June 06, 2024)
Features
- Starting with Edge App v3.1.0, it is only compatible with ALO v2.5.0 and later versions.
- Supports --index-url option for installing asset dependency packages.
Updates
- To optimize storage, backups of history and solutions registrations now exclude copying each asset's .git directory (except for .git for ALO)
- Spec-out functions below in solution register notebook.
- run train
- list solution & stream
Bug Fixed
-
Fixed an issue in operational loop mode, where the solution metadata would be overwritten with the default experimental_plan.yaml from ALO every time. Instead, it now correctly overwrites the experimental plan kept in memory
-
Fixed an issue in operational loop mode, where the sequence of Redis operations and the creation of inference artifact files would get entangled, leading to alo errors and subsequent improper functioning with the Edge App
- send fail redis after creating error artifact zip file
- skip error backup history
- save_artifacts() logic error fixed (for redis publish)
-
Resolved a bug related to the backup history size limit function
- Fixed an error caused by not creating the history/train directory when it's a single pipeline
- Made enhancements to reduce discrepancies when measuring directory size by now utilizing the linux du -sb command in python subprocess for better measuring accuracy
Supported version
- AI Conductor: v1.7.0
- Edge App: v3.1.0
v2.4.0 (May 16, 2024)
Features
- Support for inference pipeline operation when running in Sagemaker mode
- Use options together when executing main.py, such as --mode inference --computing sagemaker
- Two keys added to the control part of experimental_plan.yaml
- save_inference_format: external_path - determines the compression file format of inference artifacts to be stored in the external_path - save_inference_artifacts_path (supports tar.gz, zip)
- check_resource: Determines whether to display logs related to resource usage such as CPU, Memory, etc. for each Asset (supports True, False)
- Reflecting default values for experimental_plan.yaml - control
- If the user does not enter some key, value in the control part of experimental_plan.yaml, the default value is applied
- get_asset_source: once
- backup_artifacts: True
- backup_log: True
- backup_size: 1000
- interface_mode: memory
- save_inference_format: tar.gz
- check_resource: False - Addition of redis publish function
- Added function to publish ALO's status / fail message to redis (used when run with Edgeapp)
Updates
- Removal of REMOTE_BUILD key in setting/infra_config.yaml
- Replaced by writing codebuild in the value of BUILD_METHOD
- Expansion of the function of inference_only=True in solution_info of register-ai-solution.ipynb
- Support for Single pipeline: The method of determining whether it is a single pipeline or not is that train_pipeline must exist in both user_parameters and asset_source of experiemntal_plan.yaml to be False
Bug Fixed
- Bug fix for incorrect operation related to deleting data already existing in s3 when registering a solution
Supported version
- AI Conductor: v1.7.0