Report outline

This page is meant as a kind of top-down report specification/disposition. It should list each of the parts/chapters/sections to be present in the report, and how they should support or illuminate the argument of the report. From this document you should be able to get an overview of the report structure.

Preface

• [Status: Done] What does the report contain
• Who have contributed

Introduction

• [Status: Done] Argue that this is a relevant field of study
• Explain our project on a high level
• Argue that this is a relevant project
• Explain our approach
• Summarise our contributions

Cases

• [Status: Done] Introduce option pricing
• Argue that optimizing the way option pricing is performed is a relevant problem for our society
• [Martin] Introduce binomial option pricing
• Argue that binomial option pricing is a practically relevant case
• [Martin] Introduce Sobol sequence generation
• Argue that Sobol sequence generation is a practically relevant case
• (Longstaff & Schwartz)
• (LexiFi example)

Survey

Survey setup

• Argue for the selection of Nikola, Accelerate, Repa
• Argue for the deselection of Obsidian, Feldspar, etc.
• Argue for our chosen parameters of comparison

Evaluation of project health

• ??

Evaluation of performance

• ??

Evaluation of expressivity

• [Martin] Argue that existing Nikola & Accelerate are hampered by lack of nesting. Display it using our cases that how the programmer must work around the restriction (eg. by rewriting nested maps to use replicate and multidimensional maps in accelerate).

• [Martin] Argue for our choice of Nikola as our subject for further extensions. (eg. by deeming the Acc/Exp structure of accelerate too limiting.)

'Our developments/extensions': sequential in Nikola

• Introduction & Motivation.

  Here we should describe the sequential operator, and how it changes the execution model, and how it alleviates the problem of nested operations.