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

Improvement of FillTask and TaskManager #19

Open
eugene274 opened this issue Sep 30, 2020 · 2 comments
Open

Improvement of FillTask and TaskManager #19

eugene274 opened this issue Sep 30, 2020 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@eugene274
Copy link
Contributor

Requirements:

  • pass data object (together with configuration) from task to task and let user to modify it
  • let user interfere into task flow (reject event, etc), keep per-task statistics on rejected events
@viktorklochkov viktorklochkov self-assigned this Oct 27, 2020
@viktorklochkov viktorklochkov added the enhancement New feature or request label Oct 27, 2020
@eugene274
Copy link
Contributor Author

Small comment:

There are two kinds of user actions:

  • modification of event structure:
    • adding new branch
    • defining new variable
    • what else?
  • modification of event data

Combining that with tasks concept any modification of the event structure must be allowed at Init step only (before event loop), while modification of the data itself must be allowed only during the event loop.

@eugene274
Copy link
Contributor Author

Few notes on events cuts.

At this moment there is a possibility to set event cuts to reject bad events. Object Cuts is passed to TaskManager. Cuts acts on either on or two branches of the event header. But in general there could by any number of "event branches" (e.g. RecEvent, SimEvent, Centrality).

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

No branches or pull requests

2 participants