Skip to content

Commit 2920ee5

Browse files
committed
add error opt, name ref
1 parent e9389ae commit 2920ee5

File tree

1 file changed

+13
-3
lines changed

1 file changed

+13
-3
lines changed

README.md

Lines changed: 13 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -46,16 +46,26 @@ source("nmfconsensus.R")
4646
runNMF()
4747
```
4848

49+
Enter your name (or any name that you recognize) so you can see how your runtime
50+
compares to other approaches later.
51+
4952
You will realize that it throws an error. Try to spot and correct it. You can get
5053
get a quick overview of the context with `traceback()`.
5154

5255
**Using the debugger**
5356

5457
If there is an error you can not spot right away, it makes sense to run your code
5558
through the debugger. You can debug a function by calling `debug()` on it. In our
56-
case, you will want to call `debug(nmfconsensus)` and then the function again. It
57-
will show the chunk of code that is about to be executed. Within the debugger, you
58-
can type in the following commands:
59+
case, you will want to call
60+
61+
```splus
62+
options(error=recover) # if there is an error, don't just quit
63+
debug(nmfconsensus) # use the debugger for this function
64+
runNMF()
65+
```
66+
67+
It will show the chunk of code that is about to be executed. Within the debugger,
68+
you can type in the following commands:
5969

6070
* **<Enter> or n:** execute the next single statement
6171
* **c:** execute the next block

0 commit comments

Comments
 (0)