Skip to content

Commit

Permalink
minor bugfixes
Browse files Browse the repository at this point in the history
  • Loading branch information
ArthurDeclercq committed Jul 15, 2024
1 parent 0d2fb2e commit 77e7c1b
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
2 changes: 1 addition & 1 deletion Dockerfile
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,6 @@ ADD ms2rescore /ms2rescore/ms2rescore

RUN apt-get update \
&& apt install -y procps \
&& pip install /ms2rescore
&& pip install /ms2rescore --only-binary :all:

ENTRYPOINT [""]
4 changes: 2 additions & 2 deletions docs/source/userguide/tims2Rescore.rst
Original file line number Diff line number Diff line change
Expand Up @@ -36,8 +36,8 @@ To use `timsrescore`, follow these steps:
timsrescore -p <path_to_psm_file> -s <path_to_spectrum_file> -o <path_to_output_file>
Replace `<path_to_psm_file>`, `<path_to_tims_file>`, and `<path_to_output_file>` with the actual paths to your input and output files.
_NOTE_ By default timsTOF specific models will be used for predictions. Optionally you can further configure settings through a configuration file. For more information on configuring `timsrescore`, refer to the :doc:`configuration` tab in the user guide.
Replace `<path_to_psm_file>`, `<path_to_tims_file>`, and `<path_to_output_file>` with the actual paths to your input and output files.
_NOTE_ By default timsTOF specific models will be used for predictions. Optionally you can further configure settings through a configuration file. For more information on configuring `timsrescore`, refer to the :doc:`configuration` tab in the user guide.

3. Review the results:
- Once the `timsrescore` process completes, you will find the rescoring results in the specified output file or if not specified in the same directory as the input files
Expand Down

0 comments on commit 77e7c1b

Please sign in to comment.