This content has been marked as final. Show 5 replies
The Column Filter implementation does not actually create a AI Model to generate the ranking.
So there is basically a different implementation being used.
We are working on a ODMr enhancement that will generate a sqlplus script that will expose all the pl/sql used during the model building process.
At that point, it should be much easier to analyze the details.
They both use the same implementation.
ODMr does not need to create a model, so instead, a function is used that returns a result set.
Either approach will produce the same result, as long as you build the model properly.
See script below, that produces an AI model using he same data you noted.
You need to create a settings table and turn ADP on.
set serveroutput on
DROP TABLE ai_mk_model_settings;
-- Create the settings table
CREATE TABLE ai_mk_model_settings (
INSERT INTO ai_mk_model_settings (setting_name, setting_value) VALUES
-- Create the model using the specified settings
model_name => 'AI_SH_SAMPLE_3',
mining_function => DBMS_DATA_MINING.ATTRIBUTE_IMPORTANCE,
data_table_name => 'mining_data_build_v',
case_id_column_name => 'cust_id',
target_column_name => 'affinity_card',
settings_table_name => 'ai_mk_model_settings');
ORDER BY RANK;
ADP is off by default in ODM proper.
ODMr uses ADP extensively. Users can turn it off per column via the build node settings if they wish.
Viewing ADP Transformations:
ODMr will display these in model viewer Settings tab under the sub tab Inputs.
THe Inputs panel is a split panel viewer so you sometimes need to grab the splitter to move it up, to make the transformations more visible.
From the API you can use the following to query the transformations:
select * from
TABLE(DBMS_DATA_MINING.GET_MODEL_TRANSFORMATIONS ('CLAS_GLM_1_1')) T
The ODM Doc provides details on how to use ADP and specify your own embedded transformations.