dolfin-adjoint

Versioning

Asked by Martin Sandve Alnæs

Hi guys, what are your ideas about matching dolfin versions and dolfin-adjoint releases? And keeping up with trunk? The buildbot is currently red for dolfin-adjoint because I decided to break compatibility in 1D in UFL, so vector valued 1D quantities have shape (1,) instead of () now. This makes code more dimension dependent, and solved a tricky case internally In UFL. If you want to stay up to date with trunk, I can try to look out for issues like this when doing UFL updates the coming weeks, and make merge requests.

Question information

Language:
English Edit question
Status:
Answered
For:
dolfin-adjoint Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Patrick Farrell (pefarrell) said : 		#1

Yes, both of those are very good ideas!

I've changed the d-a version numbering to match DOLFIN's (so now it's 1.1.0).

We would definitely like to stay up to date with trunk (though I've given up on doing it every day, it's too unstable for my purposes), so any help would be extremely welcome. Thanks, Martin.

Can you help with this problem?

Provide an answer of your own, or ask Martin Sandve Alnæs for more information if necessary.

To post a message you must log in.