What are WiseBreak's remarkable features?

The error FB auto-picked is fitted and screened out which in turn is edited exculsively. The processor can skip the correct FBs and focuses on the erroneous ones while editing. This increases the productivity of FB picking dramatically.

What platforms does WiseBreak run on？

64-bit Linux and Windows 7/8/10.

Does the licenses of WiseBreak can be shared on the LAN network?

Yes, the license for any module can be shared on the LAN. The dongle can be attached to a server running any OS, such as Windows, Linux, Solaris, Aix, and etc.

Are there any differences in the productivity for different near-surface conditions?

Yes, the productivity can be increased by several to dozens of times which depends on near-surface condition and seismic data.

Can WiseBreak deal with vibroseis data?

Yes, WiseBreak performs better for vibroseis data than other tools. It is not easy to identify the first arrival because of longer wavelet in vibroseis data. Having model FB time as guidance the processor can probably avoid picking different events in adjacent shots.

How about WiseBreak's auto-picking?

WiseBreak auto-picks the FB by some extraordinary algorithms developed independently. The picking is almost free of prosessor intervention. It is excellant to pick low-SNR data.

How to cope with complicated near-surface data?

For the area where the near-surface condition is very complicated, such as in the outcrop of hard rock, the weathering model may be inverted poorly and the model FB may not be valid. So the processor has to edit in the "All-FB" mode, sometimes with no correction. After working into the simple area, the editing can be switched to the "error-FB-only" mode, which is more efficient.

What format of seimic data does WiseBreak need?

WiseBreak can only use the SEGY data as input, which is in compliance with SEG rev 1. The sample format must be one of the follows: IBM 32bit floating（dsf=1）, IEEE 32bit floating（dsf=5）,or 16 bit integer（dsf=3）.

Does WiseBreak need the geometry data?

Yes, WiseBreak need to acquire geometry data from the trace header. We assume that the user has written the geometry data into trace headers by other tools before picking FB.

How to output the FB for static computation?

WiseBreak exports the FB to a text file in linux/windows format, Or writes them to the SEGY trace header.

Is there any difference between 2D and 3D?

There is no difference for picking 2D and 3D data. What you need to do is to set "0" as the position of "Sou_line" and the "Grp_line" when defining 2D trace header.