#236 closed feature_request (invalid)
Re-implement analysis cuts
| Reported by: | Juergen Reuter | Owned by: | ALL |
|---|---|---|---|
| Priority: | P1 | Milestone: | |
| Component: | core | Version: | 2.0.0rc2 |
| Severity: | major | Keywords: | |
| Cc: |
Description
Re-implement cuts that are only valid when working on either generated or read-in events.
Note: See
TracTickets for help on using
tickets.
That's implemented, and the idea of SINDARIN is to be more flexible than that.
all <some-condition> [some-particles] and ...
can be part of either the 'cuts' or 'analyis' prescription. The 'cuts' are always applied, the 'analysis' comes on top.
You could also write analysis expressions such as
if all <...> [...] then ... endif
Any expression would do.
Or do I misunderstand the question? There should no distinction between generated and read-in, however.