Open GeorgWa opened 5 months ago
The thing is that precursor_df
is sorted in-place by nAA and I assume it is for computational speed purposes.
Apart from altering the precursor_df
the predictions are not returned with the same original ordering
Describe the bug This is not really a bug, rather unexpected behaviour. The use case is a filtered spectral library which does not have the expected precursor & fragment order. It would be good to know, what the expected precursor and fragment order is.
To Reproduce
Results
Expected behavior as
ModelManager.predict_all()
returns a Dataframe it would be expected thatprecursor_df
is not changed.