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

[analyticalproblems] use LincombFunction to represent affine decompositions #318

Merged
merged 1 commit into from Nov 5, 2016

Conversation

@sdrave
Copy link
Member

@sdrave sdrave commented Nov 2, 2016

This addresses #205.

@sdrave sdrave force-pushed the ellipticproblem_no_affine_decomp branch 3 times, most recently from c0f6896 to 8b18b99 Nov 4, 2016
@coveralls
Copy link

@coveralls coveralls commented Nov 4, 2016

Coverage Status

Coverage decreased (-45.2%) to 34.891% when pulling 8b18b99 on ellipticproblem_no_affine_decomp into ea9965b on master.

1 similar comment
@coveralls
Copy link

@coveralls coveralls commented Nov 4, 2016

Coverage Status

Coverage decreased (-45.2%) to 34.891% when pulling 8b18b99 on ellipticproblem_no_affine_decomp into ea9965b on master.

@sdrave sdrave force-pushed the ellipticproblem_no_affine_decomp branch from 8b18b99 to 1b843ae Nov 4, 2016
@coveralls
Copy link

@coveralls coveralls commented Nov 4, 2016

Coverage Status

Coverage decreased (-0.006%) to 80.075% when pulling 1b843ae on ellipticproblem_no_affine_decomp into ea9965b on master.

@sdrave sdrave merged commit aa361fe into master Nov 5, 2016
2 checks passed
2 checks passed
continuous-integration/travis-ci/pr The Travis CI build passed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details
@sdrave sdrave deleted the ellipticproblem_no_affine_decomp branch Nov 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants