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

lookahead clarification/tweaks #86

Open
JohnPJenkins opened this issue Feb 25, 2016 · 0 comments
Open

lookahead clarification/tweaks #86

JohnPJenkins opened this issue Feb 25, 2016 · 0 comments

Comments

@JohnPJenkins
Copy link

I recently walked through some simulation code with our friends from Japan and came away with a few observations:

  1. there's no command-line parameter for lookahead
  2. there's no longer any documentation for lookahead, now that the user guide is gone. Our friends were using the default of 0.005 (ns), which naturally led to awful conservative performance.
  3. there's no good way to determine what the lookahead should be

Each are pretty simple to address, I would think. 3 can be aided by printing out stats on the time deltas for events (min, avg, max?).

Another thing came to mind while determining what lookahead they should use is whether it is necessary to check all events in tw_event_new for lookahead violations or just events to LPs in different PEs. A lot of models we develop rely heavily on self events with small deltas for control flow or events to "local" components (e.g. a process telling a model-net lp to do some work). We could definitely ramp up the lookahead and hence conservative performance if so, though on the CODES side we would need to make assurances that we're not splitting up LPs within a "group" to different PEs, which can be done easily enough.

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

1 participant