USE OF MINDB PARAMETER TO CLEAR UP MIGRATION SWINGS
After the migration, each output trace has stored in it's header the distance to the nearest input trace that contributed to it. This is stored in the byte offset referred to by the mindb=parameter.

The two following stacks show the affect of using this parameter when you stack. In the first case, all the traces were included in the stack. In the second case, only those traces where the mindb was less than 400 feet were included in the stack. Traces were rejected when the nearest input trace contributing to that output trace were greater than 400 feet.

As this example shows, it clears up the migration swings. While these are most noticeable on the edges of the survey, they can occur in a more subtle way where there are holes in some of the acquired offset planes.