Frequently Asked Questions

Q: What is WiseCloud and WiseUser?

A: WiseCloud is a cloud platform, and WiseUser is its user tool. Now they are mainly for the service of FB picking.

Q: How does it work?

A: Firstly, with WiseUser in user computer, encrypt and transform the seismic data to the WDF file. Secondly, upload the WDF file to WiseCloud and complete picking on cloud. Finally, download the FB file created on cloud, calibrate and edit it locally. The technology of picking is the same as WiseBreak. Because of its improvement in technology the accuracy of picking is even better. Try it! The result will certainly give you a surprise.

Q: How to tackle the transmission of seismic data, which is generally of huge volume?

A: The size of WDF file, which is transformed from a SEGY file before being uploaded for picking, is only a twentieth of the raw SEGY file. The uploading can be resumed from the break point if necessary.

Q: Could I upload more than one file at the same time?

A: No, not now. Because of limited computation resources WiseCloud can only keep one WDF file(and its CFB file) on cloud for each user. If you upload a new WDF file, the old files will be squeezed out.

Q: Do I have to worry about the security of WDF file.

A: No, not necessary. Firstly, in the WDF file the length of trace is very short, which is normally not longer than 500 ms. Secondly, the sample interval is 8ms or 4ms, and the value is written in 1-byte/2-byte integer, which is of poor precision. Finally, the coordinates may have been encrypted.

Q: How long does it take to pick on cloud?

A: For a WDF file including 10 million traces, it takes about 5 minutes to pick on cloud. If the server is busy, the processing job may need to wait in the queue.

Q: What's your suggestions about the security of raw data?

A: Install WiseUser on a computer(first) which connects to the internet(WiseCloud) and on another computer(second) which is offline, or in your LAN. Transform SEGY to WDF on the second computer, and do cloud picking on the first one. Finally calibrate and edit the FB on the second computer. For more details, please read here.

Q: Is WiseUser multi-language?

A: Yes, but only in English and Chinese now. You can switch among different languages by the menu “Tools->Language”

Q: What is the requirement for the seismic(SEGY) data?

A: It must be in compliance with SEG-Y_r1.0. The format of sample data must be: (1) 4-byte IBM floating-point, (2) 4-byte IEEE floating-point, or (3) 2-byte, two's complement integer.

Q: I want to test with my own data, what are your suggestions?

A: It is very important to include fully geometry parameters in the trace header, except the coordinate scalar, all the parameters must be included. Further more, the data should include a number of shots, among which some have fairly high SNR for the sake of correctly modeling of near-surface. It is a good idea to limit the offset range(say, 0-3500m, if you want to get the FB of 0-3000m for static). It is strongly suggested that the data should not be processed, such as static correction, filtering, etc.

Q: What is the maximum size of WDF file allowed?

A: Now the maximum size allowed to be uploaded is 10 GB. If your segy file is very large(say, 100 GB or larger) and the transformed WDF may be larger than 10 GB, it is wise to divide it into 2-3 offset segments, for instance, transforming the offset range 0-2000 to the first WDF, and 2000-4000 to the 2nd WDF.

Q: Should I use the sample interval of 4ms, or 8ms while transforming?

A: For the seismic data with a main frequency between 20-50Hz, "8ms-1byte", which we suggest, is good enough. If the data is for high resolution survey, or its SNR is very low, you can choose "4ms-1byte".

Q: What should I pay attention to for the picking of vibrosis data?

A: The vibrosis data is normally with low SNR. A dataset should include some shots with fairly high SNR. In first arrivals of vibrosis data, more often than not, the event of negative polarity has a better coherence, it is a good practice to compare the pickings with different polarities(positive and negative). Moreover, it is not suggested that the data be filtered for denoise or minimizing phase.

Q: Can I edit the FB with WiseUser?

A: Yes! from the version 1.1 and on. The user can edit the FB.

Q: What is the difference between the "red" FB and the "purple"?

A: Statistically, the purple FB is more likely correct than the red one. After auto-picking WiseCloud distinguishs by means of modeling near-surface the error FB from the correct. For the first type WiseCloud will automatically modify them guided by the model and label them in red. For the second type WiseCloud will label them in purple.

Q: Must I edit the "red" FB?

A: Not necessarily so. The red FB is very likely correct after modifying by WiseCloud. The purple one is not totally correct because of the model precision and may need to be modified manually.

Q: What are the suggestions about FB editing for different situations?

A: For urgent situations, such as on-site processing, or, in a survey with simple near-surface structure, we suggest that the user edit FB with the "Error_FB_Only" mode. In this mode the purple FB is hidden(by checking "Display Err. FB Only"), so the processor can efficiently edit the red FB. In processing practice, more often than not, this mode is used because of the huge workload. On the contrary, for the fine proceessing, or, in a survey with complicated near-surface structure, it is reasonable to check every FB with the "All-FB" mode and make necessary modifications. In the matter of fact, the processor can switch between the two modes at any time while editing.

Q: How to output the FB data?

A: As in WiseBreak, you can export the FB to a textual file, Or write them to the SEGY trace header. In order to speed up the header writting, it is necessary to shorten the SEGY trace into a shorter length with only one or several samples.

Q: What is the difference in dealing with 2D and 3D?

A: The processing flow is almost the same except for setting "0" to "s-line" and "g-line" while defining trace header.