Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
S src
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 61
    • Issues 61
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OPAL
  • src
  • Issues
  • #706

Closed
Open
Created Jan 28, 2022 by albajacas_a@albajacas_aDeveloper

Bug with Temporal Monitor when running in parallel

Summary

@muralikrishnan pointed out that he was having this error:

When a temporal monitor is used, and you run on multiple cores, you get the following error:

Error{1}>                                                                                                                                                                                                          
Error{1}> *** Error:                                                                                                                                                                                               
Error{1}>     Internal OPAL error:                                                                                                                                                                                 
Error{1}>     basic_string::_M_construct null not valid                                                                                                                                                            
Error{1}>     basic_string::_M_construct null not valid   

This happens for example running test_fft.in, only when run on multiple cores. When running on a single core it works fine.

The problem seems to come from the line auto stats = lossDs_m->computeStatistics(1); (https://gitlab.psi.ch/OPAL/src/-/blob/master/src/Classic/AbsBeamline/Monitor.cpp#L132), which was added in !557 (merged)

I don't exactly know why this line was added or why it gives an error here. Maybe @kraus can comment.

Edited Jan 28, 2022 by albajacas_a
Assignee
Assign to
2022.1
Milestone
2022.1 (Past due)
Assign milestone
Time tracking