Changes between Initial Version and Version 1 of Ticket #2613
- Timestamp:
- 02/02/18 07:34:56 (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #2613
- Property Owner changed from gkronber to mkommend
- Property Status changed from new to assigned
- Property Milestone changed from HeuristicLab 3.3.x Backlog to HeuristicLab 3.3.16
-
Ticket #2613 – Description
initial v1 1 1 Currently, GBT does not consider missing values (or NaNs in our case) specifically. The training phase uses only comparisons therefore NaN values are implicitly treated as very small (or very large) values (1). When calculating estimated values the output of the right subtree is always used for NaN values. 2 2 3 3 4 I think it would be better to do the following