# Missing "paired" input for fastp tool

**URL:** <https://help.galaxyproject.org/t/missing-paired-input-for-fastp-tool/14750>\
**Category:** Resources\
**Tags:** development-tools, resources, tool-help, fastp\
**Created:** [February 16, 2025, 5:53pm UTC](https://help.galaxyproject.org/t/missing-paired-input-for-fastp-tool/14750 "2025-02-16T17:53:10Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![bernt-matthias](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/bernt-matthias/32/502_2.png) [@bernt-matthias](https://help.galaxyproject.org/u/bernt-matthias)\
**Post date:** [February 20, 2025, 10:09pm UTC](https://help.galaxyproject.org/t/missing-paired-input-for-fastp-tool/14750/5 "2025-02-20T22:09:06Z")

</div>

As mentioned in the linked ticket the removal of the option was intentional. The reason for the removal was to simplify the complexity of the tool wrapper.

Since paired data can still be used, no functionality is lost in my opinion. You “just” need to organize the data as paired collection.

Would you agree with my argumentation? I would be happy to discuss. What is your use case?

---

_[View the full topic](https://help.galaxyproject.org/t/missing-paired-input-for-fastp-tool/14750)._