Release 0.15

New features - Core BaseModel Repository:

• Entity-based splits
  Users will now be able to separate training, validation and testing sets based on time range or entity ID (e.g. create user hold-out rather than temporal one).

• New method for selecting entity IDs
  Users now have more flexible control over which entity IDs are included in training and testing:

  • A new entity_ids parameter can be added to the YAML configuration to act as a global filter during foundation model training, prior to training and validation splits.
  • The sameentity_ids parameter is now available in TrainingParams and TestingParams to control entity selection during specific scenario training or testing runs.
  • [BREAKING CHANGE]: the previously used entities_ids_subquery parameter has been removed.

• Refactoring of feature loading pipeline

  • Improvements to ensure stability, clarity of error messages and to prevent accidental misconfiguration when training scenario models or two-stage pretraining.

  • [BREAKING CHANGE]: The parameters use_recency_sketches and use_last_basket_sketches are no longer read from data_params block in YAML configuration file and must be passed directly to the pretrain() or train_foundation_model functions.

  • [BREAKING CHANGE]: the features_path can no longer be modified at scenario training stage, to eliminate the risk of misconfiguration. The path is now always derived from the checkpoint path so that features are in predictable location in the checkpoint.

  • [BREAKING CHANGE]: the data_loading_params block has been removed from the configuration file.
    The following parameters must now be defined as follows:

    • limit_entity_num_events → limit_entity_num_eventsunder the data_params block
    • cache_dir → cache_pathunder the data_params block.

  • Serialization is now enabled for all modalities.

• Enhanced BiqQuery connector (minimum viable feature)
  Users can now specify a different project as computation engine and a different one as data location.

• Standardised Dependency Error Messages
  All optional dependency checks generate standardized error messages with clear instruction to install missing packages.

New features - GUI Application (Snowflake Native):

• Minor UI fixes only.

Fixes:

• Fixed an error when validation set starting date could be picked in a way that resulted with empty history.
• Fixed an error when the starting date of testing set could be treated as history.
• Fixed an error when a column with less than two values overridden to the categorical type was causing preprocessing stage to fail.
• Fixed an error when interpretability returned duplicated modality names.
• Fixed an error where classification tasks required thresholds even when the user did not expect predicted labels and output type was set to SEMANTIC.
• Updated packages to improve performance, improve security and for compatibility with the latest features.