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

Modify portabilities for new Ubuntus #205

Draft
wants to merge 16 commits into
base: develop
Choose a base branch
from

Conversation

kwabenantim
Copy link
Member

Copy link

codecov bot commented Jan 16, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.99%. Comparing base (e26ac25) to head (e172aaf).
Report is 31 commits behind head on develop.

Current head e172aaf differs from pull request most recent head 6c28b3f

Please upload reports for the commit 6c28b3f to get more accurate results.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #205      +/-   ##
===========================================
- Coverage   100.00%   99.99%   -0.01%     
===========================================
  Files         1029     1029              
  Lines        51386    51377       -9     
===========================================
- Hits         51386    51375      -11     
- Misses           0        2       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@fcooper8472
Copy link
Member

Following our discussion this morning, I have opened #231 which outlines a strategy for temporarily ignoring (in a very selective and targeted way) some -Wmaybe-uninitialized c_vector warnings.

The discussion indicated a preference to temporarily ignore the warnings, with a view to migrating from Boost uBLAS to Eigen in due course, as part of Milestone 2.2.

@fcooper8472
Copy link
Member

I'm stuck on something that appears to be a genuine compiler warning; perhaps something for @jmpf or @mirams:

The following line calls ComputeLinearInUCoeffInSourceTerm with a second parameter as nullptr.

return ComputeLinearInUCoeffInSourceTerm(rNode.GetPoint(), nullptr);

In AbstractLinearEllipticPde, the function ComputeLinearInUCoeffInSourceTerm is pure virtual, but one place it's defined is in:

template<unsigned DIM>
double AveragedSourceEllipticPde<DIM>::ComputeLinearInUCoeffInSourceTerm(const ChastePoint<DIM>& rX, Element<DIM,DIM>* pElement) // now takes in element
{
assert(!mCellDensityOnCoarseElements.empty());
return mSourceCoefficient * mCellDensityOnCoarseElements[pElement->GetIndex()];
}

What should this specialisation do in the case that the element is null?

@jmpf
Copy link
Contributor

jmpf commented Feb 28, 2024

What should this specialisation do in the case that the element is null?

What happens if we assert that it's not null? Does any test-suite fall over?

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

Successfully merging this pull request may close these issues.

None yet

3 participants