"'Weights Table' to AttributeWeights"
Hi,
Can I convert the "Weights Table" output of an SVM model into an object of type "AttribteWeights" or even an "ExampleSet", so that later I can apply these weights on my data?
My second question is: Can i somehow store the Bias (Offset) in a macro variable (or an examplset), so that it can be used in further calculations?
Below I produce an example:
<参数键= " number_of_attributes" value="6"/>
I hope the above questions are fine and sensible... Tried hard to solve this, but at last ended up as a question in the Forum. Thanks for your help...
Can I convert the "Weights Table" output of an SVM model into an object of type "AttribteWeights" or even an "ExampleSet", so that later I can apply these weights on my data?
My second question is: Can i somehow store the Bias (Offset) in a macro variable (or an examplset), so that it can be used in further calculations?
Below I produce an example:
<参数键= " number_of_attributes" value="6"/>
I hope the above questions are fine and sensible... Tried hard to solve this, but at last ended up as a question in the Forum. Thanks for your help...
Tagged:
0
Answers
Had tried with SVM Weightings... but it gives the weights rather than any model. I basically wanted to extract the weights generated from a model. And ofcourse, the weights are different from the applied models and the SVM weightings. Is there a method to extract these weigts even in text-view? Does 'ParameterSet' or 'ProcessLog' operator be useful in this regard?
Does Rewriting the HyperHyper mean, whether the options in the operator need to be changed or the built-in code could be modified to our requirements by writing the extension plugins?
I am a bit cautious to again ask these questions...
And yes, the bias represents the intercept term of the separating hyperplane in the kernel (linear, radial etc) space... In other words, if g(.) is the hyperplane, g(0) will yield the bias.
HyperHyper, according to the operator info, takes two inputs, one positive and one negative example; moreover SVMs need normalised input. So we get.... My guess is that under these conditions Bias will always be zero!