You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to request the addition of support for the .dia file format as an input option in the quantms pipeline. Currently, as per the documentation and community feedback, the pipeline supports .raw, .mzML, and Bruker .d file formats. However, .dia files are not supported as input at this time.
Given that DIA-NN is capable of handling .dia files directly, implementing support for this format would enhance the flexibility and usability of the quantms pipeline. This would enable users who work with .dia files to directly utilise the pipeline without having to convert file formats beforehand, thus streamlining the workflow.
This feature would be valuable for users who generate .dia files and wish to take advantage of quantms's capabilities without needing additional file conversion steps. It would improve the pipeline's versatility and cater to a wider range of workflows.
Thank you for considering this feature request.
The text was updated successfully, but these errors were encountered:
Description of feature
Hello quantms team,
I would like to request the addition of support for the
.dia
file format as an input option in the quantms pipeline. Currently, as per the documentation and community feedback, the pipeline supports.raw
,.mzML
, and Bruker.d
file formats. However,.dia
files are not supported as input at this time.Given that DIA-NN is capable of handling
.dia
files directly, implementing support for this format would enhance the flexibility and usability of the quantms pipeline. This would enable users who work with.dia
files to directly utilise the pipeline without having to convert file formats beforehand, thus streamlining the workflow.This feature would be valuable for users who generate
.dia
files and wish to take advantage of quantms's capabilities without needing additional file conversion steps. It would improve the pipeline's versatility and cater to a wider range of workflows.Thank you for considering this feature request.
The text was updated successfully, but these errors were encountered: