Things to do

• Prettify the plots
• Reconcile the scripts, e.g. prob don't need one_spike and theta_one_spike.
• Some refactoring so we can stay on top of the architecture
• Then make fuzzyAVO as awesome as possible (add crossplot, gathers, distributions, etc)
• Scripts need to be even simpler I think.
• Separate 'plot' parameters from 'model' parameters in script help
• Fully separate model from reflectivities and reflectivities from imaging
• Model builder for creating new geometries easily — started
  • Script to get SVGs or PNGs via URL
  • Try to get cairosvg working
• Crack into the enhancement wishlist
• Output:
  • Chart of amplitudes
  • Get model view back
  • Get metadata, e.g. elastic moduli, critical angle
  • Plot critical angle
• Abstract 'parameters' so the basic ones are easier to add (they're almost always the same)
  • E.g. standard inputs: colormap, wavelet, reflectivity_method, etc.

Front end

• Email log in with confirmation
• Authentication for a particular domain
• Billing
• Pretty front page
• Basic Getting started page
• Video

And the sciencey stuff...

• Save rocks
• Save wavelets
• Run all the basic scripts, providing the parameters
• Save a scenario
• Write and upload a script
• Prettify... here are some Bootstrap resources:
  • Bootstrap customizer
  • Jetstrap
  • Bootsnip
  • Lavish Bootstrap — use a colour scheme from an image
  • Style

Done recently

• Non-Zoeppritz reflectivity algorithms are not working
• signals with respect to rample interval (i.e. 1 ms, or 2 ms, or 4 ms), not number of samples or sample rate.
• to choose other wavelets than Ricker. Want to give f = 25 for Ricker and f = 6,12,80,100 for Ormsby. Should 'just work'. Make sure we have length right - I only really care about length in time, not samples
• Make and run units tests for reflectivity algorithms
• Ensure our tests are correct and that they work
• a wiggle trace
• Do a wiggle trace with variable density fill