You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Passing timelimit specified on command line to pyomo solver (#97)
* Passing timelimit specified on command line to pyomo solver; bug fix with cd; check-solver in docs
* Added an entry for the check-solver command and an associated doc page
Copy file name to clipboardExpand all lines: docs/source/README.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -137,6 +137,8 @@ section of your `hatchet.ini` (if using the [hatchet run](doc_runhatchet.html) c
137
137
solver. Make sure the relevant solver binaries are in your `$PATH`, otherwise Pyomo will not be able to find them
138
138
correctly.
139
139
140
+
One HATCHet command that is very useful to sanity-check your solver is `hatchet check-solver`. This command runs the HATCHet `compute_cn` step on a small set of pre-packaged data files and completes fairly quickly (a few seconds for the Gurobi optimizer, but up to a few minutes for glpk). Running this command will ensure that you have your solver settings (including licenses) set up correctly, so you should always run this command first before trying out the `compute_cn` step on your large data files.
This command of HATCHet runs the `compute_cn` step on a set of small data files (.bbc/.seg) pre-packaged with HATCHet, and is a quick way to verify if your solver is working correctly.
4
+
If you are unable to run this command, it likely indicates a licensing issue with default (Gurobi) solver. To use alternative solvers, see the
5
+
[Using a different Pyomo-supported solver](README.html#usingasolver_other) section of the README for more details).
6
+
7
+
## Input
8
+
9
+
This command takes no inputs.
10
+
11
+
## Output
12
+
13
+
This command produces debugging output from the solver. Look for the message towards the end of the output:
14
+
15
+
```
16
+
# Your current solver ... seems to be working correctly
17
+
```
18
+
19
+
to verify if your selected solver works correctly.
Copy file name to clipboardExpand all lines: docs/source/doc_compute_cn.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# hatchet
1
+
# compute-cn
2
2
3
3
This step computes allele-specific fractional copy numbers, solves a constrained distance-based simultaneous factorization to compute allele and clone-specific copy numbers and clone proportions, and deploys a model-selection criterion select the number of clone by explicitly considering the trade-off between subclonal copy-number aberrations and whole-genome duplication.
4
4
The step offers some parameters to control each of these features.
Copy file name to clipboardExpand all lines: docs/source/doc_fullpipeline.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,6 +64,7 @@ hatchet <step>
64
64
| (5) |[*plot-bins*](doc_plot_bins.html)| BBot | This step produces informative plots concerning the computed RDRs, BAFs, and clusters. The information produced by this step are important to validate the compute clusters of genomic regions. |
65
65
| (6) |[*compute-cn*](doc_compute_cn.html)| hatchet | This step computes allele-specific fractional copy numbers, solves a constrained distance-based simultaneous factorization to compute allele and clone-specific copy numbers and clone proportions, and deploys a model-selection criterion select the number of clone by explicitly considering the trade-off between subclonal copy-number aberrations and whole-genome duplication. |
66
66
| (7) |[*plot-cn*](doc_plot_cn.html)| BBeval | This step analyzes the inferred copy-number states and clone proportions and produces informative plots jointly considering all samples from the same patient. In addition, this step can also combine results obtained for different patients and perform integrative analysis. |
67
+
| (8) |[*check-solver*](doc_check_solver.html)|| This step runs the `compute_cn` step on a set of small data files pre-packaged with HATCHet, and is a quick way to verify if your solver is working correctly. |
0 commit comments