Uploaded image for project: 'UIMA'
  1. UIMA
  2. UIMA-6344

Ruta: ConjunctRules fires without justification

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.8.1ruta, 3.0.1ruta
    • 2.9.0ruta, 3.1.0ruta
    • Ruta
    • None

    Description

      Hi.

      I believe there is currently an issue with CunjunctRules (%) firing in cases they are not supposed to. As I understand the Guide on this topic, any actions assigned to any part of this kind of rule are to be applied only if all parts of the respective rule (the simple rules in between the %-symbols) match at least once in the current scope. However, this does not seem to hold for actions assigned to the first rule element in each part, at least when the first element matches but later ones don't. They just fire anyways.

      Consider the following test case:
      Text:

       a Bb a Bb
      

      Script:

      DECLARE T1, T2, T3, T4;
      
      SW{-> T1} % CW{-> T3} CW{-> T4};
      CW{-> T1} CW{-> T2} % SW{-> T3};
      SW{-> T1} SW{-> T2} % CW{-> T3} CW{-> T4};
      

      Each rule creates 2 annotations of types T1 and T3 each, although at least one part of each rule - in the last case both parts - doesn't match.

      Note:

      CAP{-> T1} SW{-> T2} % CW{-> T3} CW{-> T4};
      

      This works as expected, i.e. no actions are being applied.

      Regards,
      Michael

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            pkluegl Peter Klügl
            Michael Stenger Michael Stenger
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment