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
  • #564

Closed
Open
Created Jul 15, 2020 by snuverink_j@snuverink_jDeveloper

LONG-TRANSV-SHORT-RANGE wake not implemented

Summary

As discovered by @ext-piot_p the LONG-TRANSV-SHORT-RANGE wake is not implemented.

Steps to reproduce

WAKE command with TYPE=LONG-TRANSV-SHORT-RANGE.

What is the current bug behavior?

No warning message, no wakefield.

What is the expected correct behavior?

Correctly implemented wake, or exception thrown.

Relevant logs and/or screenshots

    } else if (Attributes::getString(itsAttr[TYPE]) == "LONG-TRANSV-SHORT-RANGE") {
        //FIXME: NOT IMPLEMENTED YET!!!
    } else {
        wf_m = 0;
        INFOMSG("no wakefunction attached" << endl);
    }

Possible fixes

An exception can be thrown, also in the case of a non-matching type (might be a typo). The mention of LONG-TRANSV-SHORT-RANGE should be removed from the manual.

Assignee
Assign to
OPAL 2.4.0
Milestone
OPAL 2.4.0 (Past due)
Assign milestone
Time tracking