Model: dhruvnayee/help_texted_mined_r3s_0810
Author: dhruvnayee
Pipeline: sentence-similarity
Library: sentence-transformers
Tags: sentence-transformers, safetensors, bert, sentence-similarity, feature-extraction, dense, generated_from_trainer, dataset_size:16688, loss:TripletLoss, arxiv:1908.10084, arxiv:1703.07737, base_model:BAAI/bge-large-en-v1.5, base_model:finetune:BAAI/bge-large-en-v1.5, text-embeddings-inference, endpoints_compatible, region:us
Base models (finetune): id: BAAI/bge-large-en-v1.5
Card metadata: tags: sentence-transformers, sentence-similarity, feature-extraction, dense, generated_from_trainer, dataset_size:16688, loss:TripletLoss
base_model: BAAI/bge-large-en-v1.5
widget: source_sentence: Where do I select the build type in R³S Modeler?
sentences: ## Perform build on(requiresR³S Enterprise) The Perform build on drop-down list is not available when running a results workspace. You can use the Perform build on drop-down list to specify whether to use distributed processing to build (generate, compile, and link) the calculations specified in the batch or the model. You can select an option from the drop-down list: * Local: build the batch or the model on the current machine (the controller) without using distributed processing. * Remote: use distributed processing to build the batch or the model on one of the remote machines (a worker). This is useful when you do not want to occupy the controller with these tasks. If you build or run a batch or a model, R³S Modeler uses the value of the Perform build on property of the batch or model as the default value of the drop-down list. R³S Modeler uses the value of the Perform build on drop-down list to set the value of the Perform build on property of the batch or the model in the results workspace. You can specify the connector to use for distributed processing on the Distribution tab of the Options dialog box. For the Remote option to use distributed processing, you must use the Microsoft® HPC Pack connector or the Azure® Batch connector., Server hierarchy The Server hierarchy property is a property of the following components: - **Development sandbox workspace or approval sandbox workspace(requiresR³S Development Manager)**: The Server hierarchy property of a development sandbox workspace or an approval sandbox workspace shows the name of the sandbox, branch, and library with which you associated the workspace. - **Snapshot workspace(requiresR³S Development Manager)**: The Server hierarchy property of a snapshot workspace shows the name of the changeset, label, or sandbox, the branch, and the library from which you created the snapshot., Result grid The result grid of the Analyzer tab of a results workspace shows the results at different calculation dates for the current variable, the variables that it depends on, and the variables that depend on it if these results are available in sample output. The result grid is more useful for analyzing layers than data layers, because a data layer has only one calculation date, corresponding to the portfolio date of the model or model alias. Each scalar numeric and indicator variable has a checkbox before its name. Selecting one of these checkboxes clears the others. In the graph pane, R³S Modeler graphs the results for the variable whose checkbox you select. If events occur in a projection step of a layer, R³S Modeler shows these in pink in the result grid. To hide the results for the events, select the Hide events checkbox. This also stops events from being indicated by the green vertical line in the graph pane. If loops occur in a projection step of a layer, R³S Modeler shows these in blue in the result grid. To hide the results for the loops, select the Hide loops checkbox. Because loop variables have no time associated with them, they are never shown in the graph pane. Selecting the Hide events checkbox to hide event results or the Hide loops checkbox to hide loop results does not affect the results; it just hides them in the result grid. With these checkboxes selected, it might not be easy to understand the calculation of non-portfolio variables that are summed across event dates in the step or how the final values of loop variables have been extracted into step variables. The dependency diagram still shows all the precedents and is not affected by the checkboxes. The result grid shows the variable being analyzed in its first row. Precedent variables are shown immediately beneath the chosen variable, and dependent variables are shown below these. The currently selected date is highlighted with a yellow box. Yellow boxes also highlight the variable being analyzed and its precedents and dependents. Highlighting a cell in the result grid and pressing the Enter key makes the corresponding variable and date the subject of the analysis. You can also do this by right-clicking in the result grid and choosing Analyze from the context menu. Highlighting a cell in the result grid and pressing the Home key makes the corresponding variable the subject of the analysis at the layer start date. You can also do this by right-clicking in the result grid and choo, source_sentence: Are MtF views supported in R³S Modeler?
sentences: ## Properties - **MtF views**: - **General**: Name - **Filters**: Filter formula - **Data inputs**: File format - **MtF cube**: MtF view type - **Auditing**: Last modified - **Sub MtF views**: - **General**: Sub MtF view The other properties of a sub MtF view are the same as those of the underlying MtF view. - **MtF view variables**: - **General**: Variable - **Formula**: Formula - **Auditing**: Last modified Additionally, the properties of the variable specified in the Variable property are inherited as global properties., ## Remarks This function acts like the Choose_Life_Table function followed by the Reduce_Life_Table function. It avoids the need to use a separate life table variable to store the chosen life table before reducing it. When you use this function in the formula of a variable, that formula can contain nothing outside the call to this function. This means that you cannot include the function call as part of a larger expression in a single formula. Instead, you can use a variable to call the function and then refer to this variable in the formula of another variable. The function first uses the character expression to select a life table in the workspace by name. R³S Modeler knows how many dimensions the life table should have by counting the number of arguments. If there are no arguments for the additional dimensions then there should be just two dimensions: * Select_Duration should be dimension 1 with start position 0 and * Age should be dimension 2 with start position 0. If there are no life tables in the workspace with these dimensions and, where applicable, the dimension names and start positions you specify for dimensions 3, 4 and 5 then a generator error occurs. If the life table named in the character expression does not have the dimension names and start positions you specify then a runtime error occurs. Then the function removes any dimensions in addition to the mandatory Select_Duration and Age dimensions by selecting only the life table rates corresponding to the specified element position in each of the additional dimensions. This is similar to using the Slice function repeatedly. This then leaves a 2-dimensional life table for the function to reduce further. Suppose that: * The Select_Duration dimension has size r (corresponding to a select period of r-1). * The Age dimension has size n (corresponding to a maximum age of n-1). * Qx(x, t) denotes the select rate for current age x and current select duration t (t < r-1). * Qx(x, ) denotes the ultimate rate for current age x. * y is an integer that specifies the age at entry. The function returns a reduced life table with dimensions: * Select_Duration of size 1 and start position 0 and * Age of size n and start position 0. If y is in the select age range of the life table (greater than or equal to the value of the Minimum select age property and less than or equal to the value of the Maximum select age property) then the life table rates in the reduced life table are: | Select_Duration Age | 0 0 | 0, The main topic 'Layers' has the following related sub-topics: * **Layer examples** : The example user workspace includes examples of layers., source_sentence: What data structure is required for the 'Array' argument?
sentences: Maximum select age The Maximum select age property is a property of the following component: * Life table You can use this mandatory property to specify the highest age at entry for which select rates are available in the life table. R³S Modeler uses ultimate rates for ages at entry above this age. You can specify an integer greater than or equal to 0 and less than or equal to 200. The value you specify should be greater than or equal to the value of the Minimum select age property. When the size of the Select_Duration dimension of the life table is 1, the value you specify should be less than or equal to the size of the Age dimension minus 1 (that is, the maximum age of the life table), though this property makes no difference in this situation, because there are no select rates in the life table. When the size of the Select_Duration dimension is greater than 1, the value you specify should be less than or equal to the size of the Age dimension minus the size of the Select_Duration dimension plus 1 (that is, the maximum age of the life table plus 1 minus the select period of the life table) to as to give enough element positions in the Age dimension for the select rates for this maximum select age at entry., ## Circumstances The formula for the specified variable contains a Move_Left or Move_Right function call - say Move_Left(Array_1, <Dimension>, Array_2) or Move_Right(Array_1, <Dimension>, Array_2). The function call is invalid because the dimension start positions of Array_2 (the 'replacement' array to be attached to Array_1) do not all match the start positions of the corresponding dimensions of Array_1., ## Arguments Array | An array variable or expression. Dimension | A dimension name of the arrayArray. The dimension must have at least one index value that is not blank., source_sentence: How does R3S Modeler handle non-integer arguments when the data type is indicator?
sentences: ## Remarks When you use the Range function in a formula or other property whose data type is numeric or indicator, all three arguments should be numeric or indicator expressions. When the data type of the formula or other property is indicator, R³S Modeler rounds values of the arguments that are not integers towards zero to give integers. When the data type of the formula or other property is date, the first two arguments should be date expressions. You can combine sequences of values from different calls to the Range and Set functions by separating the function calls with a semicolon (;). You can use the Range and Set functions in the Formula property of variables in a data view, database view or MtF view to produce multiple copies of each data record, which can be useful for producing test data., Pareto (not available in R³S Modeler Lite ) Returns values relating to the Pareto distribution., ## Circumstances Division of an indicator variable by zero has been attempted., source_sentence: What inputs does Qx accept?
sentences: ## Examples q | =Qx(58, , LT) q | =Qx(59+1, 1, LT), Invalid Target Variable Message: '<name>' cannot be an array because it is the target input range., ## Circumstances The definition of a user function has no arguments defined.
pipeline_tag: sentence-similarity
library_name: sentence-transformers
Likes: 0 | All-time downloads: 18
Created: 2025-10-08 14:18:28