Provides a fast and scalable joint estimator for integrating additional knowledge in learning multiple related sparse Gaussian Graphical Models (JEEK). The JEEK algorithm can be used to fast estimate multiple related precision matrices in a large-scale. For instance, it can identify multiple gene networks from multi-context gene expression datasets. By performing data-driven network inference from high-dimensional and heterogeneous data sets, this tool can help users effectively translate aggregated data into knowledge that take the form of graphs among entities. Please run demo(jeek) to learn the basic functions provided by this package. For further details, please read the original paper: Beilun Wang, Arshdeep Sekhon, Yanjun Qi "A Fast and Scalable Joint Estimator for Integrating Additional Knowledge in Learning Multiple Related Sparse Gaussian Graphical Models" (ICML 2018) <arXiv:1806.00548>.
| Version: | 1.1.1 |
| Depends: | R (≥ 3.0.0), lpSolve, pcaPP, igraph |
| Suggests: | parallel |
| Published: | 2018-07-07 |
| Author: | Beilun Wang [aut, cre], Yanjun Qi [aut], Zhaoyang Wang [aut] |
| Maintainer: | Beilun Wang <bw4mw at virginia.edu> |
| BugReports: | https://github.com/QData/jeek |
| License: | GPL-2 |
| URL: | https://github.com/QData/jeek |
| NeedsCompilation: | no |
| CRAN checks: | jeek results |
| Reference manual: | jeek.pdf |
| Package source: | jeek_1.1.1.tar.gz |
| Windows binaries: | r-devel: jeek_1.1.1.zip, r-release: jeek_1.1.1.zip, r-oldrel: jeek_1.1.1.zip |
| OS X binaries: | r-release: jeek_1.1.1.tgz, r-oldrel: jeek_1.1.1.tgz |
| Old sources: | jeek archive |
Please use the canonical form https://CRAN.R-project.org/package=jeek to link to this page.


Home
About
Contact Us
Traverse
Eastern Hemisphere
Western Hemisphere
Future Plans
Tips
Traverse The Earth
Oh, the places you can go...
Interested in finding more about the places we have been ?
Send us a request for more information.
First name
(required)
Last name
(required)
Email
(Email required)
Submit
-->


|
|
char | name [64] |
| |
|
float | ka [3] |
| |
|
float | kd [3] |
| |
|
float | ks [3] |
| |
|
float | ns |
| |
|
float | tr |
| |
|
int | illum |
| |
|
char | map_ka [64] |
| |
|
char | map_kd [64] |
| |
|
char | map_ks [64] |
| |
|
char | map_ns [64] |
| |
|
char | map_bump [64] |
| |
|
char | map_disp [64] |
| |
|
char | decal [64] |
| |
The documentation for this struct was generated from the following file:
- /home/genkinger/devel/C/azathoth/inc/ams.h


| SSH_CONFIG(5) | File Formats Manual | SSH_CONFIG(5) |
ssh_config
—
For each parameter, the first obtained value will be used. The
configuration files contain sections separated by
Host
specifications, and that section is only
applied for hosts that match one of the patterns given in the specification.
The matched host name is usually the one given on the command line (see the
CanonicalizeHostname
option for exceptions).
Since the first obtained value for each parameter is used, more host-specific declarations should be given near the beginning of the file, and general defaults at the end.
The file contains keyword-argument pairs, one per line. Lines
starting with ‘#
’ and empty lines are
interpreted as comments. Arguments may optionally be enclosed in double
quotes (") in order to represent arguments containing spaces.
Configuration options may be separated by whitespace or optional whitespace
and exactly one ‘=
’; the latter format
is useful to avoid the need to quote whitespace when specifying
configuration options using the ssh
,
scp
, and sftp
-o
option.
The possible keywords and their meanings are as follows (note that keywords are case-insensitive and arguments are case-sensitive):
Host
Host
or Match
keyword) to
be only for those hosts that match one of the patterns given after the
keyword. If more than one pattern is provided, they should be separated by
whitespace. A single ‘*
’ as a
pattern can be used to provide global defaults for all hosts. The host is
usually the hostname argument given on the command
line (see the CanonicalizeHostname
keyword for
exceptions).
A pattern entry may be negated by prefixing it with an
exclamation mark (‘!’). If a negated entry is matched,
then the Host
entry is ignored, regardless of
whether any other patterns on the line match. Negated matches are
therefore useful to provide exceptions for wildcard matches.
See PATTERNS for more information on patterns.
Match
Host
or Match
keyword) to
be used only when the conditions following the
Match
keyword are satisfied. Match conditions are
specified using one or more criteria or the single token
all
which always matches. The available criteria
keywords are: canonical
,
final
, exec
,
host
, originalhost
,
user
, and localuser
. The
all
criteria must appear alone or immediately
after canonical
or final
.
Other criteria may be combined arbitrarily. All criteria but
all
, canonical
, and
final
require an argument. Criteria may be negated
by prepending an exclamation mark (‘!’).
The canonical
keyword matches only
when the configuration file is being re-parsed after hostname
canonicalization (see the CanonicalizeHostname
option). This may be useful to specify conditions that work with
canonical host names only.
The final
keyword requests that the
configuration be re-parsed (regardless of whether
CanonicalizeHostname
is enabled), and matches
only during this final pass. If
CanonicalizeHostname
is enabled, then
canonical
and final
match during the same pass.
The exec
keyword executes the
specified command under the user's shell. If the command returns a zero
exit status then the condition is considered true. Commands containing
whitespace characters must be quoted. Arguments to
exec
accept the tokens described in the
TOKENS section.
The other keywords' criteria must be single entries or
comma-separated lists and may use the wildcard and negation operators
described in the PATTERNS section.
The criteria for the host
keyword are matched
against the target hostname, after any substitution by the
Hostname
or
CanonicalizeHostname
options. The
originalhost
keyword matches against the
hostname as it was specified on the command-line. The
user
keyword matches against the target username
on the remote host. The localuser
keyword
matches against the name of the local user running
ssh(1) (this keyword may be
useful in system-wide ssh_config
files).
AddKeysToAgent
yes
and a key is loaded from a
file, the key and its passphrase are added to the agent with the default
lifetime, as if by
ssh-add(1). If this option
is set to ask
,
ssh(1) will require
confirmation using the SSH_ASKPASS
program before
adding a key (see
ssh-add(1) for details).
If this option is set to confirm
, each use of the
key must be confirmed, as if the -c
option was
specified to ssh-add(1).
If this option is set to no
, no keys are added to
the agent. The argument must be yes
,
confirm
, ask
, or
no
(the default).AddressFamily
any
(the default), inet
(use IPv4 only), or inet6
(use IPv6 only).BatchMode
yes
, user interaction such as password
prompts and host key confirmation requests will be disabled. This option
is useful in scripts and other batch jobs where no user is present to
interact with ssh(1). The
argument must be yes
or no
(the default).BindAddress
BindInterface
CanonicalDomains
CanonicalizeHostname
is enabled, this option
specifies the list of domain suffixes in which to search for the specified
destination host.CanonicalizeFallbackLocal
yes
, will attempt to look up
the unqualified hostname using the system resolver's search rules. A value
of no
will cause
ssh(1) to fail instantly if
CanonicalizeHostname
is enabled and the target
hostname cannot be found in any of the domains specified by
CanonicalDomains
.CanonicalizeHostname
no
, is not to perform any name rewriting
and let the system resolver handle all hostname lookups. If set to
yes
then, for connections that do not use a
ProxyCommand
or ProxyJump
,
ssh(1) will attempt to
canonicalize the hostname specified on the command line using the
CanonicalDomains
suffixes and
CanonicalizePermittedCNAMEs
rules. If
CanonicalizeHostname
is set to
always
, then canonicalization is applied to
proxied connections too.
If this option is enabled, then the configuration files are
processed again using the new target name to pick up any new
configuration in matching Host
and
Match
stanzas.
CanonicalizeMaxDots
CanonicalizePermittedCNAMEs
For example, “*.a.example.com:*.b.example.com,*.c.example.com” will allow hostnames matching “*.a.example.com” to be canonicalized to names in the “*.b.example.com” or “*.c.example.com” domains.
CASignatureAlgorithms
ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521, ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa
ssh(1) will not accept host certificates signed using algorithms other than those specified.
CertificateFile
IdentityFile
directive
or -i
flag to
ssh(1), via
ssh-agent(1), or via a
PKCS11Provider
or
SecurityKeyProvider
.
Arguments to CertificateFile
may use
the tilde syntax to refer to a user's home directory or the tokens
described in the TOKENS section.
It is possible to have multiple certificate files specified in
configuration files; these certificates will be tried in sequence.
Multiple CertificateFile
directives will add to
the list of certificates used for authentication.
ChallengeResponseAuthentication
yes
(the default) or
no
.CheckHostIP
yes
(the default),
ssh(1) will additionally check
the host IP address in the known_hosts file. This
allows it to detect if a host key changed due to DNS spoofing and will add
addresses of destination hosts to
~/.ssh/known_hosts in the process, regardless of
the setting of StrictHostKeyChecking
. If the
option is set to no
, the check will not be
executed.Ciphers
The supported ciphers are:
3des-cbc aes128-cbc aes192-cbc aes256-cbc aes128-ctr aes192-ctr aes256-ctr<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>The default is:
<EMAIL_ADDRESS>aes128-ctr,aes192-ctr,aes256-ctr, aes128-gcm<EMAIL_ADDRESS>The list of available ciphers may also be obtained using “ssh -Q cipher”.
ClearAllForwardings
yes
or no
(the
default).Compression
yes
or no
(the
default).ConnectionAttempts
ConnectTimeout
ControlMaster
yes
,
ssh(1) will listen for
connections on a control socket specified using the
ControlPath
argument. Additional sessions can
connect to this socket using the same ControlPath
with ControlMaster
set to
no
(the default). These sessions will try to reuse
the master instance's network connection rather than initiating new ones,
but will fall back to connecting normally if the control socket does not
exist, or is not listening.
Setting this to ask
will cause
ssh(1) to listen for control
connections, but require confirmation using
ssh-askpass(1). If
the ControlPath
cannot be opened,
ssh(1) will continue without
connecting to a master instance.
X11 and ssh-agent(1) forwarding is supported over these multiplexed connections, however the display and agent forwarded will be the one belonging to the master connection i.e. it is not possible to forward multiple displays or agents.
Two additional options allow for opportunistic multiplexing:
try to use a master connection but fall back to creating a new one if
one does not already exist. These options are:
auto
and autoask
. The
latter requires confirmation like the ask
option.
ControlPath
ControlMaster
section above or
the string none
to disable connection sharing.
Arguments to ControlPath
may use the tilde syntax
to refer to a user's home directory or the tokens described in the
TOKENS section. It is recommended that
any ControlPath
used for opportunistic connection
sharing include at least %h, %p, and %r (or alternatively %C) and be
placed in a directory that is not writable by other users. This ensures
that shared connections are uniquely identified.ControlPersist
ControlMaster
,
specifies that the master connection should remain open in the background
(waiting for future client connections) after the initial client
connection has been closed. If set to no
(the
default), then the master connection will not be placed into the
background, and will close as soon as the initial client connection is
closed. If set to yes
or 0, then the master
connection will remain in the background indefinitely (until killed or
closed via a mechanism such as the “ssh -O exit”). If set to
a time in seconds, or a time in any of the formats documented in
sshd_config(5), then
the backgrounded master connection will automatically terminate after it
has remained idle (with no client connections) for the specified
time.DynamicForward
The argument must be
[bind_address:]port. IPv6
addresses can be specified by enclosing addresses in square brackets. By
default, the local port is bound in accordance with the
GatewayPorts
setting. However, an explicit
bind_address may be used to bind the connection to
a specific address. The bind_address of
localhost
indicates that the listening port be
bound for local use only, while an empty address or ‘*’
indicates that the port should be available from all interfaces.
Currently the SOCKS4 and SOCKS5 protocols are supported, and ssh(1) will act as a SOCKS server. Multiple forwardings may be specified, and additional forwardings can be given on the command line. Only the superuser can forward privileged ports.
EnableSSHKeysign
yes
in the global client
configuration file /etc/ssh/ssh_config enables the
use of the helper program
ssh-keysign(8) during
HostbasedAuthentication
. The argument must be
yes
or no
(the default).
This option should be placed in the non-hostspecific section. See
ssh-keysign(8) for
more information.EscapeChar
~
’). The escape character can also
be set on the command line. The argument should be a single character,
‘^
’ followed by a letter, or
none
to disable the escape character entirely
(making the connection transparent for binary data).ExitOnForwardFailure
ExitOnForwardFailure
does not apply to connections
made over port forwardings and will not, for example, cause
ssh(1) to exit if TCP
connections to the ultimate forwarding destination fail. The argument must
be yes
or no
(the
default).FingerprintHash
md5
and
sha256
(the default).ForwardAgent
yes
, no
(the default), an
explicit path to an agent socket or the name of an environment variable
(beginning with ‘$’) in which to find the path.
Agent forwarding should be enabled with caution. Users with the ability to bypass file permissions on the remote host (for the agent's Unix-domain socket) can access the local agent through the forwarded connection. An attacker cannot obtain key material from the agent, however they can perform operations on the keys that enable them to authenticate using the identities loaded into the agent.
ForwardX11
DISPLAY
set. The argument
must be yes
or no
(the
default).
X11 forwarding should be enabled with caution. Users with the
ability to bypass file permissions on the remote host (for the user's
X11 authorization database) can access the local X11 display through the
forwarded connection. An attacker may then be able to perform activities
such as keystroke monitoring if the
ForwardX11Trusted
option is also enabled.
ForwardX11Timeout
ForwardX11Timeout
to zero will disable the timeout
and permit X11 forwarding for the life of the connection. The default is
to disable untrusted X11 forwarding after twenty minutes has elapsed.ForwardX11Trusted
yes
, remote X11 clients
will have full access to the original X11 display.
If this option is set to no
(the
default), remote X11 clients will be considered untrusted and prevented
from stealing or tampering with data belonging to trusted X11 clients.
Furthermore, the xauth(1)
token used for the session will be set to expire after 20 minutes.
Remote clients will be refused access after this time.
See the X11 SECURITY extension specification for full details on the restrictions imposed on untrusted clients.
GatewayPorts
GatewayPorts
can be used to specify that ssh
should bind local port forwardings to the wildcard address, thus allowing
remote hosts to connect to forwarded ports. The argument must be
yes
or no
(the
default).GlobalKnownHostsFile
GSSAPIAuthentication
no
.GSSAPIDelegateCredentials
no
.HashKnownHosts
no
. Note that existing
names and addresses in known hosts files will not be converted
automatically, but may be manually hashed using
ssh-keygen(1).HostbasedAuthentication
yes
or
no
(the default).HostbasedKeyTypes
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521<EMAIL_ADDRESS><EMAIL_ADDRESS>rsa-sha2-512,rsa-sha2-256,ssh-rsa
The -Q
option of
ssh(1) may be used to list
supported key types.
HostKeyAlgorithms
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521<EMAIL_ADDRESS><EMAIL_ADDRESS>rsa-sha2-512,rsa-sha2-256,ssh-rsa
If hostkeys are known for the destination host then this default is modified to prefer their algorithms.
The list of available key types may also be obtained using “ssh -Q HostKeyAlgorithms”.
HostKeyAlias
Hostname
Hostname
accept the tokens described in the
TOKENS section. Numeric IP addresses are
also permitted (both on the command line and in
Hostname
specifications). The default is the name
given on the command line.IdentitiesOnly
ssh_config
files or passed on the
ssh(1) command-line), even if
ssh-agent(1) or a
PKCS11Provider
or
SecurityKeyProvider
offers more identities. The
argument to this keyword must be yes
or
no
(the default). This option is intended for
situations where ssh-agent offers many different identities.IdentityAgent
This option overrides the
SSH_AUTH_SOCK
environment variable and can be
used to select a specific agent. Setting the socket name to
none
disables the use of an authentication
agent. If the string “SSH_AUTH_SOCK” is specified, the
location of the socket will be read from the
SSH_AUTH_SOCK
environment variable. Otherwise if
the specified value begins with a ‘$’ character, then it
will be treated as an environment variable containing the location of
the socket.
Arguments to IdentityAgent
may use the
tilde syntax to refer to a user's home directory or the tokens described
in the TOKENS section.
IdentityFile
IdentitiesOnly
is set. If no certificates
have been explicitly specified by CertificateFile
,
ssh(1) will try to load
certificate information from the filename obtained by appending
-cert.pub to the path of a specified
IdentityFile
.
Arguments to IdentityFile
may use the
tilde syntax to refer to a user's home directory or the tokens described
in the TOKENS section.
It is possible to have multiple identity files specified in
configuration files; all these identities will be tried in sequence.
Multiple IdentityFile
directives will add to the
list of identities tried (this behaviour differs from that of other
configuration directives).
IdentityFile
may be used in
conjunction with IdentitiesOnly
to select which
identities in an agent are offered during authentication.
IdentityFile
may also be used in conjunction
with CertificateFile
in order to provide any
certificate also needed for authentication with the identity.
IgnoreUnknown
ssh_config
contains options that are
unrecognised by ssh(1). It is
recommended that IgnoreUnknown
be listed early in
the configuration file as it will not be applied to unknown options that
appear before it.Include
Include
directive may appear inside a
Match
or Host
block to
perform conditional inclusion.IPQoS
af11
, af12
,
af13
, af21
,
af22
, af23
,
af31
, af32
,
af33
, af41
,
af42
, af43
,
cs0
, cs1
,
cs2
, cs3
,
cs4
, cs5
,
cs6
, cs7
,
ef
, le
,
lowdelay
, throughput
,
reliability
, a numeric value, or
none
to use the operating system default. This
option may take one or two arguments, separated by whitespace. If one
argument is specified, it is used as the packet class unconditionally. If
two values are specified, the first is automatically selected for
interactive sessions and the second for non-interactive sessions. The
default is af21
(Low-Latency Data) for interactive
sessions and cs1
(Lower Effort) for
non-interactive sessions.KbdInteractiveAuthentication
yes
(the default) or
no
.KbdInteractiveDevices
bsdauth
and pam
.KexAlgorithms
<EMAIL_ADDRESS>ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521, diffie-hellman-group-exchange-sha256, diffie-hellman-group16-sha512, diffie-hellman-group18-sha512, diffie-hellman-group14-sha256
The list of available key exchange algorithms may also be obtained using “ssh -Q kex”.
LocalCommand
LocalCommand
accept the tokens described in the
TOKENS section.
The command is run synchronously and does not have access to the session of the ssh(1) that spawned it. It should not be used for interactive commands.
This directive is ignored unless
PermitLocalCommand
has been enabled.
LocalForward
IPv6 addresses can be specified by enclosing addresses in
square brackets. Multiple forwardings may be specified, and additional
forwardings can be given on the command line. Only the superuser can
forward privileged ports. By default, the local port is bound in
accordance with the GatewayPorts
setting.
However, an explicit bind_address may be used to
bind the connection to a specific address. The
bind_address of localhost
indicates that the listening port be bound for local use only, while an
empty address or ‘*’ indicates that the port should be
available from all interfaces. Unix domain socket paths accept the
tokens described in the TOKENS
section.
LogLevel
MACs
The algorithms that contain “-etm” calculate the MAC after encryption (encrypt-then-mac). These are considered safer and their use recommended.
The default is:
umac-64-etm<EMAIL_ADDRESS>hmac-sha2-256-etm<EMAIL_ADDRESS><EMAIL_ADDRESS>umac-64<EMAIL_ADDRESS>hmac-sha2-256,hmac-sha2-512,hmac-sha1
The list of available MAC algorithms may also be obtained using “ssh -Q mac”.
NoHostAuthenticationForLocalhost
yes
or
no
(the default).NumberOfPasswordPrompts
PasswordAuthentication
yes
(the default) or
no
.PermitLocalCommand
LocalCommand
option or using the !
command
escape sequence in ssh(1). The
argument must be yes
or no
(the default).PKCS11Provider
none
to
indicate that no provider should be used (the default). The argument to
this keyword is a path to the PKCS#11 shared library
ssh(1) should use to
communicate with a PKCS#11 token providing keys for user
authentication.Port
PreferredAuthentications
keyboard-interactive
) over another method (e.g.
password
). The default is:
gssapi-with-mic,hostbased,publickey, keyboard-interactive,password
ProxyCommand
exec
’ directive to avoid a
lingering shell process.
Arguments to ProxyCommand
accept the
tokens described in the TOKENS section.
The command can be basically anything, and should read from its standard
input and write to its standard output. It should eventually connect an
sshd(8) server running on
some machine, or execute sshd -i
somewhere. Host
key management will be done using the Hostname
of the host being connected (defaulting to the name typed by the user).
Setting the command to none
disables this option
entirely. Note that CheckHostIP
is not available
for connects with a proxy command.
This directive is useful in conjunction with nc(1) and its proxy support. For example, the following directive would connect via an HTTP proxy at <IP_ADDRESS>:
ProxyCommand /usr/bin/nc -X connect -x <IP_ADDRESS>:8080 %h %p
ProxyJump
ProxyJump
host and then establishing a
TCP forwarding to the ultimate target from there.
Note that this option will compete with the
ProxyCommand
option - whichever is specified
first will prevent later instances of the other from taking effect.
Note also that the configuration for the destination host (either supplied via the command-line or the configuration file) is not generally applied to jump hosts. ~/.ssh/config should be used if specific configuration is required for jump hosts.
ProxyUseFdpass
ProxyCommand
will pass a connected
file descriptor back to ssh(1)
instead of continuing to execute and pass data. The default is
no
.PubkeyAcceptedKeyTypes
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521<EMAIL_ADDRESS><EMAIL_ADDRESS>rsa-sha2-512,rsa-sha2-256,ssh-rsa
The list of available key types may also be obtained using “ssh -Q PubkeyAcceptedKeyTypes”.
PubkeyAuthentication
yes
(the default) or
no
.RekeyLimit
RekeyLimit
is
default none
, which means that rekeying is
performed after the cipher's default amount of data has been sent or
received and no time based rekeying is done.RemoteCommand
RemoteCommand
accept the tokens described in the
TOKENS section.RemoteForward
IPv6 addresses can be specified by enclosing addresses in square brackets. Multiple forwardings may be specified, and additional forwardings can be given on the command line. Privileged ports can be forwarded only when logging in as root on the remote machine. Unix domain socket paths accept the tokens described in the TOKENS section.
If the port argument is 0, the listen port will be dynamically allocated on the server and reported to the client at run time.
If the bind_address is not specified,
the default is to only bind to loopback addresses. If the
bind_address is
‘*
’ or an empty string, then the
forwarding is requested to listen on all interfaces. Specifying a remote
bind_address will only succeed if the server's
GatewayPorts
option is enabled (see
sshd_config(5)).
RequestTTY
no
(never request a TTY),
yes
(always request a TTY when standard input is a
TTY), force
(always request a TTY) or
auto
(request a TTY when opening a login session).
This option mirrors the -t
and
-T
flags for
ssh(1).RevokedHostKeys
SecurityKeyProvider
If the specified value begins with a ‘$’ character, then it will be treated as an environment variable containing the path to the library.
SendEnv
TERM
environment variable is always sent whenever
a pseudo-terminal is requested as it is required by the protocol. Refer to
AcceptEnv
in
sshd_config(5) for how
to configure the server. Variables are specified by name, which may
contain wildcard characters. Multiple environment variables may be
separated by whitespace or spread across multiple
SendEnv
directives.
See PATTERNS for more information on patterns.
It is possible to clear previously set
SendEnv
variable names by prefixing patterns
with -. The default is not to send any
environment variables.
ServerAliveCountMax
TCPKeepAlive
(below). The server alive messages are sent through the encrypted channel
and therefore will not be spoofable. The TCP keepalive option enabled by
TCPKeepAlive
is spoofable. The server alive
mechanism is valuable when the client or server depend on knowing when a
connection has become unresponsive.
The default value is 3. If, for example,
ServerAliveInterval
(see below) is set to 15 and
ServerAliveCountMax
is left at the default, if
the server becomes unresponsive, ssh will disconnect after approximately
45 seconds.
ServerAliveInterval
SetEnv
SendEnv
, the
server must be prepared to accept the environment variable.StreamLocalBindMask
The default value is 0177, which creates a Unix-domain socket file that is readable and writable only by the owner. Note that not all operating systems honor the file mode on Unix-domain socket files.
StreamLocalBindUnlink
StreamLocalBindUnlink
is not
enabled, ssh
will be unable to forward the port to
the Unix-domain socket file. This option is only used for port forwarding
to a Unix-domain socket file.
The argument must be yes
or
no
(the default).
StrictHostKeyChecking
yes
,
ssh(1) will never
automatically add host keys to the
~/.ssh/known_hosts file, and refuses to connect to
hosts whose host key has changed. This provides maximum protection against
man-in-the-middle (MITM) attacks, though it can be annoying when the
/etc/ssh/ssh_known_hosts file is poorly maintained
or when connections to new hosts are frequently made. This option forces
the user to manually add all new hosts.
If this flag is set to “accept-new” then ssh
will automatically add new host keys to the user known hosts files, but
will not permit connections to hosts with changed host keys. If this
flag is set to “no” or “off”, ssh will
automatically add new host keys to the user known hosts files and allow
connections to hosts with changed hostkeys to proceed, subject to some
restrictions. If this flag is set to ask
(the
default), new host keys will be added to the user known host files only
after the user has confirmed that is what they really want to do, and
ssh will refuse to connect to hosts whose host key has changed. The host
keys of known hosts will be verified automatically in all cases.
SyslogFacility
TCPKeepAlive
The default is yes
(to send TCP
keepalive messages), and the client will notice if the network goes down
or the remote host dies. This is important in scripts, and many users
want it too.
To disable TCP keepalive messages, the value should be set to
no
. See also
ServerAliveInterval
for protocol-level
keepalives.
Tunnel
yes
, point-to-point
(layer
3), ethernet
(layer 2), or
no
(the default). Specifying
yes
requests the default tunnel mode, which is
point-to-point
.TunnelDevice
The argument must be
local_tun[:remote_tun]. The
devices may be specified by numerical ID or the keyword
any
, which uses the next available tunnel
device. If remote_tun is not specified, it
defaults to any
. The default is
any:any
.
UpdateHostKeys
UserKnownHostsFile
. The argument must be
yes
, no
or
ask
. This option allows learning alternate
hostkeys for a server and supports graceful key rotation by allowing a
server to send replacement public keys before old ones are removed.
Additional hostkeys are only accepted if the key used to authenticate the
host was already trusted or explicitly accepted by the user.
UpdateHostKeys
is enabled by default
if the user has not overridden the default
UserKnownHostsFile
setting, otherwise
UpdateHostKeys
will be set to
ask
.
If UpdateHostKeys
is set to
ask
, then the user is asked to confirm the
modifications to the known_hosts file. Confirmation is currently
incompatible with ControlPersist
, and will be
disabled if it is enabled.
Presently, only sshd(8) from OpenSSH 6.8 and greater support the<EMAIL_ADDRESS>protocol extension used to inform the client of all the server's hostkeys.
User
UserKnownHostsFile
VerifyHostKeyDNS
yes
, the client
will implicitly trust keys that match a secure fingerprint from DNS.
Insecure fingerprints will be handled as if this option was set to
ask
. If this option is set to
ask
, information on fingerprint match will be
displayed, but the user will still need to confirm new host keys according
to the StrictHostKeyChecking
option. The default
is no
.
See also VERIFYING HOST KEYS in ssh(1).
VisualHostKey
yes
, an ASCII art
representation of the remote host key fingerprint is printed in addition
to the fingerprint string at login and for unknown host keys. If this flag
is set to no
(the default), no fingerprint strings
are printed at login and only the fingerprint string will be printed for
unknown host keys.XAuthLocation
Host *.co.uk
The following pattern would match any host in the 192.168.0.[0-9] network range:
Host 192.168.0.?
A pattern-list is a comma-separated list of patterns. Patterns within pattern-lists may be negated by preceding them with an exclamation mark (‘!’). For example, to allow a key to be used from anywhere within an organization except from the “dialup” pool, the following entry (in authorized_keys) could be used:
from="!*.dialup.example.com,*.example.com"
Note that a negated match will never produce a positive result by itself. For example, attempting to match “host3” against the following pattern-list will fail:
from="!host1,!host2"
The solution here is to include a term that will yield a positive match, such as a wildcard:
from="!host1,!host2,*"
CertificateFile
,
ControlPath
, IdentityAgent
,
IdentityFile
, LocalForward
,
Match exec
, RemoteCommand
,
and RemoteForward
accept the tokens %%, %C, %d, %h,
%i, %L, %l, %n, %p, %r, and %u.
Hostname
accepts the tokens %% and %h.
LocalCommand
accepts all tokens.
ProxyCommand
accepts the tokens %%, %h,
%n, %p, and %r.
| April 11, 2020 | Fidelix 0.2 |


--- title: Israel shot 111 date: 2004-04-21T00:00:00.000Z filepathOriginal: photos/IMG0113.jpg filepathThumbnail: photos/IMG0113.thumbnail.jpg filepathPreview: photos/IMG0113.preview.jpg ---
Nahal Kziv: Jase, Yoni, Raf, Yummies, Me, Porntoy, Ari, and Crembo, having no idea how soaked our feet would get


Raw denim you probably haven't heard of them jean shorts Austin. Nesciunt tofu stumptown aliqua, retro synth master cleanse. Mustache cliche tempor, williamsburg carles vegan helvetica. Reprehenderit butcher retro keffiyeh dreamcatcher synth.
Chief Technology Officer
Information Technology | StepWise


SocialMiner
Form to submit your callback request
Title: *
Name: *
Phone: *
Feed Id: *
ECC Callback:
Call Variable 1:
Call Variable 2:
Call Variable 3:
Call Variable 4:
Call Variable 5:
Call Variable 6:
Call Variable 7:
Call Variable 8:
Call Variable 9:
Call Variable 10:
Call me back
Back
Status
Cancel callback


BTS Jumps hundreds of spots to top Itunes Album Charts
by greenbaypackersWith the controversy surrounding the E! People's Awards, ARMY have resolved to show their support for the boys by buying Map of The Soul: Persona.
On the US Album Charts, Persona is currently at number 2 and it won't be a surprise if it reaches number one.
ARMYs believe that change will come from showing people who they really support, no matter what awards they show. They realized that bashing the E! People Music Awards was not going to work so they showed something else. Unity. The #BuyPersonOnITunes has amassed almost 600k tweets and has only been growing over the day. ARMYs around the world hope to show people they will always be behind the bangtan boys no matter what.
If you have Chart News for any other country, please be sure to comment below!!!
EDIT:
WE HAVE NEWS THAT MAP OF THE SOUL PERSONA IS NOW NUMBER ONE ON WORLD CHARTS TOO!
EDIT 2:
ARMY IS TAKING OVER THE WORLD!!!!!!!!!!!!
Thanks for the chart @lynne001


Distributed Cloud Computing generalizes the cloud computing model to position, process, and serve data and applications from geographically distributed sites to meet requirements for performance, redundancy and regulations.
The traditional cloud computing model offers on-demand, metered access to computing resources—storage, servers, databases, and applications—to users who do not want to build, buy, or run their own IT infrastructure. Public cloud service providers maintain and run large server farms whose resources are shared between users, with virtualization techniques that provide isolation and security of individual user data. Site redundancy across regions provides for recovery from outages and disasters, with all the monitoring and management aspects of keeping the cloud up and running transparent to cloud users.
While distributed computing spreads computation workload across multiple, interconnected servers, distributed cloud computing generalizes this to the cloud infrastructure itself. A distributed cloud is an execution environment where application components are placed at appropriate geographically-dispersed locations chosen to meet the requirements of the application.
Such requirements include: Location: to enable more responsive and performant service delivery for certain types of applications, where latency is critical and bulk data transfer to and from a central cloud is expensive. Regulations: which may require that data never leaves the user’s country, as is the requirement in the EU. Security: to ensure that certain data and processes remain within an enterprise’s private cloud or data center, with which a public cloud is integrated. Redundancy: beyond that provided by local, regional, or national site redundancy to mitigate large scale outages that can affect enterprises. The distributed cloud service provider ensures the end-to-end management for the optimal placement of data, computing processes, and network interconnections based on the above-mentioned requirements. And it appears as a single solution from the cloud user’s point of view. A Content Delivery Network (CDN) is one example of a distributed cloud, where storage (e.g., video content) is positioned in geographically diverse regions to reduce the latency of delivery. Enterprises using CDNs to distribute content get the benefits of scaling both storage and performance.


9.823
Members online
February
My First dataset59
9.823
Members online
February
My First dataset18
9.823
Members online
9.823
Members online
February
My First dataset84
Traffic
November 2017
M
My First dataset165
My Second dataset92
My Third dataset65
89k
friends
459
feeds
973k
followers
1.792
tweets
500+
contacts
292
feeds
894
followers
92
circles
Traffic & Sales
New Clients
9,123
9,123
Recuring Clients
22,643
22,643
Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
Sunday
Pageviews
78,623
78,623
Organic
49,123
49,123
Male
43%
Female
37%
Organic Search
191.235
(56%)
Facebook
51.223
(15%)
Twitter
37.564
(11%)
LinkedIn
27.319
(8%)
| User | Country | Usage | Payment Method | Activity | |
|---|---|---|---|---|---|
|
|
Yiorgos Avraamu
New | Registered: Jan 1, 2015
|
50%
Jun 11, 2015 - Jul 10, 2015
|
Last login
10 sec ago
|
||
|
|
Avram Tarasios
Recurring | Registered: Jan 1, 2015
|
10%
Jun 11, 2015 - Jul 10, 2015
|
Last login
5 minutes ago
|
||
|
|
Quintin Ed
New | Registered: Jan 1, 2015
|
74%
Jun 11, 2015 - Jul 10, 2015
|
Last login
1 hour ago
|
||
|
|
Enéas Kwadwo
New | Registered: Jan 1, 2015
|
98%
Jun 11, 2015 - Jul 10, 2015
|
Last login
Last month
|
||
|
|
Agapetus Tadeáš
New | Registered: Jan 1, 2015
|
22%
Jun 11, 2015 - Jul 10, 2015
|
Last login
Last week
|
||
|
|
Friderik Dávid
New | Registered: Jan 1, 2015
|
43%
Jun 11, 2015 - Jul 10, 2015
|
Last login
Yesterday
|


Ginsburg hospitalized for treatment of chills and fever
WASHINGTON — The Supreme Court says Justice Ruth Bader Ginsburg has been hospitalized after experiencing chills and fever.
In a statement Saturday, the court’s public information office says Ginsburg was admitted Friday night to Johns Hopkins Hospital in Baltimore.
The court says Ginsburg was initially evaluated at Sibley Memorial Hospital in Washington before being transferred to Johns Hopkins for further evaluation and treatment of any possible infection.
The court says that with intravenous antibiotics and fluids, her symptoms have abated and she expects to be released from the hospital as early as Sunday morning.
The Associated Press


/>
Add some information about the album below, the author, or any other background context. Make it a few sentences long so folks can pick up some informative tidbits. Then, link them off to some social networking sites or contact information.
{{message}}


Kirstin Morris
One of my favourite sites is
Goodreads
where I track all my books.
I love
Instagram
because it is a nice distraction.
Reddit
is a guilty pleasure.
Youtube
is where I watch the majority of my videos.


Constructor
new Query(objectClass)
Creates a new maxleap ML.Query for the given ML.Object subclass.
Parameters:
| Name |
Type |
Description |
objectClass |
|
An instance of a subclass of ML.Object, or a ML className string. |
- Source:
Methods
(static) and(…var_args) → {ML.Query}
Constructs a ML.Query that is the AND of the passed in queries. For
example:
var compoundQuery = ML.Query.and(query1, query2, query3);
will create a compoundQuery that is an 'and' of the query1, query2, and
query3.
Parameters:
| Name |
Type |
Attributes |
Description |
var_args |
ML.Query
|
<repeatable>
|
The list of queries to AND. |
- Source:
Returns:
The query that is the AND of the passed in queries.
-
Type
-
ML.Query
(static) doCloudQuery(cql,, pvalues,, options) → {ML.Promise}
Retrieves a list of MLObjects that satisfy the CQL.
CQL syntax please see
CQL Guide.
Either options.success or options.error is called when the find
completes.
Parameters:
| Name |
Type |
Description |
cql, |
String
|
A CQL string, see CQL Guide. |
pvalues, |
Array
|
An array contains placeholder values. |
options |
Object
|
A Backbone-style options object,it's optional. |
- Source:
Returns:
A promise that is resolved with the results when
the query completes,it's optional.
-
Type
-
ML.Promise
(static) or(…var_args) → {ML.Query}
Constructs a ML.Query that is the OR of the passed in queries. For
example:
var compoundQuery = ML.Query.or(query1, query2, query3);
will create a compoundQuery that is an or of the query1, query2, and
query3.
Parameters:
| Name |
Type |
Attributes |
Description |
var_args |
ML.Query
|
<repeatable>
|
The list of queries to OR. |
- Source:
Returns:
The query that is the OR of the passed in queries.
-
Type
-
ML.Query
_addCondition()
Helper for condition queries
- Source:
_andQuery(queries) → {ML.Query}
Add constraint that both of the passed in queries matches.
Parameters:
| Name |
Type |
Description |
queries |
Array
|
|
- Source:
Returns:
Returns the query, so you can chain this call.
-
Type
-
ML.Query
_orQuery(queries) → {ML.Query}
Add constraint that at least one of the passed in queries matches.
Parameters:
| Name |
Type |
Description |
queries |
Array
|
|
- Source:
Returns:
Returns the query, so you can chain this call.
-
Type
-
ML.Query
_quote()
Converts a string into a regex that matches it.
Surrounding with \Q .. \E does this, we just need to escape \E's in
the text separately.
- Source:
addAscending(key) → {ML.Query}
Also sorts the results in ascending order by the given key. The previous sort keys have
precedence over this key.
Parameters:
| Name |
Type |
Description |
key |
String
|
The key to order by |
- Source:
Returns:
Returns the query so you can chain this call.
-
Type
-
ML.Query
addDescending(key) → {ML.Query}
Also sorts the results in descending order by the given key. The previous sort keys have
precedence over this key.
Parameters:
| Name |
Type |
Description |
key |
String
|
The key to order by |
- Source:
Returns:
Returns the query so you can chain this call.
-
Type
-
ML.Query
ascending(key) → {ML.Query}
Sorts the results in ascending order by the given key.
Parameters:
| Name |
Type |
Description |
key |
String
|
The key to order by. |
- Source:
Returns:
Returns the query, so you can chain this call.
-
Type
-
ML.Query
collection() → {ML.Collection}
Returns a new instance of ML.Collection backed by this query.
- Source:
Returns:
-
Type
-
ML.Collection
containedIn(key, values) → {ML.Query}
Add a constraint to the query that requires a particular key's value to
be contained in the provided list of values.
Parameters:
| Name |
Type |
Description |
key |
String
|
The key to check. |
values |
Array
|
The values that will match. |
- Source:
Returns:
Returns the query, so you can chain this call.
-
Type
-
ML.Query
contains(key, substring) → {ML.Query}
Add a constraint for finding string values that contain a provided
string. This may be slow for large datasets.
Parameters:
| Name |
Type |
Description |
key |
String
|
The key that the string to match is stored in. |
substring |
String
|
The substring that the value must contain. |
- Source:
Returns:
Returns the query, so you can chain this call.
-
Type
-
ML.Query
containsAll(key, values) → {ML.Query}
Add a constraint to the query that requires a particular key's value to
contain each one of the provided list of values.
Parameters:
| Name |
Type |
Description |
key |
String
|
The key to check. This key's value must be an array. |
values |
Array
|
The values that will match. |
- Source:
Returns:
Returns the query, so you can chain this call.
-
Type
-
ML.Query
Counts the number of objects that match this query.
Either options.success or options.error is called when the count
completes.
Parameters:
| Name |
Type |
Description |
options |
Object
|
A Backbone-style options object. |
- Source:
Returns:
A promise that is resolved with the count when
the query completes.
-
Type
-
ML.Promise
descending(key) → {ML.Query}
Sorts the results in descending order by the given key.
Parameters:
| Name |
Type |
Description |
key |
String
|
The key to order by. |
- Source:
Returns:
Returns the query, so you can chain this call.
-
Type
-
ML.Query
destroyAll(options) → {ML.Promise}
Delete objects retrieved by this query.
Parameters:
| Name |
Type |
Description |
options |
Object
|
Standard options object with success and error
callbacks. |
- Source:
Returns:
A promise that is fulfilled when the save
completes.
-
Type
-
ML.Promise
doesNotExist(key) → {ML.Query}
Add a constraint for finding objects that do not contain a given key.
Parameters:
| Name |
Type |
Description |
key |
String
|
The key that should not exist |
- Source:
Returns:
Returns the query, so you can chain this call.
-
Type
-
ML.Query
doesNotMatchKeyInQuery(key, queryKey, query) → {ML.Query}
Add a constraint that requires that a key's value not match a value in
an object returned by a different ML.Query.
Parameters:
| Name |
Type |
Description |
key |
String
|
The key that contains the value that is being
excluded. |
queryKey |
String
|
The key in the objects returned by the query to
match against. |
query |
ML.Query
|
The query to run. |
- Source:
Returns:
Returns the query, so you can chain this call.
-
Type
-
ML.Query
doesNotMatchQuery(key, query) → {ML.Query}
Add a constraint that requires that a key's value not matches a
ML.Query constraint.
Parameters:
| Name |
Type |
Description |
key |
String
|
The key that the contains the object to match the
query. |
query |
ML.Query
|
The query that should not match. |
- Source:
Returns:
Returns the query, so you can chain this call.
-
Type
-
ML.Query
each(callback, options) → {ML.Promise}
Iterates over each result of a query, calling a callback for each one. If
the callback returns a promise, the iteration will not continue until
that promise has been fulfilled. If the callback returns a rejected
promise, then iteration will stop with that error. The items are
processed in an unspecified order. The query may not have any sort order,
and may not use limit or skip.
Parameters:
| Name |
Type |
Description |
callback |
function
|
Callback that will be called with each result
of the query. |
options |
Object
|
An optional Backbone-like options object with
success and error callbacks that will be invoked once the iteration
has finished. |
- Source:
Returns:
A promise that will be fulfilled once the
iteration has completed.
-
Type
-
ML.Promise
endsWith(key, suffix) → {ML.Query}
Add a constraint for finding string values that end with a provided
string. This will be slow for large datasets.
Parameters:
| Name |
Type |
Description |
key |
String
|
The key that the string to match is stored in. |
suffix |
String
|
The substring that the value must end with. |
- Source:
Returns:
Returns the query, so you can chain this call.
-
Type
-
ML.Query
equalTo(key, value) → {ML.Query}
Add a constraint to the query that requires a particular key's value to
be equal to the provided value.
Parameters:
| Name |
Type |
Description |
key |
String
|
The key to check. |
value |
|
The value that the ML.Object must contain. |
- Source:
Returns:
Returns the query, so you can chain this call.
-
Type
-
ML.Query
Add a constraint for finding objects that contain the given key.
Parameters:
| Name |
Type |
Description |
key |
String
|
The key that should exist. |
- Source:
Returns:
Returns the query, so you can chain this call.
-
Type
-
ML.Query
Retrieves a list of MLObjects that satisfy this query.
Either options.success or options.error is called when the find
completes.
Parameters:
| Name |
Type |
Description |
options |
Object
|
A Backbone-style options object. |
- Source:
Returns:
A promise that is resolved with the results when
the query completes.
-
Type
-
ML.Promise
Retrieves at most one ML.Object that satisfies this query.
Either options.success or options.error is called when it completes.
success is passed the object if there is one. otherwise, undefined.
Parameters:
| Name |
Type |
Description |
options |
Object
|
A Backbone-style options object. |
- Source:
Returns:
A promise that is resolved with the object when
the query completes.
-
Type
-
ML.Promise
get(objectId, options)
Constructs a ML.Object whose id is already known by fetching data from
the server. Either options.success or options.error is called when the
find completes.
Parameters:
| Name |
Type |
Description |
objectId |
|
The id of the object to be fetched. |
options |
Object
|
A Backbone-style options object. |
- Source:
greaterThan(key, value) → {ML.Query}
Add a constraint to the query that requires a particular key's value to
be greater than the provided value.
Parameters:
| Name |
Type |
Description |
key |
String
|
The key to check. |
value |
|
The value that provides an lower bound. |
- Source:
Returns:
Returns the query, so you can chain this call.
-
Type
-
ML.Query
greaterThanOrEqualTo(key, value) → {ML.Query}
Add a constraint to the query that requires a particular key's value to
be greater than or equal to the provided value.
Parameters:
| Name |
Type |
Description |
key |
String
|
The key to check. |
value |
|
The value that provides an lower bound. |
- Source:
Returns:
Returns the query, so you can chain this call.
-
Type
-
ML.Query
include(key) → {ML.Query}
Include nested ML.Objects for the provided key. You can use dot
notation to specify which fields in the included object are also fetch.
Parameters:
| Name |
Type |
Description |
key |
String
|
The name of the key to include. |
- Source:
Returns:
Returns the query, so you can chain this call.
-
Type
-
ML.Query
lessThan(key, value) → {ML.Query}
Add a constraint to the query that requires a particular key's value to
be less than the provided value.
Parameters:
| Name |
Type |
Description |
key |
String
|
The key to check. |
value |
|
The value that provides an upper bound. |
- Source:
Returns:
Returns the query, so you can chain this call.
-
Type
-
ML.Query
lessThanOrEqualTo(key, value) → {ML.Query}
Add a constraint to the query that requires a particular key's value to
be less than or equal to the provided value.
Parameters:
| Name |
Type |
Description |
key |
String
|
The key to check. |
value |
|
The value that provides an upper bound. |
- Source:
Returns:
Returns the query, so you can chain this call.
-
Type
-
ML.Query
Sets the limit of the number of results to return. The default limit is
100, with a maximum of 1000 results being returned at a time.
Parameters:
| Name |
Type |
Description |
n |
Number
|
the number of results to limit to. |
- Source:
Returns:
Returns the query, so you can chain this call.
-
Type
-
ML.Query
matches(key, regex) → {ML.Query}
Add a regular expression constraint for finding string values that match
the provided regular expression.
This may be slow for large datasets.
Parameters:
| Name |
Type |
Description |
key |
String
|
The key that the string to match is stored in. |
regex |
RegExp
|
The regular expression pattern to match. |
- Source:
Returns:
Returns the query, so you can chain this call.
-
Type
-
ML.Query
matchesKeyInQuery(key, queryKey, query) → {ML.Query}
Add a constraint that requires that a key's value matches a value in
an object returned by a different ML.Query.
Parameters:
| Name |
Type |
Description |
key |
String
|
The key that contains the value that is being
matched. |
queryKey |
String
|
The key in the objects returned by the query to
match against. |
query |
ML.Query
|
The query to run. |
- Source:
Returns:
Returns the query, so you can chain this call.
-
Type
-
ML.Query
matchesQuery(key, query) → {ML.Query}
Add a constraint that requires that a key's value matches a ML.Query
constraint.
Parameters:
| Name |
Type |
Description |
key |
String
|
The key that the contains the object to match the
query. |
query |
ML.Query
|
The query that should match. |
- Source:
Returns:
Returns the query, so you can chain this call.
-
Type
-
ML.Query
near(key, point) → {ML.Query}
Add a proximity based constraint for finding objects with key point
values near the point given.
Parameters:
| Name |
Type |
Description |
key |
String
|
The key that the ML.GeoPoint is stored in. |
point |
ML.GeoPoint
|
The reference ML.GeoPoint that is used. |
- Source:
Returns:
Returns the query, so you can chain this call.
-
Type
-
ML.Query
notContainedIn(key, values) → {ML.Query}
Add a constraint to the query that requires a particular key's value to
not be contained in the provided list of values.
Parameters:
| Name |
Type |
Description |
key |
String
|
The key to check. |
values |
Array
|
The values that will not match. |
- Source:
Returns:
Returns the query, so you can chain this call.
-
Type
-
ML.Query
notEqualTo(key, value) → {ML.Query}
Add a constraint to the query that requires a particular key's value to
be not equal to the provided value.
Parameters:
| Name |
Type |
Description |
key |
String
|
The key to check. |
value |
|
The value that must not be equalled. |
- Source:
Returns:
Returns the query, so you can chain this call.
-
Type
-
ML.Query
select(keys) → {ML.Query}
Restrict the fields of the returned ML.Objects to include only the
provided keys. If this is called multiple times, then all of the keys
specified in each of the calls will be included.
Parameters:
| Name |
Type |
Description |
keys |
Array
|
The names of the keys to include. |
- Source:
Returns:
Returns the query, so you can chain this call.
-
Type
-
ML.Query
sizeEqualTo(key, value) → {ML.Query}
Add a constraint to the query that requires a particular
array key's length to be equal to the provided value.
Parameters:
| Name |
Type |
Description |
key |
String
|
The array key to check. |
value |
|
The length value. |
- Source:
Returns:
Returns the query, so you can chain this call.
-
Type
-
ML.Query
Sets the number of results to skip before returning any results.
This is useful for pagination.
Default is to skip zero results.
Parameters:
| Name |
Type |
Description |
n |
Number
|
the number of results to skip. |
- Source:
Returns:
Returns the query, so you can chain this call.
-
Type
-
ML.Query
startsWith(key, prefix) → {ML.Query}
Add a constraint for finding string values that start with a provided
string. This query will use the backend index, so it will be fast even
for large datasets.
Parameters:
| Name |
Type |
Description |
key |
String
|
The key that the string to match is stored in. |
prefix |
String
|
The substring that the value must start with. |
- Source:
Returns:
Returns the query, so you can chain this call.
-
Type
-
ML.Query
toJSON() → {Object}
Returns a JSON representation of this query.
- Source:
Returns:
-
Type
-
Object
withinGeoBox(key, southwest, northeast) → {ML.Query}
Add a constraint to the query that requires a particular key's
coordinates be contained within a given rectangular geographic bounding
box.
Parameters:
| Name |
Type |
Description |
key |
String
|
The key to be constrained. |
southwest |
ML.GeoPoint
|
The lower-left inclusive corner of the box. |
northeast |
ML.GeoPoint
|
The upper-right inclusive corner of the box. |
- Source:
Returns:
Returns the query, so you can chain this call.
-
Type
-
ML.Query
withinKilometers(key, point, maxDistance) → {ML.Query}
Add a proximity based constraint for finding objects with key point
values near the point given and within the maximum distance given.
Radius of earth used is 6371.0 kilometers.
Parameters:
| Name |
Type |
Description |
key |
String
|
The key that the ML.GeoPoint is stored in. |
point |
ML.GeoPoint
|
The reference ML.GeoPoint that is used. |
maxDistance |
Number
|
Maximum distance (in kilometers) of results
to return. |
- Source:
Returns:
Returns the query, so you can chain this call.
-
Type
-
ML.Query
withinMiles(key, point, maxDistance) → {ML.Query}
Add a proximity based constraint for finding objects with key point
values near the point given and within the maximum distance given.
Radius of earth used is 3958.8 miles.
Parameters:
| Name |
Type |
Description |
key |
String
|
The key that the ML.GeoPoint is stored in. |
point |
ML.GeoPoint
|
The reference ML.GeoPoint that is used. |
maxDistance |
Number
|
Maximum distance (in miles) of results to
return. |
- Source:
Returns:
Returns the query, so you can chain this call.
-
Type
-
ML.Query
withinRadians(key, point, maxDistance) → {ML.Query}
Add a proximity based constraint for finding objects with key point
values near the point given and within the maximum distance given.
Parameters:
| Name |
Type |
Description |
key |
String
|
The key that the ML.GeoPoint is stored in. |
point |
ML.GeoPoint
|
The reference ML.GeoPoint that is used. |
maxDistance |
|
Maximum distance (in radians) of results to return. |
- Source:
Returns:
Returns the query, so you can chain this call.
-
Type
-
ML.Query


name: string
A unique name for the route that may be used to identify the route when generating URL fragments. Required when this route should support URL generation, such as with [[Router.generate]] or the route-href custom attribute.
name: string
A unique name for the route that may be used to identify the route when generating URL fragments. Required when this route should support URL generation, such as with [[Router.generate]] or the route-href custom attribute.


Hi, I am Arnav, a final year Computer Science undergraduate student at Nanyang Technological University in Singapore. If I'm not making really lame jokes, screaming at stars, or giving advice on extremely random topics to extremely random individuals, I'm probably working on something that I find exciting. In my free time I collect some thoughts on technology, the universe and everything on my blog, The Importance of Being Idle.
At NTU, I was the President of NTU Open Source Society, the in-house geek club. I was also the IT (Media) Officer of Computer Engineering Club, the Student Council of School Of Computer Engineering, where I was the Chief Editor of SCEne, the School's publication. You can also find some of my work in the Technology section in the old editions of The Tribune, the monthly campus newspaper, where I previously served as Layout Editor, Webmaster, and manager of all its online content.
Professionally, I interned at IBM Singapore Software Labs, where I worked on some really cool mobile stuff and before that, at a startup, XBRLWorks, where I worked on web stuff.
I have been a United follower for most of my life and a Oasis believer who is waiting for the day they re-unite. I'm also a Quicksilver enthusiast and a collector of keychains, empty refills of a certain brand and really bad jokes. When I am not doing any of the things mentioned above, I try to further my interests as a Web and iOS developer. I built dBauggle!, a word games catering to children with special needs, giving them a level playing field to play word games. I have a couple of Apps in the pipeline that I think will excite some people. I'll talk more about them when they're ready.
Apart from forking me on GitHub, you can email me, or call me on Skype. Here is where I loudly opine on Twitter, and here is what I do on Facebook. I also have a LinkedIn profile.
Thanks for stopping by!