Configuration Reference
Configuration Reference
This page is autogenerated; any changes will get overwritten (last generated on Thu Jul 11 16:50:19 -0700 2013)
Configuration Settings
- Each of these settings can be specified in
puppet.conf
or on the command line. - When using boolean settings on the command line, use
--setting
and--no-setting
instead of--setting (true|false)
. - Settings can be interpolated as
$variables
in other settings;$environment
is special, in that puppet master will interpolate each agent node’s environment instead of its own. - Multiple values should be specified as comma-separated lists; multiple directories should be separated with the system path separator (usually a colon).
- Settings that represent time intervals should be specified in duration format: an integer immediately followed by one of the units ‘y’ (years of 365 days), ‘d’ (days), ‘h’ (hours), ‘m’ (minutes), or ‘s’ (seconds). The unit cannot be combined with other units, and defaults to seconds when omitted. Examples are ‘3600’ which is equivalent to ‘1h’ (one hour), and ‘1825d’ which is equivalent to ‘5y’ (5 years).
- Settings that take a single file or directory can optionally set the owner,
group, and mode for their value:
rundir = $vardir/run { owner = puppet, group = puppet, mode = 644 }
- The Puppet executables will ignore any setting that isn’t relevant to their function.
See the configuration guide for more details.
agent_catalog_run_lockfile
A lock file to indicate that a puppet agent catalog run is currently in progress. The file contains the pid of the process that holds the lock on the catalog run.
- Default: $statedir/agent_catalog_run.lock
agent_disabled_lockfile
A lock file to indicate that puppet agent runs have been administratively disabled. File contains a JSON object with state information.
- Default: $statedir/agent_disabled.lock
allow_duplicate_certs
Whether to allow a new certificate request to overwrite an existing certificate.
- Default: false
allow_variables_with_dashes
Permit hyphens (-
) in variable names and issue deprecation warnings about them. This setting should always be false
; setting it to true
will cause subtle and wide-ranging bugs. It will be removed in a future version. Hyphenated variables caused major problems in the language, but were allowed between Puppet 2.7.3 and 2.7.14. If you used them during this window, we apologize for the inconvenience — you can temporarily set this to true
in order to upgrade, and can rename your variables at your leisure. Please revert it to false
after you have renamed all affected variables.
- Default: false
archive_file_server
During an inspect run, the file bucket server to archive files to if archive_files is set.
- Default: $server
archive_files
During an inspect run, whether to archive files whose contents are audited to a file bucket.
- Default: false
async_storeconfigs
Whether to use a queueing system to provide asynchronous database integration. Requires that puppet queue
be running.
- Default: false
autoflush
Whether log files should always flush to disk.
- Default: true
autosign
Whether to enable autosign. Valid values are true (which autosigns any key request, and is a very bad idea), false (which never autosigns any key request), and the path to a file, which uses that configuration file to determine which keys to sign.
- Default: $confdir/autosign.conf
bindaddress
The address a listening server should bind to.
- Default: <IP_ADDRESS>
bucketdir
Where FileBucket files are stored.
- Default: $vardir/bucket
ca
Whether the master should function as a certificate authority.
- Default: true
ca_name
The name to use the Certificate Authority certificate.
- Default: Puppet CA: $certname
ca_port
The port to use for the certificate authority.
- Default: $masterport
ca_server
The server to use for certificate authority requests. It’s a separate server because it cannot and does not need to horizontally scale.
- Default: $server
ca_ttl
The default TTL for new certificates. If this setting is set, ca_days is ignored. This setting can be a time interval in seconds (30 or 30s), minutes (30m), hours (6h), days (2d), or years (5y).
- Default: 5y
cacert
The CA certificate.
- Default: $cadir/ca_crt.pem
cacrl
The certificate revocation list (CRL) for the CA. Will be used if present but otherwise ignored.
- Default: $cadir/ca_crl.pem
cadir
The root directory for the certificate authority.
- Default: $ssldir/ca
cakey
The CA private key.
- Default: $cadir/ca_key.pem
capass
Where the CA stores the password for the private key
- Default: $caprivatedir/ca.pass
caprivatedir
Where the CA stores private certificate information.
- Default: $cadir/private
capub
The CA public key.
- Default: $cadir/ca_pub.pem
catalog_cache_terminus
How to store cached catalogs. Valid values are ‘json’ and ‘yaml’. The agent application defaults to ‘json’.
- Default:
catalog_format
(Deprecated for ‘preferred_serialization_format’) What format to use to dump the catalog. Only supports ‘marshal’ and ‘yaml’. Only matters on the client, since it asks the server for a specific format.
catalog_terminus
Where to get node catalogs. This is useful to change if, for instance, you’d like to pre-compile catalogs and store them in memcached or some other easily-accessed store.
- Default: compiler
cert_inventory
A Complete listing of all certificates
- Default: $cadir/inventory.txt
certdir
The certificate directory.
- Default: $ssldir/certs
certdnsnames
The certdnsnames
setting is no longer functional, after CVE-2011-3872. We ignore the value completely. For your own certificate request you can set dns_alt_names
in the configuration and it will apply locally. There is no configuration option to set DNS alt names, or any other subjectAltName
value, for another nodes certificate. Alternately you can use the --dns_alt_names
command line option to set the labels added while generating your own CSR.
certificate_expire_warning
The window of time leading up to a certificate’s expiration that a notification will be logged. This applies to CA, master, and agent certificates. This setting can be a time interval in seconds (30 or 30s), minutes (30m), hours (6h), days (2d), or years (5y).
- Default: 60d
certificate_revocation
Whether certificate revocation should be supported by downloading a Certificate Revocation List (CRL) to all clients. If enabled, CA chaining will almost definitely not work.
- Default: true
certname
The name to use when handling certificates. Defaults to the fully qualified domain name.
- Default: (the system’s fully qualified domain name)
classfile
The file in which puppet agent stores a list of the classes associated with the retrieved configuration. Can be loaded in the separate puppet
executable using the --loadclasses
option.
- Default: $statedir/classes.txt
client_datadir
The directory in which serialized data is stored on the client.
- Default: $vardir/client_data
clientbucketdir
Where FileBucket files are stored locally.
- Default: $vardir/clientbucket
clientyamldir
The directory in which client-side YAML data is stored.
- Default: $vardir/client_yaml
code
Code to parse directly. This is essentially only used by puppet
, and should only be set if you’re writing your own Puppet executable
color
Whether to use colors when logging to the console. Valid values are ansi
(equivalent to true
), html
, and false
, which produces no color. Defaults to false on Windows, as its console does not support ansi colors.
- Default: ansi
confdir
The main Puppet configuration directory. The default for this setting is calculated based on the user. If the process is running as root or the user that Puppet is supposed to run as, it defaults to a system directory, but if it’s running as any other user, it defaults to being in the user’s home directory.
- Default: /etc/puppet
config
The configuration file for the current puppet application
- Default: $confdir/${config_file_name}
config_file_name
The name of the puppet config file.
- Default: puppet.conf
config_version
How to determine the configuration version. By default, it will be the time that the configuration is parsed, but you can provide a shell script to override how the version is determined. The output of this script will be added to every log message in the reports, allowing you to correlate changes on your hosts to the source version on the server.
configprint
Print the value of a specific configuration setting. If the name of a setting is provided for this, then the value is printed and puppet exits. Comma-separate multiple values. For a list of all values, specify ‘all’.
configtimeout
How long the client should wait for the configuration to be retrieved before considering it a failure. This can help reduce flapping if too many clients contact the server at one time. This setting can be a time interval in seconds (30 or 30s), minutes (30m), hours (6h), days (2d), or years (5y).
- Default: 2m
couchdb_url
The url where the puppet couchdb database will be created. Only used when facts_terminus
is set to couch
.
- Default: http://<IP_ADDRESS>:5984/puppet
csrdir
Where the CA stores certificate requests
- Default: $cadir/requests
daemonize
Whether to send the process into the background. This defaults to true on POSIX systems, and to false on Windows (where Puppet currently cannot daemonize).
- Default: true
data_binding_terminus
Where to retrive information about data.
- Default: hiera
dbadapter
The type of database to use. This setting is only used by the ActiveRecord storeconfigs and inventory backends, which are deprecated.
- Default: sqlite3
dbconnections
The number of database connections for networked databases. Will be ignored unless the value is a positive integer. This setting is only used by the ActiveRecord storeconfigs and inventory backends, which are deprecated.
dblocation
The sqlite database file. This setting is only used by the ActiveRecord storeconfigs and inventory backends, which are deprecated.
- Default: $statedir/clientconfigs.sqlite3
dbmigrate
Whether to automatically migrate the database. This setting is only used by the ActiveRecord storeconfigs and inventory backends, which are deprecated.
- Default: false
dbname
The name of the database to use. This setting is only used by the ActiveRecord storeconfigs and inventory backends, which are deprecated.
- Default: puppet
dbpassword
The database password for caching. Only used when networked databases are used. This setting is only used by the ActiveRecord storeconfigs and inventory backends, which are deprecated.
- Default: puppet
dbport
The database password for caching. Only used when networked databases are used. This setting is only used by the ActiveRecord storeconfigs and inventory backends, which are deprecated.
dbserver
The database server for caching. Only used when networked databases are used.
- Default: localhost
dbsocket
The database socket location. Only used when networked databases are used. Will be ignored if the value is an empty string. This setting is only used by the ActiveRecord storeconfigs and inventory backends, which are deprecated.
dbuser
The database user for caching. Only used when networked databases are used. This setting is only used by the ActiveRecord storeconfigs and inventory backends, which are deprecated.
- Default: puppet
default_file_terminus
The default source for files if no server is given in a uri, e.g. puppet:///file. The default of rest
causes the file to be retrieved using the server
setting. When running apply
the default is file_server
, causing requests to be filled locally.
- Default: rest
deviceconfig
Path to the device config file for puppet device
- Default: $confdir/device.conf
devicedir
The root directory of devices’ $vardir
- Default: $vardir/devices
diff
Which diff command to use when printing differences between files. This setting has no default value on Windows, as standard diff
is not available, but Puppet can use many third-party diff tools.
- Default: diff
diff_args
Which arguments to pass to the diff command when printing differences between files. The command to use can be chosen with the diff
setting.
- Default: -u
dns_alt_names
The comma-separated list of alternative DNS names to use for the local host. When the node generates a CSR for itself, these are added to the request as the desired subjectAltName
in the certificate: additional DNS labels that the certificate is also valid answering as. This is generally required if you use a non-hostname certname
, or if you want to use puppet kick
or puppet resource -H
and the primary certname does not match the DNS name you use to communicate with the host. This is unnecessary for agents, unless you intend to use them as a server for puppet kick
or remote puppet resource
management. It is rarely necessary for servers; it is usually helpful only if you need to have a pool of multiple load balanced masters, or for the same master to respond on two physically separate networks under different names.
document_all
Whether to document all resources when using puppet doc
to generate manifest documentation.
- Default: false
dynamicfacts
(Deprecated) Facts that are dynamic; these facts will be ignored when deciding whether changed facts should result in a recompile. Multiple facts should be comma-separated.
- Default: memorysize,memoryfree,swapsize,swapfree
environment
The environment Puppet is running in. For clients (e.g., puppet agent
) this determines the environment itself, which is used to find modules and much more. For servers (i.e., puppet master
) this provides the default environment for nodes we know nothing about.
- Default: production
evaltrace
Whether each resource should log when it is being evaluated. This allows you to interactively see exactly what is being done.
- Default: false
external_nodes
An external command that can produce node information. The command’s output must be a YAML dump of a hash, and that hash must have a classes
key and/or a parameters
key, where classes
is an array or hash and parameters
is a hash. For unknown nodes, the command should exit with a non-zero exit code. This command makes it straightforward to store your node mapping information in other data sources like databases.
- Default: none
factpath
Where Puppet should look for facts. Multiple directories should be separated by the system path separator character. (The POSIX path separator is ‘:’, and the Windows path separator is ‘;’.)
- Default: $vardir/lib/facter:$vardir/facts
facts_terminus
The node facts terminus.
- Default: facter
fileserverconfig
Where the fileserver configuration is stored.
- Default: $confdir/fileserver.conf
filetimeout
The minimum time to wait between checking for updates in configuration files. This timeout determines how quickly Puppet checks whether a file (such as manifests or templates) has changed on disk. This setting can be a time interval in seconds (30 or 30s), minutes (30m), hours (6h), days (2d), or years (5y).
- Default: 15s
freeze_main
Freezes the ‘main’ class, disallowing any code to be added to it. This essentially means that you can’t have any code outside of a node, class, or definition other than in the site manifest.
- Default: false
genconfig
Whether to just print a configuration to stdout and exit. Only makes sense when used interactively. Takes into account arguments specified on the CLI.
- Default: false
genmanifest
Whether to just print a manifest to stdout and exit. Only makes sense when used interactively. Takes into account arguments specified on the CLI.
- Default: false
graph
Whether to create dot graph files for the different configuration graphs. These dot files can be interpreted by tools like OmniGraffle or dot (which is part of ImageMagick).
- Default: false
graphdir
Where to store dot-outputted graphs.
- Default: $statedir/graphs
group
The group puppet master should run as.
- Default: puppet
hiera_config
The hiera configuration file. Puppet only reads this file on startup, so you must restart the puppet master every time you edit it.
- Default: $confdir/hiera.yaml
hostcert
Where individual hosts store and look for their certificates.
- Default: $certdir/$certname.pem
hostcrl
Where the host’s certificate revocation list can be found. This is distinct from the certificate authority’s CRL.
- Default: $ssldir/crl.pem
hostcsr
Where individual hosts store and look for their certificate requests.
- Default: $ssldir/csr_$certname.pem
hostprivkey
Where individual hosts store and look for their private key.
- Default: $privatekeydir/$certname.pem
hostpubkey
Where individual hosts store and look for their public key.
- Default: $publickeydir/$certname.pem
http_compression
Allow http compression in REST communication with the master. This setting might improve performance for agent -> master communications over slow WANs.  It is harmless to activate this settings if your master doesn’t support compression, but if it supports it, this setting might reduce performance on high-speed LANs.
- Default: false
http_proxy_host
The HTTP proxy host to use for outgoing connections. Note: You may need to use a FQDN for the server hostname when using a proxy.
- Default: none
http_proxy_port
The HTTP proxy port to use for outgoing connections
- Default: 3128
httplog
Where the puppet agent web server logs.
- Default: $logdir/http.log
ignorecache
Ignore cache and always recompile the configuration. This is useful for testing new configurations, where the local cache may in fact be stale even if the timestamps are up to date - if the facts change or if the server changes.
- Default: false
ignoreimport
If true, allows the parser to continue without requiring all files referenced with import
statements to exist. This setting was primarily designed for use with commit hooks for parse-checking.
- Default: false
ignoremissingtypes
Skip searching for classes and definitions that were missing during a prior compilation. The list of missing objects is maintained per-environment and persists until the environment is cleared or the master is restarted.
- Default: false
ignoreschedules
Boolean; whether puppet agent should ignore schedules. This is useful for initial puppet agent runs.
- Default: false
inventory_port
The port to communicate with the inventory_server.
- Default: $masterport
inventory_server
The server to send facts to.
- Default: $server
inventory_terminus
Should usually be the same as the facts terminus
- Default: $facts_terminus
keylength
The bit length of keys.
- Default: 4096
lastrunfile
Where puppet agent stores the last run report summary in yaml format.
- Default: $statedir/last_run_summary.yaml
lastrunreport
Where puppet agent stores the last run report in yaml format.
- Default: $statedir/last_run_report.yaml
ldapattrs
The LDAP attributes to include when querying LDAP for nodes. All returned attributes are set as variables in the top-level scope. Multiple values should be comma-separated. The value ‘all’ returns all attributes.
- Default: all
ldapbase
The search base for LDAP searches. It’s impossible to provide a meaningful default here, although the LDAP libraries might have one already set. Generally, it should be the ‘ou=Hosts’ branch under your main directory.
ldapclassattrs
The LDAP attributes to use to define Puppet classes. Values should be comma-separated.
- Default: puppetclass
ldapparentattr
The attribute to use to define the parent node.
- Default: parentnode
ldappassword
The password to use to connect to LDAP.
ldapport
The LDAP port. Only used if node_terminus
is set to ldap
.
- Default: 389
ldapserver
The LDAP server. Only used if node_terminus
is set to ldap
.
- Default: ldap
ldapssl
Whether SSL should be used when searching for nodes. Defaults to false because SSL usually requires certificates to be set up on the client side.
- Default: false
ldapstackedattrs
The LDAP attributes that should be stacked to arrays by adding the values in all hierarchy elements of the tree. Values should be comma-separated.
- Default: puppetvar
ldapstring
The search string used to find an LDAP node.
- Default: (&(objectclass=puppetClient)(cn=%s))
ldaptls
Whether TLS should be used when searching for nodes. Defaults to false because TLS usually requires certificates to be set up on the client side.
- Default: false
ldapuser
The user to use to connect to LDAP. Must be specified as a full DN.
libdir
An extra search path for Puppet. This is only useful for those files that Puppet will load on demand, and is only guaranteed to work for those cases. In fact, the autoload mechanism is responsible for making sure this directory is in Ruby’s search path
- Default: $vardir/lib
listen
Whether puppet agent should listen for connections. If this is true, then puppet agent will accept incoming REST API requests, subject to the default ACLs and the ACLs set in the rest_authconfig
file. Puppet agent can respond usefully to requests on the run
, facts
, certificate
, and resource
endpoints.
- Default: false
localcacert
Where each client stores the CA certificate.
- Default: $certdir/ca.pem
localconfig
Where puppet agent caches the local configuration. An extension indicating the cache format is added automatically.
- Default: $statedir/localconfig
logdir
The directory in which to store log files
- Default:
manage_internal_file_permissions
Whether Puppet should manage the owner, group, and mode of files it uses internally
- Default: true
manifest
The entry-point manifest for puppet master.
- Default: $manifestdir/site.pp
manifestdir
Where puppet master looks for its manifests.
- Default: $confdir/manifests
masterhttplog
Where the puppet master web server logs.
- Default: $logdir/masterhttp.log
masterlog
Where puppet master logs. This is generally not used, since syslog is the default log destination.
- Default: $logdir/puppetmaster.log
masterport
The port for puppet master traffic. For puppet master, this is the port to listen on; for puppet agent, this is the port to make requests on. Both applications use this setting to get the port.
- Default: 8140
max_deprecations
Sets the max number of logged/displayed parser validation deprecation warnings in case multiple errors have been detected. A value of 0 is the same as value 1. The count is per manifest.
- Default: 10
max_errors
Sets the max number of logged/displayed parser validation errors in case multiple errors have been detected. A value of 0 is the same as value 1. The count is per manifest.
- Default: 10
max_warnings
Sets the max number of logged/displayed parser validation warnings in case multiple errors have been detected. A value of 0 is the same as value 1. The count is per manifest.
- Default: 10
maximum_uid
The maximum allowed UID. Some platforms use negative UIDs but then ship with tools that do not know how to handle signed ints, so the UIDs show up as huge numbers that can then not be fed back into the system. This is a hackish way to fail in a slightly more useful way when that happens.
- Default:<PHONE_NUMBER>
mkusers
Whether to create the necessary user and group that puppet agent will run as.
- Default: false
module_repository
The module repository
- Default: https://forge.puppetlabs.com
module_working_dir
The directory into which module tool data is stored
- Default: $vardir/puppet-module
modulepath
The search path for modules, as a list of directories separated by the system path separator character. (The POSIX path separator is ‘:’, and the Windows path separator is ‘;’.)
- Default: $confdir/modules:/usr/share/puppet/modules
name
The name of the application, if we are running as one. The default is essentially $0 without the path or .rb
.
- Default:
node_cache_terminus
How to store cached nodes. Valid values are (none), ‘json’, ‘yaml’ or write only yaml (‘write_only_yaml’). The master application defaults to ‘write_only_yaml’, all others to none.
- Default:
node_name
How the puppet master determines the client’s identity and sets the ‘hostname’, ‘fqdn’ and ‘domain’ facts for use in the manifest, in particular for determining which ‘node’ statement applies to the client. Possible values are ‘cert’ (use the subject’s CN in the client’s certificate) and ‘facter’ (use the hostname that the client reported in its facts)
- Default: cert
node_name_fact
The fact name used to determine the node name used for all requests the agent makes to the master. WARNING: This setting is mutually exclusive with node_name_value. Changing this setting also requires changes to the default auth.conf configuration on the Puppet Master. Please see http://links.puppetlabs.com/node_name_fact for more information.
node_name_value
The explicit value used for the node name for all requests the agent makes to the master. WARNING: This setting is mutually exclusive with node_name_fact. Changing this setting also requires changes to the default auth.conf configuration on the Puppet Master. Please see http://links.puppetlabs.com/node_name_value for more information.
- Default: $certname
node_terminus
Where to find information about nodes.
- Default: plain
noop
Whether puppet agent should be run in noop mode.
- Default: false
onetime
Run the configuration once, rather than as a long-running daemon. This is useful for interactively running puppetd.
- Default: false
parser
Selects the parser to use for parsing puppet manifests (in puppet DSL language/’.pp’ files). Available choices are ‘current’ (the default), and ‘future’. The ‘curent’ parser means that the released version of the parser should be used. The ‘future’ parser is a “time travel to the future” allowing early exposure to new language features. What these fatures are will vary from release to release and they may be invididually configurable. Available Since Puppet 3.2.
- Default: current
passfile
Where puppet agent stores the password for its private key. Generally unused.
- Default: $privatedir/password
path
The shell search path. Defaults to whatever is inherited from the parent process.
- Default: none
pidfile
The file containing the PID of a running process. This file is intended to be used by service management frameworks and monitoring systems to determine if a puppet process is still in the process table.
- Default: $rundir/${run_mode}.pid
plugindest
Where Puppet should store plugins that it pulls down from the central server.
- Default: $libdir
pluginsignore
What files to ignore when pulling down plugins.
- Default: .svn CVS .git
pluginsource
From where to retrieve plugins. The standard Puppet file
type is used for retrieval, so anything that is a valid file source can be used here.
- Default: puppet://$server/plugins
pluginsync
Whether plugins should be synced with the central server.
- Default: true
postrun_command
A command to run after every agent run. If this command returns a non-zero return code, the entire Puppet run will be considered to have failed, even though it might have performed work during the normal run.
preferred_serialization_format
The preferred means of serializing ruby instances for passing over the wire. This won’t guarantee that all instances will be serialized using this method, since not all classes can be guaranteed to support this format, but it will be used for all classes that support it.
- Default: pson
prerun_command
A command to run before every agent run. If this command returns a non-zero return code, the entire Puppet run will fail.
privatedir
Where the client stores private certificate information.
- Default: $ssldir/private
privatekeydir
The private key directory.
- Default: $ssldir/private_keys
profile
Whether to enable experimental performance profiling
- Default: false
publickeydir
The public key directory.
- Default: $ssldir/public_keys
puppetdlog
The log file for puppet agent. This is generally not used.
- Default: $logdir/puppetd.log
puppetport
Which port puppet agent listens on.
- Default: 8139
queue_source
Which type of queue to use for asynchronous processing. If your stomp server requires authentication, you can include it in the URI as long as your stomp client library is at least 1.1.1
- Default: stomp://localhost:61613/
queue_type
Which type of queue to use for asynchronous processing.
- Default: stomp
rails_loglevel
The log level for Rails connections. The value must be a valid log level within Rails. Production environments normally use info
and other environments normally use debug
. This setting is only used by the ActiveRecord storeconfigs and inventory backends, which are deprecated.
- Default: info
railslog
Where Rails-specific logs are sent. This setting is only used by the ActiveRecord storeconfigs and inventory backends, which are deprecated.
- Default: $logdir/rails.log
report
Whether to send reports after every transaction.
- Default: true
report_port
The port to communicate with the report_server.
- Default: $masterport
report_server
The server to send transaction reports to.
- Default: $server
reportdir
The directory in which to store reports received from the client. Each client gets a separate subdirectory.
- Default: $vardir/reports
reportfrom
The ‘from’ email address for the reports.
- Default: report@(the system’s fully qualified domain name)
reports
The list of reports to generate. All reports are looked for in puppet/reports/name.rb
, and multiple report names should be comma-separated (whitespace is okay).
- Default: store
reporturl
The URL used by the http reports processor to send reports
- Default: http://localhost:3000/reports/upload
req_bits
The bit length of the certificates.
- Default: 4096
requestdir
Where host certificate requests are stored.
- Default: $ssldir/certificate_requests
resourcefile
The file in which puppet agent stores a list of the resources associated with the retrieved configuration.
- Default: $statedir/resources.txt
rest_authconfig
The configuration file that defines the rights to the different rest indirections. This can be used as a fine-grained authorization system for puppet master
.
- Default: $confdir/auth.conf
route_file
The YAML file containing indirector route configuration.
- Default: $confdir/routes.yaml
rrddir
The directory where RRD database files are stored. Directories for each reporting host will be created under this directory.
- Default: $vardir/rrd
rrdinterval
How often RRD should expect data. This should match how often the hosts report back to the server. This setting can be a time interval in seconds (30 or 30s), minutes (30m), hours (6h), days (2d), or years (5y).
- Default: $runinterval
rundir
Where Puppet PID files are kept.
- Default:
runinterval
How often puppet agent applies the catalog. Note that a runinterval of 0 means “run continuously” rather than “never run.” If you want puppet agent to never run, you should start it with the --no-client
option. This setting can be a time interval in seconds (30 or 30s), minutes (30m), hours (6h), days (2d), or years (5y).
- Default: 30m
sendmail
Where to find the sendmail binary with which to send email.
- Default: /usr/sbin/sendmail
serial
Where the serial number for certificates is stored.
- Default: $cadir/serial
server
The server to which the puppet agent should connect
- Default: puppet
server_datadir
The directory in which serialized data is stored, usually in a subdirectory.
- Default: $vardir/server_data
show_diff
Whether to log and report a contextual diff when files are being replaced. This causes partial file contents to pass through Puppet’s normal logging and reporting system, so this setting should be used with caution if you are sending Puppet’s reports to an insecure destination. This feature currently requires the diff/lcs
Ruby library.
- Default: false
signeddir
Where the CA stores signed certificates.
- Default: $cadir/signed
smtpserver
The server through which to send email reports.
- Default: none
splay
Whether to sleep for a pseudo-random (but consistent) amount of time before a run.
- Default: false
splaylimit
The maximum time to delay before runs. Defaults to being the same as the run interval. This setting can be a time interval in seconds (30 or 30s), minutes (30m), hours (6h), days (2d), or years (5y).
- Default: $runinterval
srv_domain
The domain which will be queried to find the SRV records of servers to use.
- Default: (the system’s own domain)
ssl_client_ca_auth
Certificate authorities who issue server certificates. SSL servers will not be considered authentic unless they posses a certificate issued by an authority listed in this file. If this setting has no value then the Puppet master’s CA certificate (localcacert) will be used.
- Default:
ssl_client_header
The header containing an authenticated client’s SSL DN. This header must be set by the proxy to the authenticated client’s SSL DN (e.g., /CN=puppet.puppetlabs.com
). Puppet will parse out the Common Name (CN) from the Distinguished Name (DN) and use the value of the CN field for authorization. Note that the name of the HTTP header gets munged by the web server common gateway inteface: an HTTP_
prefix is added, dashes are converted to underscores, and all letters are uppercased. Thus, to use the X-Client-DN
header, this setting should be HTTP_X_CLIENT_DN
.
- Default: HTTP_X_CLIENT_DN
ssl_client_verify_header
The header containing the status message of the client verification. This header must be set by the proxy to ‘SUCCESS’ if the client successfully authenticated, and anything else otherwise. Note that the name of the HTTP header gets munged by the web server common gateway inteface: an HTTP_
prefix is added, dashes are converted to underscores, and all letters are uppercased. Thus, to use the X-Client-Verify
header, this setting should be HTTP_X_CLIENT_VERIFY
.
- Default: HTTP_X_CLIENT_VERIFY
ssl_server_ca_auth
Certificate authorities who issue client certificates. SSL clients will not be considered authentic unless they posses a certificate issued by an authority listed in this file. If this setting has no value then the Puppet master’s CA certificate (localcacert) will be used.
- Default:
ssldir
Where SSL certificates are kept.
- Default: $confdir/ssl
statedir
The directory where Puppet state is stored. Generally, this directory can be removed without causing harm (although it might result in spurious service restarts).
- Default: $vardir/state
statefile
Where puppet agent and puppet master store state associated with the running configuration. In the case of puppet master, this file reflects the state discovered through interacting with clients.
- Default: $statedir/state.yaml
storeconfigs
Whether to store each client’s configuration, including catalogs, facts, and related data. This also enables the import and export of resources in the Puppet language - a mechanism for exchange resources between nodes. By default this uses ActiveRecord and an SQL database to store and query the data; this, in turn, will depend on Rails being available. You can adjust the backend using the storeconfigs_backend setting.
- Default: false
storeconfigs_backend
Configure the backend terminus used for StoreConfigs. By default, this uses the ActiveRecord store, which directly talks to the database from within the Puppet Master process.
- Default: active_record
strict_hostname_checking
Whether to only search for the complete hostname as it is in the certificate when searching for node information in the catalogs.
- Default: false
summarize
Whether to print a transaction summary.
- Default: false
syslogfacility
What syslog facility to use when logging to syslog. Syslog has a fixed list of valid facilities, and you must choose one of those; you cannot just make one up.
- Default: daemon
tagmap
The mapping between reporting tags and email addresses.
- Default: $confdir/tagmail.conf
tags
Tags to use to find resources. If this is set, then only resources tagged with the specified tags will be applied. Values must be comma-separated.
templatedir
Where Puppet looks for template files. Can be a list of colon-separated directories.
- Default: $vardir/templates
thin_storeconfigs
Boolean; whether Puppet should store only facts and exported resources in the storeconfigs database. This will improve the performance of exported resources with the older active_record
backend, but will disable external tools that search the storeconfigs database. Thinning catalogs is generally unnecessary when using PuppetDB to store catalogs.
- Default: false
trace
Whether to print stack traces on some errors
- Default: false
use_cached_catalog
Whether to only use the cached catalog rather than compiling a new catalog on every run. Puppet can be run with this enabled by default and then selectively disabled when a recompile is desired.
- Default: false
use_srv_records
Whether the server will search for SRV records in DNS for the current domain.
- Default: false
usecacheonfailure
Whether to use the cached configuration when the remote configuration will not compile. This option is useful for testing new configurations, where you want to fix the broken configuration rather than reverting to a known-good one.
- Default: true
user
The user puppet master should run as.
- Default: puppet
vardir
Where Puppet stores dynamic and growing data. The default for this setting is calculated specially, like confdir
_.
- Default: /var/lib/puppet
waitforcert
How frequently puppet agent should ask for a signed certificate. When starting for the first time, puppet agent will submit a certificate signing request (CSR) to the server named in the ca_server
setting (usually the puppet master); this may be autosigned, or may need to be approved by a human, depending on the CA server’s configuration. Puppet agent cannot apply configurations until its approved certificate is available. Since the certificate may or may not be available immediately, puppet agent will repeatedly try to fetch it at this interval. You can turn off waiting for certificates by specifying a time of 0, in which case puppet agent will exit if it cannot get a cert. This setting can be a time interval in seconds (30 or 30s), minutes (30m), hours (6h), days (2d), or years (5y).
- Default: 2m
yamldir
The directory in which YAML data is stored, usually in a subdirectory.
- Default: $vardir/yaml
zlib
Boolean; whether to use the zlib library
- Default: true
This page autogenerated on Thu Jul 11 16:50:19 -0700 2013


|
KratosMultiphysics
KRATOS Multiphysics (Kratos) is a framework for building parallel, multi-disciplinary simulation software, aiming at modularity, extensibility, and high performance. Kratos is written in C++, and counts with an extensive Python interface.
|
This class defines a process for gradually interpolating nodal values from one model part to another, called the origin and destination model parts respectively. More...
Public Member Functions | |
| def | __init__ (self, model, settings) |
| def | ExecuteInitialize (self) |
| def | ExecuteInitializeSolutionStep (self) |
This class defines a process for gradually interpolating nodal values from one model part to another, called the origin and destination model parts respectively.
The rate of interpolation can be controlled through an increment parameter 'alpha_rampup_increment' or by specifying the total number of steps for the full interpolation 'steps_for_rampup'. The list of variables to be interpolated is also user-definable.
| def gradual_variable_interpolation_process.GradualVariableInterpolationProcess.__init__ | ( | self, | |
| model, | |||
| settings | |||
| ) |
| def gradual_variable_interpolation_process.GradualVariableInterpolationProcess.ExecuteInitialize | ( | self | ) |
| def gradual_variable_interpolation_process.GradualVariableInterpolationProcess.ExecuteInitializeSolutionStep | ( | self | ) |
| gradual_variable_interpolation_process.GradualVariableInterpolationProcess.alpha |
| gradual_variable_interpolation_process.GradualVariableInterpolationProcess.alpha_rampup_increment |
| gradual_variable_interpolation_process.GradualVariableInterpolationProcess.constrain_variables |
| gradual_variable_interpolation_process.GradualVariableInterpolationProcess.destination_model_part |
| gradual_variable_interpolation_process.GradualVariableInterpolationProcess.domain_size |
| gradual_variable_interpolation_process.GradualVariableInterpolationProcess.expected_alpha |
| gradual_variable_interpolation_process.GradualVariableInterpolationProcess.interpolation_variables_list |
| gradual_variable_interpolation_process.GradualVariableInterpolationProcess.model |
| gradual_variable_interpolation_process.GradualVariableInterpolationProcess.old_alpha |
| gradual_variable_interpolation_process.GradualVariableInterpolationProcess.origin_model_part |
| gradual_variable_interpolation_process.GradualVariableInterpolationProcess.settings |
| gradual_variable_interpolation_process.GradualVariableInterpolationProcess.steps_for_rampup |


Note: You are viewing the Sails.js v0.9.0 documentation. If you're looking for information on v0.8.x, please visit here.
There are three kinds of views in Sails. There are traditional view partials, view templates, and the layout.
In Sails a view is the representation of the UI of your application. Views are, by default, EJS (Embedded JavaScript) files. Sails uses EJS, or its other configurable templating libraries, to present your app's data as HTML. Sails allows you to create templates that are injected into the DOM.
Traditional views are defined in the /views/
directory while templates are defined in the
/assets/templates/
directory.
Server-side views in the /views/
directory are by default EJS files that will handle the job
of presenting data when a view requested by the client. The method res.view()
call will
respond to a client with the appropriate view.
Here's an example of a view (views/corndog/index.ejs) that consumes some data sent down from a controller:

My first view

My corndog collection:

<% _.each(corndogs, function (corndog) { %>

<%= corndog.name %>

<% }) %>

And here's what the controller looks like:
var CorndogController = {
index: function(req, res) {
return res.view({
corndogs: [{name: 'Hank the Corndog'}, {name: 'Lenny the Corndog'}]
});
}
}
module.exports = CorndogController;
If you need to override a layout for a specific view, you can do so in the res.view call as below:
res.view({
layout: "different_layout"
})
This could be called from any controller output.
Partials are just like they sound. A View Partial is only a small part of the overall DOM that you see on your web application. With that said, a partial is nothing more than another (smaller) EJS file. Lets take a look at a partial from the Sails example, and how we should include it from another EJS file.
/views/site/partials/footer.ejs

Balderdash © 2013

As you can see, this is nothing more than a simple EJS file. Nothing special, nothing magical.
 Well, maybe. We don't have a lot in our index.ejs file, but thats because we don't need a lot. We call the partials for the site we need to include. Simply calling a partial by relative path will have it included at runtime. This makes our code base very clean and easy to read.
Something a little more complicated? Sure! We'll do a 2 level partial this time. Using our same index.ejs file lets take a look at the "page" partial.
/views/site/partials/page.ejs

<%- partial('sections/about')%>

<%- partial('sections/blog')%>

<%- partial('sections/chat')%>

Still simple, but whats this? We are now including other partials from within our partial? YES! that is exactly what we are doing. From what you can see now... we can create a hierarchical system of partials that make it easy to navigate through the files for designers.
Lets take a look at the "about" section. Since we are dealing with HTML5, we like to name the folders that the partials are held in accordingly. Why? because it just makes sense!
/views/site/partials/sections/about.ejs

SailsJS is built on NodeJS for easily building fast, scalable network applications. SailsJS provides a MVC framework perfect for data-intensive real-time applications that run across distributed devices. SailsJS provides a JSON API right out of the box.

Current Version: v0.8.82

Lets look at this a bit now. We just included a partial from within another partial. We can use relative pathing to include and because our /views/site/partials/page.ejs page and /views/site/partials/sections folder are at the same level in the file system, relative pathing is easy to use. Simple right? We thought so, too.
We have a structure that we prefer to use for partials to make things easy to read. This is by no means a "have-to-use" structure, but we do suggest it, as it is our standard.
PROJECT FOLDER
└── views
├── 401.ejs
├── 404.ejs
├── layout.ejs
└── <controller>
├── index.ejs
├── <action>.ejs
└── partials
├── footer.ejs
├── header.ejs
├── page.ejs
└── sections
├── about.ejs
├── blog.ejs
└── chat.ejs
This layout makes it really simple to navigate and keep things organized.
One of the benefits of Sails is flexability. Sails' views system allows for other templating engines than the default (EJS). The Jade Node Template Engine is available for use as well. Just install it via npm and just change the engine in /config/views.js, or use sails new appname --template=jade
for new projects.
Express 3 removed native support for layouts. In Sails, we've managed to keep this around, but we don't officially support multiple layouts.
That said, at least in EJS, instead of indicating your custom layout with the layout
local,
you must use _layoutFile
:
res.view({
_layoutFile: 'relativePathToYourCustomLayoutFromTheTargetView.ejs'
});
The path to the layout you're wanting to use should be specified relative to the view you're rendering.
So if you're in the create action of the UserController, rendering a view (views/user/create.ejs
), the relative path to your custom layout might be: ../staticSiteLayout.ejs
PROJECT FOLDER
└── views
├── staticSiteLayout.ejs
├── layout.ejs
└── user
└── create.ejs


Class Block
Block returned by the server.
Inheritance
Namespace: Nimiq.Models
Assembly: NimiqClient.dll
Syntax
public class Block : object
Properties
| Improve this Doc View SourceAccountsHash
Hex-encoded 32-byte hash of the accounts tree root.
Declaration
public string AccountsHash { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String |
BodyHash
Hex-encoded 32-byte hash of the block body Merkle root.
Declaration
public string BodyHash { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String |
Confirmations
Number of confirmations for this transaction (number of blocks on top of the block where this transaction was in).
Declaration
public long Confirmations { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Int64 |
Difficulty
Block difficulty, encoded as decimal number in string.
Declaration
public string Difficulty { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String |
ExtraData
Hex-encoded value of the extra data field, maximum of 255 bytes.
Declaration
public string ExtraData { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String |
Hash
Hex-encoded 32-byte hash of the block.
Declaration
public string Hash { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String |
Miner
Hex-encoded 20 byte address of the miner of the block.
Declaration
public string Miner { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String |
MinerAddress
User friendly address (NQ-address) of the miner of the block.
Declaration
public string MinerAddress { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String |
Nonce
The nonce of the block used to fulfill the Proof-of-Work.
Declaration
public long Nonce { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Int64 |
Number
Height of the block.
Declaration
public long Number { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Int64 |
ParentHash
Hex-encoded 32-byte hash of the predecessor block.
Declaration
public string ParentHash { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String |
Pow
Hex-encoded 32-byte Proof-of-Work hash of the block.
Declaration
public string Pow { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String |
Size
Block size in byte.
Declaration
public long Size { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Int64 |
Timestamp
UNIX timestamp of the block.
Declaration
public long Timestamp { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Int64 |
Transactions
Array of transactions. Either represented by the transaction hash or a Transaction object.
Declaration
public object[] Transactions { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Object[] |


CINE
MIX
Home
(current)
Analytics
Recommendations
Logout
Visualization Playground
Top 20 Rated
Bottom 20 Rated
Top 20 Grossing
Bottom 20 Grossing
20 Highest Budget Movies
20 Lowest Budget Movies
Top 20 Most Lengthy
Y-values

X-values


Hardware Intrinsics in .NET Core Anibal Felipe [MSFT] September 3, 2019 Several years ago, we decided that it was time to support SIMD code in .NET. We introduced the System.Numerics namespace with Vector2, Vector3, Vector4, Vector<T>, and related types. These types expose a general-purpose API for creating, accessing, and operating on them using hardware vector instructions (when available). They also ...
Hardware Intrinsics in .NET Core Anibal Felipe [MSFT] September 3, 2019 Several years ago, we decided that it was time to support SIMD code in .NET. We introduced the System.Numerics namespace with Vector2, Vector3, Vector4, Vector<T>, and related types. These types expose a general-purpose API for creating, accessing, and operating on them using hardware vector instructions (when available). They also ...


Dashboard
Statistics
Profile
View Profile
Contacts
Mailbox
Settings
Sign out
Messages
Tasks
Categories
Bags
Scarves, foulards and hats
Small accessories
Jemelry
Belts
Eyewerman
Product
Bags
Scarves, foulards and hats
Small accessories
Jemelry
Belts
Eyewerman
Header
Light card title
Some quick example text to build on the card title and make up the bulk of the card's content.
Header
Light card title
Some quick example text to build on the card title and make up the bulk of the card's content.
Header
Light card title
Some quick example text to build on the card title and make up the bulk of the card's content.
Header
Light card title
Some quick example text to build on the card title and make up the bulk of the card's content.


There are times where it is useful to make a copy of a collection, take a random sample of a collection or even split a collection into a training set and test set. Cloning is the general term used in dataset for these types of operations.
First since dataset is a folder with collections.json, pairtree and frames we can “clone” an the complete collection by simply copying the folder and its contents. This can be done with standard operating system tools (e.g. File managers, command line) or in the case of cloud storage with the tools provided by the vendor for managing content in the cloud. If you’re working with a whole collection this is the best approach.
More frequently I’ve found I need to take a sample of a collection (e.g. because I am developing a bash or Python script that does some batch processing and testing on the whole collection takes too long). This is where you want to use dataset’s clone verb. The basic idea is to get a sample list of keys then use the clone. In the command line version we use the “-sample” option with the keys verb, in Python you need to supply your own function to get a sample list of keys.
In the following examples the origin collection is friends.ds or new sample collection will be friends-sample.ds
On the command line –
dataset keys -sample=5 friends.ds > sample.keys
dataset clone -i sample.keys friends.ds friends-sample.ds
In Python I am assuming you have defined a function called “get_sample_keys()” your self.
keys = get_sample_keys('friends.ds', 5)
err = dataset.clone('friends.ds', keys, 'friends-sample.ds')
As you can see this version of clone works off a set of supplied keys. What if you don’t want to calculate the key list first? e.g I am working in Python and I don’t want to have to write “get_sample_keys()”! That’s what clone-sample (or in Python clone_sample) is for.
The clone-sample verb is about generating sample collections without having to take the extra step of generating a list of sample keys. As an added benefit clone-sample knows which keys were not selected in the sample so it is convienent for creating “training” and “test” collection if you are applying machine learning techniques.
Let’s take a shorten version of generating a sample of size 5 for our friends collection.
dataset clone-sample -size=5 friends.ds friends-sample.ds
Likewise in python this becomes
err = dataset.clone_sample('friends.ds', 5, 'friends-sample.ds')
if err != '':
print(err)
By adding a second target collection name we can use clone-sample to create both the training and test collection. Here’s an example with our friends.ds collection creating training.ds and test.ds.
dataset clone-sample -size=5 friends.ds training.ds test.ds
err = dataset.clone_sample('friends.ds', 5, 'training.ds', 'test.ds')
if err != '':
print(err)


| 3712 - Kickdown Europe - Northeastern Europe & Russian Republic - 2006/2007 | |||||
| Submit | Ranking |
A research laboratory of a world-leading automobile company has received an order to create a special transmission mechanism, which allows for incredibly efficient kickdown -- an operation of switching to lower gear. After several months of research engineers found that the most efficient solution requires special gears with teeth and cavities placed non-uniformly. They calculated the optimal flanks of the gears. Now they want to perform some experiments to prove their findings.
The first phase of the experiment is done with planar toothed sections, not round-shaped gears. A
section of length n
There is a long stripe of width 3h
The stripe is made of an expensive alloy, so the engineers want to use
as little of it as possible. You need to ï¬nd the minimal length of
the stripe which is enough for cutting both sections simultaneously.
The input file contains several test cases, each of them as described below.
There are two lines in the input, each contains a string to
describe a section. The first line describes master section (teeth at the
bottom) and the second line describes driven section (teeth at the top).
Each character in a string represents one section unit -- 1 for a
cavity and 2 for a tooth. The sections can not be flipped or rotated.
Each string is non-empty and its length does not exceed 100.
For each test case, write to the output a line containing
a single integer number -- the minimal
length of the stripe required to cut off given sections.
Input
Output
Sample Input
2112112112
2212112
12121212
21212121
2211221122
21212
Sample Output
10
8
15
Northeastern Europe & Russian Republic 2006-2007


Module: DSL
- Includes:
- NEAT, NEAT::BasicNeuronTypes
- Defined in:
- lib/rubyneat/dsl.rb
Overview
RubyNEAT DSL
DSL is a doman-specific language for RubyNEAT to allow you to configure the NEAT engine for various evolutionary projects.
Constant Summary
Constant Summary
Constants included from NEAT
Instance Method Summary (collapse)
-
- (Object) condition_boolean_vector(vec)
Helper function to Condition boolean vectors to be +1 if true, -1 if false.
-
- (Object) define(name = NEAT.random_name_generator, &block)
DSL – Define defines the parameters to the controller.
-
- (Object) evolve(&block)
DSL – Run evolution.
-
- (Object) fitness(&block)
fitness function calls the block with 2 vectors or two hashes, input and output vectors of the critter being evaluated for fitness, as well as a sequence number that can be used to index what the actual output should be.
-
- (Object) method_missing(m, *args, &block)
This is used to handle the details of our DSL.
-
- (Object) query(&block)
Query function is called with the sequence (time evalution) number, and returns an array or hash of parameters that will be given to the input nodes.
-
- (Object) report(&block)
Report on evaluations.
-
- (Object) run_engine(&block)
Run the engine.
-
- (Object) uncondition_boolean_vector(vec)
Helper function to Uncondition boolean vectors to be +1 if true, -1 if false.
Methods included from NEAT
controller, controller=, create_controller, dpp, gaussian, new_innovation, random_name_generator
Dynamic Method Handling
This class handles dynamic methods through the method_missing method
- (Object) method_missing(m, *args, &block)
This is used to handle the details of our DSL.
82 83 84 85 86 87 88 89 90 91 92 |
# File 'lib/rubyneat/dsl.rb', line 82 def method_missing(m, *args, &block) # we want to catch parameters settings here. if NEAT::controller.parms.respond_to? (assignment = (m.to_s + '=').to_sym) raise NeatException.new("Missing value(s) to %s" % m) if args.empty? val = (args.size == 1) ? args[0] : args $log.debug { "Caught method %s with parameter of %s" % [assignment, val] } NEAT::controller.parms.send(assignment, val) else super end end |
Instance Method Details
- (Object) condition_boolean_vector(vec)
Helper function to Condition boolean vectors to be +1 if true, -1 if false
57 58 59 |
# File 'lib/rubyneat/dsl.rb', line 57 def condition_boolean_vector(vec) vec.map{|b| b ? 1 : -1} end |
- (Object) define(name = NEAT.random_name_generator, &block)
DSL – Define defines the parameters to the controller.
14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 |
# File 'lib/rubyneat/dsl.rb', line 14 def define(name = NEAT.random_name_generator, &block) [ :inputs, :outputs, :hidden # we really don't care about mapping hidden neurons, but we'll ignore them later. ].each do |iometh| instance_eval %Q[ def #{iometh}(nodes = nil, &block) neui = unless nodes.nil? nodes else block.() end NEAT::controller.neural_#{iometh} = if neui.kind_of? Hash neui else Hash[neui.map{|n| [NEAT::random_name_generator, n]}] end end] end block.(NEAT::controller) end |
- (Object) evolve(&block)
DSL – Run evolution
38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 |
# File 'lib/rubyneat/dsl.rb', line 38 def evolve(&block) # Query function is called with the sequence (time evalution) number, # and returns an array or hash of parameters that will be given # to the input nodes. In the case of hash, the keys in the hash # shall correspond to the names given to the input neurons. def query(&block) NEAT::controller.query_func = block end # fitness function calls the block with 2 vectors or two hashes, input and output # vectors of the critter being evaluated for fitness, as well as a sequence # number that can be used to index what the actual output should be. # |vin, vout, seq| def fitness(&block) NEAT::controller.fitness_func = block end # Helper function to # Condition boolean vectors to be +1 if true, -1 if false def condition_boolean_vector(vec) vec.map{|b| b ? 1 : -1} end # Helper function to # Uncondition boolean vectors to be +1 if true, -1 if false def uncondition_boolean_vector(vec) vec.map{|o| o > 0.0 ? true : false} end block.(NEAT::controller) end |
- (Object) fitness(&block)
fitness function calls the block with 2 vectors or two hashes, input and output vectors of the critter being evaluated for fitness, as well as a sequence number that can be used to index what the actual output should be. |vin, vout, seq|
51 52 53 |
# File 'lib/rubyneat/dsl.rb', line 51 def fitness(&block) NEAT::controller.fitness_func = block end |
- (Object) query(&block)
Query function is called with the sequence (time evalution) number, and returns an array or hash of parameters that will be given to the input nodes. In the case of hash, the keys in the hash shall correspond to the names given to the input neurons.
43 44 45 |
# File 'lib/rubyneat/dsl.rb', line 43 def query(&block) NEAT::controller.query_func = block end |
- (Object) report(&block)
Report on evaluations
72 73 |
# File 'lib/rubyneat/dsl.rb', line 72 def report(&block) end |
- (Object) run_engine(&block)
Run the engine. The block is called on each generation.
76 77 78 79 |
# File 'lib/rubyneat/dsl.rb', line 76 def run_engine(&block) NEAT::controller.end_run_func = block NEAT::controller.run end |
- (Object) uncondition_boolean_vector(vec)
Helper function to Uncondition boolean vectors to be +1 if true, -1 if false
63 64 65 |
# File 'lib/rubyneat/dsl.rb', line 63 def uncondition_boolean_vector(vec) vec.map{|o| o > 0.0 ? true : false} end |


OpenStack Swift storage driver
読む時間の目安: 3 分このページでは、オープンソースである Docker Registry を使って、独自にレジストリを提供する情報を示しています。 Docker Hub はホスト提供込みの Registry であり、さまざまな機能を追加することができます。 たとえばチーム、組織、ウェブフック、自動ビルドなどです。 詳しくは Docker Hub を参照してください。
An implementation of the storagedriver.StorageDriver
interface that uses
OpenStack Swift for object
storage.
Parameters
| Parameter | Required | Description |
|---|---|---|
authurl |
yes | URL for obtaining an auth token. https://storage.myprovider.com/v2.0 or https://storage.myprovider.com/v3/auth |
username |
yes | Your Openstack user name. |
password |
yes | Your Openstack password. |
region |
no | The Openstack region in which your container exists. |
container |
yes | The name of your Swift container where you wish to store the registry’s data. The driver creates the named container during its initialization. |
tenant |
no | Your Openstack tenant name. You can either use tenant or tenantid . |
tenantid |
no | Your Openstack tenant name. You can either use tenant or tenantid . |
domain |
no | Your Openstack domain name for Identity v3 API. You can either use domain or domainid . |
domainid |
no | Your Openstack domain name for Identity v3 API. You can either use domain or domainid . |
trustid |
no | Your Openstack trust ID for Identity v3 API. |
insecureskipverify |
no | Skips TLS verification if the value is wet to true . The default is false . |
chunksize |
no | Size of the data segments for the Swift Dynamic Large Objects. This value should be a number (defaults to 5M). |
prefix |
no | This is a prefix that is applied to all Swift keys to allow you to segment data in your container if necessary. Defaults to the empty string which is the container’s root. |
secretkey |
no | The secret key used to generate temporary URLs. |
accesskey |
no | The access key to generate temporary URLs. It is used by HP Cloud Object Storage in addition to the secretkey parameter. |
authversion |
no | Specify the OpenStack Auth’s version, for example 3 . By default the driver autodetects the auth’s version from the AuthURL. |
endpointtype |
no | The endpoint type used when connecting to swift. Possible values are public , internal , and admin . The default is public . |
The features supported by the Swift server are queried by requesting the /info
URL on the server. In case the administrator disabled that feature, the
configuration file can specify the following optional parameters :
| Optional parameter | Description |
|---|---|
tempurlcontainerkey |
Specify whether to use container secret key to generate temporary URL when set to true, or the account secret key otherwise. |
tempurlmethods |
Array of HTTP methods that are supported by the TempURL middleware of the Swift server. For example: ["GET", "PUT", "HEAD", "POST", "DELETE"] |


{% extends "store/base.html" %} {% load bootstrap3 %} {# The template of all pages which are presented to customers. #} {% block body %}


Impact assessment
Equality impact assessment: new funding formula for schools
This was published under the 2010 to 2015 Conservative and Liberal Democrat coalition government
This impact assessment looks at the consultation on the principles behind a new funding formula for schools arising from the review of the dedicated schools grant (DSG).
Documents
Ref:
DFE-32074-2012
PDF
,
1.07MB
,
4 pages
Details
Revenue funding for schools is provided through central government grants paid to local authorities (LAs). In the 2010 to 2011 year, school revenue funding will amount to over £42 billion, most of which is paid through the dedicated schools grant (DSG). In addition to the DSG there are a number of specific grants, the largest grants being school development grant and school standards grant, but also including other smaller grants such as the ethnic minority achievement grant and school lunch grant. Around £4.5 billion is currently allocated through specific grants.
It is a key aim of the policy for funding schools that it helps reduce and remove inequalities in success rates between different communities by raising the attainment and improving rates of progression in English, mathematics and science at key stage 2 and GCSE for certain communities, particularly those that evidence suggests are underachieving.
Includes
-
description of the policy
-
the evidence base
-
what the evidence shows – key facts
-
challenges and opportunities


GPS 1.2: The Anatomy of HTML
Summary
Welcome to HTML Anatomy 101. In this class, you will do the learn how to dissect an HTML page from the <head> to the <footer>, add a new feature to Sublime Text, and mark up your previous blog posts with semantic HTML tags. So get your gloves on, open your textbook (the HTML docs (Links to an external site.)) and begin!
Release 0: Set up
Before you can get started, you'll need to get setup for the challenge. Decide who is going to drive and who will navigate. Then each of you will need to:
- Create a feature branch in the phase-0 directory
- Using the command line, navigate to the week-3 directory
- Within that directory, (using the command line) create a blank HTML page called dissect-me.html.
- Add, commit, and push your changes to GitHub. Create a quick pull request and merge the changes.
- SUBMIT your link to the dissect-me.html file as soon as you do this. This is how your guide will give you feedback. The URL should be something like: https://github.com/[USERNAME]/phase-0/blob/master/week-3/dissect-me.html (Links to an external site.)
NOTE: You should decide whether to trade roles in each release or change roles half way through the session. If you decide to switch from release to release, you'll want to share code easily using a collaborative editor (or even a simple google doc).


Create an on-screen search capable of replacing the remote control as an input device, ensuring that it would work across all YouView devices and products
Sony London Studio
2012
Graphic Designer (Contract)
I had the pleasure of being in the team working on JK Rowling’s Harry Potter universe game for the Sony WonderBook. This augmented reality game used the Wonderbook in conjunction with both the Move controller and the PlayStation Eye to track the users movement and translate it into on screen graphics. The game followed the user embarking on a journey through ‘Hogwarts School’ and had the user ‘learn’ the spells from the Harry Potter series which they had to recreate with the Move control. This action was then turned into each level as the game combined a live video feed with on screen CGI elements.
I was also tasked within a team of researchers to help bring to life the level environments. This part of my role consisted of taking concept designs and finding reference imagery to assist the environmental artists to create accurate assets and to allow them to build 3D models quickly and easily.
I worked on general UI layouts for this game, working closely with developers to produce concepts using in the in-game engine. I was also closely involved with creating concepts for the typography of the game, in particularly the typography of the spell names which the user was presented when completing the task to learn the spell.


| Book of Mormon |
Annotations |
|
An account of the people of Nephi, according to his
record.
|
|
|
Chapter 1
|
|
|
1 And it came to pass that the thirty and fourth year
passed away, and also the thirty and fifth, and behold the disciples of Jesus
had formed a church of Christ in all the lands round about. And as many as
did come unto them, and did truly repent of their sins, were baptized in the
name of Jesus; and they did also receive the Holy Ghost.
|
|
|
2 And it came to pass in the thirty and sixth year, the
people were all converted unto the Lord, upon all the face of the land, both
Nephites and Lamanites, and there were no contentions and disputations among
them, and every man did deal justly one with another.
|
|
|
3 And they had all things common among them; therefore
there were not rich and poor, bond and free, but they were all made free, and
partakers of the heavenly gift.
|
|
|
4 And it came to pass that the thirty and seventh year
passed away also, and there still continued to be peace in the land.
|
|
|
5 And there were great and marvelous works wrought by the
disciples of Jesus, insomuch that they did heal the sick, and raise the dead,
and cause the lame to walk, and the blind to receive their sight, and the
deaf to hear; and all manner of miracles did they work among the children of
men; and in nothing did they work miracles save it were in the name of Jesus.
|
It would have been cool to have such demonstrations of
miraculous power, and they were only disciples, not even apostles.
|
|
6 And thus did the thirty and eighth year pass away, and
also the thirty and ninth, and forty and first, and the forty and second,
yea, even until forty and nine years had passed away, and also the fifty and
first, and the fifty and second; yea, and even until fifty and nine years had
passed away.
|
Jacob told us, “I cannot write but a little of my words,
because of the difficulty of engraving our words upon plates” (Jacob 4:1).
Let’s see if I can do better than Nephi.
“And thus did the years pass away from the thirty and
eighth until the fifty and ninth” (Me).
Nephi: 57 words
Me: 17 words, only 29.8% as verbose
|
|
7 And the Lord did prosper them exceedingly in the land;
yea, insomuch that they did build cities again where there had been cities
burned.
|
|
|
8 Yea, even that great city Zarahemla did they cause to be
built again.
|
|
|
9 But there were many cities which had been sunk, and
waters came up in the stead thereof; therefore these cities could not be
renewed.
|
|
|
10 And now, behold, it came to pass that the people of
Nephi did wax strong, and did multiply exceedingly fast, and became an
exceedingly fair and delightsome people.
|
|
|
11 And they were married, and given in marriage, and were
blessed according to the multitude of the promises which the Lord had made
unto them.
|
|
|
12 And they did not walk any more after the performances
and ordinances of the law of Moses; but they did walk after the commandments
which they had received from their Lord and their God, continuing in fasting
and prayer, and in meeting together oft both to pray and to hear the word of
the Lord.
|
|
|
13 And it came to pass that there was no contention among
all the people, in all the land; but there were mighty miracles wrought among
the disciples of Jesus.
|
|
|
14 And it came to pass that the seventy and first year
passed away, and also the seventy and second year, yea, and in fine, till the
seventy and ninth year had passed away; yea, even an hundred years had passed
away, and the disciples of Jesus, whom he had chosen, had all gone to the
paradise of God, save it were the three who should tarry; and there were
other disciples ordained in their stead; and also many of that generation had
passed away.
|
|
|
15 And it came to pass that there was no contention in the
land, because of the love of God which did dwell in the hearts of the people.
|
|
|
16 And there were no envyings, nor strifes, nor tumults,
nor whoredoms, nor lyings, nor murders, nor any manner of lasciviousness; and
surely there could not be a happier people among all the people who had been
created by the hand of God.
|
|
|
17 There were no robbers, nor murderers, neither were
there Lamanites, nor any manner of -ites; but they were in one, the children
of Christ, and heirs to the kingdom of God.
|
|
|
18 And how blessed were they! For the Lord did bless them
in all their doings; yea, even they were blessed and prospered until an
hundred and ten years had passed away; and the first generation from Christ
had passed away, and there was no contention in all the land.
|
|
|
19 And it came to pass that Nephi, he that kept this last
record, (and he kept it upon the plates of Nephi) died, and his son Amos kept
it in his stead; and he kept it upon the plates of Nephi also.
|
|
|
20 And he kept it eighty and four years, and there was
still peace in the land, save it were a small part of the people who had
revolted from the church and taken upon them the name of Lamanites; therefore
there began to be Lamanites again in the land.
|
|
|
21 And it came to pass that Amos died also, (and it was an
hundred and ninety and four years from the coming of Christ) and his son Amos
kept the record in his stead; and he also kept it upon the plates of Nephi;
and it was also written in the book of Nephi, which is this book.
|
|
|
22 And it came to pass that two hundred years had passed
away; and the second generation had all passed away save it were a few.
|
|
|
23 And now I, Mormon, would that ye should know that the
people had multiplied, insomuch that they were spread upon all the face of
the land, and that they had become exceedingly rich, because of their
prosperity in Christ.
|
Prosperity gospel.
|
|
24 And now, in this two hundred and first year there began
to be among them those who were lifted up in pride, such as the wearing of
costly apparel, and all manner of fine pearls, and of the fine things of the
world.
|
|
|
25 And from that time forth they did have their goods and
their substance no more common among them.
|
|
|
26 And they began to be divided into classes; and they
began to build up churches unto themselves to get gain, and began to deny the
true church of Christ.
|
|
|
27 And it came to pass that when two hundred and ten years
had passed away there were many churches in the land; yea, there were many
churches which professed to know the Christ, and yet they did deny the more
parts of his gospel, insomuch that they did receive all manner of wickedness,
and did administer that which was sacred unto him to whom it had been
forbidden because of unworthiness.
|
|
|
28 And this church did multiply exceedingly because of
iniquity, and because of the power of Satan who did get hold upon their
hearts.
|
|
|
29 And again, there was another church which denied the
Christ; and they did persecute the true church of Christ, because of their
humility and their belief in Christ; and they did despise them because of the
many miracles which were wrought among them.
|
|
|
30 Therefore they did exercise power and authority over
the disciples of Jesus who did tarry with them, and they did cast them into
prison; but by the power of the word of God, which was in them, the prisons
were rent in twain, and they went forth doing mighty miracles among them.
|
4 Ne 1:30-33
Like in verse 5, it would have been cool to have such demonstrations of
miraculous power, and they were only disciples, not even apostles.
|
|
31 Nevertheless, and notwithstanding all these miracles,
the people did harden their hearts, and did seek to kill them, even as the
Jews at Jerusalem sought to kill Jesus, according to his word.
|
Annotation for 4 Ne 1:30-33 above
|
|
32 And they did cast them into furnaces of fire, and they
came forth receiving no harm.
|
Annotation for 4 Ne 1:30-33 above
|
|
33 And they also cast them into dens of wild beasts, and
they did play with the wild beasts even as a child with a lamb; and
they did come forth from among them, receiving no harm.
|
Annotation for 4 Ne 1:30-33 above
Also, a child doesn’t play with a wild lamb, and there were no domesticated sheep in the Americas at this time, so this allusion would have made no sense to these people.
|
|
34 Nevertheless, the people did harden their hearts, for
they were led by many priests and false prophets to build up many churches,
and to do all manner of iniquity. And they did smite upon the people of
Jesus; but the people of Jesus did not smite again. And thus they did dwindle
in unbelief and wickedness, from year to year, even until two hundred and
thirty years had passed away.
|
|
|
35 And now it came to pass in this year, yea, in the two
hundred and thirty and first year, there was a great division among the
people.
|
|
|
36 And it came to pass that in this year there arose a
people who were called the Nephites, and they were true believers in Christ;
and among them there were those who were called by the Lamanites—Jacobites,
and Josephites, and Zoramites;
|
|
|
37 Therefore the true believers in Christ, and the true
worshipers of Christ, (among whom were the three disciples of Jesus who
should tarry) were called Nephites, and Jacobites, and Josephites, and
Zoramites.
|
|
|
38 And it came to pass that they who rejected the gospel
were called Lamanites, and Lemuelites, and Ishmaelites; and they did not
dwindle in unbelief, but they did wilfully rebel against the gospel of
Christ; and they did teach their children that they should not believe, even
as their fathers, from the beginning, did dwindle.
|
|
|
39 And it was because of the wickedness and abomination of
their fathers, even as it was in the beginning. And they were taught to hate
the children of God, even as the Lamanites were taught to hate the children
of Nephi from the beginning.
|
|
|
40 And it came to pass that two hundred and forty and four
years had passed away, and thus were the affairs of the people. And the more
wicked part of the people did wax strong, and became exceedingly more
numerous than were the people of God.
|
|
|
41 And they did still continue to build up churches unto
themselves, and adorn them with all manner of precious things. And thus did
two hundred and fifty years pass away, and also two hundred and sixty years.
|
|
|
42 And it came to pass that the wicked part of the people
began again to build up the secret oaths and combinations of Gadianton.
|
|
|
43 And also the people who were called the people of Nephi
began to be proud in their hearts, because of their exceeding riches, and
become vain like unto their brethren, the Lamanites.
|
|
|
44 And from this time the disciples began to sorrow for
the sins of the world.
|
|
|
45 And it came to pass that when three hundred years had
passed away, both the people of Nephi and the Lamanites had become
exceedingly wicked one like unto another.
|
|
|
46 And it came to pass that the robbers of Gadianton did
spread over all the face of the land; and there were none that were righteous
save it were the disciples of Jesus. And gold and silver did they lay up in
store in abundance, and did traffic in all manner of traffic.
|
|
|
47 And it came to pass that after three hundred and five
years had passed away, (and the people did still remain in wickedness) Amos
died; and his brother, Ammaron, did keep the record in his stead.
|
|
|
48 And it came to pass that when three hundred and twenty
years had passed away, Ammaron, being constrained by the Holy Ghost, did hide
up the records which were sacred—yea, even all the sacred records which had
been handed down from generation to generation, which were sacred—even until
the three hundred and twentieth year from the coming of Christ.
|
|
|
49 And he did hide them up unto the Lord, that they might
come again unto the remnant of the house of Jacob, according to the
prophecies and the promises of the Lord. And thus is the end of the record of
Ammaron.
|
|


Command References
Common command-line reference - usage information that is common to all/most CoApp command line tools
Common property-sheet reference - information common to CoApp tools that use property sheets for
CoApp
coapp.exe - CoApp command line utility
CoApp Developer Tools
pTk.exe - CoApp 'porting toolkit'
Autopackage.exe - Creating packages for distribution
Simplesigner.exe - Signing, Strongnaming and manipulating metadata in binaries
mkRepo.exe - Generate an ATOM feed for a repository
RepositoryService - An automated atom feed generator with upload service
Technical References
New! Overview of CoApp - General information about CoApp
New! CoApp Technical Background - Brief description of how CoApp does what it does
New! In-Depth Technical Discussion - In-Depth descriptions of CoApp's underlying technologies
New! Sys Admin Setup Guide - Short walkthrough of a domain setup (Includes a reference for settings/rights administration)
New! Side-by-side - A techincal article on Windows Side-by-side (WinSxS)
Website/Docpad References
New! Garrett-Flavored-Markdown Reference


Advanced Slide Show - Getting Started |
|
| [ Home ] [ Products ] [ Downloads ] [ Purchase ] [ Support ] |
| Add the following code to your web page:- |
| (The "WIDTH" and "HEIGHT" parameters should be adjusted for the size required) |
| Set Parameters |
|
The parameters (PARAM tags) dictate the content, colors, fonts and operation of the Advanced Slide Show. The VALUE of the parameters (added in the previous step) should be adjusted to provide the desired result. For the meaning and effect of each parameter see the Parameter Reference here |
| Add the Slide and Link Data |
|
The Advanced Slide Show will load the content from a data file specified by the "dataURL" parameter. Above this parameter is set to a value of "data.txt". The dataURL does not have to be a static text file but can be (if required) a server side script which generates the content dynamically (eg. <param name="dataURL" value="data.php"> where data.php would be a PHP script which provides the content upon request). The data file should contain a list of banners and the corresponding links in the following format:-
Where [DIRECTION] can be one of:-
left, top, right , bottom For example:- <IMG top,images/img1.jpg> <LINK http://www.jpowered.com/,_self,0,0,194,130> <IMG left,images/img2.jpg> <LINK http://www.jpowered.com/,_self,0,0,194,130> <IMG center,images/img3.jpg> <LINK http://www.jpowered.com/,_self,0,0,194,130> The ./examples/ directory of this package contains several data files. |
| Copy Files |
From the ./AppletFiles/ directory of this package copy the following files and place them in the same directory as your web page:-
|
If at any stage you require assistance, help or advice then please feel free contact us via our support pages at:-


In Pursuit of Enjoyable Developer Collaboration - DEV Community 👩💻👨💻 Collaboration is critical for any successful development team. That's a fairly uncontroversial opinio... Tagged with productivity, vscode, collaboration, webdev.
Elon Musk Says ‘Hyperloop’ Tunnel Is Now Just a Normal Car Tunnel Because ‘This Is Simple and Just Works’ Back in 2017, Elon Musk had grand visions for the test track built by The Boring Company, his tunneling firm, in Los Angeles. The Boring Company’s tunneling work was closely linked to Musk’s Hyperloop idea, which would require hundreds of miles of tunnel...
Cryptography Dispatches • Buttondown Cryptography Dispatches is Filippo Valsorda's lightly edited newsletter. It tries to bring longer form discussion of the cryptography engineering topics touched on @FiloSottile, but broader breath than those covered at blog.filippo.io. The goal is not to ...
Koalas declared "functionally extinct" The Australian Koala Foundation has declared the iconic species "functionally extinct," meaning they are unlikely to reproduce another generation. Learn more.
Top .NET Tutorials for May 2019 Twilio's top .NET tutorial choices for May 2019 including articles on Blazor, authentication and resilient service-to-service communications.
Despicable Me (9/11) Movie CLIP - I Sit on the Toilet (2010) HD Despicable Me movie clips: http://j.mp/1uyhnup BUY THE MOVIE: http://amzn.to/t8nNZO Don't miss the HOTTEST NEW TRAILERS: http://bit.ly/1u2y6pr CLIP DESCRIPTION: The girls interfere with Gru's (Steve Carell) business meeting with fellow evil-doer, Mr. Per...
First American Financial Corp. Leaked Hundreds of Millions of Title Insurance Records — Krebs on Security The Web site for Fortune 500 real estate title insurance giant First American Financial Corp. [NYSE:FAF] leaked hundreds of millions of documents related to mortgage deals going back to 2003, until notified this week by KrebsOnSecurity. The digitized reco...
Top-Level Code Prototype: Scenario E At last we’ve come to the last of my planned scenarios for this prototype–a little thing I like to think of as a WYSIWYG Web Service, or WYSIWYGWS for short. A few months back I had recently finish…
Refactor Symbol Cache by Krzysztof-Cieslak · Pull Request #384 · fsharp/FsAutoComplete It turns out that sending thousands of symbols serialized to JSON through HTTP is not the best idea I've ever had! I've started working on some performance analyses, and while I don't h...
2017 LLVM Developers’ Meeting: M. Braun “Welcome to the back-end: The LLVM machine representation” http://www.LLVM.org/devmtg/2017-10/ — Welcome to the back-end: The LLVM machine representation - Matthias Braun Slides: http://llvm.org/devmtg/2017-10/slides/Braun-Welcome%20to%20the%20Back%20End.pdf — This tutorial gives an introduction to the LLVM ma...
Rename Blazor project templates · Issue #10348 · dotnet/aspnetcore In-box is called "Blazor Server App" / blazorserver OOB is called "Blazor WebAssembly App" / blazorwasm With an option to add a hosting ASP.NET Core project


Markup Options
Button 1
Button 2
Sizes
Huge
Large
Default
Small
Colors
Default
Primary
Accent 1
Accent 2
Accent 3
Accent 4
Dark
Light
Success
Notice
Alert
Block Level
Block
Disabled
Disabled
Disabled


---
layout: post
title: "My Week in Review"
date: 2015-10-04 10:50:00 +0000
categories:
tags:
image: https://s3.amazonaws.com/audreywatters/2015-10-04-wine.jpg
imagecredits: https://www.flickr.com/photos/ferrariguy90/15866861737
---
Travel
- Hermosa Beach. Barcelona.
- Upcoming week: Barcelona.
Hack Education
Essays Elsewhere
Speaking
Known Notes and Fragments
Other Projects
- I submitted a copy of my talk at ISTE, “Is It Time to Give Up on Computers,” to Gary Stager for a collection he’s publishing.
- I made arrangements to fly to Seattle for NWLearn. (I still need to plan how I’m getting from Seattle to Olympia.)
- Therapy! Al Anon!
- It was time, once again, for my monthly backups, website updates, and invoicing.
- I updated the spreadsheet on ed-tech funding. I wrote a blog post (see above) but I feel like my analysis was totally off, in part because of three major rounds of funding this week that really skewed what I could say about September’s investment (and more generally about trends in ed-tech investing). Oh well.
- I worked on my ICDE keynote.
Listening and Viewing
- I had to see what the fuss was all about so I bought the Hamilton soundtrack.
- I watched Magic Mike XXL (Kin was out of town, yo).
Family and Friends


- MainActivity - Class in com.cmput301f19t09.vibes
-
This Activity hosts the different Fragments of the app.
- MainActivity() - Constructor for class com.cmput301f19t09.vibes.MainActivity
-
- MapFilter - Class in com.cmput301f19t09.vibes.fragments.mapfragment
-
This is the MapFilter fragment that is used
to choose between the last mood of the people
that the primary user is following or the moods
of the primary user.
- MapFilter() - Constructor for class com.cmput301f19t09.vibes.fragments.mapfragment.MapFilter
-
- MapFragment - Class in com.cmput301f19t09.vibes.fragments.mapfragment
-
- MapFragment(Context) - Constructor for class com.cmput301f19t09.vibes.fragments.mapfragment.MapFragment
-
The map fragment shows the locations of the moods.
- MapFragment.Filter - Enum in com.cmput301f19t09.vibes.fragments.mapfragment
-
This is used to filter out the moods being showed;
- mapFragmentToListFragment() - Method in class com.cmput301f19t09.vibes.NavigationTest
-
Navigate to the MapFragment and then back to MoodListFragment.
- matchesSafely(View) - Method in class com.cmput301f19t09.vibes.DrawableMatcher
-
- MaterialChipMatcher - Class in com.cmput301f19t09.vibes
-
- MaterialChipMatcher() - Constructor for class com.cmput301f19t09.vibes.MaterialChipMatcher
-
- mockUsers() - Method in class com.cmput301f19t09.vibes.UserUnitTests
-
- MoodDetailsDialogFragment - Class in com.cmput301f19t09.vibes.fragments.mooddetailsfragment
-
This fragment opens a Dialog that shows a MoodEvent.
- MoodDetailsDialogFragment() - Constructor for class com.cmput301f19t09.vibes.fragments.mooddetailsfragment.MoodDetailsDialogFragment
-
- MoodDetailsFragment - Class in com.cmput301f19t09.vibes.fragments.mooddetailsfragment
-
This fragment shows the details of a MoodEvent.
- MoodDetailsFragment() - Constructor for class com.cmput301f19t09.vibes.fragments.mooddetailsfragment.MoodDetailsFragment
-
- MoodEvent - Class in com.cmput301f19t09.vibes.models
-
Represents an event relating to a mood.
- MoodEvent(LocalDate, LocalTime, String, EmotionalState, int, Uri, Location, User) - Constructor for class com.cmput301f19t09.vibes.models.MoodEvent
-
Creates a new MoodEvent object by accepting a date, time, description, state, socialSituation,
location, and user.
- MoodEventTests - Class in com.cmput301f19t09.vibes
-
- MoodEventTests() - Constructor for class com.cmput301f19t09.vibes.MoodEventTests
-
- MoodFilterListener - Interface in com.cmput301f19t09.vibes.fragments.moodlistfragment
-
Interface for an Object that contains MoodEvents and can be filtered
- MoodListAdapter - Class in com.cmput301f19t09.vibes.fragments.moodlistfragment
-
This is an abstract class responsible for managing a list of MoodEvents.
- MoodListAdapter(Context) - Constructor for class com.cmput301f19t09.vibes.fragments.moodlistfragment.MoodListAdapter
-
Constructor for a MoodListAdapter
- MoodListFilterFragment - Class in com.cmput301f19t09.vibes.fragments.moodlistfragment
-
This fragment allows filtering of MoodFilterListener Fragments
- MoodListFilterFragment() - Constructor for class com.cmput301f19t09.vibes.fragments.moodlistfragment.MoodListFilterFragment
-
Constructor.
- MoodListFragment - Class in com.cmput301f19t09.vibes.fragments.moodlistfragment
-
This Fragment is responsible for displaying a list of MoodEvents.
- MoodListFragment() - Constructor for class com.cmput301f19t09.vibes.fragments.moodlistfragment.MoodListFragment
-
- MoodsDialogAdapter - Class in com.cmput301f19t09.vibes.fragments.mapfragment
-
This class is used as an adapter for the list dialog
in the clusters in the map screen.
- MoodsDialogAdapter(Context, ArrayList<MoodEvent>) - Constructor for class com.cmput301f19t09.vibes.fragments.mapfragment.MoodsDialogAdapter
-
Create a MoodsDialogAdapter
- mRuntimePermissionRule - Variable in class com.cmput301f19t09.vibes.EditFragmentTests
-
Grant the test device location permissions.
- mRuntimePermissionRule - Variable in class com.cmput301f19t09.vibes.NavigationTest
-
Grant the test device location permissions.
- mRuntimePermissionRule - Variable in class com.cmput301f19t09.vibes.UserTests
-
Grant the test device location permissions.


{% extends 'base.html' %} {% block content %}
Are you sure you want to cancel your subscription to AVWX?


{{ object.business.name }} Original Creation: {{ object.creationDate|date:"j F Y" }} Last Updated: {{ object.lastUpdatedDate }} Update Business Delete Business Business Type: {{ object.business.businessType.name }} Store Operation: {% if object.business.status %} Open {% else %} Closed {% endif %} {% if object.business.status %} Website: {{ object.website }} Phone Number: {{ object.phoneNumber }} Opening Time: {{ object.timeOpen }} Closing Time: {{ object.timeClose }} In-store Pickup: {{ object.inStorePickUp }} Delivery: {{ object.deliveryOption }} How To Order:{{ object.ordering }} Notes:{{ object.specialNotes }} Owner Message:{{ object.ownerMessage }} {% endif %}


codeable_models.CBundlable¶
-
class
codeable_models.
CBundlable
(name, **kwargs)¶ CBundlable
is a superclass for all elements in Codeable Models that can be placed in aCBundle
, which is used for grouping elements. Elements that can be bundled areCClass
,CObject
, etc. The class is usually not used directly but via its bundable subclasses.Superclasses:
CNamedElement
- Parameters
name (str) – An optional name.
**kwargs – Accepts keyword args defined as
legal_keyword_args
by subclasses.
CBundlable
is superclass of all classes that can be placed in aCBundle
as shown in the figure below. Please note that bundles can be placed in bundles in order to model composite structures.-
property
bundles
¶ Property that gets or sets the list of bundles this bundable element is part of. For the setter,
None
or[]
can be used to remove the element from all bundles. In the setter, a single parameter of typeCBundle
will set this single bundle as the only bundle of the element. A list of bundles (i.e., list elements of typeCBundle
) will set the whole list.- Type
list[CBundle]|CBundle
-
delete
()¶ Delete the element and remove the element from all bundles it is part of. Calls
delete()
on superclass.- Returns
None
-
get_connected_elements
(**kwargs)¶ Get all elements this element is connected to.
- Parameters
**kwargs – Configuration parameters for the method
- Returns
List of connected elements.
- Return type
List[CBundlable]
Per default associations and inheritance relations are included. Use the following
**kwargs
to specify which connections are included.add_bundles
(bool):Default value: False. If set to True, relations to bundles are included in the returned list.
process_bundles
(bool):Default value: False. If set to True, elements in connected bundles will be processed and all elements in the bundle will be added recursively (i.e. their connections will be processed, too) to the returned list.
stop_elements_inclusive
(list of CNamedElements):Default value: []. If set, searching will be stopped whenever an element on the list in encountered. The stop element will be added to the result.
stop_elements_exclusive
(list of CNamedElements):Default value: []. If set, searching will be stopped whenever an element on the list in encountered. The stop element will not be added to the result.
add_stereotypes
(bool):Default value: False. If set to True, relations to stereotypes are included in the returned list. The option is only applicable on
CMetaclass
,CBundle
, orCStereotype
.
process_stereotypes
(bool):Default value: False. If set to True, relations to stereotypes will be processed and all elements connected to the stereotype will be added recursively (i.e. their connections will be processed, too) to the returned list. The option is only applicable on
CMetaclass
,CBundle
, orCStereotype
.
add_associations
(bool):Default value: False. If set to True, relations to associations (i.e., the association objects) are included in the returned list. The option is only applicable on
CMetaclass
,CClass
, orCAssociation
.