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

fix: Update level_cell_array.hpp #286

Merged
merged 6 commits into from
Mar 14, 2025

Conversation

alexandrehoffmann
Copy link
Contributor

@alexandrehoffmann alexandrehoffmann commented Mar 13, 2025

Description

Updated the constructor of LevelCellArray from Subset so that it uses LevelCellArray::add_interval_back instead of creating a temporary LevelCellList.

Plus add_interval_back_rec has been modified so that y_offset is properly initialized when the m_cells is empty.

Code of Conduct

By submitting this PR, you agree to follow our Code of Conduct

  • I agree to follow this project's Code of Conduct

Updated the constructor from subset node so that it uses `LevelCellArray::add_interval` instead of creating a temporary `LevelCellList`
@alexandrehoffmann alexandrehoffmann changed the title Update level_cell_array.hpp fix: Update level_cell_array.hpp Mar 13, 2025
{
lcl[index].add_interval(i);
add_interval_back({i.start, i.end}, index);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why you can't put i directly ?

Comment on lines 447 to 448
const value_t xmin = x_interval.start;
const value_t xmax = x_interval.end;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We probably can remove now xmin and xmax and only work with x_interval, no ?

@gouarin gouarin merged commit 584527b into hpc-maths:master Mar 14, 2025
20 checks passed
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.

2 participants