Reporting Bugs and Other Issues
Jon Long edited this page Jun 30, 2015
·
1 revision
Pages 35
- Home
- AWS EC2 GPU enabled Caffe AMI
- Borrowing Weights from a Pretrained Network
- Caffe installing script for ubuntu 16.04 support Cuda 8
- Caffe on EC2 Ubuntu 14.04 Cuda 7
- Caffe Output: .caffemodel .solverstate
- Contributing
- Development
- Excluding Layers: Train and Test Phase
- Faster Caffe Training
- Fine Tuning or Training Certain Layers Exclusively
- GeForce GTX 1080, CUDA 8.0, Ubuntu 16.04, Caffe
- IDE Nvidia’s Eclipse Nsight
- Image Format: BGR not RGB
- Install Caffe on EC2 from scratch (Ubuntu, CUDA 7, cuDNN 3)
- Installation
- Installation (OSX)
- Making Prototxt Nets with Python
- Model Zo
- Model Zoo
- Models accuracy on ImageNet 2012 val
- OpenCV 3.2 Installation Guide on Ubuntu 16.04
- Python Layer Unit Tests
- Related Projects
- Reporting Bugs and Other Issues
- Simple Example: Sin Layer
- Solver Prototxt
- The Data Layer
- The Datum Object
- Training and Resuming
- Ubuntu 14.04 ec2 instance
- Ubuntu 14.04 VirtualBox VM
- Ubuntu 16.04 or 15.10 Installation Guide
- Using a Trained Network: Deploy
- Working with Blobs
- Show 20 more pages…
Clone this wiki locally
Bug reports and other issues are managed by the GitHub issue tracker. All are welcome to create issues on the tracker, but please search first to make sure the problem has not already been reported.
All discussion and inquiries aside from specific bugs and issues should be kept off the tracker; use the caffe-users list instead, so that developers can maintain a clear and uncluttered view of bugs and issues.
When reporting a bug, it's most helpful to provide the following information, where applicable:
- What steps reproduce the bug?
- Can you reproduce the bug using the latest master, compiled with the
DEBUGmake option? - What hardware and operating system/distribution are you running?
- If the bug is a crash, provide the backtrace (usually printed by Caffe; always obtainable with
gdb).