I suggest that you use the included API to generate your profile and then import the profile into CodeAnalyst.
So you would use fnEnableProfiling(), fnSetTimerConfiguration(), fnSetProfileOutputFile(), fnStartProfiling (startPaused), and then fnResumeProfiling () when you get to the part of your code in which you wish to start profiling. When you are done taking your profile, call fnStopProfiling() and fnReleaseProfiling ().
Open the CodeAnalyst Gui and import the data file you specified for fnSetProfileOutputFile.
There is sample code included in the installation demonstrating how to use the API.
I think using "start-dealy" and "profile duration" can achieve you want.
1) If you want CodeAnalyst GUI to launch the app for you, then setup the following options in the "Session Setting":
1200 in "start delay" -- this will let CodeAnalyst not collect data in first 20 minutes.
set 3600 in "profile duration" -- this will let CodeAnalyst collect about 1 hour data after start delay.
2) Manually signal start.
Leave blank for "launch" area.
set 3600 in "profile duration" -- profile for 1 hour
Then run your app stanalone outside CodeAnalyst. At the time of interest area, Click "start" in COdeAnalyst GUI to profile 1 hour.