Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
IFOS3D
IFOS3D
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 7
    • Issues 7
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • GPIAG-Software
  • IFOS3DIFOS3D
  • Issues
  • #6

Closed
Open
Opened Apr 13, 2016 by Tilman Steinweg@tmetzOwner

seismogramm output

  • The Seismogramm header has to be optimized in the su case,
  • segy outputs needs more testing, maybe reduce su (liitle endian), binary and ascii output would be a good idea, only ascii and su input is implemented jet anyway.
  • overwriting existing su files doesn't work right it all cases
  • merging the seismogram in the code would give a speedup (less data in/output) / or reactivate seismerge program to handle this issue after the inversion.
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
code maintenance
Milestone
code maintenance
Assign milestone
Time tracking
None
Due date
None
Reference: GPIAG-Software/IFOS3D#6