=0A=0AA capability that I still have to add to rsfbak is reading from pa= That would allow tests to =ĭistinguish which library is being used to know if arrays can be used or no= , which is set to True during the instantiation. The only =ĭifference between them is that rsfbak has an extra attribute self.noArrays= Supposed to either emulate rsf 100%, or not have that capability. T the proper library is supposed to return in that case - an array? If so,= par.ints, par.floats and par.bools), but I am not sure wha= It would be nice to have access to arrays of=Īrguments (i.e. R.int('b')=0Ac =3D par.float('c')=0Ad =3D par.bool('d')=0A=0AThat should be=Įnough for most metaprograms. Sfbak as rsf=0A=0AThen one can use the most important functions for command= Parameters only, i.e.:=0A=0Atry:=0A import rsf=0Aexcept:=0A import r= O create an "emergency backup" rsf module that gives access to command line= G string utilities in Python is easier than in C, so it was not much work t= SWIG to use the command-line parsing functions in librsf.a. They do not read the binaries, just parse ar=
S in vplot2gif.=0A=0AThe key to solving this conundrum is to notice that me= On API, one had to implement a small makeshift argument parser each time, a= The Python API cannot be counted on being present. Swig + numpy/numarray cannot be counted on being present, so= Le towards using metaprograms was the lack of a sane way to parse command l= Wn in a script and called sfprep4plot or something.=0A=0AThe biggest obstac= Like sthe sfremap1/sftransp sequence above, which begs to be thro= Ne parameters, compute the calling arguments to compiled executables, and c=Īll them. S=3Dy | xtpen=0A=0A=0AI love small "metaprograms" that read some command li= Ld not find any options or programs to do that within SEP/RSF.=0A=0AOn 1/27= Of oversampling by interpolation when using screen output. The following projects have seen very little activity for more than a year.On 1/26/07, Joachim Mispel wrote to rsf-users:=0A> SU seems to do some kind= Haishan Zheng, University of Saskatchewanĭisplay, analyse and edit SEG-Y header information Marcel.lí Farran, Institut de Ciències del Mar Muhammed Celik, Ruhr University Bochum, Kocaeli University Peggy Li & Herb Siegel, Jet Propulsion Laboratory Greg Lyzenga & Jay Parker, Jet Propulsion Laboratory in a commercial context.) They are included here because they may be of interest for those in an academic environment or access to tools like MATLAB.
#Segy detective license
(For example, the license may rule out use by certain people or for certain purposes, e.g.
#Segy detective software
The following projects have unknown licensing, licenses which place some restriction on use or redistribution, or depend on non-open-source software like MATLAB, and therefore do not meet the Open Source Definition from the Open Source Initiative. Geophysical interpretation and visualization Interfaces with Madagascar, GMT, Google Earth/Maps Geoscience interpretation and visualization Geoscience Data management and visualization platform Visualization, interpretation & analysis packages Name Includes geopsy (signal processing) & dinver (inversion) Joseph Fourier University, University of Potsdam Passive acoustic monitoring for marine mammals Non-reflection-seismic processing utilities Name Seismic reflection and refraction processing Kurt Schwehr, University of New Hampshireįelix Herrmann, Univ. Reflection seismic processing utilities Name World's most widely used (69 countries and territories). Generic format (SEGY, SU, SEPlib, USP, Madagascar) Programming Interfaces to C++, Fortran 77, Fortran 90, Python, Java, MATLAB. Multidimensional data analysis including seismic processing Reflection seismic processing packages Name
#Segy detective free
5 Not true free and open source projects.4 Visualization, interpretation & analysis packages.3 Non-reflection-seismic processing utilities.2 Reflection seismic processing utilities.1 Reflection seismic processing packages.
0 kommentar(er)
