Function: dump_unreg_callback

Product	Supported (√/x)
Atlas A3 training products/Atlas A3 inference products	√
Atlas A2 training products/Atlas A2 inference products	√
Atlas training products	√
Atlas inference products	√
Atlas 200I/500 A2 inference products	√

Deregisters the dump data callback function.

Function: init_dump, Function: dump_reg_callback, Function: dump_unreg_callback, and Function: finalize_dump work together to obtain dump data through a callback function. The callback function registered through Function: dump_reg_callback needs to be implemented by users, and the implementation logic of the callback function must include the acquisition of the dump data and data length. The specific scenarios are exemplified as follows:

Execute a model and obtain dump data through callback.
Function: init -- > Function: dump_reg_callback -- > Function: init_dump --> Model loading --> Model execution -- > Function: finalize_dump -- > Function: dump_unreg_callback --> Model unloading -- > Function: finalize
Execute two different models and obtain dump data through callback. In this context, as long as the callback function is not deregistered by calling Function: dump_unreg_callback, you can obtain the dump data of both models through the callback function.
Function: init -- > Function: dump_reg_callback -- > Function: init_dump --> Model 1 loading --> Model 1 execution -->--> Model 2 loading --> Model 2 execution -- > Function: finalize_dump --> Model unloading -- > Function: dump_unreg_callback -- > Function: finalize

None.

None

acl.mdl.dump_unreg_callback must work with acl.mdl.dump_reg_callback and is valid only after acl.mdl.dump_reg_callback is called.

Parent topic: Model Execution