IESX DK FAQ

Questions

1. When do you use IESX DK and when must you use GFDK ADI?
2. Where are the IESX DK files stored?
3. What to do if prototypes in documentation do not match that in htp_api.def ?
4. What .def files should I include in my code?
5. What errors trap? What does an 80xxxx error signify? What is error code 1?
6. How do I launch my IESX DK applications?
7. How do I decode the cryptic error messages?
8. How to get the survey geometry?
9. How to get 2D navigation data ?
10. How to find out if a 3D survey is orthogonal ?
11. How to get a trace location in latitude/longitude and in x/y ?
12. How to get a list of color maps ?
13. How to list seismic surveys?
14. How to list seismic classes?
15. What operations are available for paths?
16. What paths are supported in IESX DK ?
17. What operations are available to access horizon information such as age, color, snap window, etc?
18. What operations are available to access fault information such as color, width, style?
19. What operations are available for contacts?
20. What operations are available for fault cuts?
21. What operations are available to read/write horizon attribute data?
22. What operations are available for domain manipulation?
23. What operations are available for well data?
24. What operations are available for check shot data?
25. What operations are available for deviation survey data ?
26. What operations are available for marker data?
27. What operations are available for log data?
28. What operations are available for seismic data?
29. What operations are available for interpretation model access?
30. What operations are available for patches?
31. Why does size of give different results in 32-bit and 64-bit Linux?
32. On GF4.3 and GF4.4, I’m trying to create a 2D line using htp_create_2d_line and I see duplicate lines created, is there a workaround for this?

Answers

1. You must use IESX DK to access IESX seismic volumes. You may use IESX DK or GFDK ADI to access interpretation data. Accessing interpretation data is easier using IESX DK, especially, if you are porting your DK codes from GF 3.x.
   
   
2. IESX DK library, includes and example program files are located under $GF_PATH/ies_htp.
   
   
3. htp_api.def takes precedence over documentation writeup.
   
   
4. Do not include htp.def in your source since your DK source knows about htp.def already via batch_thtp. Only htp.mes is needed to be opened in your source program. You can read the information into memory or keep htp.mes open for your search and match.
   
   
5. There are errors that some older interfaces do not trap. IESX DK errors start with 80xxxx. Error 1-14 and 20-24 are generated due to system error with socket or shared memory. Take a look in htp_comm.def for socket and shared memory errors (1-14, 20-24). For these errors, there are no corresponding messages in the htp.mes file. As you can see from the error symbol (E_SEND_DATA) mnemonics, the message is self-explanatory.
   
   
6. There are 4 IESX DK servers where you can launch your IESX DK applications: batch_thtp, thtp, IESX/Session Manager and IESX/User Applications.
   
   
7. For errors found in htp.def/htp.mes, one could do the following: Say you get an error code (). This error number corresponds to the symbolic HTP_E_INVALID_XO_NAME. You now find the message of HTP_E_INVALID_XO_NAME in htp.mes. The corresponding message is always enclosed between "xxx". Thus, for HTP_E_INVALID_XO_NAME, the error message is "Invalid xo name". One could read into memory htp.mes and build yourself an array of error numbers and an array of the corresponding error messages. Whenever you get an error number, you find the index on the first array matching the error number, then you use the same index to get the error message in the second array. Whenever an error occurs, one can find the index on the first array matching the error number, then you use the same index to get the error message in the second array.
   
   
8. To get the survey geometry (ie. 4 corner points) use htp_get_3d_geom. (see htp_test_geom.c)
   
   
9. To get 2D navigation data, use htp_get_2d_geom (see htp_test_geom.c)
   
   
10. To verify that a 3D survey is orthogonal, use htp_validate_geom_90 (see htp_test_geom.c)
    
    
11. To get a trace location in latitude and longitude, use htp_transform_to_latlong (see htp_test_geom.c).
    To get a trace location in x and y, use htp_transform_to_xy.
    
    
12. To get a list of IESX colormaps, use htp_get_colormap_list. This interface returns IESX and Geoviz colormaps ((see htp_test_ntrp.c).
    
    
13. Use htp_select_survey with appropriate flag to get a list of 3D or 2D surveys (see htp_test_geom.c).
    
    
14. Use htp_list_classes to list 3D seismic classes and use
    htp_list_2d_classes to get a list of 2D classes (see htp_test_geom.c or htp_test_seis.c ).
    
    
15. Use htp_list_named_paths to get a list of named rectangular or poly-linear paths (see htp_test_new_ntrp.c or htp_test_seis.c)
    
    
16. Only rectangular and linear paths are supported in IESX DK.
    
    
17. Use htp_get_hor_info to retrieve horizon information and
    htp_put_hor_info to update horizon information (see htp_test_ntrp.c).
    
    
18. Use htp_get_flt_info to retrieve fault information and
    htp_put_flt_info to update fault information (see htp_test_ntrp.c).
    
    
19. Use htp_delete_contacts to delete contacts and
    htp_update_contacts to update contacts (see htp_test_ntrp.c).
    
    
20. Use htp_update_flt_cuts to update,
    htp_reassign_flt_cuts to re-assign and
    htp_delete_flt_cuts to delete (htp_test_ntrp.c)
    
    
21. Use htp_get_hor_attr_trace,
    htp_get_hor_attr_path and
    htp_get_rect_hor_attr to read horizon attribute data (see htp_test_new_ntrp.c).
    Use htp_put_hor_attr_trace,
    htp_put_hor_attr_path, and
    htp_put_rect_hor_attr to write horizon attribute data (see htp_test_new_ntrp.c).
    
    
22. Use htp_set_domain to set the domain of the current process.
    Use htp_get_domain to get the current process domain(see htp_test_ntrp.c)
    
    
23. Use htp_create_well to create a well and
    htp_retrieve_well_info to get the specified well information (see htp_test_well.c).
    
    
24. Use htp_retrieve_well_dvt_info to get checkshot data, use
    htp_create_dvt to create a checkshot data for the well and use
    htp_create_dvt_from_sonice to create a checkshot from a sonic log (see htp_test_well.c).
    
    
25. Use htp_create_deviation_survey to create a new deviation survey for the well,
    htp_retrieve_well_deviation_survey_info to get the preferred well deviation survey (see htp_test_well.c).
    
    
26. Use htp_create_markers to create well markers and use
    htp_retrieve_well_marker_info to retrieve well marker information (see htp_test_well.c).
    
    
27. Use htp_create_well_log to create a log curve,
    htp_retrieve_well_log_name_info to get the list of log names,
    htp_return_log_data to get the log data values,
    htp_return_log_data_by_type to get log data by specifying a log type (see htp_test_well.c).
    
    
28. Use htp_get_trace to retrieve a trace data and
    htp_put_trace to store a trace data into a volume (htp_test_seis.c or htp_test_geom.c)
    
    
29. Use htp_model_list to get a list of models in the project,
    htp_model_get_context to retrieve the current selected model,
    htp_model_add_surface to add a surface to a model, and
    htp_model_remove_surfaces to remove surfaces from an interpretation model (htp_test_new_ntrp.c).
    
    
30. Use htp_get_hor_patch_attr_list to get a list of horizon-patch-attribute triplets,
    htp_surf_patch_list_all to retrieve the patches for all horizons for the entire project or the current model only,
    htp_patch_attr_list_all to retrieve all attributes for a given horizon and patch,
    htp_patch_create to create a patch for a given horizon,
    htp_patch_delete to delete a patch,
    htp_patch_list to list all patches for a given horizon,
    htp_patch_order_get to get the patch order.
    (see htp_test_new_ntrp.c).
    
    
31. 32-bit Linux is byte-aligned to 4 bytes and 64-bit Linux is byte-aligned to 8 bytes. In the IESX DK, some data structures have doubles in them and do not have end-padding to make the size of function return a value that is modulus of 8. For instance, a data structure may return a size of 36 in 32-bit Linux and the same structure will return a size of 40 in 64-bit Linux. 64-bit Linux implemented this 8 byte alignment for caching and performance reasons. If you attempt to pass data between a 32-bit application and 64-bit application, it is advised to be cautious when using size of as some our ies_htp data structures may not be 8 byte aligned.
    
    
32. The issue has been resolved in GF4.4 TK_2 and GF4.5.