S2 peak timing shifted?

[FaroutYLq]

Describe the bug
Seems the peak timing of S2s have been shifted about O(1ms).

To Reproduce
Insert the MWE of how to reproduce the error

st_simu = saltax.contexts.sxenonnt(runid=33048,
             saltax_mode='simu',
             output_folder='/project/lgrandi/yuanlq/salt',
             faxconf_version="sr0_v4",
             generator_name='flat',
             recoil=7,
             mode='all')
events_simu = st_simu.get_array('033048', 'event_info')
truth = st_simu.get_array('033048', 'truth')
match = st_simu.get_array('033048', "match_acceptance_extended")

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Versions
Please add the output of:

straxen.print_versions()
	module	version	path	git
0	python	3.9.18	/project/lgrandi/xenonnt/env_tests/development...	None
1	strax	1.5.4	/project/lgrandi/xenonnt/env_tests/development...	None
2	straxen	2.1.5	/project/lgrandi/xenonnt/env_tests/development...	None
3	cutax	1.15.5	/dali/lgrandi/xenonnt/software/cutax/v1.15.5/c...	None

All italic comments can be removed from this template.

[FaroutYLq]

Should be related to #68

[FaroutYLq]

No it turns out to be a matching criteria bug. Once switched to touching_windows for matching it never shows up anymore.