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

New integrator overhaul #794

Closed
8 of 16 tasks
jaeandersson opened this issue Jul 8, 2013 · 16 comments
Closed
8 of 16 tasks

New integrator overhaul #794

jaeandersson opened this issue Jul 8, 2013 · 16 comments
Assignees

Comments

@jaeandersson
Copy link
Member

This is a new iteration (after #397) on the way AD is performed on integrator objects. This is necessary to enable support for multiple-shooting and (fast) high-order sensitivity analysis.

Prerequisites:

Subtasks:

Cf. also #929.

Possible follow-ups: #945, #946, #947.

NOTE: Strikethrough tickets have been moved to #974.

@jaeandersson
Copy link
Member Author

Branch "issue_794" created for this issue. @jgillis Note that a major change of integrators is on the way. If you want to make changes to the integrators, better make it to this branch. Otherwise it will surely lead to conflicts.

jaeandersson added a commit that referenced this issue Jul 8, 2013
jaeandersson added a commit that referenced this issue Jul 11, 2013
jaeandersson added a commit that referenced this issue Jul 12, 2013
jaeandersson added a commit that referenced this issue Jul 12, 2013
jaeandersson added a commit that referenced this issue Jul 12, 2013
jaeandersson added a commit that referenced this issue Jul 12, 2013
jaeandersson added a commit that referenced this issue Jul 12, 2013
@jgillis
Copy link
Member

jgillis commented Nov 21, 2013

Bump "Retreiving algorithmic states when using simulator"

(Anne Mai)

@jaeandersson
Copy link
Member Author

Does not make sense to address algebraic variable outputs before refactoring. Will look at it when I'm happy with the overall design. Will work on this issue after #884, which is related.

@ghorn
Copy link
Member

ghorn commented Nov 21, 2013

If you need algebraic variables, but direct coll is too expensive, could you just solve the residual at one additional point per timestep to get the alg vars manually?

@jaeandersson
Copy link
Member Author

Yes although initial guess could be an issue.

@jaeandersson
Copy link
Member Author

I don't think anymore it makes sense to implement this in a separate branch. The changes will be evolutionary and not revolutionary with few or no syntax changes. Therefore, I'll close this issue and deal deal with the specific changes in dedicated issues.

@jaeandersson
Copy link
Member Author

I'll reopen the issue, since it's good to have all the changes summarized in one place.

@jaeandersson
Copy link
Member Author

The refactoring of the generation of the augmented DAE is now complete. While the new implementation is not necessarily better for SXFunction, it should scale better and work with callback functions of any type. Added an option "expand_augmented" which can be set to "false" to achieve a possibly smaller memory footprint. If the numerical efficiency of MXFunction improves further, this option can be removed.

@jaeandersson
Copy link
Member Author

Closing this issue, postponing remaining tasks to #974.

@jaeandersson
Copy link
Member Author

Branches issue_794 and issue_794b removed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants