Unconfigured Ad

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Welmu
    Junior Member
    • Apr 2013
    • 1

    #1

    DESeq2: rows did not converge in beta

    I'm trying to run a rather complicated model in DESeq2 with 16S microbiome data. More specifically, the model is "~ confounder + diseaseStatus:subject + timepoint*diseaseStatus" (a two-timepoint case-control comparison, with the same subjects at both timepoints; all variables are factors, except for the confounder, which is numeric). Probably because of how complicated this is, I keep running into the "rows did not converge in beta, labelled in mcols(object)$betaConv. Use larger maxit argument with nbinomWaldTest" issue. Now, this wouldn't be such a big problem otherwise, but many of the rows that don't converge in beta represent microbial taxa that I am very much interested in, and would like to have results for.

    First of all, the output still includes a full set of results, complete with p-values, for the rows that were labeled as non-converging. Are these good for anything, or should I just ignore them completely? Some old discussions I found on this topic suggest deleting all the non-converging rows from the output. The DESeq2 documentation mentions a useOptim parameter, "whether to use the native optim function on rows which do not converge within maxit", for nbinomWaldTest, which is by default TRUE, and I assume is relevant to what's going on here, but I don't really understand what this means.

    Secondly, is there any way to get around this issue? I've looked at everything google/earlier conversations suggest as solutions for this, which mostly comes down to trimming the data and increasing the maxit value for nbinomWaldTest. I've tried both, and neither trimming the data aggressively nor increasing the maxit several orders of magnitude (from the default 100 all the way to 1 000 000) help lower the number of non-converging rows. I'd be extremely thankful for any additional ideas that might help.

    (I guess it might come down to "run a simpler model". I'm just fond of running it as one comparison using all the samples at once, instead of subsetting it by timepoint or some such.)

Latest Articles

Collapse

  • SEQadmin2
    Beyond CRISPR/Cas9: Understand, Choose, and Use the Right Genome Editing Tool
    by SEQadmin2



    CRISPR/Cas9 sparked the gene editing revolution for both research and therapeutics.1 But this system still showed severe issues that limited its applications. The most prominent were the heavy reliance on PAM sequences, delivery limitations, double-stranded breaks that prompt unintended edits and cell death, and editing inefficiency (both in targeting and in knock-in reliability).

    Despite this, “CRISPR helped turn genome editing from a specialized technique into
    ...
    07-31-2026, 11:01 AM
  • SEQadmin2
    Proteomic Platforms: How to Choose the Right Analytical Strategy to Improve Detection and Clinical Applications
    by SEQadmin2


    Proteomics platforms are evolving rapidly, with advances in mass spectrometry and affinity-based approaches expanding what researchers can detect and at what scale. As the field moves toward deeper proteome coverage and clinical applications, scientists face an increasingly complex landscape of tools. This article will explore how researchers are navigating these choices to find the right platform for their work.

    The systematic characterization of the human proteome has
    ...
    07-20-2026, 11:48 AM

ad_right_rmr

Collapse

News

Collapse

Topics Statistics Last Post
Started by SEQadmin2, Yesterday, 12:22 PM
0 responses
12 views
0 reactions
Last Post SEQadmin2  
Started by SEQadmin2, 08-11-2026, 10:35 AM
0 responses
14 views
0 reactions
Last Post SEQadmin2  
Started by SEQadmin2, 08-06-2026, 07:41 AM
0 responses
31 views
0 reactions
Last Post SEQadmin2  
Started by SEQadmin2, 08-03-2026, 10:13 AM
0 responses
49 views
0 reactions
Last Post SEQadmin2  
Working...