Program: MKLSGRIDEVALATTRI
mklsgridevalattri........evaluate arrival times of nodes in tri grids
call: [newgrid,newttsupport]=mklsgridevalattri(lsopt,mygrid,simpledata,evalthese,ttsupport);
lsopt: (structure)
LSOPT structure as returned by MKLSOPT
mygrid: (structure)
grid structure as returned by MKLSGRIDNEW
fxd: (strcuture)
FXD structure as returned by MKLSLS2FXD, containing all
data.
evalthese: (structure)
structure denoting grid nodes to be evaluated, as returned
by MKLSGRIDNONREADY.
The following fields are expected:
.layer: (numeric)
layer ID, only one per element of EVALTHESE
.nodes: (numeric array)
list of nodes. This is a sublist of the
nodes list in the mygrid.layer field,
contining node IDs and coordinates formatted
as in the layer structure.
.listpos: (numeric array)
list of positions of the nodes in the
original .nodes field of the input layer.
evalthese.listpos(i) is the array indes of
the node evalthese.nodes(i,:) wihtin the
original layer structure.
ttsupport: (structure)
TTSUPPORT structure. This structure might be as returned
by MKLSEMPTYTTSUPPORT, i.e. unspecific, or with fields
that are specific for the used travel time software.
result: newgrid: (structure)
as MYGRID, but with the tested-counters and fit-field actualized.
newttsupport: (structure)
as TTSUPPORT, but with actualized contents.
This routine computes the arrival times of nodes listed in EVALTHESE and
finds out which nodes fit into the desired arrival time ranges of all stations.
the .fit and .tested fields of the grid structure are updated
accordingly.
Searching for compatibility with arrival times is more complicated than
searching for back azimuth compatibility: not only the 3D spatial
coordinates have to be considered, but also the origin time coordinate.
Travel Times have to be computed and then possible origin times have to
be found.
Fortunately, the modification of the origin time can be done very
quickly, so that the search for the origin time can be done at very low
computational cost: compute travel times and just add the trial origin
time.
Travel time computation itself is done by some external software.
LOCSMITH does not contain any Travel time computation routines, but only
a generic interface. Many of the work to be done here is in that
interface routine.
Martin Knapmeyer, 31.03.2005, 17.05.2005, 05.07.2005, 20.03.2007,
22.03.2007, 02.04.2008
Read M-File Source Code
eof.