2009/7/24 Søren Hauberg <[email protected]>: > Hi > > tor, 23 07 2009 kl. 23:57 -0300, skrev Esteban Cervetto: >> I am sending the code. I copy to the community as you tell me above. >> It includes a narrative help in the m files. > > In general this looks very good. I don't have knowledge in this area, so > I can't say anything about the algorithms, but I have a few comments > about the code: > > * You should write comments in English instead of Spanish. > > * In the 'bfanalisis' help text you seem to create tables in plain > text. Can you use '@table' or '@multitable'? This looks better > when we generate web pages. > > * In 'ultimatead.m' the help text says the function is called > 'quotaad'. > > Just out of curiosity: what does 'ultimate' mean in the 'actuarial' > context?
Ultimate means the final value of a loss. For Example, An insured suffers an injury in your leg at working time. The insurer needs deploy the loss in your balance sheet, so He makes a "LOSS RESERVE" (saves money for the future payments). Along the time was passing, the insurer pays the medical expenses to cure the insured, and the reserve will began to decrease. At this moment the insurer holds an INCURRED COST = sum payments + the reserves left. When the insured has definitely restored his health, the insurer knows the final value of the loss. THIS IS THE ULTIMATE VALUE However, the current portfolio of claims have the majorty of your claims parcially developed. They need time to finish. The insurer needs the ultimate value because it is the basic cost of the insurance. In the source code, I pass my time working with triangular matrixs. Each row represents the time at accident, and the columns, the time from the accident date. More columns to the right, more ancient is the claim and more developed is the claim (or, more nearer the ULTIMATE VALUE is). The great diagonal represent the current values; it is my current portfolio of claims. The most recent the accident is, less infomation I have from the claim, but I have fresh information about many variables. In the other hand, a more older claim has got many years observed, but It may be so older to believe It would be repeat in the same way in the future (obsolete). THIS IS THE MAIN REASON TO ESTIMATE THE VALUES with this code: try to COMPLETE the below's TRIANGLE and estimate the real final cost incurred at the moment. > >> I make a directory in my documents /octave-forge/main, put the >> actuarial directory in it, and next do the commands >> >> $ cd octave-forge/main >> $ svn add actuarial >> >> then the console says >> >> svn: '/home/esteban' no es una copia de trabajo >> svn: No se pudo abrir el archivo '/home/esteban/.svn/entries': No >> existe el fichero ó directorio >> >> english traduction: >> svn: '/home/esteban' is not a work copy >> svn: cant open '/home/esteban/.svn/entries': this directory/file >> doesn't exist > > You need to checkout Octave-Forge from svn, and then add the files. See, > http://octave.sourceforge.net/developers.html > > Søren > > I spend 1 hour installing $ svn co https://octave.svn.sourceforge.net/svnroot/octave octave but it continues! It was correct install the whole project in my computer? I only want develop actuarial and statistical packages, nomore for the moment. ------------------------------------------------------------------------------ _______________________________________________ Octave-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/octave-dev
