1 / 25

CWP/SU:Seismic Un*x Past, Present, and Future

CWP/SU:Seismic Un*x Past, Present, and Future. EAGE Workshop: Open Source Software in E & P Vienna, 11 June 2006. J ohn Stockwell, Research Associate Center for Wave Phenomena Colorado School of Mines Golden Colorado USA. http://www.cwp.mines.edu/cwpcodes. Acknowledgment of Support.

jud
Download Presentation

CWP/SU:Seismic Un*x Past, Present, and Future

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CWP/SU:Seismic Un*x Past, Present, and Future EAGE Workshop: Open Source Software in E & P Vienna, 11 June 2006 John Stockwell, Research Associate Center for Wave Phenomena Colorado School of Mines Golden Colorado USA http://www.cwp.mines.edu/cwpcodes

  2. Acknowledgment of Support • CWP Consortium Project on Inverse Problems in Complex Structures • Society of Exploration Geophysicists Foundation • Gas Research Institute

  3. Topics • What SU is and is not • History of SU • Current issues • Future plans

  4. Issues • role of SU in geophysics • structure of the code • human factor • ``rules'' of open source

  5. What Seismic Unix is • open source • education and research • CWP's home environment • instant and personal environment

  6. What Seismic Unix is not • not GUI driven • not a lot of 3D • neither perfect nor complete • not a substitute for commercial software • ...but fills a role that commercial software cannot fill

  7. Who uses SU? • academics • government researchers • small independent contractors • researchers in larger companies

  8. Uses of SU • seismic trace manipulation • data processing/modeling • prototyping/software development • quick look at data • non-seismic (i.e. GPR radar)

  9. Usage Statistics • approx. 3300+ install messages • 2 install messages every 3 days • 3-10 downloads per day • 524 active listserver members • 68 country codes

  10. What makes SU SU? • written in C • getpars • selfdocs • readable source code • SEG Y data structure • Unix or Unix-like platform

  11. The SEG Y data format • 3200 byte EBCDIC reel indentifier • 400 byte binary reel header • 240 byte binary trace header • data in 32 bit IBM tape format • Repeat trace header and data

  12. The SU data format • 240 byte binary trace header • data native binary floats • Repeat trace header and data

  13. SY and the origins of SU • SY 1979-1984 Einar Kjartansson (at Stanford) • SY 1984-1986 Shuki Ronen • SU 1986 Jack K. Cohen (at CSM) • SU 1987 Jack takes SU to Texaco

  14. SU expands • 1989-1993 Jack Cohen and Dave Hale • 1989-1996 Jack Cohen and John Stockwell • 1992 first Internet release of SU • 1996-present

  15. Some ``rules'' of open source • stress portability and readability • port to many platforms • enlist the aid of the users • take users needs under consideration • know who your users are and how they use your code

  16. Benefits of open source • clean house • new colleagues and partners • bug fixes and extensions • new codes • worldwide presence

  17. Challenges • ``no charge''=``no value'' • pressure from users • grandiose suggestions • project expansion • some contributed code not open source

  18. Remedies • ``open source''=``instant standard'' • separate need from want • ask for an example • keep your project in its scope • require references for contributed code

  19. More ``rules'' • minimize dependency on 3rd party items • avoid relying on ``special features'' • give credit to contributors • demos should accompany code submissions • stress stability and longevity over novelty

  20. Current and Future issues • SEG Y Rev 1 support • 3C • 3D • cluster • update license?

  21. The SEG Y Rev 0 data format • 3200 byte EBCDIC reel indentifier • 400 byte binary reel header • 240 byte binary trace header • data in 32 bit IBM tape format • ...Repeat trace header and data

  22. Proposed solution, SU Rev 1 • 512 byte binary header • data in big-endian 32 bit • ...backward compatability to SU Rev 0 • ...with MPI 3D, 3C, and cluster follow directly

  23. Concluding remarks • SU is here to stay • Your help and feedback are welcome • Thank you!

  24. Jack K. Cohen, 1939-1996

More Related