-
Notifications
You must be signed in to change notification settings - Fork 51
State after manually chosen set of events #375
Copy link
Copy link
Open
Labels
analysisAdds or changes evolution analysis tools, e.g., `WolframModelEvolutionObject` propertiesAdds or changes evolution analysis tools, e.g., `WolframModelEvolutionObject` propertiesfeatureNew functionality, or change in existing functionalityNew functionality, or change in existing functionalitygood first issueGood for newcomersGood for newcomershelp wantedExtra attention is neededExtra attention is neededwolfram languageRequires Wolfram Language implementationRequires Wolfram Language implementation
Milestone
Description
Metadata
Metadata
Assignees
Labels
analysisAdds or changes evolution analysis tools, e.g., `WolframModelEvolutionObject` propertiesAdds or changes evolution analysis tools, e.g., `WolframModelEvolutionObject` propertiesfeatureNew functionality, or change in existing functionalityNew functionality, or change in existing functionalitygood first issueGood for newcomersGood for newcomershelp wantedExtra attention is neededExtra attention is neededwolfram languageRequires Wolfram Language implementationRequires Wolfram Language implementation
The problem
Currently, there are limited capabilities of selecting reference frames in
WolframModelEvolutionObject. In particular, in order to select a state for a particular slice through a causal graph, one can either specify a single generation, or a single event, and that's it.What we want, most generally, is to specify a list of events. It would then be auto-completed to include its past light cone, and the resulting state would be returned (assuming selected events were spacelike).
Possible solution
We could have a property called
"StateAfterEvents"with an API like this:and it will return the state (list of non-destroyed expressions) after applying events
{0, 4, 6, 8}and their dependencies, but not any other events.Additional context
This function is already needed internally, and will soon be used by both
"StateAfterEvent", and"Generation", it just needs to be exposed.