Skip to content

TIMS_MaxDIA_Object reference not set to an instance of an object_Writing_tables 0243.error #156

@JBLEEKE

Description

@JBLEEKE

LS,

Thank-you in advance for your time and effort.

Lately I have been trying to process data acquired with a Bruker timsTOF in PASEF-DIA mode, based on a HeLa sample. This is to test several options we are investigating with regards to data acquisition and processing.

I have been running into several faults now, most of them were user error and with some effort I have managed to get to line 43 "Writing Tables". This is were I am stuck, running Maxquant in "Discovery Mode" based on .fasta files etc. supplied through: annotations.perseus-framework.org, does give me the desired output. The fault occurs when using the evidence.txt and msms.txt obtained through DDA data processing. I am using these in the TIMS-MaxDIA processing in MQv2.6.7.0. As is read the changelog on this version I came across a fixed issue with regards to writing tables. This is why I opted to address my/the issue here.

I have also tried changing operating system, by default we are processing our data via Windows Server, I have also tried Windows 10. (Currently we do not have Windows 11 yet on our work stations). Up-to-date as of May 1st 2025.

#runningTimes.txt
Writing_tables 0243.error.txt

Steps to reproduce the behavior:
In principle, running from any line before 43, returns the error, as well as processing from scratch. In all cases I have been using the same set of data files. I have my mqpar.xml/evidence.txt/msms.txt and datafiles as a .zip file. I can directly upload this when needed/requested. (~8GB)

Thank-you for your time and effort. I hope this is actually user error so that it might be an easy/low-effort fix.

Kind regards,
Jurre Bleeker

Metadata

Metadata

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions