Frequently Asked Questions
- Why this project name ?
- What is this logo ?
- What is the project's maturity ?
- What about performance ?
- Why can the input files be gzipped (*.gz) but not zipped (*.zip) ?
- Some samples exhibit strange behavior. What is happening ?
- Where is the ccruncher-inf documentation ?
CCruncher software uses a numerically intensive procedure to quantify the portfolio credit risk. These kinds of programs are called 'number crunchers'. The mix between the terms 'credit' and 'number cruncher' generates the name 'credit cruncher'.
CCruncher's logo is based on a sculpture by Robert Llimós, a catalan artist. The original work is named Threshold and is located in Atlanta. It has a twin version named Marc that is located in Barcelona.
ccruncher-2.6.0 is a stable version. If you have any bug or suggestion to report, please send an email to CCruncher team.
CCruncher is designed to be extremely fast. When there are 10 obligors, it computes 1000000 simulations in few seconds. When obligors are 50000 it takes few minutes to do the same task. CCruncher execution time depends on multiple factors: machine (processor, L1/L2 caches, cores, etc.), number of simulations, number of obligors, number of ratings, number of factors, number of segmentations, and number of assets.
The zip algorithm is covered by patents, but gzip is not; furthermore gzip is open source. You can download a gzip tool for windows from 7-zip. UNIX environments have the gzip/gunzip commands out of the box. You can read more at the gzip website.
1) Standard Error of VaR increase when the number of simulations increases:
We use the Maritz-Jarrett method to obtain these values. To reduce the
computational cost we truncate the involved sum. In some cases, this action
causes the observed behavior.
2) VaR plot has jumps: This happens because the resulting portfolio loss
distribution is discrete with a support composed of few values.
CCruncher-inf is a modeling tool for advanced users (they must have
knowledge of statistics and programming). Fundamentals are in the technical
documentation. Input file format is commented in file
samples/inference01.cfg
.
Don't hesitate to read the code (Metropolis.cpp), it is short and simple.