- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
Up to now, we have finished demo to realize following targets through VPAC LDC:
input frontview image -- > VPAC(ldc) --> output birdview image
However, I found unreasonable process for my demo, let me describe it in detail.
Take a testcase from vision_apps for example, we offen notice main function as follows:
int main(int argc, char* argv[]) {
AppObj *obj = &gAppObj;
app_parse_cmd_line_args(obj, argc, argv);
app_init(obj);
app_create_graph(obj);
app_run_graph(obj);
app_delete_graph(obj);
app_deinit(obj);
return 0;
}
That means app_create_graph called at first, app_run_graph secondly, and app_delete_graph
called at last. Meanwhile, you can see that a batch of pics can be dealed in app_run_graph.
I want to learn from upper experience for main function, just call app_create_graph once, and
for every coming frame data, we call app_run_graph every time.That means, every frame must
share many same paras such as app_create_graph created. However, in my demo I have different
3*3 warp matrix for construct ldc node to call tivxVpacLdcNode, so I have to realize my demo
as follows:
int main(int argc, char* argv[]) {
AppObj *obj = &gAppObj;
app_parse_cmd_line_args(obj, argc, argv);
app_init(obj);
while(1) {
app_create_graph(obj);
app_run_graph(obj);
app_delete_graph(obj);
}
app_deinit(obj);
return 0;
}
Then, we have to create graph again for every new frame, which consume more time for repeat ops.
In order to optimize upper process, can you offer me a better scheme to create ldc node only once,
and we can change 3*3 warp matrix value, and pass it to ldc node meanwhile ?
