Skip to content

Troubleshooting

Jump to bottom
robertprior-fixstars edited this page Sep 26, 2019 · 3 revisions

Here are some tips for resolving any errors encountered:

  1. If a pipeline stage failed with an out of memory error try reducing the parallelization option in loadParameters.m. In the worst case can run in a single thread (requiring the least amount of memory) by setting _WORKERS and _THREADS parameters to 1 for the failed stage.
  2. In the log directory (set in loadParameters.m) there will be log files for each stage with a name like: matlab-nameOfStage.log. Some stages will have a number before the file extension designating a round number for a particular stage. These log files contain the output directly form MATLAB and can see exactly what line of code generated an error.
  3. In some cases, re-running the stage is sufficient to get past errors. It is possible to use the -e option of the pipeline to run just a single or set of stages or -s to skip stages up to the problem stage. It is important to note that the pipeline checks for output files existing before running so to force a stage to re-run delete the associated output files of the target stage.

Home

Documentation

Quick Start

System Requirements

Input Data Preparation

Stages

Parameters

runPipeline Options

Example Dataset

Miscellaneous

  • Performance Profile
  • Example Batching
  • Summary Reporting (link to page) / Analysis (link to page) All of above would be bullet points but thought each folder with useful scripts in the repository would have its own page with example usages and descriptions for the files under the given directory. Unsure on this as haven't used anything under these directories directly myself (i.e not through runPipeline) apart from tests/perf-profile/summarize-stat-logs.sh. Should any of these have a separate page? Note have not made pages for this yet as not sure how many should be made or if this break down makes sense.
  • Troubleshooting

Clone this wiki locally