![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Agilent Bioanalyzer alternatives? | rmetz | Sample Prep / Library Generation | 20 | 06-18-2015 01:14 AM |
ChIP- Different DNA size for Input DNA and ChIP DNA on Agilent Bioanalyzer | rahulr1485 | Epigenetics | 19 | 05-17-2013 09:14 PM |
Agilent Bioanalyzer 2100 detects no DNA | obischof | Sample Prep / Library Generation | 5 | 01-11-2011 08:15 AM |
Insert size with Agilent SureSelect | sdavis | Sample Prep / Library Generation | 12 | 05-14-2010 11:39 AM |
Help! illumina sequencing sample size shifted in Bioanalyzer? | RUmustang | Illumina/Solexa | 4 | 04-22-2010 03:35 PM |
![]() |
|
Thread Tools |
![]() |
#1 |
Senior Member
Location: Purdue University, West Lafayette, Indiana Join Date: Aug 2008
Posts: 2,317
|
![]()
A perennial irritation with using the Agilent Bioanalyzer for DNA or RNA QC is that it frequently refuses to convert the x-axis from time (seconds) to size (bases). In our most recent case the issue that seems to trigger this stubbornness on the part of the application is that the data was collected for 69.8 seconds instead of the 84 seconds the application believes it should have collected data for.
I know of no way to control this behavior. Any ideas? I've been through all the trouble shooting sections in the manual, but none of them address this issue. -- Phillip |
![]() |
![]() |
![]() |
#2 |
Junior Member
Location: Germany Join Date: Dec 2009
Posts: 1
|
![]()
Hi,
the sizing does not work if - marker(s) were not recognized correctly - ladder wasn't recognized correctly. if you can't solve the problem by reassigning markers and adjusting peak find settings, I suggest to contact Agilent on-line tech support at Bioanalyzer Line: (800) 227-9770 x3 x4 x1 Direct Line: (800) 894-1304 x5454 or bioanalyzer@agilent.com Cheers RR |
![]() |
![]() |
![]() |
#3 | |
Senior Member
Location: Purdue University, West Lafayette, Indiana Join Date: Aug 2008
Posts: 2,317
|
![]() Quote:
Thanks for the answer. I may contact Agilent as you recommend. But I do not know anyone who has used a Bioanalyzer frequently who does not run into this issue on a regular basis. So I think it worth discussing here. I have used the methods you mention previously to solve some "failure to size" issues in the past. But there is another class of these that is particularly maddening. That is, there is no failure to size per se. Instead the program refuses to convert the x-axis to size (bases). That is, using other methods (eg "smear analysis") the program will correctly label the sizes of peaks. Therefore the program has recognized the ladder and and the markers were recognized correctly. Nevertheless, it proves impossible to force the program to convert the x-axis from seconds to bases. This phenomenon seems particularly prevalent on pico RNA labchip runs. |
|
![]() |
![]() |
![]() |
#4 |
Senior Member
Location: Purdue University, West Lafayette, Indiana Join Date: Aug 2008
Posts: 2,317
|
![]()
It seems that any errors (which appear as red dots at the top of a lane) in any lane will prevent the x-axis from converting to size (nucleotides). This would just be a plain old bug in the code. Either that or a design flaw in the work flow. There is no sense to it.
The workaround is to clear those errors by any means necessary. Unfortunately this is not necessarily trivial. On the pico RNA lab chips it is not unusual for the lower size marker not to appear on the electropherogram for one or two samples. If the software has called any peaks for any reason, you can right-click on one them and one of the choices is to set that peak to the lower size marker. This should clear the error. Once all errors for the run are clear, the x-axis can be switched to size (nucleotides). If the software has not called a peak, then it is much more difficult in RNA assays. Beyond the scope of this post. But, in brief, it seems to require adding a fragment analysis to the "local settings" pane and setting the integrator parameters to a low enough stringency to call a peak in the interval set by the fragment analysis. One hurdle here is that even though the time<->size button will not change the x-axis, maddeningly, it does switch the unit in the "add fragment" table. So, if you happen to have it set to "size" and don't notice, the interval you set will be invalid ("nt" instead of "s") and you will never be able to convince the software to call a peak. -- Phillip |
![]() |
![]() |
![]() |
#5 |
Junior Member
Location: none of your biz Join Date: Aug 2010
Posts: 2
|
![]()
0) as noted, this is a real pain in the software, and it is one of many pains in the software. If you don't complain to agilent, or tell them that you are not thinking of the new shimadzu (reusable cartridge) or the biorad, they won't do anything - btw, the least they can do is send you a free kit; if enough people complain, maybe they will do something.
Remember, the 1st law of business is, if it isn't impacting sales, it isn't a problem. 1) the workaround that I found was to set the "peak height" value (under global settings) to some very low value - when you do this, the software will call very small (noise) peaks as peaks, this allows you to set an upper and lower marker in each lane, which at least allows the software to work. 2) there is also a problem in that the x axis values are not "real" - if you assign some peak to be the upper or lower marker, note that the x axis value, IN TIME, changes - this means that that time scale is some sort of computed scale, not a real scale 3) Another big problem with the software is that they don't give you an equation giving bp as a function of time, which would be nice if you wanted to export data and do some stuff 4) the results reporting is not very useful, I find myself having to do huge amounts of work 5) you can't set the region to a peak |
![]() |
![]() |
![]() |
#6 |
Senior Member
Location: Purdue University, West Lafayette, Indiana Join Date: Aug 2008
Posts: 2,317
|
![]()
Hi Roger,
0) In general, I agree. But many of us are used to the support we get on instruments that cost half a million dollars and for which we pay fifty thousand a year in service contracts. Since the Bioanalyzer costs "only" $20K or so and the software glitches are an occasional issue, there is likely to be little complaint. 1) Yes, that is one I use also. 2) I'm sure that is just an offset, right? 4) Seems like most people just accept what the software gives them. For example, the completely fabricated metric the "RIN" score, for total RNA quality, is accepted without question by most. But only the most vague description of how the software comes by the "RIN" score is given. 5) And the tricks one can use to accomplish this indirectly (eg "smear analysis") are different for different analysis (chip) types. -- Phillip |
![]() |
![]() |
![]() |
#7 |
Junior Member
Location: none of your biz Join Date: Aug 2010
Posts: 2
|
![]()
Normally, I would agree with you about the cost thing - you can't expect the level of service you get on a half million dollar HPLC/MS with a cheap instrument
However, the bio analyzer is a bit unusual for the lab market, in that the volume is very, very high (for the lab market). Thus, we can expect better. More generally, as an academic turned industry guy, I am constatnly amazed at how accepting scientists are of obvious flaws, Agilent is making a ot of money on this instrument; we have the right to demand better software. |
![]() |
![]() |
![]() |
#8 |
Senior Member
Location: USA Join Date: Apr 2009
Posts: 482
|
![]()
Agilent has always had very poor technical support. I'll never forget when Silicon Genetics was bought out by them and then they moved all the tech support to India and hired people who couldn't speak English well.
Caliper sells their own new instrument now (they developed the Bioanalyzer for Agilent). Hopefully their support is better. |
![]() |
![]() |
![]() |
#9 |
Member
Location: Germany Join Date: Aug 2009
Posts: 33
|
![]()
There's a little info inside the software on the RIN - go to Help - Contents and Index. in the Application Notes under "Related Documents", there's something on RIN, and also you could search for RIN.
Last edited by Susanne; 08-27-2010 at 05:09 AM. Reason: typo |
![]() |
![]() |
![]() |
#10 |
Member
Location: Germany Join Date: Aug 2009
Posts: 33
|
![]()
Referring to the time shown (x-axis) that changes when the markers are changed (DNA chips): in order to calculate the correct sizes for all lanes, a 'virtual time' is assigned to the markers, and these are aligned with each other (all lanes) and with the Ladder. So if you change a upper or lower marker, clearly, the time annotation of the x-axis does change. To see the "real" migration time, just turn off the analysis (stop button).
|
![]() |
![]() |
![]() |
#11 |
Member
Location: Dallass Join Date: Nov 2009
Posts: 49
|
![]()
Has anyone tried the Caliper instrument?
|
![]() |
![]() |
![]() |
#12 |
Junior Member
Location: Western Australia Join Date: Aug 2010
Posts: 4
|
![]()
There are instances where this solution will not work, for instance if the run is stopped before the trace data begins for a particular sample. The result file is just an empty xy graph, with no chance of assigning markers.
I tried using the Comparison context to import the working samples, leaving out the failed sample, but even with no failed samples present in the comparison window the x axis wouldn't switch from time to size. |
![]() |
![]() |
![]() |
#13 |
Member
Location: Germany Join Date: Aug 2009
Posts: 33
|
![]()
Unfortunately, in the comparison context, it doesn't work to change the x-axis to size. Only time is available.
![]() |
![]() |
![]() |
![]() |
#14 |
Senior Member
Location: Purdue University, West Lafayette, Indiana Join Date: Aug 2008
Posts: 2,317
|
![]()
I don't use the Comparison context much. But I did not think it ever displayed size -- only time.
One last possibility I can think of in your case: Click on the "Files" tab and choose "Save selected sample...". Choose only the lanes that did complete. Save the new, partial .xad file. Open that file. See if it will now size your samples. -- Phillip |
![]() |
![]() |
![]() |
Thread Tools | |
|
|