Combining performance mesasures

ozgeozyazar
ozgeozyazar New Altair Community Member
edited November 2024 in Community Q&A
hi !

ı am using cross validation and try to measure the performance of model. I need both classification and binomial performance results but I do not know now to combine them. 

Could you please help me ? 
Tagged:

Best Answer

  • varunm1
    varunm1 New Altair Community Member
    edited May 2019 Answer ✓
    Hello @ozgeozyazar

    Simple way is to use a multiply operator inside testing part of CV. Connect the apply model output to multiply and you can use the outputs of multiply operators to connect to the two performance operators.


Answers

  • varunm1
    varunm1 New Altair Community Member
    edited May 2019 Answer ✓
    Hello @ozgeozyazar

    Simple way is to use a multiply operator inside testing part of CV. Connect the apply model output to multiply and you can use the outputs of multiply operators to connect to the two performance operators.


  • ozgeozyazar
    ozgeozyazar New Altair Community Member
    @varunm1

    Yes Sir, 

    It definately works.

    Thanks so much :smiley:
  • Telcontar120
    Telcontar120 New Altair Community Member
    Another way is to connect the performance output of one operator to the input of another performance operator. This creates a combined performance output. All the performance operators allow you to do this.  Then you don't even need the Multiply operator.
  • MartinLiebig
    MartinLiebig
    Altair Employee
    Hi,
    Just because i ran into this: Are there more people around who want to change the main criterion of a performance vector after building it like @Telcontar120 described it? I ran into this like 3 times and i am close to add a new operator to Toolbox.

    There is a 3 line groovy solution though.

    BR,
    Martin
  • varunm1
    varunm1 New Altair Community Member
    Till I saw @Telcontar120 solution, I am not aware that we can do this way. This is useful.

  • Telcontar120
    Telcontar120 New Altair Community Member
    @mschmitz an operator sounds useful but also not a problem that personally I have faced very often in this setup---but sometimes in optimization scenarios it is also useful to be able to change the main performance criterion.