Re: x2sys tools: time gap does not work

Hi Yan Lei-

WOuld you be able to put together a very small subset (say two track segments) that shows the problem so that I may debug the code. If you are right then you would just need to send me two small files with data for two tracks that intersect but has times such that they should be skipped via -W.

-p

On Nov 12, 2013, at 5:50 PM, 杨磊 <[email protected]> wrote:

> hello GMT,
> 
> First  thanks Paul for giving the excellent x2sys tools. 
> The problem I meet is the time gap unworkable.
> I set the  maximum time gap to 864000 seconds (10 days) by
>  x2sys_init CROSSHY2 -Dxys -Exys  -Cg  -Gd -Ndk -Wd8 -Wt864000 -F
> 
> But the output is the same with the one without setting a time gap.
> It still contains times longer than 10 days, such as 
> '2013-08-31T03:03:35	2013-08-07T17:22:53' which are t_1 and t_2 fields in out file.
> 
> That means that the -Wt864000 dose not work. right ?
> 
> In addition, there is a little bug of x2sys_cross when out put the headers to outfile, which is the  'Command' line is wrote twice. 
> Here is headers in my out put:
> # Command : x2sys_cross -TCROSSHY2 srl_sla.xys -Qi -W10 -Ia -Rd -V2
> # Tag: CROSSHY2
> # Command: x2sys_cross -TCROSSHY2 srl.xys -Qi -W10 -Ia -Rd -V2 
> # lon	lat	t_1	t_2	dist_1	dist_2	head_1	head_2	vel_1	vel_2	ssh_X	ssh_M	sla_X	sla_M
> 
> thanks very much 
> 
> Yang Lei
> 
> 
> To unsubscribe, send the message "signoff gmt-help" to [email protected]


To unsubscribe, send the message "signoff gmt-help" to [email protected]