Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Start stat collection at specified simulation time or code region #2189

Closed
plafratt opened this issue Jul 31, 2023 · 6 comments
Closed

Start stat collection at specified simulation time or code region #2189

plafratt opened this issue Jul 31, 2023 · 6 comments

Comments

@plafratt
Copy link

Is there a way to start stat collection at a specific simulation time?

I have a simulation that has about 500 us of initialization phase during which the stats are not of interest to me. I wanted to ask if there is a way to tell SST to exclude this period of the simulation from stats collection.

Any help is appreciated.

@feldergast
Copy link
Contributor

It is possible to start and stop stats at specific times. This is controlled by parameters to the enableStatistics calls.

More information on statistics can be found here:

http://sst-simulator.org/sst-docs/docs/config/stats/overview

Look for startat and stopat on the overview page, and examples can be found in the specific enableStatistics calls.

@plafratt
Copy link
Author

plafratt commented Aug 1, 2023

Thank you! I was able to find the relevant info at the provided link.

@plafratt plafratt closed this as completed Aug 1, 2023
@plafratt plafratt changed the title Start stat collection at specified simulation time Start stat collection at specified simulation time or code region Feb 29, 2024
@plafratt
Copy link
Author

plafratt commented Feb 29, 2024

I had a follow up question to this - is it possible to start and stop stat collection for a specific region of code?

I think one way of doing it is to run the simulation once to determine the times at which the region starts and ends, then set the startat and stopat parameters to correspond to those times. But, there are some cons to that approach (e.g. it involves running the simulation twice).

Is there possibly a better way?

@plafratt plafratt reopened this Feb 29, 2024
@gvoskuilen
Copy link
Contributor

Vanadis does not have this capability, but SST Core supports it (with some limitations) and Ariel does this today. When Ariel detects a particular dummy function call in the simulated application, it calls this component API function: http://sst-simulator.org/sst-docs/docs/core/component/stat/performGlobalStatisticOutput.

Caveat: the output is limited to statistics belonging to components on the same rank/thread as the component that triggered the output. We have some thoughts on how to make it truly global which involve deferring the dump until the simulation's next sync point.

Could you create an enhancement issue for vanadis to track this feature? If you need it sooner and end up implementing it, we can merge the capability in. Otherwise, we'll add it to our backlog for features.

@plafratt
Copy link
Author

plafratt commented Feb 29, 2024

Thank you for the helpful information. I will create the enhancement issue as requested and post an update there if we end up implementing it.

@plafratt
Copy link
Author

plafratt commented Mar 1, 2024

As requested, I created an enhancement request #2325. If we are able to implement this feature internally, I will post an update there. Thank you again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants