DW-CGF : SETUP and TEARDOWN recalled at any epoch

Please provide the following info (tick the boxes after creating this topic):
Software Version
DRIVE OS 6.0.8.1
DRIVE OS 6.0.6
DRIVE OS 6.0.5
DRIVE OS 6.0.4 (rev. 1)
DRIVE OS 6.0.4 SDK
other

Target Operating System
Linux
QNX
other

Hardware Platform
DRIVE AGX Orin Developer Kit (940-63710-0010-300)
DRIVE AGX Orin Developer Kit (940-63710-0010-200)
DRIVE AGX Orin Developer Kit (940-63710-0010-100)
DRIVE AGX Orin Developer Kit (940-63710-0010-D00)
DRIVE AGX Orin Developer Kit (940-63710-0010-C00)
DRIVE AGX Orin Developer Kit (not sure its number)
other

SDK Manager Version
1.9.3.10904
other

Host Machine Version
native Ubuntu Linux 20.04 Host installed with SDK Manager
native Ubuntu Linux 20.04 Host installed with DRIVE OS Docker Containers
native Ubuntu Linux 18.04 Host installed with DRIVE OS Docker Containers
other

Hello, I have been able to write my own CGF example, composed of three nodes cascade connected (one output is connected to the previous node’s input) and managed to run it successfully.

However, I noticed that once i launch my CGF example, each time a node is called, both the SETUP and TEARDOWN phase are executed together with the PROCESS.
Do you know if it is possible to set the stmcompiler so to execute the SETUP and TEARDOWN of each node just once and so using CPUs resoruces to just run PROCESS phase?

Thanks in advance for clarification.

Dear @antonio.iovine,
Could you share details about the usecase? Are you using node multiple times in application graph? Generally the workflow is setup-> process->teardown.

Yes i apologize for the confusion. it is indeed working like that according to the logfile:

<13>1 2023-12-13T15:33:01.457300+01:00 - mainClient 4427 - - [1702477884815092us][DEBUG][tid:37][inputNodeImpl.cpp:85][inputNode] Entered the InputNode Process Pass !
<13>1 2023-12-13T15:33:01.457333+01:00 - mainClient 4427 - - [1702477884815126us][DEBUG][tid:37][testNodeImpl.cpp:83][testNode] Entered the testNode Process Pass !
<13>1 2023-12-13T15:33:01.490303+01:00 - mainClient 4427 - - [1702477884848094us][DEBUG][tid:37][inputNodeImpl.cpp:85][inputNode] Entered the InputNode Process Pass !
<13>1 2023-12-13T15:33:01.490339+01:00 - mainClient 4427 - - [1702477884848132us][DEBUG][tid:37][testNodeImpl.cpp:83][testNode] Entered the testNode Process Pass !
<13>1 2023-12-13T15:33:01.520416+01:00 - mainClient 4427 - - [1702477884878207us][DEBUG][tid:scheduleManagerReceiver][ScheduleManagerReceiver.cpp:211][Receiver] [Receiver] listening
<13>1 2023-12-13T15:33:01.523303+01:00 - mainClient 4427 - - [1702477884881095us][DEBUG][tid:37][inputNodeImpl.cpp:85][inputNode] Entered the InputNode Process Pass !
<13>1 2023-12-13T15:33:01.523337+01:00 - mainClient 4427 - - [1702477884881130us][DEBUG][tid:37][testNodeImpl.cpp:83][testNode] Entered the testNode Process Pass !
<11>1 2023-12-13T15:33:01.533395+01:00 - mainClient 4427 - - [1702477884891184us][ERROR][tid:rr2_main][TopExecutor.hpp:640][TopExecutor] Caught signal 15 sent by pid 4425
<13>1 2023-12-13T15:33:01.533424+01:00 - mainClient 4427 - - [1702477884891217us][DEBUG][tid:rr2_main][TopExecutor.hpp:664][TopExecutor] Caught user interruption signal
.
.
.
<13>1 2023-12-13T15:33:01.620966+01:00 - mainClient 4427 - - [1702477884978759us][DEBUG][tid:rr2_main][inputNodeImpl.cpp:51][inputNode] Entered the InputNode teardown Pass !
<13>1 2023-12-13T15:33:01.621432+01:00 - mainClient 4427 - - [1702477884979224us][DEBUG][tid:rr2_main][testNodeImpl.cpp:51][testNode] Entered the testNode teardown Pass !

Dear @antonio.iovine,

So. You don’t see any issue and topic can be closed?

it’s a feature, not a bug.

Yes, by mistake i had called the node multiple time, as you suggested to check, and now SETUP passes are executed just once per node at the beginning as expected, as well TEARDOWN ones at the end of the execution.

Topic can be closed.

Thanks for the hint.

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.