Free cookie consent management tool by TermsFeed Policy Generator

Changes between Version 1 and Version 3 of Ticket #2882


Ignore:
Timestamp:
01/22/18 14:24:48 (7 years ago)
Author:
mkommend
Comment:

After further investigations on this issue the following conclusions can be drawn:

  • Philipp is right
  • Only GBT models are affected, because cloning of a GBT surrogate model trigges a recalculation of the model. The fix to check whether a value is created solves this issue, but has the described disadvantage of freezing the GUI.
  • CreateEnsembleMenuItem triggers cloning of solutions whenever a view is changed to check if it should be enabled. There must be a better way with less overhead to enable /disable the menu item.
  • For models that are not stored completely a special solution view should be created that allows explicitly to trigger the model recalculation and blocks access to the solution evaluation view until the recalculation is finished.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #2882 – Description

    v1 v3  
    1 On deserializing a gradient boosted tree solution, the GBTSurrogateModel recaltulates the actual GBTModel even if the model is not yet used - which can be quite runtime expensive. The same issue applies to all regression models.
     1On deserializing a gradient boosted tree solution, the GBTSurrogateModel recaltulates the actual GBTModel even if the model is not yet used - which can be quite runtime expensive.
    22
    33Instead, the model should only be created when the model is actually needed to estimate values.