Skip to content

Conversation

@jcharkow
Copy link
Owner

@jcharkow jcharkow commented Aug 4, 2025

Description

Checklist

  • Make sure that you are listed in the AUTHORS file
  • Add relevant changes and new features to the CHANGELOG file
  • I have commented my code, particularly in hard-to-understand areas
  • New and existing unit tests pass locally with my changes
  • Updated or added python bindings for changed or new classes (Tick if no updates were necessary.)

How can I get additional information on failed tests during CI

Click to expand If your PR is failing you can check out
  • The details of the action statuses at the end of the PR or the "Checks" tab.
  • http://cdash.seqan.de/index.php?project=OpenMS and look for your PR. Use the "Show filters" capability on the top right to search for your PR number.
    If you click in the column that lists the failed tests you will get detailed error messages.

Advanced commands (admins / reviewer only)

Click to expand
  • /reformat (experimental) applies the clang-format style changes as additional commit. Note: your branch must have a different name (e.g., yourrepo:feature/XYZ) than the receiving branch (e.g., OpenMS:develop). Otherwise, reformat fails to push.
  • setting the label "NoJenkins" will skip tests for this PR on jenkins (saves resources e.g., on edits that do not affect tests)
  • commenting with rebuild jenkins will retrigger Jenkins-based CI builds

⚠️ Note: Once you opened a PR try to minimize the number of pushes to it as every push will trigger CI (automated builds and test) and is rather heavy on our infrastructure (e.g., if several pushes per day are performed).

jpfeuffer and others added 29 commits July 16, 2025 13:21
… use it within its child Protease Digestion; expand ProteaseDigestion_test; expand ProteaseDigestion python binding test and move it from test000.py to new test_ProteaseDigestion.py
Expanded and reworded documentation, added some input data checks and exceptions to `ProteaseDigestion.digest()` and `EnzymaticDigestion.semiSpecificDigestion_()`, added some tests.
[FIX] DIAScore slow, unprecise dotproduct. Add ASAN support for Windows
Fixed invalid (not implemented)  use of SPEC_NONE with `ProteaseDigestion::digest()` by functions `DecoyGenerator::reversePeptides()` and `DecoyGenerator::shufflePeptides()`.
These now use `SPEC_FULL`, which should produce identical results as before - but perhaps this was not the behaviour intended?
…tion_; missing documentation; additional tests; fix pyOpenMS tests
* FileInfo reports J instead of I for FASTA files

* add some math convenience functions; use them in FileInfo

* add tests

* don't add small AAA's by accident

* fix doxygen

* fix tests and counting
* fix docs for annotate()

* Apply suggestions from code review

---------

Co-authored-by: Timo Sachsenberg <timo.sachsenberg@uni-tuebingen.de>
* merged

* adapt test to account for two extra hydrogens due to charge==2

* handle negative charges

* update CHANGELOG

---------

Co-authored-by: Samuel Wein <sam@samwein.com>
Co-authored-by: Timo Sachsenberg <timo.sachsenberg@uni-tuebingen.de>
…aware (OpenMS#7975)

* modify MTD and EPD to be ion mobility aware

* add static iterativeweight function. Simplify floatdataarray handling. Bug fux moving up in rt dimension

* Update src/openms/include/OpenMS/FEATUREFINDER/MassTraceDetection.h

Co-authored-by: Timo Sachsenberg <timo.sachsenberg@uni-tuebingen.de>

* attempt to remove code duplication by unifying im and im-free logic flow

* removed redundant im array check

* added hard coded strings to constants.h. Must coordinate with peakpickerIM pr

* improve im check readability

* added getIMIndices_() private function to handle im meta array index

* MassTraceExtractor was manually checking meta values -- causing test errors.

* replacted MassTraceExtractor_1_output.featureXML with a new file containing fwhm_mz_avg for all traces

* replaced MassTraceExtractor_2_output.featureXML. It used to have 9/101 traces annotated with fwhm_mz_avg. Now all traces are annotated

* updated MassTraceExtractor json test files to include ion_mobility_tolerance parameter

* regenerate test output files using test mode. Add name

* regenerate MassTraceExtractor_3_expected.ini in test condition

* added new MassTraceExtractor test with ion mobility data

* write 0.0 as 0 cleanup

* fix MTD_3 test

* Sort MTD output before writing to file

* faster lookup of closest im value

* update test

* fix uninitialized

* introduce a smaller test (mtd-5). Comment out mtd-4.

* add larger test (mtd-6).

* reorder new mtd tests. Remove old mtd-4 test

* comment cleanup

* numbering fix

* isolate problem trace in a separate file in an attempt to reproduce error

* push files

* try to change quant method for mtd-5 test to max_height.

* revert back to area quant

* attempt to reproduce mtd-5 error in mtd-6

* cmakelist fix

* update test

---------

Co-authored-by: Mohammed AlHigaylan <alhigaylan@Mohammeds-MacBook-Pro-2.local>
Co-authored-by: Mohammed AlHigaylan <alhigaylan@macbookpro.home>
Co-authored-by: Timo Sachsenberg <timo.sachsenberg@uni-tuebingen.de>
Co-authored-by: Julianus Pfeuffer <8102638+jpfeuffer@users.noreply.github.com>
@jcharkow jcharkow closed this Aug 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.