Using PRXNEXT to capture all instances of a keyword2019 Community Moderator ElectionMatch all occurrences of a regexHow to replace all occurrences of a string in JavaScriptHow do I remove all non alphanumeric characters from a string except dash?What is a non-capturing group? What does (?:) do?Using regex to match any character until a substring is reached?All overlapping substrings matching a java regexFinding words around a substringPHP Regex to extract columns of text delimited by multiple spacesExtract parts of a string after a key word in SAS EGRegex pattern to validate string with multiple conditions

How old is Nick Fury?

Unable to get newly inserted Product's Id using After Plugin for Catalog Product save controller method

What is the reasoning behind standardization (dividing by standard deviation)?

Friend wants my recommendation but I don't want to give it to him

UK Tourist Visa- Enquiry

Single word to change groups

How to determine the greatest d orbital splitting?

label a part of commutative diagram

Why are there no stars visible in cislunar space?

If I cast the Enlarge/Reduce spell on an arrow, what weapon could it count as?

What is it called when someone votes for an option that's not their first choice?

Why is indicated airspeed rather than ground speed used during the takeoff roll?

Would this string work as string?

Hot air balloons as primitive bombers

Recursively updating the MLE as new observations stream in

How can an organ that provides biological immortality be unable to regenerate?

Do native speakers use "ultima" and "proxima" frequently in spoken English?

Pre-Employment Background Check With Consent For Future Checks

Nested Dynamic SOQL Query

How to understand 「僕は誰より彼女が好きなんだ。」

Does fire aspect on a sword, destroy mob drops?

Exit shell with shortcut (not typing exit) that closes session properly

Is there any common country to visit for uk and schengen visa?

Error in master's thesis, I do not know what to do



Using PRXNEXT to capture all instances of a keyword



2019 Community Moderator ElectionMatch all occurrences of a regexHow to replace all occurrences of a string in JavaScriptHow do I remove all non alphanumeric characters from a string except dash?What is a non-capturing group? What does (?:) do?Using regex to match any character until a substring is reached?All overlapping substrings matching a java regexFinding words around a substringPHP Regex to extract columns of text delimited by multiple spacesExtract parts of a string after a key word in SAS EGRegex pattern to validate string with multiple conditions










2















I'm searching through medical notes to capture all instances of a phrase, in particular 'carbapenemase producing'. At times this phrasing can occur > 1 time in a string. From some research I think PRXNEXT would make the most sense but I'm having difficulty getting it to do what I want to. As an example for this string:




if amikacin results are needed please notify microbiology lab at ext
for further testing the organism will be held until meropenem result
obtained by disc diffusion presumptive carbapenemase producing cre see
spmi for carba r pcr results not confirmed carbapenemase producing cre




From this comment above, I'd like to extract the phrases




presumptive carbapenemase producing




and




not confirmed carbapenemase producing




I realize I can't extract, I don't think, those exact phrases but some variation of it with a substring. The code i've been using I found here. Here's what I have thus far but it's only capturing the 1st phrase:



carba_cnt = count(as_comments,'carba','i');

if _n_ = 1 then do;
retain reg1 neg1;
reg1 = prxparse("/ca[bepr]w+ prod/");
end;

start = 1;
stop = length(as_comments);
position = 0;
length = 0;

/* Use PRXNEXT to find the first instance of the pattern, */
/* then use DO WHILE to find all further instances. */
/* PRXNEXT changes the start parameter so that searching */
/* begins again after the last match. */

call prxnext(reg1, start, stop, as_comments, position, length);

lastpos = 0;
do while (position > 0);
if lastpos then do;
length found $200;
found = substr(as_comments,lastpos,position-lastpos);
put found=;
output;
end;
lastpos = position;

call prxnext(reg1, start, stop, as_comments, position, length);
end;

if lastpos then do;
found = substr(as_comments,lastpos);
put found=;
output;
end;









share|improve this question






















  • In the end, do you want the 2 text strings? Or do you want the information "presumptive" / "not confirmed" / "confirmed" in a new variable ?

    – stallingOne
    Mar 7 at 12:40











  • Ideally, one variable that has "presumptive carbapenemase" and then a variable that says "carbapenem confirmed". The tricky part is that the 1st occurrence is "presumptive carba" and then later in the note it's "carbapenem confirmed", and I'd like to be able to evaluate each of them in separate variables. Thanks for your help.

    – Brian Bartle
    Mar 7 at 15:39















2















I'm searching through medical notes to capture all instances of a phrase, in particular 'carbapenemase producing'. At times this phrasing can occur > 1 time in a string. From some research I think PRXNEXT would make the most sense but I'm having difficulty getting it to do what I want to. As an example for this string:




if amikacin results are needed please notify microbiology lab at ext
for further testing the organism will be held until meropenem result
obtained by disc diffusion presumptive carbapenemase producing cre see
spmi for carba r pcr results not confirmed carbapenemase producing cre




From this comment above, I'd like to extract the phrases




presumptive carbapenemase producing




and




not confirmed carbapenemase producing




I realize I can't extract, I don't think, those exact phrases but some variation of it with a substring. The code i've been using I found here. Here's what I have thus far but it's only capturing the 1st phrase:



carba_cnt = count(as_comments,'carba','i');

if _n_ = 1 then do;
retain reg1 neg1;
reg1 = prxparse("/ca[bepr]w+ prod/");
end;

start = 1;
stop = length(as_comments);
position = 0;
length = 0;

/* Use PRXNEXT to find the first instance of the pattern, */
/* then use DO WHILE to find all further instances. */
/* PRXNEXT changes the start parameter so that searching */
/* begins again after the last match. */

call prxnext(reg1, start, stop, as_comments, position, length);

lastpos = 0;
do while (position > 0);
if lastpos then do;
length found $200;
found = substr(as_comments,lastpos,position-lastpos);
put found=;
output;
end;
lastpos = position;

call prxnext(reg1, start, stop, as_comments, position, length);
end;

if lastpos then do;
found = substr(as_comments,lastpos);
put found=;
output;
end;









share|improve this question






















  • In the end, do you want the 2 text strings? Or do you want the information "presumptive" / "not confirmed" / "confirmed" in a new variable ?

    – stallingOne
    Mar 7 at 12:40











  • Ideally, one variable that has "presumptive carbapenemase" and then a variable that says "carbapenem confirmed". The tricky part is that the 1st occurrence is "presumptive carba" and then later in the note it's "carbapenem confirmed", and I'd like to be able to evaluate each of them in separate variables. Thanks for your help.

    – Brian Bartle
    Mar 7 at 15:39













2












2








2








I'm searching through medical notes to capture all instances of a phrase, in particular 'carbapenemase producing'. At times this phrasing can occur > 1 time in a string. From some research I think PRXNEXT would make the most sense but I'm having difficulty getting it to do what I want to. As an example for this string:




if amikacin results are needed please notify microbiology lab at ext
for further testing the organism will be held until meropenem result
obtained by disc diffusion presumptive carbapenemase producing cre see
spmi for carba r pcr results not confirmed carbapenemase producing cre




From this comment above, I'd like to extract the phrases




presumptive carbapenemase producing




and




not confirmed carbapenemase producing




I realize I can't extract, I don't think, those exact phrases but some variation of it with a substring. The code i've been using I found here. Here's what I have thus far but it's only capturing the 1st phrase:



carba_cnt = count(as_comments,'carba','i');

if _n_ = 1 then do;
retain reg1 neg1;
reg1 = prxparse("/ca[bepr]w+ prod/");
end;

start = 1;
stop = length(as_comments);
position = 0;
length = 0;

/* Use PRXNEXT to find the first instance of the pattern, */
/* then use DO WHILE to find all further instances. */
/* PRXNEXT changes the start parameter so that searching */
/* begins again after the last match. */

call prxnext(reg1, start, stop, as_comments, position, length);

lastpos = 0;
do while (position > 0);
if lastpos then do;
length found $200;
found = substr(as_comments,lastpos,position-lastpos);
put found=;
output;
end;
lastpos = position;

call prxnext(reg1, start, stop, as_comments, position, length);
end;

if lastpos then do;
found = substr(as_comments,lastpos);
put found=;
output;
end;









share|improve this question














I'm searching through medical notes to capture all instances of a phrase, in particular 'carbapenemase producing'. At times this phrasing can occur > 1 time in a string. From some research I think PRXNEXT would make the most sense but I'm having difficulty getting it to do what I want to. As an example for this string:




if amikacin results are needed please notify microbiology lab at ext
for further testing the organism will be held until meropenem result
obtained by disc diffusion presumptive carbapenemase producing cre see
spmi for carba r pcr results not confirmed carbapenemase producing cre




From this comment above, I'd like to extract the phrases




presumptive carbapenemase producing




and




not confirmed carbapenemase producing




I realize I can't extract, I don't think, those exact phrases but some variation of it with a substring. The code i've been using I found here. Here's what I have thus far but it's only capturing the 1st phrase:



carba_cnt = count(as_comments,'carba','i');

if _n_ = 1 then do;
retain reg1 neg1;
reg1 = prxparse("/ca[bepr]w+ prod/");
end;

start = 1;
stop = length(as_comments);
position = 0;
length = 0;

/* Use PRXNEXT to find the first instance of the pattern, */
/* then use DO WHILE to find all further instances. */
/* PRXNEXT changes the start parameter so that searching */
/* begins again after the last match. */

call prxnext(reg1, start, stop, as_comments, position, length);

lastpos = 0;
do while (position > 0);
if lastpos then do;
length found $200;
found = substr(as_comments,lastpos,position-lastpos);
put found=;
output;
end;
lastpos = position;

call prxnext(reg1, start, stop, as_comments, position, length);
end;

if lastpos then do;
found = substr(as_comments,lastpos);
put found=;
output;
end;






regex sas






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Mar 6 at 23:36









Brian BartleBrian Bartle

284




284












  • In the end, do you want the 2 text strings? Or do you want the information "presumptive" / "not confirmed" / "confirmed" in a new variable ?

    – stallingOne
    Mar 7 at 12:40











  • Ideally, one variable that has "presumptive carbapenemase" and then a variable that says "carbapenem confirmed". The tricky part is that the 1st occurrence is "presumptive carba" and then later in the note it's "carbapenem confirmed", and I'd like to be able to evaluate each of them in separate variables. Thanks for your help.

    – Brian Bartle
    Mar 7 at 15:39

















  • In the end, do you want the 2 text strings? Or do you want the information "presumptive" / "not confirmed" / "confirmed" in a new variable ?

    – stallingOne
    Mar 7 at 12:40











  • Ideally, one variable that has "presumptive carbapenemase" and then a variable that says "carbapenem confirmed". The tricky part is that the 1st occurrence is "presumptive carba" and then later in the note it's "carbapenem confirmed", and I'd like to be able to evaluate each of them in separate variables. Thanks for your help.

    – Brian Bartle
    Mar 7 at 15:39
















In the end, do you want the 2 text strings? Or do you want the information "presumptive" / "not confirmed" / "confirmed" in a new variable ?

– stallingOne
Mar 7 at 12:40





In the end, do you want the 2 text strings? Or do you want the information "presumptive" / "not confirmed" / "confirmed" in a new variable ?

– stallingOne
Mar 7 at 12:40













Ideally, one variable that has "presumptive carbapenemase" and then a variable that says "carbapenem confirmed". The tricky part is that the 1st occurrence is "presumptive carba" and then later in the note it's "carbapenem confirmed", and I'd like to be able to evaluate each of them in separate variables. Thanks for your help.

– Brian Bartle
Mar 7 at 15:39





Ideally, one variable that has "presumptive carbapenemase" and then a variable that says "carbapenem confirmed". The tricky part is that the 1st occurrence is "presumptive carba" and then later in the note it's "carbapenem confirmed", and I'd like to be able to evaluate each of them in separate variables. Thanks for your help.

– Brian Bartle
Mar 7 at 15:39












1 Answer
1






active

oldest

votes


















1














You are correct to use PRXNEXT for locating each occurrence of a regex match in a source. The regex pattern can be modified to use a group capture to search for an optional leading "not confirmed". The scenario for the least likely 'coder fail' is to focus loop and extract around a single call to PRXNEXT.



This example uses pattern /((not confirmeds*)?(ca[bepr]w+ prod)) and outputs one row per match.



data have;
id + 1;
length comment $2000;
infile datalines eof=done;
do until (_infile_ = '----');
input;
if _infile_ ne '----' then
comment = catx(' ',comment,_infile_);
end;
done:
if not missing(comment);
datalines4;
if amikacin results are needed please notify microbiology lab at ext
for further testing the organism will be held until meropenem result
obtained by disc diffusion presumptive carbapenemase producing cre
see spmi for carba r pcr results not confirmed carbapenemase producing cre
----
if amikacin results are needed please notify microbiology lab at ext
for further testing the organism will be held until meropenem result
obtained by disc diffusion conjectured carbapenems producing cre
see spmi for carba r pcr results not confirmed carbapenemase producing cre
----
;;;;
run;

data want;
set have;
prx = prxparse('/((not confirmeds*)?(ca[bepr]w+ prod))/');

_start_inout = 1;

do hitnum = 1 by 1 until (pos=0);
call prxnext (prx, _start_inout, length(comment), comment, pos, len);
if len then do;
content = substr(comment,pos,len);
output;
end;
end;

keep id hitnum content;
run;


Bonus info: The prxparse does not need to be inside an if _n_=1 block. See PRXPARSE docs




If perl-regular-expression is a constant or if it uses the /o option, the Perl regular expression is compiled only once. Successive calls to PRXPARSE do not cause a recompile, but returns the regular-expression-id for the regular expression that was already compiled. This behavior simplifies the code because you do not need to use an initialization block (IF _N_ = 1) to initialize Perl regular expressions.







share|improve this answer























  • Richard, thank you so much for your time.

    – Brian Bartle
    Mar 7 at 16:10











  • Great! Be sure to accept useful answers and vote up useful ones you come across. For the case of a much larger text universe and wider range of diagnostic signals to be teased out your organization might need to step up to SAS Text Miner

    – Richard
    Mar 7 at 16:28










Your Answer






StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55033872%2fusing-prxnext-to-capture-all-instances-of-a-keyword%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









1














You are correct to use PRXNEXT for locating each occurrence of a regex match in a source. The regex pattern can be modified to use a group capture to search for an optional leading "not confirmed". The scenario for the least likely 'coder fail' is to focus loop and extract around a single call to PRXNEXT.



This example uses pattern /((not confirmeds*)?(ca[bepr]w+ prod)) and outputs one row per match.



data have;
id + 1;
length comment $2000;
infile datalines eof=done;
do until (_infile_ = '----');
input;
if _infile_ ne '----' then
comment = catx(' ',comment,_infile_);
end;
done:
if not missing(comment);
datalines4;
if amikacin results are needed please notify microbiology lab at ext
for further testing the organism will be held until meropenem result
obtained by disc diffusion presumptive carbapenemase producing cre
see spmi for carba r pcr results not confirmed carbapenemase producing cre
----
if amikacin results are needed please notify microbiology lab at ext
for further testing the organism will be held until meropenem result
obtained by disc diffusion conjectured carbapenems producing cre
see spmi for carba r pcr results not confirmed carbapenemase producing cre
----
;;;;
run;

data want;
set have;
prx = prxparse('/((not confirmeds*)?(ca[bepr]w+ prod))/');

_start_inout = 1;

do hitnum = 1 by 1 until (pos=0);
call prxnext (prx, _start_inout, length(comment), comment, pos, len);
if len then do;
content = substr(comment,pos,len);
output;
end;
end;

keep id hitnum content;
run;


Bonus info: The prxparse does not need to be inside an if _n_=1 block. See PRXPARSE docs




If perl-regular-expression is a constant or if it uses the /o option, the Perl regular expression is compiled only once. Successive calls to PRXPARSE do not cause a recompile, but returns the regular-expression-id for the regular expression that was already compiled. This behavior simplifies the code because you do not need to use an initialization block (IF _N_ = 1) to initialize Perl regular expressions.







share|improve this answer























  • Richard, thank you so much for your time.

    – Brian Bartle
    Mar 7 at 16:10











  • Great! Be sure to accept useful answers and vote up useful ones you come across. For the case of a much larger text universe and wider range of diagnostic signals to be teased out your organization might need to step up to SAS Text Miner

    – Richard
    Mar 7 at 16:28















1














You are correct to use PRXNEXT for locating each occurrence of a regex match in a source. The regex pattern can be modified to use a group capture to search for an optional leading "not confirmed". The scenario for the least likely 'coder fail' is to focus loop and extract around a single call to PRXNEXT.



This example uses pattern /((not confirmeds*)?(ca[bepr]w+ prod)) and outputs one row per match.



data have;
id + 1;
length comment $2000;
infile datalines eof=done;
do until (_infile_ = '----');
input;
if _infile_ ne '----' then
comment = catx(' ',comment,_infile_);
end;
done:
if not missing(comment);
datalines4;
if amikacin results are needed please notify microbiology lab at ext
for further testing the organism will be held until meropenem result
obtained by disc diffusion presumptive carbapenemase producing cre
see spmi for carba r pcr results not confirmed carbapenemase producing cre
----
if amikacin results are needed please notify microbiology lab at ext
for further testing the organism will be held until meropenem result
obtained by disc diffusion conjectured carbapenems producing cre
see spmi for carba r pcr results not confirmed carbapenemase producing cre
----
;;;;
run;

data want;
set have;
prx = prxparse('/((not confirmeds*)?(ca[bepr]w+ prod))/');

_start_inout = 1;

do hitnum = 1 by 1 until (pos=0);
call prxnext (prx, _start_inout, length(comment), comment, pos, len);
if len then do;
content = substr(comment,pos,len);
output;
end;
end;

keep id hitnum content;
run;


Bonus info: The prxparse does not need to be inside an if _n_=1 block. See PRXPARSE docs




If perl-regular-expression is a constant or if it uses the /o option, the Perl regular expression is compiled only once. Successive calls to PRXPARSE do not cause a recompile, but returns the regular-expression-id for the regular expression that was already compiled. This behavior simplifies the code because you do not need to use an initialization block (IF _N_ = 1) to initialize Perl regular expressions.







share|improve this answer























  • Richard, thank you so much for your time.

    – Brian Bartle
    Mar 7 at 16:10











  • Great! Be sure to accept useful answers and vote up useful ones you come across. For the case of a much larger text universe and wider range of diagnostic signals to be teased out your organization might need to step up to SAS Text Miner

    – Richard
    Mar 7 at 16:28













1












1








1







You are correct to use PRXNEXT for locating each occurrence of a regex match in a source. The regex pattern can be modified to use a group capture to search for an optional leading "not confirmed". The scenario for the least likely 'coder fail' is to focus loop and extract around a single call to PRXNEXT.



This example uses pattern /((not confirmeds*)?(ca[bepr]w+ prod)) and outputs one row per match.



data have;
id + 1;
length comment $2000;
infile datalines eof=done;
do until (_infile_ = '----');
input;
if _infile_ ne '----' then
comment = catx(' ',comment,_infile_);
end;
done:
if not missing(comment);
datalines4;
if amikacin results are needed please notify microbiology lab at ext
for further testing the organism will be held until meropenem result
obtained by disc diffusion presumptive carbapenemase producing cre
see spmi for carba r pcr results not confirmed carbapenemase producing cre
----
if amikacin results are needed please notify microbiology lab at ext
for further testing the organism will be held until meropenem result
obtained by disc diffusion conjectured carbapenems producing cre
see spmi for carba r pcr results not confirmed carbapenemase producing cre
----
;;;;
run;

data want;
set have;
prx = prxparse('/((not confirmeds*)?(ca[bepr]w+ prod))/');

_start_inout = 1;

do hitnum = 1 by 1 until (pos=0);
call prxnext (prx, _start_inout, length(comment), comment, pos, len);
if len then do;
content = substr(comment,pos,len);
output;
end;
end;

keep id hitnum content;
run;


Bonus info: The prxparse does not need to be inside an if _n_=1 block. See PRXPARSE docs




If perl-regular-expression is a constant or if it uses the /o option, the Perl regular expression is compiled only once. Successive calls to PRXPARSE do not cause a recompile, but returns the regular-expression-id for the regular expression that was already compiled. This behavior simplifies the code because you do not need to use an initialization block (IF _N_ = 1) to initialize Perl regular expressions.







share|improve this answer













You are correct to use PRXNEXT for locating each occurrence of a regex match in a source. The regex pattern can be modified to use a group capture to search for an optional leading "not confirmed". The scenario for the least likely 'coder fail' is to focus loop and extract around a single call to PRXNEXT.



This example uses pattern /((not confirmeds*)?(ca[bepr]w+ prod)) and outputs one row per match.



data have;
id + 1;
length comment $2000;
infile datalines eof=done;
do until (_infile_ = '----');
input;
if _infile_ ne '----' then
comment = catx(' ',comment,_infile_);
end;
done:
if not missing(comment);
datalines4;
if amikacin results are needed please notify microbiology lab at ext
for further testing the organism will be held until meropenem result
obtained by disc diffusion presumptive carbapenemase producing cre
see spmi for carba r pcr results not confirmed carbapenemase producing cre
----
if amikacin results are needed please notify microbiology lab at ext
for further testing the organism will be held until meropenem result
obtained by disc diffusion conjectured carbapenems producing cre
see spmi for carba r pcr results not confirmed carbapenemase producing cre
----
;;;;
run;

data want;
set have;
prx = prxparse('/((not confirmeds*)?(ca[bepr]w+ prod))/');

_start_inout = 1;

do hitnum = 1 by 1 until (pos=0);
call prxnext (prx, _start_inout, length(comment), comment, pos, len);
if len then do;
content = substr(comment,pos,len);
output;
end;
end;

keep id hitnum content;
run;


Bonus info: The prxparse does not need to be inside an if _n_=1 block. See PRXPARSE docs




If perl-regular-expression is a constant or if it uses the /o option, the Perl regular expression is compiled only once. Successive calls to PRXPARSE do not cause a recompile, but returns the regular-expression-id for the regular expression that was already compiled. This behavior simplifies the code because you do not need to use an initialization block (IF _N_ = 1) to initialize Perl regular expressions.








share|improve this answer












share|improve this answer



share|improve this answer










answered Mar 7 at 10:21









RichardRichard

9,56221329




9,56221329












  • Richard, thank you so much for your time.

    – Brian Bartle
    Mar 7 at 16:10











  • Great! Be sure to accept useful answers and vote up useful ones you come across. For the case of a much larger text universe and wider range of diagnostic signals to be teased out your organization might need to step up to SAS Text Miner

    – Richard
    Mar 7 at 16:28

















  • Richard, thank you so much for your time.

    – Brian Bartle
    Mar 7 at 16:10











  • Great! Be sure to accept useful answers and vote up useful ones you come across. For the case of a much larger text universe and wider range of diagnostic signals to be teased out your organization might need to step up to SAS Text Miner

    – Richard
    Mar 7 at 16:28
















Richard, thank you so much for your time.

– Brian Bartle
Mar 7 at 16:10





Richard, thank you so much for your time.

– Brian Bartle
Mar 7 at 16:10













Great! Be sure to accept useful answers and vote up useful ones you come across. For the case of a much larger text universe and wider range of diagnostic signals to be teased out your organization might need to step up to SAS Text Miner

– Richard
Mar 7 at 16:28





Great! Be sure to accept useful answers and vote up useful ones you come across. For the case of a much larger text universe and wider range of diagnostic signals to be teased out your organization might need to step up to SAS Text Miner

– Richard
Mar 7 at 16:28



















draft saved

draft discarded
















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55033872%2fusing-prxnext-to-capture-all-instances-of-a-keyword%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

1928 у кіно

Захаров Федір Захарович

Ель Греко