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

Fork memory #27

Open
Tracked by #29
LinqLover opened this issue Jan 23, 2022 · 1 comment
Open
Tracked by #29

Fork memory #27

LinqLover opened this issue Jan 23, 2022 · 1 comment
Labels
discussion engineering Technical change to the machinery

Comments

@LinqLover
Copy link
Collaborator

Create a copy of the memory at a certain time index. The copy can be continued independently of the original memory.

@LinqLover LinqLover added the engineering Technical change to the machinery label Jan 23, 2022
@LinqLover
Copy link
Collaborator Author

LinqLover commented Mar 13, 2022

This needs further discussion: What exactly should be copied? One option would be an eager copy of the process, which could be shallow (including side effects on the original process) or deep (very expensive). Another option would be a lazy copy via something like SimulationStudio's Sandbox, which would be slower and have unclear proceed semantics. In the latter case, there would also be an engineering issue to find out whether tracing simulators and sandbox simulators can be plugged together as simply as the Simulator CoR is designed (see #68).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion engineering Technical change to the machinery
Projects
None yet
Development

No branches or pull requests

1 participant