Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No filename when adding id data #39

Closed
lgatto opened this issue Oct 14, 2014 · 6 comments
Closed

No filename when adding id data #39

lgatto opened this issue Oct 14, 2014 · 6 comments

Comments

@lgatto
Copy link
Owner

lgatto commented Oct 14, 2014

When loading mzid files that do not return the id filename as part of the data.frame column, addIdentificationData throws the following error via utils.addSingleIdentificationDataFile:

Error in basename(id$spectrumFile) : a character vector argument expected

See https://groups.google.com/forum/#!topic/rbioc-sig-proteomics/na-dMumFgAU

There should be another or a second mechanism to handle this situations.

@lgatto
Copy link
Owner Author

lgatto commented Oct 17, 2014

The code accommodate such cases has been written, the real issue might lie somewhere else.

The bug report comes from a user that uses X!TANDEM, that uses mgf files as input, rather than directly mz[X]ML. The current changes in the code will detect and warn that there is a discrepancy between what was used to produce the mzid file (i.e. foo.mgf) and what the MSnExp was created with (i.e. foo.mzML). But I still have to figure out if it remains possible to do the actual matching between spectra in the MSnExp and mzid in such situations (or even in cases where both stem from foo.mgf).

@Xabiermm1
Copy link

I think this could works , with iTRAQ 4

Its the default input.xml file, for xtandem

2014-10-17 10:49 GMT+02:00 Laurent Gatto notifications@github.com:

The code accommodate such cases has been written, the real issue might lie
somewhere else.

The bug report comes from a user that uses X!TANDEM, that uses mgf files
as input, rather than directly mz[X]ML. The current changes in the code
will detect and warn that there is a discrepancy between what was used to
produce the mzid file (i.e. foo.mgf) and what the MSnExp was created with
(i.e. foo.mzML). But I still have to figure out if it remains possible to
do the actual matching between spectra in the MSnExp and mzid in such
situations (or even in cases where both stem from foo.mgf).


Reply to this email directly or view it on GitHub
#39 (comment).

@sgibb
Copy link
Collaborator

sgibb commented Oct 20, 2014

According to the mzIdentML specification there must be a <SpectraData> element (maybe it is worth to ask for a fix upstream?). As fallback it should be sufficient to show a warning and compare both filenames. In most cases the filenames should be the same.

The current changes in the code will detect and warn that there is a discrepancy between what was used to produce the mzid file (i.e. foo.mgf) and what the MSnExp was created with (i.e. foo.mzML).

@lgatto Did you already push these changes?

@lgatto
Copy link
Owner Author

lgatto commented Oct 20, 2014

Just pushed now.

The issue is not <SpectraData> in mzid files, but the absence thereof (and any other well defined annotation) if the mzid was generated using an mgf file, which is very poor in meta-data. I will need to run some tests to figure out, but I have the feeling that such cases will have to be dealt with manually by the user.

@mdkasoji
Copy link

Hi,

From reading the thread, it seems that you have fixed this issue? I am still receiving this error message. My raw data input files were mzXML (converted from .raw to mzXML) using proteowizard and the mzIdent files were generated from Mascot.

Any suggestions on how to get past this error?

Here is my code:

files=dir("/Users/kasojimd/Projects/ccrifx-541/Raw2mzXML",full.names=T,patter="mzXML")

rawdata=readMSData(files)

identFile=list.files(pattern=".mzid$")

msexp <- addIdentificationData(rawdata, filenames = identFile, verbose = FALSE)
Error in basename(id$spectrumFile) : a character vector argument expected

Any suggestions will be appreciated!

Thanks!

@lgatto
Copy link
Owner Author

lgatto commented Jan 15, 2015

Please do not cross-post. See your post on the Bioc support site for an answer.

@lgatto lgatto closed this as completed Jan 15, 2015
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

No branches or pull requests

4 participants