Selecting the right hardware for Reverse Time Migration

Property compression

Usually we store our velocity, density, and anisotropic parameters as 4 byte floats. This is far more precision than is warranted by our knowledge of velocity, let alone our anisotropic density parameters. All of our property descriptors can be compressed, increasing the number of output points that can be computed per cache line read and the amount of space the storing property description takes up on the L1, L2, and L3 cache. For example, storing velocity as a short (2 bytes) rather than float would double the number of output points that could be calculated per cache line read.