The Altair Community and the RapidMiner community is on read-only mode until further notice. Technical support via cases will continue to work as is. For any urgent requests from Students/Faculty members, please submit the form linked here.
Options
Same output format for W-M5P and W-REPTree
![nicugeorgian](https://us.v-cdn.net/6030995/uploads/defaultavatar/nCCNNSPK1YM69.jpg)
![](https://s3.amazonaws.com/rapidminer.community/vanilla-rank-images/maven-16x16.png )
For the next release:
it would be great if W-REPTree's generated regression trees had exactly the same layout/format as the ones produced by W-M5P. :-*
I have developed a small parser for the W-M5P's trees, which, unfortunately, does not work for W-REPTree's.
Thanks!
it would be great if W-REPTree's generated regression trees had exactly the same layout/format as the ones produced by W-M5P. :-*
I have developed a small parser for the W-M5P's trees, which, unfortunately, does not work for W-REPTree's.
Thanks!
![:) :)](https://community.rapidminer.com/resources/emoji/smile.png)
0
Answers
if this would be in our scope I would only be too glad to fulfill this requirement (since I do not like different formats myself too much
But unfortunately both methods, W-M5P and W-REPTree are taken from the Weka toolbox (as you tell from the starting "W-") and hence I can only deliver this request to the Weka developers and ask them and hopefully they will change this in the future.
Until then: the only option is to write another parser, sorry.
Cheers,
Ingo