String tokenization and transformation ( character string or path to a file )
tokenize_transform_text(
object = NULL,
batches = NULL,
read_file_delimiter = "\n",
to_lower = FALSE,
to_upper = FALSE,
utf_locale = "",
remove_char = "",
remove_punctuation_string = FALSE,
remove_punctuation_vector = FALSE,
remove_numbers = FALSE,
trim_token = FALSE,
split_string = FALSE,
split_separator = " \r\n\t.,;:()?!//",
remove_stopwords = FALSE,
language = "english",
min_num_char = 1,
max_num_char = Inf,
stemmer = NULL,
min_n_gram = 1,
max_n_gram = 1,
skip_n_gram = 1,
skip_distance = 0,
n_gram_delimiter = " ",
concat_delimiter = NULL,
path_2folder = "",
stemmer_ngram = 4,
stemmer_gamma = 0,
stemmer_truncate = 3,
stemmer_batches = 1,
threads = 1,
vocabulary_path_file = NULL,
verbose = FALSE
)a character vector
either a character string (text data) or a character-string-path to a file (for big .txt files it's recommended to use a path to a file).
a numeric value. If the batches parameter is not NULL then the object parameter should be a valid path to a file and the path_2folder parameter should be a valid path to a folder. The batches parameter should be used in case of small to medium data sets (for zero memory consumption). For big data sets the big_tokenize_transform R6 class and especially the big_text_tokenizer function should be used.
the delimiter to use when the input file will be red (for instance a tab-delimiter or a new-line delimiter).
either TRUE or FALSE. If TRUE the character string will be converted to lower case
either TRUE or FALSE. If TRUE the character string will be converted to upper case
the language specific locale to use in case that either the to_lower or the to_upper parameter is TRUE and the text file language is other than english. For instance if the language of a text file is greek then the utf_locale parameter should be 'el_GR.UTF-8' ( language_country.encoding ). A wrong utf-locale does not raise an error, however the runtime of the function increases.
a character string with specific characters that should be removed from the text file. If the remove_char is "" then no removal of characters take place
either TRUE or FALSE. If TRUE then the punctuation of the character string will be removed (applies before the split function)
either TRUE or FALSE. If TRUE then the punctuation of the vector of the character strings will be removed (after the string split has taken place)
either TRUE or FALSE. If TRUE then any numbers in the character string will be removed
either TRUE or FALSE. If TRUE then the string will be trimmed (left and/or right)
either TRUE or FALSE. If TRUE then the character string will be split using the split_separator as delimiter. The user can also specify multiple delimiters.
a character string specifying the character delimiter(s)
either TRUE, FALSE or a character vector of user defined stop words. If TRUE then by using the language parameter the corresponding stop words vector will be uploaded.
a character string which defaults to english. If the remove_stopwords parameter is TRUE then the corresponding stop words vector will be uploaded. Available languages are afrikaans, arabic, armenian, basque, bengali, breton, bulgarian, catalan, croatian, czech, danish, dutch, english, estonian, finnish, french, galician, german, greek, hausa, hebrew, hindi, hungarian, indonesian, irish, italian, latvian, marathi, norwegian, persian, polish, portuguese, romanian, russian, slovak, slovenian, somalia, spanish, swahili, swedish, turkish, yoruba, zulu
an integer specifying the minimum number of characters to keep. If the min_num_char is greater than 1 then character strings with more than 1 characters will be returned
an integer specifying the maximum number of characters to keep. The max_num_char should be less than or equal to Inf (in this function the Inf value translates to a word-length of 1000000000)
a character string specifying the stemming method. One of the following porter2_stemmer, ngram_sequential, ngram_overlap. See details for more information.
an integer specifying the minimum number of n-grams. The minimum number of min_n_gram is 1.
an integer specifying the maximum number of n-grams. The minimum number of max_n_gram is 1.
an integer specifying the number of skip-n-grams. The minimum number of skip_n_gram is 1. The skip_n_gram gives the (max.) n-grams using the skip_distance parameter. If skip_n_gram is greater than 1 then both min_n_gram and max_n_gram should be set to 1.
an integer specifying the skip distance between the words. The minimum value for the skip distance is 0, in which case simple n-grams will be returned.
a character string specifying the n-gram delimiter (applies to both n-gram and skip-n-gram cases)
either NULL or a character string specifying the delimiter to use in order to concatenate the end-vector of character strings to a single character string (recommended in case that the end-vector should be saved to a file)
a character string specifying the path to the folder where the file(s) will be saved
a numeric value greater than 1. Applies to both ngram_sequential and ngram_overlap methods. In case of ngram_sequential the first n characters will be picked, whereas in the case of ngram_overlap the overlapping stemmer_ngram characters will be build.
a float number greater or equal to 0.0. Applies only to ngram_sequential. Is a threshold value, which defines how much frequency deviation of two N-grams is acceptable. It is kept either zero or to a minimum value.
a numeric value greater than 0. Applies only to ngram_sequential. The ngram_sequential is modified to use relative frequencies (float numbers between 0.0 and 1.0 for the ngrams of a specific word in the corpus) and the stemmer_truncate parameter controls the number of rounding digits for the ngrams of the word. The main purpose was to give the same relative frequency to words appearing approximately the same on the corpus.
a numeric value greater than 0. Applies only to ngram_sequential. Splits the corpus into batches with the option to run the batches in multiple threads.
an integer specifying the number of cores to run in parallel
either NULL or a character string specifying the output path to a file where the vocabulary should be saved once the text is tokenized
either TRUE or FALSE. If TRUE then information will be printed out
It is memory efficient to read the data using a path file in case of a big file, rather than importing the data in the R-session and then calling the tokenize_transform_text function.
It is memory efficient to give a path_2folder in case that a big file should be saved, rather than return the vector of all character strings in the R-session.
The skip-grams are a generalization of n-grams in which the components (typically words) need not to be consecutive in the text under consideration, but may leave gaps that are skipped over. They provide one way of overcoming the data sparsity problem found with conventional n-gram analysis.
Many character string pre-processing functions (such as the utf-locale or the split-string function ) are based on the boost library ( https://www.boost.org/ ).
Stemming of the english language is done using the porter2-stemmer, for details see https://github.com/smassung/porter2_stemmer
N-gram stemming is language independent and supported by the following two functions:
The ngram_overlap stemming method is based on N-Gram Morphemes for Retrieval, Paul McNamee and James Mayfield, http://clef.isti.cnr.it/2007/working_notes/mcnameeCLEF2007.pdf
The ngram_sequential stemming method is a modified version based on Generation, Implementation and Appraisal of an N-gram based Stemming Algorithm, B. P. Pande, Pawan Tamta, H. S. Dhami, https://arxiv.org/pdf/1312.4824.pdf
The list of stop-words in the available languages was downloaded from the following link, https://github.com/6/stopwords-json
library(textTinyR)
token_str = "CONVERT to lower, remove.. punctuation11234, trim token and split "
res = tokenize_transform_text(object = token_str, to_lower = TRUE, split_string = TRUE)
Run the code above in your browser using DataLab