Chapter format

Each chapter must be written in textbook form and should function as a user guide and tutorial for a specific module. To this end, the chapter must motivate the module, why it is interesting, and what types of problems can it be applied for; teach the methods and/or models implemented; and go through a few selected examples that outline the main functionality. However, reproducible case studies using existing modules are also welcome. The style should follow the first book on Advanced Modelling with MRST with code excerpts intermingled with background theory and examples the readers can run themselves. All results must be reproducible, so that each chapter must be accompanied by a full set of code and data that will be made part of the official MRST releases and should be publicly accessible on Bitbucket (or GitHub). 

Author instructions

Instructions for preparing a manuscript for possible inclusion in this book are provided on a separate page. The book will be provided as a camera-ready manuscript to the publisher, which the editors will compile using LaTeX. All chapters should therefore be prepared in LaTeX using a basic style file provided by the editors. To ensure timely publication of the book, we kindly request your help by carefully reading the detailed instructions.

Preparing and releasing accompanying source code as an MRST module

Each chapter should be supported by full source code and necessary data made in the form of a complete add-on module to MRST.  The module should be made publicly available on Bitbucket and will be included in future releases of MRST. The module can only be based on functionality that is already available in a public version of MRST or functionality described by another chapter of this book. In the latter case, you also need to provide this code as part of your submission. During the peer review, our reviewers should be able to recreate the results of all examples discussed in your chapter as well as any other tutorial example in the module. They will also perform a review of how the module is organized and the extent and quality of its documentation. They will, however, not be asked to perform an extensive code review.  Further instructions on how to make the module available will be added later.

Requirements for MRST modules

A module in MRST is strictly speaking a collection of functions, object declarations, and example scripts located in a folder. Each module needs to have a unique name and reside in a different folder than other modules. Our only requirements are that the code is well tested and documented in a format that does not deviate too far from that used elsewhere in MRST, uses a clear naming convention that avoids potential clashes with other parts of MRST, and contains a few tutorial examples that outline the main functionality and explain the most common syntax. The code also needs to contain a clear specification of copyright and the license under which it can be used (the GNU General Public License). In addition, we also require that the core functionality of your code does not use functionality from MATLAB's many toolboxes, which potential users may not have access to.