Databases
StackOverflow2013
Postsdbo
POException handling and stack unwinding in R
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POException handling and stack unwinding in R
    primarykey
    data
    text
    <p>In order to set up a coherent exception handling interface for my colleagues' and my R scripts, I would like to employ the following tryCatch structure.</p> <ol> <li>An outer tryCatch is wrapped around a given R script. It is used to catch and handle fatal errors that require the script to abort.</li> <li>User-specific tryCatch commands within the user's scripts. These should catch and, possibly, handle <ul> <li>2a. non-fatal errors, where no script abortion is necessary</li> <li>2b. fatal-errors that require the script to abort. The error is handled by the outer tryCatch [see 1.]</li> <li>2c. fatal-errors with additional error information. Error handled by outer tryCatch.</li> </ul></li> </ol> <p>The following code is how I would implement these features. However, since I am not an expert in R, I would like to ask whether this is a good approach. Specifically:</p> <p>Q1. Is it ok not to specify an error handler in the inner tryCatch and to wait for the outer tryCatch to handle that error (see 2b. above and code below)?</p> <p>Q2. Is rethrowing the same error (see 2c. above/below) within a handler correct/considered good coding style?</p> <p>Thank you!</p> <pre><code>#outer tryCatch, see 1. tryCatch({ #user code block #2a. user specific tryCatch, object "vec" not defined tryCatch(print(vec),error=function(e) {print("Non-fatal error. Script execution continued.");print(e);}) #2b. user specific tryCatch tryCatch(vec*2) #2c. user specific tryCatch tryCatch(vec*parameter1, error=function(e) {print("Additional fatal error information. Script execution aborted.");stop(e);}) #end of user code block }, #outer tryCatch error handler in order to handle fatal errors error=function(e) {print("Fatal error");print(e);} ) </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. UScryo111
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POException handling and stack unwinding in R
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POException handling and stack unwinding in R
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload