Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • E elsa
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 54
    • Issues 54
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 19
    • Merge requests 19
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • IP
  • elsa
  • Issues
  • #157

Closed
Open
Created Mar 11, 2022 by David Frank@david.frankMaintainer

EllipseGenerator generates indices out of bounds

Adding a line similar to the operator() which takes an index vector like this:

template <typename data_t>
data_t& DataContainer<data_t>::operator()(IndexVector_t coordinate)
{
    const auto arr = coordinate.array();
    const auto shape = _dataDescriptor->getNumberOfCoefficientsPerDimension().array();
    if((arr >= shape).all()) {
        throw Error("This is wrong");
    }

    return (*this)[_dataDescriptor->getIndexFromCoordinate(std::move(coordinate))];
}

The EllipseGenerator triggers this if statement. This mostly happens with volume sizes of powers of two. But also isn't 100% reproducible, I'm not sure why.

Assignee
Assign to
Time tracking