Predicts the outcome class and puts the predicted values into a SQL table
Argument and Default Value¶
Feature name for the SQL table.
Given a classification model (--load_model), this switch will predict the outcome class on the groups given in the outcome table and puts the values into a MySQL table. This is useful for a set of groups that you don't have the outcomes for, but you have a prediction model for it (here are the outcomes we can predict from language). The table created will look like: feat$p_modelType_ARGUMENT$message_table$group_id where modelType is the first 4 letter of the model name. If you used linear:doc:fwflag_svc for instance, it will look like feat$p_line_ARGUMENT$message_table$group_id.
Make sure the features are in the right order (i.e. the order they were put into when creating the model). A good place to check for that is the name of the pickle file (if you're using a pre:doc:fwflag_made picklefile, like those in here)
For now, you need to make an output table that contains non null values for the outcomes & groups that you want predictions for, cause it uses the --predict_classifiers code to run this, which is why it also outputs comparisons between the values in the outcome table and the predicted outcomes. This should be changed soon though, so stay tuned!
# Loads the classifier in deleteMeGender.pickle, and uses the features to predict the genders of the users in # masterstats_andy_r10k, and inserts those values into a table called feat$p_line_deleteMeGender$messages_en$user_id. # Note that it only predicts gender for those groups with non null gender values in masterstats_andy_r10k. ~/fwInterface.py -d fb20 -t messages_en -c user_id -f 'feat$1gram$messages_en$user_id$16to16$0_01' --outcome_table masterstats_andy_r10k --outcomes gender --load_model --picklefile deleteMeGender.pickle --predict_classifiers_to_feats deleteMeGender