Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: Search for perfect tense vocabulary

  1. #1
    Join Date
    Apr 2012
    Posts
    124

    Default Search for perfect tense vocabulary

    Hello all,

    Using BW9, I'm trying to build a list of NT verbs in the perfect tense, indicative mood. Using the Morphology assistant allows me to find the verbs as they appear in the NT, but I'm especially interested in sorting out the data, and building it into a list, i.e., something like this:
    γράφω 70x
    οἶδα 213x
    ἵστημι 27x
    etc.
    It would also be nice to be able to build a list like this that distinguishes between active and m-p uses, although that may be asking to much...

    Related to this, I'm wondering if there's any way to show this data on the stats tab.

    Does anyone have any suggestions?

    Thanks!

  2. #2

    Default

    You want "to build a list of NT verbs in the perfect tense, indicative mood."
    1. Switch to BNM version > On command line: BNM Enter
    2. Make sure you clear your limits > On command line: L Enter
    3. Find all perfect indicatives > .*@vix* Enter
    4. Open the Word List Manager (WLM): either via button bar or menu: Tools > Analyzing the Text > Word List Manager
    5. In WLM, click on "Load or Generate Word List"
    6. In the "Create Word List" box that opens, choose:
      1. Version: BNM
      2. Source: Load Highlighted Words from last query
      3. Verse Range: Check "Use Search Window limits"
      4. Other options: UNcheck all the boxes
      5. Click "Create List"

    There you go!

    To find all active forms, repeat steps using: .*@vixa*
    To find all Mid/Pass forms, repeat using: .*@vix[mp]*

    The stats window is not intended to graph usage of words across the Bible. It's just for number of hits in book/chapter/verse.
    Mark G. Vitalis Hoffman
    Professor of Biblical Studies
    Lutheran Theological Seminary at Gettysburg
    ltsg.edu - CrossMarks.com
    Biblical Studies and Technological Tools

  3. #3
    Join Date
    Apr 2012
    Posts
    124

    Default

    Quote Originally Posted by MGVH View Post
    You want "to build a list of NT verbs in the perfect tense, indicative mood."
    1. Switch to BNM version > On command line: BNM Enter
    2. Make sure you clear your limits > On command line: L Enter
    3. Find all perfect indicatives > .*@vix* Enter
    4. Open the Word List Manager (WLM): either via button bar or menu: Tools > Analyzing the Text > Word List Manager
    5. In WLM, click on "Load or Generate Word List"
    6. In the "Create Word List" box that opens, choose:
      1. Version: BNM
      2. Source: Load Highlighted Words from last query
      3. Verse Range: Check "Use Search Window limits"
      4. Other options: UNcheck all the boxes
      5. Click "Create List"
    There you go!

    To find all active forms, repeat steps using: .*@vixa*
    To find all Mid/Pass forms, repeat using: .*@vix[mp]*

    The stats window is not intended to graph usage of words across the Bible. It's just for number of hits in book/chapter/verse.
    Thank you! This is exactly what I was trying to do! I was missing the step with the word list manager, though.

    As for the stats tab, I figured it was probably stretching things a bit, but thought I'd ask anyway. One never knows. Perhaps it can be an idea for BW 10...

  4. #4
    Join Date
    Mar 2004
    Posts
    838

    Default Another solution

    There are multiple ways to do most things in BibleWorks. In this case a new feature was added a couple of weeks ago that answers this request, with the added plus of adding glosses:

    1. Select BNM and activate the Words tab
    2. Activate accent sensitive searching (right click on command line)
    3. enter .*@vix* on the command line. Note that since the * key doubles as an accent, when in accent sensitive mode you have to press the insert key before typing the *.
    4. press return
    5. activate the
    6. right click on the Wildcard expansion pane in the words tab and select "copy list to editor"
    7. Wallah! This is probably French but I don't know how to spell it

    οἶδα, to know [215]
    γράφω, to write [69]
    γίνομαι, to become, be [47]
    δίδωμι, to give [36]
    ὁράω, to see [30]
    ἵστημι, to cause to stand, stand [20]
    γινώσκω, to come to know, learn, know, realize [19]
    ἔρχομαι, to come, go [17]
    λέγω, to say, speak [17]
    etc.

  5. #5
    Join Date
    Mar 2009
    Posts
    376

    Default

    Spectacular!

    The French word you're looking for is voilą (pronounced "vwah - la"), more or less equivalent to ἰδοὺ in its origins.
    David Rensberger
    Atlanta, Georgia

  6. #6

    Default

    Thanks, Michael. I remember that you reported on that feature a bit ago.
    Question: the way you provided appears to provide accurate counts when search the whole NT. When I apply any search limit, however, I get results that don't make sense to me.
    E.g., for perfect indicatives in the NT, most common (as your search generated) is: οἶδα, to know [215]
    If I set my limit to Mark and run the same search it says that most common is: οἶδα, to know [204]
    There are actually only 13 uses of the indicative perfect of οἶδα in Mark, so what is that 204 counting?
    Mark G. Vitalis Hoffman
    Professor of Biblical Studies
    Lutheran Theological Seminary at Gettysburg
    ltsg.edu - CrossMarks.com
    Biblical Studies and Technological Tools

  7. #7
    Join Date
    Apr 2012
    Posts
    124

    Default

    Quote Originally Posted by MBushell View Post
    There are multiple ways to do most things in BibleWorks. In this case a new feature was added a couple of weeks ago that answers this request, with the added plus of adding glosses:

    1. Select BNM and activate the Words tab
    2. Activate accent sensitive searching (right click on command line)
    3. enter .*@vix* on the command line. Note that since the * key doubles as an accent, when in accent sensitive mode you have to press the insert key before typing the *.
    4. press return
    5. activate the
    6. right click on the Wildcard expansion pane in the words tab and select "copy list to editor"
    7. Wallah! This is probably French but I don't know how to spell it

    οἶδα, to know [215]
    γράφω, to write [69]
    γίνομαι, to become, be [47]
    δίδωμι, to give [36]
    ὁράω, to see [30]
    ἵστημι, to cause to stand, stand [20]
    γινώσκω, to come to know, learn, know, realize [19]
    ἔρχομαι, to come, go [17]
    λέγω, to say, speak [17]
    etc.
    Yes, this is very nice. I had already noticed that the Wildcard box in the verse tab compiled the list, but hadn't tried copying it to the editor. I haven't gotten the glosses, but perhaps that's in an update that I haven't yet downloaded.

    I had also noticed, as Mark Hoffman mentioned, that the stats in the Wildcard expansion don't seem trustworthy when book limits are applied (I tried the same thing for the Gospel of John, and οἶδα went from 215 in the NT to 212 in John... as opposed to 61 times when the search is done with .οιδα@vixa*).

    One other issue with this function: living and working in France means I use a French keyboard. BW9 improves on BW7 in this regard, as it "remembers" from one session to the other that my default keyboard French (thanks! It was a bit of a pain setting it back to French each time I opened a session). However, I notice that when I export the results of the Wildcard expansion to the editor, the English default overrides the French keyboard... and I'm back to having to reset it to French. Either that or writing "voilq" each time! (qwerty and not azerty) :-)

    Regards and blessings during this Easter season,

    Don Cobb

  8. #8
    Join Date
    Mar 2004
    Posts
    838

    Default Words Tab stats isssue

    Hi All,

    I investigated this and posted a new executable to address part of the "issue". It's complicated:

    When you select the option to hide morphology codes in the Words Tab for the search and wildcard expansion panes, what the program does is simply collapse the items with the same lemma into one list item adding up the counts as the words are collapsed. The problem was that items with mutiple parsings (like pd/pg) are double counted. I fixed the code so that double parsings are not counted twice. So the stats should match the search stats now.

    The other problems is the way stats are reported if you have search limits on. To see what is happening you have to understand that the numbers beside the words in the Words tab are whole version stats and do not account for search limits. You can see what is going on by turning off the option to prune the morph codes. However, the actual word+code entries in the wildcard expansion and search word panes DO account for the search limits. If a word+code pair does not occur in the limit range, the word will not appear. So when you collaspe the codes, it is adding up only the word+code pairs that appear in the range. What this means is that the numbers beside the collapsed entries are not wrong, but not very useful either.

    If you want to explore what is going on do a wild card search on a simple word like eggus@*. It has few occurrences but does have entries with multiple parsings. Do the search with collapsed and uncollapsed forms.

    The quest probably occues as to why we don't just modify the hit counts by each word when search limits are on so they reflect the limits. The answe is that this information is not available on the fly. It would require doing a rabge limited search on eac word as it is displayed and that would take a long, long time. You would not be very happy with the responsiveness. The word frequency occurrence of each lemma+code pair is stored in the version data so it is easy to display on the fly.

    Hope this makes a little sense.

    Mike

  9. #9
    Join Date
    Apr 2012
    Posts
    124

    Default

    Quote Originally Posted by MBushell View Post
    Hi All,

    I investigated this and posted a new executable to address part of the "issue". It's complicated:

    When you select the option to hide morphology codes in the Words Tab for the search and wildcard expansion panes, what the program does is simply collapse the items with the same lemma into one list item adding up the counts as the words are collapsed. The problem was that items with mutiple parsings (like pd/pg) are double counted. I fixed the code so that double parsings are not counted twice. So the stats should match the search stats now.

    The other problems is the way stats are reported if you have search limits on. To see what is happening you have to understand that the numbers beside the words in the Words tab are whole version stats and do not account for search limits. You can see what is going on by turning off the option to prune the morph codes. However, the actual word+code entries in the wildcard expansion and search word panes DO account for the search limits. If a word+code pair does not occur in the limit range, the word will not appear. So when you collaspe the codes, it is adding up only the word+code pairs that appear in the range. What this means is that the numbers beside the collapsed entries are not wrong, but not very useful either.

    If you want to explore what is going on do a wild card search on a simple word like eggus@*. It has few occurrences but does have entries with multiple parsings. Do the search with collapsed and uncollapsed forms.

    The quest probably occues as to why we don't just modify the hit counts by each word when search limits are on so they reflect the limits. The answe is that this information is not available on the fly. It would require doing a rabge limited search on eac word as it is displayed and that would take a long, long time. You would not be very happy with the responsiveness. The word frequency occurrence of each lemma+code pair is stored in the version data so it is easy to display on the fly.

    Hope this makes a little sense.

    Mike
    I won't say I understand everything... But thanks for the work! It gives an idea of the usefulness of the stats tab and its limits, at least for the time being. I'll download the update.

    Again, Thanks!

    Donald Cobb
    Aix-en-Provence, France

  10. #10
    Join Date
    Sep 2007
    Posts
    1,206

    Default

    Hey Donald, I couldn't help but notice the Aix-en-Provence address. Are you at the seminary there? Years ago, in Marseille, I met a guy who taught at the seminary: Fredric Beaudin. I wonder if he's still there. Soyez beni!

    Irving


Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •