Download EnSight Interface Manual

2.5 Converting a 1.0 API Reader to a 2.0 API READER
D) Changes related to multiple timeset support.
The timeset_number argument needs to be added for the following three routines.
The multiple timeset support also includes the change in B) above for USERD_get_gold_variable_info and the
three new routines in the next section.
API 1.0
API 2.0
USERD_get_number_of_time_steps
(
void
)
USERD_get_num_of_time_steps
(
int timeset_number
)
USERD_get_solution_times
(
USERD_get_sol_times
(
int timeset_number,
float *solution_times
)
float *solution_times
)
USERD_set_time_step
(
USERD_set_time_set_and_step
(
int timeset_number,
int time_step
)
int time_step
}
Third, deleted and new routines. (Here is where the work lies)
Several old routines are gone. You will have to create the new routines that replace them. I think you will
find in most cases that your old routines will form the basis of the new routines, and that it isn’t too
difficult to provide the information in the new way.
See Detailed Specifications in this chapter for the needed information on these new routines.
API 1.0
API 2.0
These routines:
replaced by the single routine:
USERD_get_block_scalar_values
USERD_get_block_vector_values_by_component
USERD_get_scalar_values
USERD_get_vector_values
USERD_get_var_by_component
These global coordinate routines:
replaced by part coord routines:
USERD_get_global_coords
USERD_get_global_node_ids
USERD_get_number_of_global_nodes
USERD_get_part_coords
USERD_get_part_node_ids
These par connectivity routines:
replaced by part by type routines:
USERD_get_element_connectivities_for_part
USERD_get_element_ids_for_part
USERD_get_part_elements_by_type
USERD_get_part_element_ids_by_type
These are new routines:
(Can be a dummy) -> USERD_exit_routine
(Can be a dummy) -> USERD_get_model_extents
(Required) -> USERD_get_reader_version
2-166
EnSight Interface Manual