CMosek added variable bounds

Hey @iglesias I made changes in Mosek.cpp for adding bounds on variables. Unfortunately, I have to touch many files to make the arguments consistent. Could you review the little patch for me? 

I am not sure we want to add unit-test for Mosek related class. But I am pretty sure these changes make sense. I have tested them on my own computer. BTW, I think @Jiaolong will test this part of code in his GraphCut inference thoroughly. 
Yeah, I understand. This way is ugly. But I don't want to add too many
things here, as I am just helping Jiaolong to add the bounding
functionality. Actually he'll implement the setters in FactorGraphModel for
learning with GraphCut. Maybe we abort this PR and wait Jiaolong to do
unit-test for thorough PrimalMosekSOSVM test?



On Sun, Jul 6, 2014 at 11:39 PM, Fernando Iglesias <notifications@github.com
> wrote:

> In tests/unit/structure/PrimalMosekSOSVM_unittest.cc:
>
> > +		dPsi.zero();
> > +		result->psi_pred_sparse.add_to_dense(1.0, dPsi.vector, dPsi.vlen);
> > +		result->psi_truth_sparse.add_to_dense(-1.0, dPsi.vector, dPsi.vlen);
> > +	}
> > +	else
> > +	{
> > +		SG_SPRINT("Should have either of psi_computed or psi_computed_sparse"
> > +				"to be set true\n");
> > +	}
> > +
> > +	return ( mosek->add_constraint_sosvm(dPsi, con_idx, train_idx,
> > +			model->get_num_aux(), -result->delta) == MSK_RES_OK );
> > +}
> > +
> > +SGVector<float64_t> dummy_mosek_sosvm(CFactorGraphModel* model,
> > +		SGVector<float64_t> lb, SGVector<float64_t> ub)
>
> I would say we either need these setters or do the unit test in a
> different way (e.g. testing it through classes that use different
> configurations of lb and ub). I do not really as an option to copy paste in
> the unit test the code we want to test.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/shogun-toolbox/shogun/pull/2372/files#r14582843>.
>



-- 
/**
* ============HuShell============
*/