The Altair Community is migrating to a new platform to provide a better experience for you. In preparation for the migration, the Altair Community is on read-only mode from October 28 - November 6, 2024. Technical support via cases will continue to work as is. For any urgent requests from Students/Faculty members, please submit the form linked here
How to resolve the join operator problem?
Best Answer
-
emilie Member Posts: 4 Learner IHello Roland You're genius. This is my first time seeking help online, I am impressive with your timeliness of your response and your unbelievable professional skill. Thank you so much!0
Answers
Could you possibly post screenshots of what you're seeing, and if possible share the datasets? Otherwise, I'd suggest at looking at the Join operator tutorials to understand where the possible issues are coming from.
Best,
Roland
Thank you for your reply. Here are my screenshots. The first one is left port input data, the second one is the right port input data, then the process and the output data. The output data only shows the id attribute from right port without other attributes, that's my problem as I'd like to compare the LOF_outlier from left port and the Distance_outlier from the right port. I already installed extensions. I didn't get any inspiration from the tutorial. Can you identify the reason for me? Thanks!
Emilie
Do the variables of interest in the two tables have the same name? RapidMiner doesn't allow columns with the same name and I can see on the Join operator you have the option ticked on to remove double attributes, rather than rename.
Best,
Roland
I have discovered the cause by building a small sample. Because the columns of interest are classed as metadata (shown in yellow), only the metadata columns from the left table are carried forward. You can get round this by manually setting the columns to be regular or labels with a Set Role operator before you use the Join. I've attached my example underneath - let me know if this doesn't make sense.
Best,
Roland