Skip to content

--apply_weights requires --ss_main_score to be specified as in the original command #151

@jcharkow

Description

@jcharkow

I get unexpected results when using --apply_weights with XGBoost if a --ss_main_score was set manually.

E.g.

pyprophet score --in in.oswpq --level=ms1ms2 --classifier=XGBoost --ss_main_score=var_dotprod_score

  • Trains the model as expected
Image

However if this command is used
pyprophet score --in in.oswpq --level=ms1ms2 --classifier=XGBoost --apply_weights=weights.bin

The weights are applied to the incorrect scores

Image (Same weights on different columns)

To get the expected results the --ss_main_score has to be specified as in the original run
pyprophet score --in in.oswpq --level=ms1ms2 --classifier=XGBoost --ss_main_score=var_dotprod_score --apply_weights=weights.bin

Image

It would be nice if this was detected automatically somehow

Metadata

Metadata

Assignees

Labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions