-
Notifications
You must be signed in to change notification settings - Fork 26
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
threads limitatiton and "Error in if (sol_epgap > opt$epgap) { : the condition has length > 1" #107
Comments
So this error arises from a final guard which checks if the solution epgap meets the threshold. I would double check the |
Hi @shihabdider, thank you for reply. Another bug occured. I run jabba on 71 samples, 57 successfully output Error in orimap[sapply(seq_along(ori), function(i) ori[[i]][iid[i]])] :
invalid subscript type 'list'
Calls: suppressPackageStartupMessages -> withCallingHandlers -> JaBbA -> read.junctions
In addition: Warning messages:
1: JaBbA 2024-11-16 04:13:15.006408: Vcf not in proper format. Will treat rearrangements as if in BND format
2: JaBbA 2024-11-16 04:13:15.012265: 602 rows of vcf do not have svtype BND, treat them as non-BND! My junction input file is Delly raw output. rtracklayer::export(
StructuralVariantAnnotation::breakpointgr2pairs(
StructuralVariantAnnotation::partner(
StructuralVariantAnnotation::breakpointRanges(
VariantAnnotation::readVcf(
commandArgs(trailingOnly = TRUE)[1]
),
inferMissingBreakends = TRUE
)
)
),
con = commandArgs(trailingOnly = TRUE)[2]
) to convert vcf to bedpe. |
And this is another bug: JaBbA 2024-11-16 13:25:14.650338: Number of gaps with nonzero width: 6732
JaBbA 2024-11-16 13:25:14.650628: Number of segments before gap filtering: 27165
JaBbA 2024-11-16 13:25:15.206296: 20433 segments produced after gap filtering
JaBbA 2024-11-16 13:25:17.242545: Brand new function for reciprocal junctions calling.
..
JaBbA 2024-11-16 13:25:18.447472: Excluding 1 aberrant junctions whose both breakpoints are in NA coverage regions
JaBbA 2024-11-16 13:25:18.448: Cancel nudge for 18 aberrant junctions where one of the 2 breakpoint is in NA coverage regions
JaBbA 2024-11-16 13:25:18.448293: In sum, we are forcing 0 junctions, excluding 1 junctions, and nudging 14 junctions
JaBbA 2024-11-16 13:25:19.293571: Excluding aberrant junctions: 509
JaBbA 2024-11-16 13:25:19.377128: Adjusting the kag (naive solution) as mipstart (initial solution).
Error in `:=`(cn, cnmle) :
Check that is.data.table(DT) == TRUE. Otherwise, :=, `:=`(...) and let(...) are defined for use in j, once only and in particular ways. Note that namespace-qualification like data.table::`:=`(...) is not supported. See help(":=").
Calls: suppressPackageStartupMessages ... [.data.frame -> := -> stopf -> raise_condition -> signal
In addition: Warning messages:
1: JaBbA 2024-11-16 13:24:39.904294: Tier field tier missing: giving every junction the same tier, i.e. all have the potential to be incorporated
2: JaBbA 2024-11-16 13:25:15.248105: Skipping over karyograph creation because file already exists and overwrite = FALSE
3: `clusters()` was deprecated in igraph 2.0.0.
ℹ Please use `components()` instead.
4: `graph.adjacency()` was deprecated in igraph 2.0.0.
ℹ Please use `graph_from_adjacency_matrix()` instead.
5: In `[.data.table`(junc.dt, , `:=`(from = NULL, to = NULL)) :
Tried to assign NULL to column 'from', but this column does not exist to remove
6: In `[.data.table`(junc.dt, , `:=`(from = NULL, to = NULL)) :
Tried to assign NULL to column 'to', but this column does not exist to remove
Execution halted |
Hello,
This error message is from jabba with R 4.3.3 and gurobi.
Is this a bug of jabba?
Another problem is Gurobi is using all cores instead of my setting
jba --cores 3
.I've tried using
echo "Threads 1" > gurobi.env
, but It seems not working.https://support.gurobi.com/hc/en-us/articles/14126085438481-How-do-I-set-parameters-in-Gurobi
It's ends up that
gGnome::run_gurobi
did not set threads limitation:And in
jbaMIP
:I turned this packages into a script and solved these anyway.
The text was updated successfully, but these errors were encountered: