model validation
- Thread starter Lun
- Start date
- Joined
- 6/10/09
- Messages
- 27
- Points
- 18
we just trade them on small test accounts.
- Joined
- 1/27/10
- Messages
- 1,038
- Points
- 173
Then two key documents are OCC 2000-16 and OCC 2011-12. Both are readily available on the web. You should also review papers by Rebonato and by Derman.
OMG.....
Are we in two different worlds ?
I always find job ad recruiting Quants for model validation, is it fake job ad ?
I just quote some, it should not be difficult to find
http://jobs.efinancialcareers.hk/job-4000000000809824.htm
http://jobs.efinancialcareers.hk/job-4000000000812993.htm
http://jobs.efinancialcareers.hk/job-4000000000812859.htm
http://jobs.efinancialcareers.hk/job-4000000000813050.htm
Are we in two different worlds ?
I always find job ad recruiting Quants for model validation, is it fake job ad ?
I just quote some, it should not be difficult to find
http://jobs.efinancialcareers.hk/job-4000000000809824.htm
http://jobs.efinancialcareers.hk/job-4000000000812993.htm
http://jobs.efinancialcareers.hk/job-4000000000812859.htm
http://jobs.efinancialcareers.hk/job-4000000000813050.htm
- Joined
- 3/8/11
- Messages
- 24
- Points
- 11
Lun, it may be obvious but let me re-emphasize this. Every model is incorrect in reality but accurate if and only if the assumptions are realized and become true. Moreover, you can test the validity of the model's robustness by using a monte carlo simulation. I hope this helps.
I understand your points. My point is that it is very common for us to have human errors when (1) we develop a model, and (2) write a program, how can we figure these mistakes out by "testing"
I mean, it's impossible to always expect that we don't make mistakes. The fact is we always make mistake, and we need to figure it out. If there's no mistake, Microsoft need not service packs.
I mean, it's impossible to always expect that we don't make mistakes. The fact is we always make mistake, and we need to figure it out. If there's no mistake, Microsoft need not service packs.
- Joined
- 1/27/10
- Messages
- 1,038
- Points
- 173
- Joined
- 1/27/10
- Messages
- 1,038
- Points
- 173
I made all my students read this. If you're interviewing for model review at a bank, you'd better be familiar with it.
Ken,
Model validation is a kind of scientific study (we call it "risk management") of models. Can we say in this way ?
And it is usually done by other parties such that everything is independent from the party for development & implementation. However, can 2 independent parties think in the same way and get the same result ? For example, with the same goal, different banks can develop different models to achieve the same goal, does it contradict ?
From the doc, I find
"Developers should be able to demonstrate that such data and information are suitable for the model and that they are consistent with the theory behind the approach and with the chosen methodology."
It is a little bit open for discussion. I mean, there should be more than one exact way to achieve what is defined, right ?
My feeling is that the doc is still abstract, it is an overview instead of sth very strict defined. I know that space should be left, but I want to know the details (or an example) of how things (validation) are done. Say, what are the exact steps you will do to fullfill the regulation ? I know nothing, that's why I look for examples (or step by step)
Am I thinking on the right track ? Thanks ....
Model validation is a kind of scientific study (we call it "risk management") of models. Can we say in this way ?
And it is usually done by other parties such that everything is independent from the party for development & implementation. However, can 2 independent parties think in the same way and get the same result ? For example, with the same goal, different banks can develop different models to achieve the same goal, does it contradict ?
From the doc, I find
"Developers should be able to demonstrate that such data and information are suitable for the model and that they are consistent with the theory behind the approach and with the chosen methodology."
It is a little bit open for discussion. I mean, there should be more than one exact way to achieve what is defined, right ?
My feeling is that the doc is still abstract, it is an overview instead of sth very strict defined. I know that space should be left, but I want to know the details (or an example) of how things (validation) are done. Say, what are the exact steps you will do to fullfill the regulation ? I know nothing, that's why I look for examples (or step by step)
Am I thinking on the right track ? Thanks ....
put it simpler, I want the program to calculate the sum of Fibonacci numbers
1 + 1 + 2 + 3 + 5 + 8 + 13 + 21 + .... (for 50 terms)
without knowing the answer first, how can I know that the value returned by my program is correct (bug free) ?
well, one may suggest to compare with market data, but the point is that I haven't made sure my progam is bug-free, can values returned by program be trusted and compared with the market data ?
If we do compare with the market data, where is the source of error when we find differences ? problem of the program ? problem of the model ? I mean, how can we track down the source of error ? or how do we make sure that we have no human error ?
Is there anything we can reference before comparing with the market data ?
1 + 1 + 2 + 3 + 5 + 8 + 13 + 21 + .... (for 50 terms)
without knowing the answer first, how can I know that the value returned by my program is correct (bug free) ?
well, one may suggest to compare with market data, but the point is that I haven't made sure my progam is bug-free, can values returned by program be trusted and compared with the market data ?
If we do compare with the market data, where is the source of error when we find differences ? problem of the program ? problem of the model ? I mean, how can we track down the source of error ? or how do we make sure that we have no human error ?
Is there anything we can reference before comparing with the market data ?
