Hello, I need some help please.
I submitted two jobs on Xcms online, but after two weeks, the % of processing remains on 0 %, so I am trying to delete this jobs
But, when I select the delete option, the jobs are not deleted, and only appears the text: Job(s) NOT deleted
Someone know how to delete this processing jobs?
Hi all. I was wondering if someone could shed some light on my situation. I submitted a job, and afterwards I received emails saying "Job Queued", followed by "Job Complete". This is all well and good. However, when I go onto the XCMS online site (while logged into my account) and I click the "View results" page, the job in question still says "Queued" in the status column - and so I can't seem to view the results. This is despite receiving an email telling me "Job Complete" - and yes, it is the same job number.
Within the "Job Complete" email itself, it reads:
Your job (#1155533) was successfully completed. You may access XCMS Online ([%FORMS_RETURN_URL%]%FORMS_RETURN_URL%) to view your results.
However, the link they provided in the email ([%FORMS_RETURN_URL%]%FORMS_RETURN_URL%) did not work, quite obviously.
I'm a bit confused as to why this is happening. The job seems to have been submitted successfully, was queued and then (according to the email notification at least) was completed. However on the website, it's still in the "queued" stage so I cannot access the completed job results. Has anyone encountered this problem before? How do I resolve it, so that I can actually view my results? Am I forgetting to do something I'm supposed to in order to get access to the completed job? Any help is appreciated.
Thanks in advance!
I still miss T338, T345, T370, T470, T500, T510, T580 and T620. Do you find them?
I've also tried to change the minimum peakwidth but I still miss some peaks... when I find peaks with overlapping I miss the less intense peaks.
Last post by DanielWillems -
I have some data that was acquired on an Agilent 6340 ion trap, so low resolution. The data was acquired in positive mode and all in one 300 minute (5 hour) run. I have since used proteowizard to "chop it up" into smaller (195 sec) chunks. I have found that the original timing was retained and the chunks are indeed 195 seconds in length. The samples were introduced into the MS through a novel device that has very little if any chromatography and thus is much more like direct injections. To work out the analysis, I am currently working with a small subset of these runs (5 injections).
I also have a set of this data that I have gone into and replaced the original scan data with the scan numbers from just the 1st run in an attempt to group the data per the retention time data.
OK now to the question. I am using xcmsSet in R to analyze the data. I have picked peaks with this code:
"xset <- xcmsSet(samples, snthresh= 1.8, method = c("matchedFilter"), step = 0.2, steps = 1)"
and I think I have good results but am unsure how to visualize this data, any suggestions there? Then when I group using:
"xset <- group(xset)"
It looks OK but again, I am not sure how to visualize this to check. Finally when I try to RT correct this data across what are now separate files using:
"xset2 <- retcor(xset, family = "symmetric", plottype = "mdevden")"
All I get is an error that says :
"Error in .local(object, ...) : No group information found"
Indeed the picked xset returns with Peak Groups: 0
Two questions here, 1. is this likely to be because the original retention time data was saved during the file clipping and conversion step? 2. Is there away around this so I can look for differences in this data?
Thank you so much for any help you can offer,
I need a small peakwidth because of triacylglycerols coming off around the same time as the cholesterol esters. Isobaric compounds (different combinations acyl chains that add up to the same m/z but are chromatographically separated) that elute close together. Everything is fine, except the CholE.
However, explaining the problem here, led me to a solution: what I needed was getPeaks(). One can define the peakrange (an mz range and rt range) and get the integrated peak area from the xcmsRaw object. I will replace the appropriate xset@peaks with the result from this function and that should do the trick.
I haven't tried to manipulate it like that so I don't know.
But your peakwidth is too narrow I think if you want all in one. You have a max of 10 sec. If you want to merge all you need several minutes I assume. At least I'd try that.
I'm integrating as:
xset <- xcmsSet(files=project.files, profmethod = "bin", method="centWave", ppm = 2, peakwidth=c(3,10), snthresh = 10, prefilter = c(5,2e4), mzdiff = 0.003, fitgauss = TRUE, integrate = 1, BPPARAM = MulticoreParam(4,progressbar=TRUE))
so I'm already using a positive mzdiff.
I was thinking to change the rt boundaries in xset@groups, clearing out the xset@groupidx and then do a fillpeaks, leaving the original peaks intact to prevent messing up the peakidx part. But feeding an empty list to fillpeaks() doesn't seem to be allowed.
which peak exactly are you missing ? As you see below, I can happily find
One way to achieve this, I think, is to set mzdiff to something positive. That should make everything connected integrate as one. Of course this might have unwanted effects in other places.