MULTIFAN-CL (MFCL) is a fisheries stock assessment model written by Dave Fournier of Otter Research, Canada.

R4MFCL uses the statistical software R to read, manipulate, write, analyze, and plot the MFCL input and output files. One of our goals is to automate the running of stock assessments using MFCL. Additional developments are planned, and we encourage you to contribute. For example, in future we hope to facilitate translation of input and output data objects between MFCL and Stock Synthesis formats.

R4MFCL was developed by the Secretariat of the Pacific Community (SPC). The project was led by Simon Hoyle, and also includes code by Shelton Harley, Nick Davies, and Adam Langley of the SPC, and Pierre Kleiber of the US National Marine Fisheries Service.

See also the 'r4ss' code repository which inspired this site.

Important links

Anyone unfamiliar with R can learn more here: http://www.r-project.org Limited documentation of the R code available here will be added to the Documentation page in the Wiki section of this site. To get the R code, click on the Downloads tab above.

Making contributions

This Google Code website has many features that could be useful for sharing the development and refinement of R code associated with MFCL. Google Code websites require registration to make comments or add issues. To register, provide an email address and create password at http://www.google.com/accounts/NewAccount. If you would also like to edit the documentation in the wiki or post files for download, please register first and then email Simon Hoyle to be added as a project member.

Keeping up to date

An email list / message board has been created to keep people updated on changes to this site or the code. To join the email list, follow the link to the right.

Disclaimer

Code available on this website comes with no warranty or guarantee of accuracy - in fact errors are to be expected. It merely represents an ongoing attempt to provide useful tools for data preparation, plotting, analysis, and diagnostics. The user should check results for errors and the code for bugs.