plone

R-sciplot-1.1.0-10.lbn25.noarch
A collection of functions that creates graphs with error bars for data collected from one-way or higher factorial designs
Located in LBN / … / Big Data / BastionLinux 25
R-snow-0.4.2-2.lbn25.noarch
Support for simple parallel computing in R.
Located in LBN / … / Big Data / BastionLinux 25
R-systemfit-1.1.15-10.lbn25.noarch
This R package contains functions for fitting simultaneous systems of linear and nonlinear equations using Ordinary Least Squares (OLS), Weighted Least Squares (WLS), Seemingly Unrelated Regressions (SUR), Two-Stage Least Squares (2SLS), Weighted Two-Stage Least Squares (W2SLS), Three-Stage Least Squares (3SLS), and Weighted Three-Stage Least Squares (W3SLS).
Located in LBN / … / Big Data / BastionLinux 25
R-timeDate-3010.98-7.lbn25.noarch
Environment for teaching Financial Engineering and Computational Finance.
Located in LBN / … / Big Data / BastionLinux 25
R-tkWidgets-1.42.0-5.lbn25.noarch
Widgets to provide user interfaces. tcltk should have been installed for the widgets to run. This package is a part of the bioconductor (bioconductor.org) project
Located in LBN / … / Big Data / BastionLinux 25
R-widgetTools-1.42.0-5.lbn25.noarch
This package contains tools to support the construction of tcltk widgets. This library is part of the bioconductor (bioconductor.org) project
Located in LBN / … / Big Data / BastionLinux 25
R-xtable-1.7.1-4.lbn25.noarch
Coerce data to LaTeX and HTML tables.
Located in LBN / … / Big Data / BastionLinux 25
meminfo-1.0.2-3.lbn25.noarch
meminfo was born out of a need to report large system memory usage in some meaningful way. ps and top have their uses, as do others, but they have two problems (in my opinion): 1) they don't show URES (unique resident size) 2) the information they provide is of limited value once you start having 1000+ processes on a multi-user system meminfo fills the gap (or aims to at least). Tested on 2.6 kernels and one 2.4 system (debian 3.1) --------------------------- meminfo is Copyright 2006 Aleksandr Koltsoff. meminfo is released under the GPLv2 in the hopes that it may be of use to other people (please see the accompanying COPYING file, or if the file is missing [bad!] you can find it at http://www.gnu.org/licenses/gpl.txt). --------------------------- generates three lists according to real memory usage: - first is sorted by URES per process - second one groups processes according to usernames and sorts that based on ures - third groups based on process names and again sorts based on total ures - fourth is optional and depends whether you have SMP-system or not tries to group memory and runtimes according to logical CPUs if you don't have SMP (enabled), you won't see the fourth report and the first report will be missing the C#-field (CPU that last executed a process). For explanation on URES, please see http://koltsoff.com/pub/ures/ For feedback and patches, please contact me via czr(at)iki(dot)fi while including 'meminfo' in the subject.
Located in LBN / … / Core Linux / BastionLinux 25
rubygem-hiera-3.4.2-1.lbn25.noarch
A pluggable data store for hierarcical data.
Located in LBN / … / Cloud Computing / BastionLinux 25
rubygem-hiera-aws-parameter-store-0.1.0-1.lbn25.noarch
Configuration hiera-aws-parameter-store configuration is quite simple. It uses default AWS connection and the following parameters: prefix : prefix used to find parameters in AWS Parameter Store. Mandatory. max_results : maximum number of results per AWS Parameter Store request. Default value is 50 (which is the maximum at 2017-01-21). Here is a sample hiera.yaml: --- :backends: - aws_parameter_store :aws_parameter_store: :prefix: puppet. :max_results: 50 :logger: console AWS credentials You need AWS credentials in order to access to AWS Parameter Store. The following policy shows you the required permissions: { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "ssm:DescribeParameters" ], "Resource": "*" }, { "Effect": "Allow", "Action": [ "ssm:GetParameters" ], "Resource": "arn:aws:ssm:{region}:{account}:parameter/{prefix}*" } ] } where: region: AWS region in which parameters are stored. account: your AWS account. prefix: prefix for those parameters you want to access from Hiera. E.g. if you want to organize your parameters starting with puppet., you have to use this as prefix. As an example, you can have parameters like: puppet.myapp.version. Conversions between AWS Parameter Store and Hiera types In AWS Parameter Store are present the following types: String: if the parameter name does not contains dots (.), the resulting hiera object is a String with parameter's value. If it contains dots, it's splitted and converted into a hash of objects with the last element as a string. String List: Converted into an array. Secure String: Not compatible yet. Examples: myappname=MyAppName (String) -> hiera('myappname') = "MyAppName" (String) myapp.name=MyAppName (String) myapp.version=1.3 (String) -> hiera_hash('myapp') = {"name"=>"MyAppName","version"=>"1.3"} (Hash) mylist=e1,e2,e3 (String List) -> hiera('mylist') = ["e1","e2","e3"] myapp.name=MyAppName (String) myapp.list=1,2,3 (String List) -> hiera_hash('myapp') = {"name"=>"MyAppName","list"=>["1",
Located in LBN / … / Cloud Computing / BastionLinux 25

« Previous 10 items Next 10 items » 1 ... 4573 4574 4575 4576 4577 4578 4579 ... 4852

Sections

Search results


	Copyright © 2000-2025 Corporation of Balclutha Inc. All rights reserved.