Skip to content

Does Tune_ConQuR function test all options I input? #18

@mhjonathan

Description

@mhjonathan

Hi, thank you for the amazing tool and it helps me a lot now :)

I want to ask you one thing about Tune_ConQuR function. I checked that default setting of ConQur works best so far, and want to check if it could give me a better performance with fine tuning.

I first run Tune_ConQuR with same code written in the manual (https://wdl2459.github.io/ConQuR/ConQuR.Vignette.html), but it gives me worse performance compared to default setting (less decreased batch effect and also decreased key covariate effect).

So what I want to ask you is, if I give all possible parameters of Tune_ConQur like below, does it test all possible combinations of given parameters and give me the best one at the end?

result_tuned = Tune_ConQuR(tax_tab=total_taxa, batchid=batchid, covariates=covar,
batch_ref_pool=c("0","1"),
logistic_lasso_pool=T,
quantile_type_pool=c("standard", "lasso", "composite"),
simple_match_pool=T,
lambda_quantile_pool=c(NA, "2p/n"),
interplt_pool=T,
frequencyL=0,
frequencyU=1)

For example, if I run above code, does it test "logistic_lasso_pool=T" for all parameters and "logistic_lasso_pool=F" combination also?

And would it be possible that this fine-tuned conqur result show worse performance than default setting?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions