Content-type: text/html
Manpage of CTAGS
CTAGS
Section: User Commands (1)
Updated: Version 5.5
Index
Return to Main Contents
NAME
ctags - Generate tag files for source code
SYNOPSIS
- ctags [options] [file(s)]
-
- etags [options] [file(s)]
-
DESCRIPTION
The ctags and etags programs (hereinafter collectively referred to
as ctags, except where distinguished) generate an index (or "tag") file
for a variety of language objects found in file(s).
This tag file allows these items to be quickly and easily located by a text
editor or other utility. A "tag" signifies a language object for which an
index entry is available (or, alternatively, the index entry created for that
object).
Alternatively, ctags can generate a cross reference file which lists, in
human readable form, information about the various source objects found in a
set of language files.
Tag index files are supported by numerous editors, which allow the user to
locate the object associated with a name appearing in a source file and jump
to the file and line which defines the name. Those known about at the time of
this release are:
-
Vi(1) and its derivatives (e.g. Elvis, Vim, Vile, Lemmy),
CRiSP,
Emacs,
FTE (Folding Text Editor),
JED,
jEdit,
NEdit (Nirvana Edit),
TSE (The SemWare Editor),
UltraEdit,
WorkSpace,
X2,
Zeus
Ctags is capable of generating different kinds of tags for each of many
different languages. For a complete list of supported languages, the names
by which they are recognized, and the kinds of tags which are generated for
each, see the --list-languages and --list-kinds options.
SOURCE FILES
Unless the --language-force option is specified, the language of each
source file is automatically selected based upon a mapping of file names to
languages. The mappings in effect for each language may be display using the
--list-maps option and may be changed using the --langmap option.
On platforms which support it, if the name of a file is not mapped
to a language and the file is executable, the first line of the file is
checked to see if the file is a "#!" script for a recognized language.
By default, all other files names are ignored. This permits running
ctags on all files in either a single directory (e.g. "ctags *"), or on
all files in an entire source directory tree (e.g. "ctags -R"), since only
those files whose names are mapped to languages will be scanned.
[The reason that .h extensions are mapped to C++ files rather than C files
is because it is common to use .h extensions in C++, and no harm results in
treating them as C++ files.]
OPTIONS
Despite the wealth of available options, defaults are set so that ctags
is most commonly executed without any options (e.g. "ctags *", or "ctags -R"),
which will create a tag file in the current directory for all recognized
source files. The options described below are provided merely to allow custom
tailoring to meet special needs.
Note that spaces separating the single-letter options from their parameters
are optional.
Note also that the boolean parameters to the long form options (those
beginning with "--" and that take a "[=yes|no]" parameter) may
be omitted, in which case "=yes" is implied. (e.g. --sort
is equivalent to --sort=yes). Note further that "=1" and
"=on" are considered synonyms for "=yes", and that "=0"
and "=off" are considered synonyms for "=no".
Some options are either ignored or useful only when used while running in
etags mode (see -e option). Such options will be noted.
Most options may appear anywhere on the command line, affecting only those
files which follow the option. A few options, however, must appear before the
first file name and will be noted as such.
Options taking language names will accept those names in either upper or lower
case. See the --list-languages option for a complete list of the
built-in language names.
- -a
-
Equivalent to --append.
- -B
-
Use backward searching patterns (e.g. ?pattern?). [Ignored in etags mode]
- -e
-
Enable etags mode, which will create a tag file for use with the Emacs editor.
Alternatively, if ctags is invoked by a name containing the string
"etags" (either by renaming, or creating a link to, the executable), etags
mode will be enabled. This option must appear before the first file name.
- -f tagfile
-
Use the name specified by tagfile for the tag file (default is "tags",
or "TAGS" when running in etags mode). If tagfile is specified as
"-", then the tag file is written to standard output instead. Ctags
will stubbornly refuse to take orders if tagfile exists and its first
line contains something other than a valid tags line. This will save your neck
if you mistakenly type "ctags -f *.c", which would otherwise overwrite your
first C file with the tags generated by the rest! It will also refuse to
accept a multi character file name which begins with a '-' (dash) character,
since this most likely means that you left out the tag file name and this
option tried to grab the next option as the file name. If you really want to
name your output tag file "-ugly", specify it as "./-ugly". This option must
appear before the first file name. If this option is specified more than once,
only the last will apply.
- -F
-
Use forward searching patterns (e.g. /pattern/) (default).
[Ignored in etags mode]
- -h list
-
Specifies a list of file extensions, separated by periods, which are to be
interpreted as include (or header) files. To indicate files having no
extension, use a period not followed by a non-period character (e.g. ".",
"..x", ".x."). This option only affects how the scoping of a particular kinds
of tags is interpreted (i.e. whether or not they are considered as globally
visible or visible only within the file in which they are defined); it does
not map the extension to any particular language. Any tag which is located in
a non-include file and cannot be seen (e.g. linked to) from another file is
considered to have file-limited (e.g. static) scope. No kind of tag appearing
in an include file will be considered to have file-limited scope. If the first
character in the list is a plus sign, then the extensions in the list will be
appended to the current list; otherwise, the list will replace the current
list. See, also, the --file-scope option. The default list is
".h.H.hh.hpp.hxx.h++.inc.def". To restore the default list, specify -h
default. Note that if an extension supplied to this option is not
already mapped to a particular language (see SOURCE FILES, above), you
will also need to use either the --langmap or --language-force
option.
- -I tokenlist
-
Specifies a list of tokens which are to be specially handled while parsing C
and C++ source files. This option is specifically provided to handle special
cases arising through the use of preprocessor macros. When the tokens listed
are simple tokens, these tokens will be ignored during parsing of the source
files. If a token is suffixed with a '+' character, ctags will also
ignore any parenthesis-enclosed argument list which may immediately follow the
token in the source files. If two tokens are separated with the '=' character,
the first token is replaced by the second token for parsing purposes. The list
of tokens may be supplied directly on the command line or read in from a
separate file. If the first character of tokenlist is '@', '.' or a
pathname separator ('/' or '\'), or the first two characters specify a drive
letter (e.g. "C:"), the parameter tokenlist will be interpreted as a
filename from which to read a list of tokens, one per input line.
Otherwise, tokenlist is a list of tokens (or token pairs) to be
specially handled, each delimited by a either a comma or by white space (in
which case the list should be quoted to keep the entire list as one command
line argument). Multiple -I options may be supplied. To clear the list
of ignore tokens, supply a single dash ("-") for tokenlist.
This feature is useful when preprocessor macros are used in such a way that
they cause syntactic confusion due to their presence. Indeed, this is the best
way of working around a number of problems caused by the presence of
syntax-busting macros in source files (see BUGS, below). Some examples
will illustrate this point.
-
int foo ARGDECL4(void *, ptr, long int, nbytes)
-
In the above example, the macro "ARGDECL4" would be mistakenly interpreted to
be the name of the function instead of the correct name of "foo". Specifying
-I ARGDECL4 results in the correct behavior.
-
/* creates an RCS version string in module */
MODULE_VERSION("$Revision: 1.30 $")
-
In the above example the macro invocation looks too much like a function
definition because it is not followed by a semicolon (indeed, it could even be
followed by a global variable definition that would look much like a K&R style
function parameter declaration). In fact, this seeming function definition
could possibly even cause the rest of the file to be skipped over while trying
to complete the definition. Specifying -I MODULE_VERSION+ would
avoid such a problem.
-
CLASS Example {
// your content here
};
-
The example above uses "CLASS" as a preprocessor macro which expands to
something different for each platform. For instance CLASS may be defined as
"class __declspec(dllexport)" on Win32 platforms and simply "class" on UNIX.
Normally, the absence of the C++ keyword "class" would cause the source file
to be incorrectly parsed. Correct behavior can be restored by specifying
-I CLASS=class.
- -L file
-
Read from file a list of file names for which tags should be generated.
If file is specified as "-", then file names are read from standard
input. File names read using this option are processed following file names
appearing on the command line. Options all also accepted in this input. If
this option is specified more than once, only the last will apply. Note:
file is read in line-oriented mode, where a new line is the only
delimiter and spaces are considered significant, in order that file names
containing spaces may be supplied; this can affect how options are parsed if
included in the input.
- -n
-
Equivalent to --excmd=number.
- -N
-
Equivalent to --excmd=pattern.
- -o tagfile
-
Equivalent to -f tagfile.
- -R
-
Equivalent to --recurse.
- -u
-
Equivalent to --sort=no (i.e. "unsorted").
- -V
-
Equivalent to --verbose.
- -w
-
This option is silently ignored for backward-compatibility with the ctags
of SVR4 Unix.
- -x
-
Print a tabular, human-readable cross reference (xref) file to standard output
instead of generating a tag file. The information contained in the output
includes: the tag name; the kind of tag; the line number, file name, and
source line (with extra white space condensed) of the file which defines the
tag. No tag file is written and all options affecting tag file output will be
ignored. Example applications for this feature are generating a listing of all
functions located in a source file (e.g. ctags -x --c-kinds=f
file), or generating a list of all externally visible global variables
located in a source file (e.g. ctags -x --c-kinds=v
--file-scope=no file). This option must appear before the first
file name.
- --append[=yes|no]
-
Indicates whether tags generated from the specified files should be appended
to those already present in the tag file or should replace them. This option
is off by default. This option must appear before the first file name.
- --etags-include=file
-
Include a reference to file in the tag file. This option may be
specified as many times as desired. This supports Emacs' capability to use a
tag file which "includes" other tag files. [Available only in etags mode]
- --exclude=[pattern]
-
Add pattern to a list of excluded files and directories. This option
may be specified as many times as desired. For each file name considered by
ctags, each pattern specified using this option will be compared
against both the complete path (e.g. some/path/base.ext) and the base name
(e.g. base.ext) of the file, thus allowing patterns which match a given file
name irrespective of its path, or match only a specific path. If appropriate
support is available from the runtime library of your C compiler, then
pattern may contain the usual shell wildcards (not regular expressions)
common on Unix (be sure to quote the option parameter to protect the wildcards
from being expanded by the shell before being passed to ctags; also be
aware that wildcards can match the slash character, '/'). You can determine if
shell wildcards are available on your platform by examining the output of the
--version option, which will include "+wildcards" in the compiled
feature list; otherwise, pattern is matched against file names using a
simple textual comparison.
If pattern begins with the character '@', then the rest of the string
is interpreted as a file name from which to read exclusion patterns, one per
line. If pattern is empty, the list of excluded patterns is cleared.
Note that at program startup, the default exclude list contains "EIFGEN",
"SCCS", "RCS", and "CVS", which are names of directories for which it is
generally not desirable to descend while processing the --recurse
option.
- --excmd=type
-
Determines the type of EX command used to locate tags in the source file.
[Ignored in etags mode]
The valid values for type (either the entire word or the first letter is
accepted) are:
-
- number
-
Use only line numbers in the tag file for locating tags. This has four
advantages:
-
- 1.
-
Significantly reduces the size of the resulting tag file.
- 2.
-
Eliminates failures to find tags because the line defining the tag has
changed, causing the pattern match to fail (note that some editors, such as
vim, are able to recover in many such instances).
- 3.
-
Eliminates finding identical matching, but incorrect, source lines (see
BUGS, below).
- 4.
-
Retains separate entries in the tag file for lines which are identical in
content. In pattern mode, duplicate entries are dropped because the
search patterns they generate are identical, making the duplicate entries
useless.
-
However, this option has one significant drawback: changes to the source files
can cause the line numbers recorded in the tag file to no longer correspond
to the lines in the source file, causing jumps to some tags to miss the target
definition by one or more lines. Basically, this option is best used when the
source code to which it is applied is not subject to change. Selecting this
option type causes the following options to be ignored: -BF.
- pattern
-
Use only search patterns for all tags, rather than the line numbers usually
used for macro definitions. This has the advantage of not referencing obsolete
line numbers when lines have been added or removed since the tag file was
generated.
- mixed
-
In this mode, patterns are generally used with a few exceptions. For C, line
numbers are used for macro definition tags. This was the default format
generated by the original ctags and is, therefore, retained as the
default for this option. For Fortran, line numbers are used for common blocks
because their corresponding source lines are generally identical, making
pattern searches useless for finding all matches.
- --extra=[+|-]flags
-
Specifies whether to include extra tag entries for certain kinds of
information. The parameter flags is a set of one-letter flags, each
representing one kind of extra tag entry to include in the tag file. If
flags is preceded by by either the '+' or '-' character, the effect of
each flag is added to, or removed from, those currently enabled; otherwise the
flags replace any current settings. The meaning of each flag is as follows:
-
- f
-
Include an entry for the base file name of every source file (e.g.
"example.c"), which addresses the first line of the file.
- q
-
Include an extra class-qualified tag entry for each tag which is a member
of a class (for languages for which this information is extracted; currently
C++, Eiffel, and Java). The actual form of the qualified tag depends upon the
language from which the tag was derived (using a form that is most natural for
how qualified calls are specified in the language). For C++, it is in the form
"class::member"; for Eiffel and Java, it is in the form "class.member". This
may allow easier location of a specific tags when multiple occurrences of a
tag name occur in the tag file. Note, however, that this could potentially
more than double the size of the tag file.
- --fields=[+|-]flags
-
Specifies the available extension fields which are to be included in the
entries of the tag file (see TAG FILE FORMAT, below, for more
information). The parameter flags is a set of one-letter flags, each
representing one type of extension field to include, with the following
meanings (disabled by default unless indicated):
-
- a
-
Access (or export) of class members
- f
-
File-restricted scoping [enabled]
- i
-
Inheritance information
- k
-
Kind of tag as a single letter [enabled]
- K
-
Kind of tag as full name
- l
-
Language of source file containing tag
- m
-
Implementation information
- n
-
Line number of tag definition
- s
-
Scope of tag definition [enabled]
- S
-
Signature of routine (e.g. prototype or parameter list)
- z
-
Include the "kind:" key in kind field
-
Each letter or group of letters may be preceded by either '+' to add it to the
default set, or '-' to exclude it. In the absence of any preceding '+' or '-'
sign, only those kinds explicitly listed in flags will be included in
the output (i.e. overriding the default set). This option is ignored if the
option --format=1 has been specified. The default value
of this options is fks.
- --file-scope[=yes|no]
-
Indicates whether tags scoped only for a single file (i.e. tags which cannot
be seen outside of the file in which they are defined, such as "static" tags)
should be included in the output. See, also, the -h option. This option
is enabled by default.
- --filter[=yes|no]
-
Causes ctags to behave as a filter, reading source file names from
standard input and printing their tags to standard output on a file-by-file
basis. If --sorted is enabled, tags are sorted only within the source
file in which they are defined. File names are read from standard output in
line-oriented input mode (see note for -L option) and only after file
names listed on the command line or from any file supplied using the -L
option. When this option is enabled, the options -f, -o,
and --totals are ignored. This option is quite esoteric and is disabled
by default. This option must appear before the first file name.
- --filter-terminator=string
-
Specifies a string to print to standard output following the tags for each
file name parsed when the --filter option is enabled. This may permit an
application reading the output of ctags to determine when the output for each
file is finished. Note that if the file name read is a directory and
--recurse is enabled, this string will be printed only one once at the
end of all tags found for by descending the directory. This string will always
be separated from the last tag line for the file by its terminating newline.
This option is quite esoteric and is empty by default. This option must appear
before the first file name.
- --format=level
-
Change the format of the output tag file. Currently the only valid values for
level are 1 or 2. Level 1 specifies the original tag file
format and level 2 specifies a new extended format containing extension fields
(but in a manner which retains backward-compatibility with original
vi(1) implementations). The default level is 2. This option must appear
before the first file name. [Ignored in etags mode]
- --help
-
Prints to standard output a detailed usage description.
- --if0[=yes|no]
-
Indicates a preference as to whether code within an "#if 0" branch of a
preprocessor conditional should be examined for non-macro tags (macro tags are
always included). Because the intent of this construct is to disable code, the
default value of this options is no. Note that this indicates a
preference only and does not guarantee skipping code within an "#if 0" branch,
since the fall-back algorithm used to generate tags when preprocessor
conditionals are too complex follows all branches of a conditional. This
option is disabled by default.
- --<LANG>-kinds=[+|-]kinds
-
Specifies a list of language-specific kinds of tags (or kinds) to include in
the output file for a particular language, where <LANG> is
case-insensitive and is one of the built-in language names (see the
--list-languages option for a complete list). The parameter kinds
is a group of one-letter flags designating kinds of tags (particular to the
language) to either include or exclude from the output. The specific sets of
flags recognized for each language, their meanings and defaults may be list
using the --list-kinds option. Each letter or group of letters may be
preceded by either '+' to add it to, or '-' to remove it from, the default
set. In the absence of any preceding '+' or '-' sign, only those kinds
explicitly listed in kinds will be included in the output (i.e.
overriding the default for the specified language).
As an example for the C language, in order to add prototypes and external
variable declarations to the default set of tag kinds, but exclude macros,
use --c-kinds=+px-d; to include only tags for functions, use
--c-kinds=f.
- --langdef=name
-
Defines a new user-defined language, name, to be parsed with regular
expressions. Once defined, name may be used in other options taking
language names. The typical use of this option is to first define the
language, then map file names to it using --langmap, then specify
regular expressions using --regex-<LANG> to define how its tags are
found.
- --langmap=map[,map[...]]
-
Controls how file names are mapped to languages (see the --list-maps
option). Each comma-separated map consists of the language name (either
a built-in or user-defined language), a colon, and a list of file extensions
and/or file name patterns. A file extension is specified by preceding the
extension with a period (e.g. ".c"). A file name pattern is specified by
enclosing the pattern in parentheses (e.g. "([Mm]akefile)"). If appropriate
support is available from the runtime library of your C compiler, then the
file name pattern may contain the usual shell wildcards common on Unix (be
sure to quote the option parameter to protect the wildcards from being
expanded by the shell before being passed to ctags). You can determine
if shell wildcards are available on your platform by examining the output of
the --version option, which will include "+wildcards" in the compiled
feature list; otherwise, the file name patterns are matched against file names
using a simple textual comparison.
If the first character in a map is a plus sign, then the extensions and file
name patterns in that map will be appended to the current map for that
language; otherwise, the map will replace the current map. For example, to
specify that only files with extensions of .c and .x are to be treated as C
language files, use "--langmap=c:.c.x"; to also add files with
extensions of .j as Java language files, specify
"--langmap=c:.c.x,java:+.j". To map makefiles (.e.g files
named either "Makefile", "makefile", or having the extension ".mak") to a
language called "make", specify "--langmap=make:([Mm]akefile).mak".
To map files having no extension, specify a period not followed by a
non-period character (e.g. ".", "..x", ".x."). To clear the mapping for a
particular language (thus inhibiting automatic generation of tags for that
language), specify an empty extension list (e.g.
"--langmap=fortran:"). To restore the default language mappings
for all a particular language, supply the keyword "default" for the mapping.
To specify restore the default language mappings for all languages, specify
"--langmap=default". Note that file extensions are tested before
file name patterns when inferring the language of a file.
- --language-force=language
-
By default, ctags automatically selects the language of a source file,
ignoring those files whose language cannot be determined (see
SOURCE FILES, above). This option forces the specified language
(case-insensitive; either built-in or user-defined) to be used for every
supplied file instead of automatically selecting the language based upon its
extension. In addition, the special value auto indicates that the
language should be automatically selected (which effectively disables this
option).
- --languages=[+|-]list
-
Specifies the languages for which tag generation is enabled, with list
containing a comma-separated list of language names (case-insensitive; either
built-in or user-defined). If the first language of list is not preceded
by either a '+' or '-', the current list will be cleared before adding or
removing the languages in list. Until a '-' is encountered, each
language in the list will be added to the current list. As either the '+' or
removed from the current list, respectively. Thus, it becomes simple to
replace the current list with a new one, or to add or remove languages from
the current list. The actual list of files for which tags will be generated
depends upon the language extension mapping in effect (see the --langmap
option). Note that all languages, including user-defined languages are enabled
unless explicitly disabled using this option. Language names included in
list may be any built-in language or one previously defined with
--langdef. The default is "all", which is also accepted as a valid
argument. See the --list-languages option for a complete list of the
built-in language names.
- --license
-
Prints a summary of the software license to standard output.
- --line-directives[=yes|no]
-
Specifies whether "#line" directives should be recognized. These are present
in the output of preprocessors and contain the line number, and possibly the
file name, of the original source file(s) from which the preprocessor output
file was generated. When enabled, this option will cause ctags to
generate tag entries marked with the file names and line numbers of their
locations original source file(s), instead of their actual locations in the
preprocessor output. The actual file names placed into the tag file will have
the same leading path components as the preprocessor output file, since it is
assumed that the original source files are located relative to the
preprocessor output file (unless, of course, the #line directive specifies an
absolute path). This option is off by default. Note: This option is
generally only useful when used together with the --excmd=number
(-n) option. Also, you may have to use either the --langmap or
--language-force option if the extension of the preprocessor output file
is not known to ctags.
- --links[=yes|no]
-
Indicates whether symbolic links (if supported) should be followed. When
disabled, symbolic links are ignored. This option is on by default.
- --list-kinds[=language|all]
-
Lists the tag kinds recognized for either the specified language or all
languages. Each kind of tag recorded in the tag file is represented by a
one-letter flag, which is also used to filter the tags placed into the output
through use of the --<LANG>-kind option. Note that some languages and/or
tag kinds may be implemented using regular expressions and may not be
available if regex support is not compiled into ctags (see the
--regex-<LANG> option). Each kind listed is enabled unless followed by
"[off]".
- --list-maps[=language|all]
-
Lists the file extensions and file name patterns which associate a file name
with a language for either the specified language or all languages. See
the --langmap option, and SOURCE FILES, above.
- --list-languages
-
Lists the names of the languages understood by ctags. These language
names are case insensitive and may be used in the --language-force,
--languages, --<LANG>-kinds, and --regex-<LANG> options.
- --options=file
-
Read additional options from file. As a special case, if
--options=NONE is specified as the first option on the command
line, it will disable the automatic reading of any configuration options from
either a file or the environment (see FILES).
- --recurse[=yes|no]
-
Recurse into directories encountered in the list of supplied files. If the
list of supplied files is empty and no file list is specified with the
-L option, then the current directory (i.e. ".") is assumed. Symbolic
links are followed. If you don't like these behaviors, either explicitly
specify the files or pipe the output of find(1) into ctags -L-
instead. Note: This option is not supported on all platforms at present.
It is available if the output of the --help option includes this option.
See, also, the --exclude to limit recursion.
- --regex-<LANG>=/regexp/replacement/[kind-spec/][flags]
-
The /regexp/replacement/ pair define a regular expression replacement
pattern, similar in style to sed substitution commands, with which to
generate tags from source files mapped to the named language, <LANG>,
(case-insensitive; either a built-in or user-defined language). The regular
expression, regexp, defines an extended regular expression (roughly that
used by egrep(1)), which is used to locate a single source line
containing a tag and may specify tab characters using \t. When a matching
line is found, a tag will be generated for the name defined by
replacement, which generally will contain the special back-references
\1 through \9 to refer to matching sub-expression groups within
regexp. The '/' separator characters shown in the parameter to the
option can actually be replaced by any character. Note that whichever
separator character is used will have to be escaped with a backslash ('\')
character wherever it is used in the parameter as something other than a
separator. The regular expression defined by this option is added to the
current list of regular expressions for the specified language unless the
parameter is omitted, in which case the current list is cleared.
Unless modified by flags, regexp is interpreted as a Posix
extended regular expression. The replacement should expand for all
matching lines to a non-empty string of characters, or a warning message will
be reported. An optional kind specifier for tags matching regexp may
follow replacement, which will determine what kind of tag is reported in
the "kind" extension field (see TAG FILE FORMAT, below). The full form
of kind-spec is in the form of a single letter, a comma, a name (without
spaces), a comma, a description, followed by a separator, which specify
the short and long forms of the kind value and its textual description
(displayed using --list-kinds). Either the kind name and/or the
description may be omitted. If kind-spec is omitted, it defaults to
"r,regex". Finally, flags are one or more single-letter characters
having the following effect upon the interpretation of regexp:
-
- b
-
The pattern is interpreted as a Posix basic regular expression.
- e
-
The pattern is interpreted as a Posix extended regular expression (default).
- i
-
The regular expression is to be applied in a case-insensitive manner.
-
Note that this option is available only if ctags was compiled with
support for regular expressions, which depends upon your platform. You can
determine if support for regular expressions is compiled in by examining the
output of the --version option, which will include "+regex" in the
compiled feature list.
For more information on the regular expressions used by ctags, see
either the regex(5,7) man page, or the GNU info documentation for regex
(e.g. "info regex").
- --sort[=yes|no|foldcase]
-
Indicates whether the tag file should be sorted on the tag name (default is
yes). Note that the original vi(1) required sorted tags.
The foldcase value specifies case insensitive (or case-folded) sorting.
Fast binary searches of tag files sorted with case-folding will require
special support from tools using tag files, such as that found in the ctags
readtags library, or Vim version 6.2 or higher (using "set ignorecase"). This
option must appear before the first file name. [Ignored in etags mode]
- --tag-relative[=yes|no]
-
Indicates that the file paths recorded in the tag file should be relative to
the directory containing the tag file, rather than relative to the current
directory, unless the files supplied on the command line are specified with
absolute paths. This option must appear before the first file name. The
default is yes when running in etags mode (see the -e
option), no otherwise.
- --totals[=yes|no]
-
Prints statistics about the source files read and the tag file written during
the current invocation of ctags. This option is off by default.
This option must appear before the first file name.
- --verbose[=yes|no]
-
Enable verbose mode. This prints out information on option processing and a
brief message describing what action is being taken for each file considered
by ctags. Normally, ctags does not read command line arguments
until after options are read from the configuration files (see FILES,
below) and the CTAGS environment variable. However, if this option is
the first argument on the command line, it will take effect before any options
are read from these sources. The default is no.
- --version
-
Prints a version identifier for ctags to standard output. This is
guaranteed to always contain the string "Exuberant Ctags".
OPERATIONAL DETAILS
As ctags considers each file name in turn, it tries to determine the
language of the file by applying the following three tests in order: if the
file extension has been mapped to a language, if the file name matches a shell
pattern mapped to a language, and finally if the file is executable and its
first line specifies an interpreter using the Unix-style "#!" specification
(if supported on the platform). If a language was identified, the file is
opened and then the appropriate language parser is called to operate on the
currently open file. The parser parses through the file and adds an entry to
the tag file for each language object it is written to handle. See
TAG FILE FORMAT, below, for details on these entries.
This implementation of ctags imposes no formatting requirements on C
code as do legacy implementations. Older implementations of ctags tended to
rely upon certain formatting assumptions in order to help it resolve coding
dilemmas caused by preprocessor conditionals.
In general, ctags tries to be smart about conditional preprocessor
directives. If a preprocessor conditional is encountered within a statement
which defines a tag, ctags follows only the first branch of that
conditional (except in the special case of "#if 0", in which case it follows
only the last branch). The reason for this is that failing to pursue only one
branch can result in ambiguous syntax, as in the following example:
-
#ifdef TWO_ALTERNATIVES
struct {
#else
union {
#endif
-
short a;
long b;
}
Both branches cannot be followed, or braces become unbalanced and ctags
would be unable to make sense of the syntax.
If the application of this heuristic fails to properly parse a file,
generally due to complicated and inconsistent pairing within the conditionals,
ctags will retry the file using a different heuristic which does not
selectively follow conditional preprocessor branches, but instead falls back
to relying upon a closing brace ("}") in column 1 as indicating the end of a
block once any brace imbalance results from following a #if conditional branch.
Ctags will also try to specially handle arguments lists enclosed in
double sets of parentheses in order to accept the following conditional
construct:
-
extern void foo __ARGS((int one, char two));
Any name immediately preceding the "((" will be automatically ignored and
the previous name will be used.
C++ operator definitions are specially handled. In order for consistency with
all types of operators (overloaded and conversion), the operator name in the
tag file will always be preceded by the string "operator " (i.e. even if the
actual operator definition was written as "operator<<").
After creating or appending to the tag file, it is sorted by the tag name,
removing identical tag lines.
TAG FILE FORMAT
When not running in etags mode, each entry in the tag file consists of a
separate line, each looking like this in the most general case:
-
tag_name<TAB>file_name<TAB>ex_cmd;"<TAB>extension_fields
The fields and separators of these lines are specified as follows:
-
- 1.
-
tag name
- 2.
-
single tab character
- 3.
-
name of the file in which the object associated with the tag is located
- 4.
-
single tab character
- 5.
-
EX command used to locate the tag within the file; generally a search pattern
(either /pattern/ or ?pattern?) or line number (see --excmd). Tag file
format 2 (see --format) extends this EX command under certain
circumstances to include a set of extension fields (described below) embedded
in an EX comment immediately appended to the EX command, which leaves it
backward-compatible with original vi(1) implementations.
A few special tags are written into the tag file for internal purposes. These
tags are composed in such a way that they always sort to the top of the file.
Therefore, the first two characters of these tags are used a magic number to
detect a tag file for purposes of determining whether a valid tag file is
being overwritten rather than a source file.
Note that the name of each source file will be recorded in the tag file
exactly as it appears on the command line. Therefore, if the path you
specified on the command line was relative to the current directory, then it
will be recorded in that same manner in the tag file. See, however, the
--tag-relative option for how this behavior can be modified.
Extension fields are tab-separated key-value pairs appended to the end of the
EX command as a comment, as described above. These key value pairs appear in
the general form "key:value". Their presence in the lines of the
tag file are controlled by the --fields option. The possible keys and
the meaning of their values are as follows:
- access
-
Indicates the visibility of this class member, where value is specific
to the language.
- file
-
Indicates that the tag has file-limited visibility. This key has no
corresponding value.
- kind
-
Indicates the type, or kind, of tag. Its value is either one of the
corresponding one-letter flags described under the various
--<LANG>-kinds options above, or a full name. It is permitted (and is,
in fact, the default) for the key portion of this field to be omitted. The
optional behaviors are controlled with the --fields option.
- implementation
-
When present, this indicates a limited implementation (abstract vs. concrete)
of a routine or class, where value is specific to the language
("virtual" or "pure virtual" for C++; "abstract" for Java).
- inherits
-
When present, value. is a comma-separated list of classes from which
this class is derived (i.e. inherits from).
- signature
-
When present, value. is a language-dependent representation of the
signature of a routine. A routine signature in its complete form specifies the
return type of a routine and its formal argument list. This extension field is
presently supported only for C-based languages and does not include the return
type.
In addition, information on the scope of the tag definition may be available,
with the key portion equal to some language-dependent construct name and its
value the name declared for that construct in the program. This scope entry
indicates the scope in which the tag was found. For example, a tag generated
for a C structure member would have a scope looking like "struct:myStruct".
HOW TO USE WITH VI
Vi will, by default, expect a tag file by the name "tags" in the current
directory. Once the tag file is built, the following commands exercise the tag
indexing feature:
- vi -t tag
-
Start vi and position the cursor at the file and line where "tag" is defined.
- :ta tag
-
Find a tag.
- Ctrl-]
-
Find the tag under the cursor.
- Ctrl-T
-
Return to previous location before jump to tag (not widely implemented).
HOW TO USE WITH GNU EMACS
Emacs will, by default, expect a tag file by the name "TAGS" in the current
directory. Once the tag file is built, the following commands exercise the
tag indexing feature:
- M-x visit-tags-table <RET> FILE <RET>
-
Select the tag file, "FILE", to use.
- M-. [TAG] <RET>
-
Find the first definition of TAG. The default tag is the identifier under the
cursor.
- M-*
-
Pop back to where you previously invoked "M-.".
- C-u M-.
-
Find the next definition for the last tag.
For more commands, see the Tags topic in the Emacs info document.
HOW TO USE WITH NEDIT
NEdit version 5.1 and later can handle the new extended tag file format (see
--format). To make NEdit use the tag file, select "File->Load Tags
File". To jump to the definition for a tag, highlight the word, the press
Ctrl-D. NEdit 5.1 can can read multiple tag files from different directories.
Setting the X resource nedit.tagFile to the name of a tag file instructs NEdit
to automatically load that tag file at startup time.
CAVEATS
Because ctags is neither a preprocessor nor a compiler, use of
preprocessor macros can fool ctags into either missing tags or
improperly generating inappropriate tags. Although ctags has been
designed to handle certain common cases, this is the single biggest cause of
reported problems. In particular, the use of preprocessor constructs which
alter the textual syntax of C can fool ctags. You can work around many
such problems by using the -I option.
White space is treated as a separator for file names and options read from
list files, specified using the -L option, and in filter mode (specified
using the --filter option). Therefore, it is not currently possible to
supply file names or other options containing embedded white space (spaces,
etc.) through these options.
Note that when ctags generates uses patterns for locating tags (see
the --excmd option), it is entirely possible that the wrong line may be
found by your editor if there exists another source line which is identical to
the line containing the tag. The following example demonstrates this condition:
-
int variable;
/* ... */
void foo(variable)
int variable;
{
-
/* ... */
}
Depending upon which editor you use and where in the code you happen to be, it
is possible that the search pattern may locate the local parameter declaration
in foo() before it finds the actual global variable definition, since the
lines (and therefore their search patterns are identical). This can be avoided
by use of the --excmd=n option.
BUGS
Ctags has more options than ls(1).
When parsing a C++ member function definition (e.g. "className::function"),
ctags cannot determine whether the scope specifier is a class name or a
namespace specifier and always lists it as a class name in the scope portion
of the extension fields. Also, if a C++ function is defined outside of the
class declaration (the usual case), the access specification (i.e. public,
protected, or private) and implementation information (e.g. virtual, pure
virtual) contained in the function declaration are not known when the tag is
generated for the function definition. It will, however be available for
prototypes (e.g --c++-kinds=+p).
No qualified tags are generated for language objects inherited into a class.
ENVIRONMENT VARIABLES
- CTAGS
-
If this environment variable exists, it will be expected to contain a set of
default options which are read when ctags starts, after the
configuration files listed in FILES, below, are read, but before any
command line options are read. Options appearing on the command line will
override options specified in this variable. Only options will be read from
this variable. Note that all white space in this variable in considered a
separator, making it impossible to pass an option parameter containing an
embedded space. If this is a problem, use a configuration file instead.
- ETAGS
-
Similar to the CTAGS variable above, this variable, if found, will be
read when etags starts. If this variable is not found, etags will
try to use CTAGS instead.
- TMPDIR
-
On Unix-like hosts where mkstemp() is available, the value of this variable
specifies the directory in which to place temporary files. This can be useful
if the size of a temporary file becomes too large to fit on the partition
holding the default temporary directory defined at compilation time.
ctags creates temporary files only if either (1) an emacs-style tag file
is being generated, (2) the tag file is being sent to standard output, or (3)
the program was compiled to use an internal sort algorithm to sort the tag
files instead of the the sort utility of the operating system. If the sort
utility of the operating system is being used, it will generally observe this
variable also. Note that if ctags is setuid, the value of TMPDIR will be
ignored.
FILES
/ctags.cnf (on MSDOS, MSWindows only)
/etc/ctags.conf
/usr/local/etc/ctags.conf
$HOME/.ctags ($HOME/ctags.cnf on MSDOS, MSWindows)
.ctags (ctags.cnf on MSDOS, MSWindows)
-
If any of these configuration files exist, each will be expected to contain a
set of default options which are read in the order listed when ctags
starts, but before the CTAGS environment variable is read or any command
line options are read. This makes it possible to set up site-wide, personal
or project-level defaults. It is possible to compile ctags to read an
additional configuration file before any of those shown above, which will be
indicated if the output produced by the --version option lists the
"custom-conf" feature. Options appearing in the CTAGS environment
variable or on the command line will override options specified in these
files. Only options will be read from these files. Note that the option files
are read in line-oriented mode in which spaces are significant (since
shell quoting is not possible). Each line of the file is read as one command
line parameter (as if it were quoted with single quotes). Therefore, use new
lines to indicate separate command-line arguments.
- tags
-
The default tag file created by ctags.
- TAGS
-
The default tag file created by etags.
SEE ALSO
The official Exuberant Ctags web site at:
-
http://ctags.sourceforge.net
Also ex(1), vi(1), elvis, or, better yet, vim, the
official editor of ctags. For more information on vim, see the VIM
Pages web site at:
-
http://www.vim.org/
AUTHOR
Darren Hiebert<EMAIL_ADDRESS>http://DarrenHiebert.com/
MOTIVATION
"Think ye at all times of rendering some service to every member of the human
race."
"All effort and exertion put forth by man from the fullness of his heart is
worship, if it is prompted by the highest motives and the will to do service
to humanity."
-
-- From the Baha'i Writings
CREDITS
This version of ctags was originally derived from and inspired by the
ctags program by Steve Kirkendall<EMAIL_ADDRESS>that comes with the
Elvis vi clone (though virtually none of the original code remains).
Credit is also due Bram Moolenaar<EMAIL_ADDRESS>the author of vim, who
has devoted so much of his time and energy both to developing the editor as a
service to others, and to helping the orphans of Uganda.
The section entitled "HOW TO USE WITH GNU EMACS" was shamelessly stolen from
the info page for GNU etags.

Time: 05:02:47 GMT, April 01, 2003


National Data
- Population:
- Total Tests:
- Total U.S. Cases:
- Total Dead:
- Total Recovered:
- Per 100K People: Tests
- Per 100K People: Cases
- Positive Test Rate: %
- Recovery Rate for Confirmed Cases: %
- Death Rate for Confirmed Cases: %
- Active Confirmed Cases: %
State Data
- State Population:
- Total Tests in State:
- Total Cases in State:
- Total Dead in State:
- Total Recovered in State:
- Per 100K People: Tests
- Per 100K People: Cases
- Tests Per 100K People: %
- State Recovery Rate: %
- State Death Rate: %
- Active Confirmed Cases: %


About The Event
TogaHacks I is a 24 hour programming event where high school students all over Silicon Valley come together to develop a software or hardware project!
Where
Silicon Valley, California
When
Currently postponed due to COVID-19.
Saturday & Sunday
2021
Event Venue
TBD, California
We are currently finalizing our venue.
Event Schedule
Currently postponed due to COVID-19.
Hacker Check In Begins
Opening Ceremony
Team Formation
Lunch
Workshop 1
Snacks
Workshop 2
Dinner
Cup Stacking
Midnight Snack
Breakfast
Submissions to Devpost
Presentations and Judging
Prizes and Closing Ceremony
Event End
F.A.Q
-
Does this event cost money?
Not at all! It is completely free, thanks to the generous donations by our sponsors.
-
What is the theme?
We'll announce it at the event! Stay tuned.
-
What is a Hackathon?
A Hackathon is a 24 hour programming event where students work together to develop a software or hardware project.
-
Who can participate?
All high school students are welcome to participate!
-
What if I don't know how to code?
No problem! We will be hosting several workshops throughout the event intended to help you learn to code.
-
What should I bring?
A laptop and a charger is all that you need. A sleeping bag is recommended (if you plan to sleep 😉).
-
How do I form a team?
If you do not have a team already, there will be team formation at the beginning of the hackathon. This is an opportunity for you to meet new people and form teams. Each team should have a maximum of four people.
Team
Vignav Ramesh
Executive Director
Mason Wang
Executive Director
Howard Huang
Executive Director
Mateo Wang
Tech Director
Interested in joining the team? Fill out this form.
Advisors
Arman Rafati
Emeritus Executive Director
Tony Jiang
Emeritus Executive Director
Sidney Hough
Emeritus Sponsorship Director
Partners
Sponsor Us
We are under fiscally sponsored by a 501(c)(3) non-profit. All donations are tax-deductible.
Want to sponsor us? Email sponsor@togahacks.com.


pets
Trail Tails
Want to go hiking, visit a beach, or a park with your pup and make other friends? Create or Join an event today!
CREATE
Create your own event!
VIEW
Explore upcoming events!


Error 404
The page you are looking for might have been removed, had its name changed or is temporarily unavailable.
Please try to go back or return to the homepage.
Good luck.
The page you are looking for might have been removed, had its name changed or is temporarily unavailable.
Please try to go back or return to the homepage.
Good luck.


filmcritic.com presents a review from staff member David Bezanson. You can find the review with full credits at http://www.filmcritic.com/misc/emporium.nsf/2a460f93626cd4678625624c007f2b46/c07dc6534306c06d8825691c0006e12f?OpenDocument
SUNSHINE A film review by David Bezanson Copyright 2000 filmcritic.com filmcritic.com
Now that the 20th century is finally over, I guess it's time to start re-interpreting it. Hopefully, summarizers of the century will follow the example of Hungarian director Istvan Svabo and honestly face the truth, no matter how painful. (Unfortunately, many intellectuals don't always seem interested in the truth --- especially about subjects like communism, which many continue to embrace.)
In Sunshine, Svabo looks back through the last 100 years of his country's history for meaning, and finds some --- enough to fill a three-hour, soapy epic about the century's chaos. The film mostly works, and is a worthy addition to Svabo's art.
Sunshine begins at the end of the 19th century, focusing on three young people who take Hungarian surnames and abandon the traditions espoused by their father, a Jewish entrepeneur named Emmanuel Sonnenschein ("Sunshine" in English). The ambitious son Ignatz (Fiennes, who also plays Ignatz' son and grandson) rises to power in the Hungarian government, then goes down with the monarchy. His silly, free-spirited cousin Valerie (Jennifer Ehle) deserts him over his conformity and allegiance to the regime; his brother (James Frain) turns communist.
After WWI, the focus shifts from this triangle to Ignatz's son Adam (Fiennes again), who becomes an Olympic champion and public hero after renouncing Judaism, only to find his father's admonishment not to trust in political power proved true. When the Nazis ("philistines" as one character describes them) overrun Hungary, Adam fails to save his family from being killed or scattered. Valerie is almost the only survivor. She is played in later life by Rosemary Harris (Ehle's real-life mother), whose luminous performance is easily the film's best.
Adam's son Ivan (Fiennes once again) is scarred by watching his father's murder at Auschwitz and, after the war, becomes an official in the equally brutal and philistine Communist Party. The Communists are also anti-Semites (because they hate the wealthy classes) and Ivan finds himself again imprisoned and dehumanized. At the end of the film, Ivan and Valerie remember their family and faith, and Ivan changes his name back to Sonnenschein, though the name is all he has left. His house has been confiscated; the furniture, keepsakes, and cultural artifacts that decorate the movie are thrown onto a garbage truck.
Sunshine clearly cost some bucks to make, and the result is the most meticulous recreation of a historical period that I've seen on film. The screenplay is not as flawless: some characters are sketchy and others are unappealing (especially Adam's girlfriend, played by Rachel Wiesz) --- though to be fair, only Valerie and Ivan live long enough to reach maturity.  But ultimately, the film is redeemed by its religious core and its powerful use of images and themes, both good (love, freedom, civilization, family) and evil (politics, power, ambition, envy). The film starts off slow but gets better and better as it goes, building to a powerful, thoughtful conclusion.
In the film, Svabo clearly draws distinctions between good beliefs and bad beliefs. Aware that he has lost his faith and followed the false gods of political ideals, Ivan asks, "If there never was a God, then why do we miss Him so much?" Among the film's many characters, it is perhaps great-grandfather Emmanuel (played by David de Keyser) who comes off best, because he remains true to sensible beliefs.
On New Year's Day of 1900, Ignatz predicts that the new century will be a time of "love, justice, and tolerance." Lots of people probably still think the 20th century was a time of greater love, justice and tolerance (along with modern improvements, walking on the moon, etc.) so it's probably a good thing that the movie brutally underscores the irony of Ignatz's prediction. The 20th century was the most murderous and "philistine" century in history, in which Europe actually became less civilized. It was not a century of improvements but of "breaking all our inheritance" (as one character says) and throwing it onto garbage trucks.
At the end of the film and the century, Hungary knows freedom for the first time in almost a century. But in a world that is becoming ever more "philistine" (judging from say, Eminem's new CD), less religious, and less diverse, will the next century be much better?

The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


Old editors:
The original
, command line.
The 1st GUI
, must be downloaded.
The 2nd GUI
, primitive web interface.
The 3rd GUI
, advanced interface (still in development, but working).


The Metrix blockchain network
Better understand and manage risks in agricultural value chains!
Advisory services for farms should be based on site-specific data analysis. However, the current reality of data collection at the farm level is that most smallholder farmers do not keep farm records. Supply-chain actors buying products at the farm gate have realized the problem and have started collecting data from sourced farms. However, the lack of farm data availability and interoperability between different actors hinders the planning of supply-chain activities and the delivery of proper farmers’ advisory services. All actors realize the importance of bringing data together, what hinders data sharing is technical and governance issues surrounding data interoperability, data privacy, trust, and competitiveness.
The Metrix addresses the problem of lack of data interoperability at the supply side of the value chain. It applies data science to collectively provided data to produce smart-metrics for the supply side of the value chain. The Metrix is using a distributed data approach instead of centralized data storage. The advantage of such an approach is that nobody owns the newly calculated risk insights. It is a piece of common knowledge in the shared ledger that is available for all participating network peers and data providers.
The Metrix is a ‘gentleman’s agreement’ for data sharing among private sector value-chain actors and research for development organizations to produce better insights on value-chain risks. Technically spoken, it uses a blockchain network and encryption to self-enforce the informal agreement and guarantees that nobody can access the data origin. The Metrix joins multi-data-sources with scientific methods to calculate risk-metrics, developed in research projects and provided as algorithms and code to the Metrix blockchain. Risk indicators that are calculated from collectively shared farm data are aggregated on zoomable geographic tiles.
Better understand and manage risks in agricultural value chains!
A ‘gentleman’s’ trust-based data-sharing agreement underwritten by blockchain technology!
The Metrix delivers improved insights on risks by combining farm data.
Keeping the composite risk indicators in distributed ledger files!
Spatially located on hierarchical map tiles!


| Name | Mercator |
| EPSG Code | 9805 |
| OGC WKT | Mercator_2SP |
| Supported By | OGC WKT, PROJ.4 |
| Name | EPSG # | GeoTIFF ID | OGC WKT | Units | Notes |
|---|---|---|---|---|---|
| Latitude of first standard parallel | standard_parallel_1 | Angular | |||
| Latitude of natural origin | latitude_of_origin | Angular | |||
| Longitude of natural origin | central_meridian | Angular | |||
| False Easting | 6 | FalseEasting | false_easting | Linear | |
| False Northing | 7 | FalseNorthing | false_northing | Linear |
The difference between 1SP and 2SP formulations is that the initial parameters are different: in 1SP you start from the longitude of natural origin and the scale factor, while in 2SP you start from the longitude of natural origin and the latitude of one of the standard parallels (the other is symmetrical in relation to the equator). So, the formulas of 2SP are just those for 1SP after calculating the scale factor from the absolute value of the latitude of the standard parallels and the "e" parameter of the datum.
+proj=merc +lat_ts=Latitude of first standard parallel +lon_0=Longitude of natural origin +x_0=False Easting +y_0=False Northing
The Mercator projection is a special case of the Lambert Conic Conformal projection with the equator as the single standard parallel. All other parallels of latitude are straight lines and the meridians are also straight lines at right angles to the equator, equally spaced. It is little used for land mapping purposes but is in universal use for navigation charts and is the basis for the transverse and oblique forms of the Mercator. As well as being conformal, it has the particular property that straight lines drawn on it are lines of constant bearing. Thus navigators may derive their course from the angle the straight course line makes with the meridians.
In the few cases in which the Mercator projection is used for terrestrial applications or land mapping, such as in Indonesia prior to the introduction of the Universal Transverse Mercator, a scale factor may be applied to the projection. This has the same effect as choosing two standard parallels on which the true scale is maintained at equal north and south latitudes either side of the equator.
The formulas to derive projected Easting and Northing coordinates are:
For the two standard parallel case, k0 is first calculated from k0 = cos*1/(1 - e2sin2*1)1/2 where *1 is the absolute value of the first standard parallel (i.e. positive). Then, for both one and two standard parallel cases, E = FE + ak0(* - *0) N = FN + ak0 logn{tan(*/4 + */2)[(1 - esin*) / (1 + esin*)]e/2 } where symbols are as listed above and logarithms are natural. The reverse formulas to derive latitude and longitude from E and N values are: * = * + (e2/2 + 5e4/24 + e6/12 + 13e8/360) sin(2*) + (7e4/48 + 29e6/240 + 811e8/11520) sin(4*) + (7e6/120 + 81e8/1120) sin(6*) + (4279e8/161280) sin(8*) where * = */2 - 2 arctan t t = B (FN-N)/(ak0) B = base of the natural logarithm, 2.7182818... and for the 2 SP Case, k0 is calculated as for the forward transformation above. * = ((E - FE)/ak0) + *0","For Projected Coordinate System Pulkovo 1942 / Mercator Caspian Sea Parameters: Ellipsoid Krassowski 1940 a = 6378245.00m 1/f = 298.300 then e = 0.08181333 and e^2 = 0.00669342 Latitude first SP 42o00'00""N = 0.73303829 rad Longitude Natural Origin 51o00'00""E = 0.89011792 rad False Eastings FE 0.00 m False Northings (at equator) FN 0.00 m then natural origin at latitude of 0oN has scale factor k0= 0.74426089 Forward calculation for: Latitude 53o00'00.00""N = 0.9250245 rad Longitude 53o00'00.00""E = 0.9250245 rad gives Easting E = 165704.29 m Northing N = 5171848.07 m Reverse calculation for same easting and northing first gives : t = 0.33639129 chi = 0.92179596 Then Latitude = 53o00'00.000""N Longitude = 53o00'00.000""E"


| Home | Trees | Indices | Help |
|
|---|
|
|
object --+ | StructureProvider
Base class for all PDB data source providers.
Concrete classes need to implement the find
method, which
abstracts the retrieval of a PDB structure file by a structure
identifier. This is a hook method called internally by get
,
but subclasses can safely override both find
and {get} to in
order to achieve completely custom behavior.
| Nested Classes | |
|
__metaclass__ Metaclass for defining Abstract Base Classes (ABCs). |
| Instance Methods | |||
|
|||
| str or None |
|
||
| csb.bio.Structure |
|
||
|
Inherited from |
| Class Variables | |
__abstractmethods__ =
|
| Properties | |
|
Inherited from |
| Method Details |
Attempt to discover a PDB file, given a specific PDB
|
Discover, parse and return the PDB structure, corresponding to the
specified
|
| Home | Trees | Indices | Help |
|
|---|
| Generated by Epydoc 3.0.1 on Tue Jul 4 20:19:05 2017 | http://epydoc.sourceforge.net |


{% extends 'basic_app/base.html' %} {% load static %} {% block content %}
An AI based financial adviser and portfolio manager. Financely allows users to look up stock quotes and offers streamlined technical and financial analysis, news analysis, future price predictions and simple recommendations to buy, sell or hold stocks. Users can also set up there own portfolios and receive recommendations to maximise profits.
| Stock Symbol | Stock Name | Quantity | Date added | |
|---|---|---|---|---|
| {{stock.stock_symbol}} | {{stock.stock_name}} | {{stock.quantity}} | {{stock.date_added}} |


Telephone Reimbusment Persona
Name
Id No:
Grade Pay
Service Provider
Designation
Acc No:
Landline No:
Login
Remember me
Cancel
Forgot password?


Contents
classdef AsciiDevice < Zaber.Device
% ASCIIDEVICE Implements the Zaber.Device interface for the ASCII protocol. % % device = Zaber.ASCIIDEVICE.initialize(protocol, address); % protocol - An instance of Zaber.AsciiProtocol. % address - The numeric address of the device on a daisy chain. % Legal values are 1-99. % device - Output: An initialized instance of this class. % % This class represents a single Zaber device on a possible daisy chain % of multiple devices. An instance of this class can be used to % communicate with the device, and its peripherals if it has any. The % generic methods and properties defined by the base class can be used % for interaction with basic features. More advanced usage requires % use of protocol-specific commands; the request method is useful for % that as it will automatically ensure your message is addressed to the % device represented by the class instance. % % See also Zaber.Device, Zaber.Protocol.detect, Zaber.AsciiProtocol % Author: Zaber Technologies Software Team<EMAIL_ADDRESS>Public instance properties
properties (SetAccess = protected) % FLAGS Last status flags returned by the device. Values of empty % or '--' indicate no warnings and can be ignored. It is best % practice to check the flags after completing a move command or % when determining the cause of an error. Meanings are documented % in the Zaber ASCII Protocol Manual: % http://www.zaber.com/wiki/Manuals/ASCII_Protocol_Manual#Warning_Flags Flags end
Public instance methods
methods function reply = request(obj, aCommand, aData) % REQUEST Shortcut for transacting with a device. % reply = device.REQUEST(command, data); % % command - Command to send the device. This is always a % string, but can be empty or have multiple words. % data - Arguments for the command. Can be the empty array, % a number, a string or an array of numbers or % strings, depending on the command. % reply - Response from the device as an AsciiMessage. % % This method is a shortcut for calling device.Protocol.request() % with the difference that this method will automatically attach % the device and axis numbers and will update the device's flags % from the response each time. % % This method requires knowledge of the Zaber ASCII protocol. Use % it when other methods do not provide the functionality you need. % % See also AsciiProtocol.request, AsciiMessage message = Zaber.AsciiMessage(... obj.DeviceNo, aCommand, aData, 'AxisNo', obj.AxisNo); reply = obj.Protocol.request(message); if (isa(reply, 'Zaber.AsciiMessage')) obj.Flags = reply.Flags; else error('Zaber:AsciiDevice:request:communicationError', ... 'Device %d failed to respond to request.', ... obj.DeviceNo); end end function value = get(obj, aSetting) % GET Read a setting from the device. % value = device.GET(setting) % % setting - Name of the setting to read. See the % Zaber ASCII protocol manual for legal values: % http://www.zaber.com/wiki/Manuals/ASCII_Protocol_Manual#Device_Settings % value - Current value of the setting. This can be a number, an % array of numbers or a string. % % In the event of a communication error, an error will be thrown. % If the device returns an error result, a warning will occur and % the method will return the empty array. % % See also set value = []; reply = obj.request('get', aSetting); if (isa(reply, 'Zaber.AsciiMessage')) if (reply.IsError) warning('Zaber:AsciiDevice:get:readError', ... 'Attempt to read setting %s from device %d resulted in error %s.', ... aSetting, obj.DeviceNo, reply.DataString); else if (length(reply.Data) > 0) value = reply.Data; else value = reply.DataString; end end end end function result = set(obj, aSetting, aValue) % SET Write a value to a device setting. % result = device.set(setting, value) % % setting - Numeric identifier for the setting to write. For legal % values, see the Zaber ASCII protocol manual: % http://www.zaber.com/wiki/Manuals/ASCII_Protocol_Manual#Device_Settings % value - New value of the setting, as a 32-bit integer or a string. % Note that many settings expect integer values and will % produce an error if sent a number with a decimal point. % If passing in a number that is not expected to have a % decimal point, it is recommended that you cast it to % int32 first. % result - True if the write succeeded, or the reply message if % the device returned an error response. % % Errors will be thrown if there is a communication error. If the % setting does not exist, if the setting is read-only, or if the % value provided is out of range for the setting then a warning % will occur and the device's response message will be returned. % % See also get result = false; reply = obj.request(sprintf('set %s', aSetting), aValue); if (isa(reply, 'Zaber.AsciiMessage')) if (reply.IsError) warning('Zaber:BinaryDevice:set:writeError', ... 'Attempt to read setting %s from device %d resulted in error %s.', ... aSetting, obj.DeviceNo, reply.DataString); result = reply.DataString; else result = true; end end end function error = waitforidle(obj, aPingInterval) % WAITFORIDLE Block until the device stops moving. % error = device.WAITFORIDLE(); % error = device.WAITFORIDLE(interval); % % interval - Optional; number of seconds to wait between checks % of the device's state. Defaults to 0.1 seconds. % error - Return value, normally empty. If the device % entered an error state while this method was % checking for idleness, this method will return the % error message. % % This method will ping the device repeatedly until the device % either becomes idle or produces an error response. % % See also home, stop, moveabsolute, moverelative, % moveatvelocity, moveindexed interval = 0.1; if (nargin > 1) interval = aPingInterval; end moving = true; if (~obj.IsAxis) moving = false; end while (moving) reply = obj.request('', []); if (~isa(reply, 'Zaber.AsciiMessage')) moving = false; error = reply; elseif (reply.IsError) moving = false; error = reply.Data; elseif (reply.IsIdle) moving = false; else pause(interval); end end end function range = getrange(obj) % GETRANGE Determine the movement limits of the device. % range = device.GETRANGE(); % % range - A 1x2 matrix with the first entry being the lower bound % on legal device position and the second entry being the % upper bound. Empty array if the concept doesn't apply. % For a multi-axis controller the result will be an Nx2 % array where N is the number of axes. For rotary devices % the result is the range for one full rotation. Note % that the range returned may not reflect physical limits % if the device has been configured to use less than its % full range of travel. % % Reads device settings to determine the device's current idea of % its range of movement. Returns the empty array if the concept % does not apply to the device type. % % See also getposition, getnumindices, Units devices = obj; if (~isempty(obj.Axes)) devices = obj.Axes; elseif (~obj.IsAxis) range = []; return; end range = zeros(length(devices), 2); for (i = 1:length(devices)) d = devices(i); if (d.FirmwareVersion >= 6.06) range(i, 1) = d.get('limit.min'); else range(i, 1) = 0; end if (d.MotionType == Zaber.MotionType.Rotary) if (d.FirmwareVersion >= 6.20) rotationSize = d.get('limit.cycle.dist'); else rotationSize = d.get('limit.max'); end circle = d.Units.positiontonative(360.0); range(i, 2) = min(circle, rotationSize); else range(i, 2) = d.get('limit.max'); end end end function error = home(obj) % HOME Move the device to its home position. % error = device.HOME(); % % error - Error message from the device, if the command fails. See % the list of error codes in the Zaber Binary protocol % manual: % http://www.zaber.com/wiki/Manuals/Binary_Protocol_Manual#Error_Codes % % This command does not block. The device will likely be moving % after control returns to the caller. To wait for completion of % the move, use waitforidle(). % % See also stop, waitforidle, moveabsolute, moverelative, % moveatvelocity, moveindexed error = []; reply = obj.request('home', []); if (isa(reply, 'Zaber.AsciiMessage') && reply.IsError) error = reply.DataString; end end function error = moveabsolute(obj, aPosition) % MOVEABSOLUTE Move the device to an absolute position. % error = device.moveabsolute(position); % % position - Position to move to, in native device units. If this % device has multiple axes, this must be an array of % positions with the same number of entries as there are % axes. To move an individual axis, use its device entry % from the Axes property. % error - Error message from the device, if the command fails. % % This command does not block. The device will likely be moving % after control returns to the caller. To wait for completion of % the move, use waitforidle(). % % See also home, stop, waitforidle, getposition, moverelative, % moveatvelocity, moveindexed, Units error = obj.multiaxiscommand('move abs', int32(aPosition)); end function error = moverelative(obj, aDelta) % MOVERELATIVE Move the device by a relative amount. % error = device.MOVERELATIVE(delta); % % delta - Distance to move by, in native device units. % error - Error information from the device, if any. % % This method returns immediately upon receiving acknowledgement % from the device. Movement will continue after that. Use % waitforidle() to block until the move finishes. % % See also home, stop, waitforidle, getposition, moveabsolute, % moveatvelocity, moveindexed, Units error = obj.multiaxiscommand('move rel', int32(aDelta)); end function error = moveatvelocity(obj, aVelocity) % MOVEATVELOCITY Move the device at a specified velocity. % error = device.MOVEATVELOCITY(velocity); % % velocity - Speed to move at, in native device units. % error - Error information from the device, if any. % % This method returns immediately upon receiving acknowledgement % from the device. Movement will continue after that, until either % a limit is reached or a pre-empting command is send. Use % waitforidle() if you want to block until the end of the stage is % reached. % % See also home, stop, waitforidle, getposition, moveabsolute, % moverelative, moveindexed, Units error = obj.multiaxiscommand('move vel', int32(aVelocity)); end function error = stop(obj) % STOP Stop the device if it is moving. % error = device.STOP(); % % error - Error information from the device(s), if any. % % If this device is a multi-axis controller, all axes will be % stopped. To stop an individual axis, retrieve it from the Axes % property and invoke its stop method instead. % % See also waitforidle, moveabsolute, moverelative, moveatvelocity, % moveindexed error = []; reply = obj.request('stop', []); if (isa(reply, 'Zaber.AsciiMessage') && reply.IsError) error = reply.DataString; end end function pos = getposition(obj) % GETPOSITION Get the current device position in native units. % pos = device.GETPOSITION(); % % If there is a communication error or the device is not an axis, % the empty array will be returned. % % This method can be called while a device is moving, and will % return its position as of the time the message was received. % % See also stop, waitforidle, moveabsolute, moverelative, % moveatvelocity, moveindexed, getnumindices, Units pos = obj.get('pos'); end function num = getnumindices(obj) % GETNUMINDICES Determine how many indexed positions the device has. % num = getvice.GETNUMINDICES(); % % Return value is the maximum position that can be passed to % MOVEINDEXED. Returns zero on devices that do not support the % MOVEINDEXED command. % % This method is intended for use with devices such as the X-FWR % Filter Wheel holder. % % See also moveindexed, stop, waitforidle, getposition, range num = 0; reply = obj.request('get', 'limit.cycle.dist'); maxDist = []; if (isa(reply, 'Zaber.AsciiMessage') && ~reply.IsError) maxDist = reply.Data; else reply = obj.request('get', 'limit.max.dist'); if (isa(reply, 'Zaber.AsciiMessage') && ~reply.IsError) maxDist = reply.Data; end end if (~isempty(maxDist)) indexSize = obj.get('motion.index.dist'); if (~isempty(indexSize)) num = int32(floor(maxDist / indexSize)); end end end function error = moveindexed(obj, aIndex) % MOVEINDEXED Move to an indexed position. % error = device.MOVEINDEXED(index); % % index - The index of the position to move to. Minimum value is 1, % and maximum value is the number returned by % GETNUMINDICES. Will be rejected on devices that don't % support indexed moves. % error - Protocol-specific error code if the command is rejected % or generates an error. Empty on success. % % This command is intended for use with indexed-position devices % such as the Filter Wheel. Although the other movement commands % will often work with such devices, this method provides an easier % way to reach a useful position. % % This method returns immediately after communicating with the % device. The hardware may continue moving for some time afterward; % use WAITFORIDLE to wait for the move to complete. % % See also getnumindices, getposition, stop, waitforidle, % moveabsolute, moverelative, moveatvelocity error = obj.multiaxiscommand('move index', aIndex); end end
Public static methods
methods (Static) function instance = initialize(aProtocol, aDeviceNumber, aDeviceId) % INITIALIZE Construct a representation for a single device. % device = Zaber.AsciiDevice.INITIALIZE(protocol, address, id) % % protocol - An AsciiProtocol instance. % address - The daisy chain address of a device to represent. % id - The numeric device type ID of the device. % Optional; if not provided the device will be % queried for it. % obj - An initialized AsciiDevice instance. % % Given the daisy chain address and device type ID for a device % that has been found using the given protocol, queries the device % for its properties and constructs a new Zaber.Device subclass % instance to represent that device. % % See also AsciiDevice, BinaryDevice.initialize if (~isa(aProtocol, 'Zaber.AsciiProtocol')) error('Zaber:AsciiDevice:initialize:wrongProtocol', ... 'Protocol must be ASCII to use this method.'); end if (nargin > 2) deviceId = aDeviceId; else reply = aProtocol.request(... Zaber.AsciiMessage(aDeviceNumber, 'get', 'deviceid')); if (~isempty(reply) && ~reply.IsError) deviceId = reply.Data; else error('Zaber:AsciiDevice:initialize:idError', ... 'Failed to get the type ID for device %d.', ... aDeviceNumber); end end instance = Zaber.AsciiDevice(aProtocol, aDeviceNumber, deviceId); % Get the firmware version. data = instance.get('version'); if (isnumeric(data)) instance.FirmwareVersion = data; end % Get database record for device. db = Zaber.DeviceDatabase.instance(); deviceRecord = db.finddevice(instance.DeviceId); % Identify axes numAxes = instance.get('system.axiscount'); hasPeripherals = false; if (numAxes > 0) hasPeripherals = true; peripheralIds = zeros(numAxes); for (iAxis = 1:numAxes) reply = aProtocol.request(... Zaber.AsciiMessage(aDeviceNumber, 'get', 'peripheralid', ... 'AxisNo', iAxis)); if (~isempty(reply) && ~reply.IsError) peripheralIds(iAxis) = reply.Data; else hasPeripherals = false; end end end if (hasPeripherals) % Controller with peripherals instance.Name = db.getdevicename(deviceRecord); for (iAxis = 1:numAxes) axis = Zaber.AsciiDevice(instance.Protocol, ... instance.DeviceNo, instance.DeviceId); axis.AxisNo = iAxis; axis.IsAxis = true; axis.FirmwareVersion = instance.FirmwareVersion; % get axis peripheral ID axis.PeripheralId = peripheralIds(iAxis); % Get database record for peripheral. periRecord = db.findperipheral(deviceRecord, axis.PeripheralId); axis.Name = db.getdevicename(deviceRecord, periRecord); % Get unit conversion properties from the database. if (~isempty(periRecord)) [axis.MotionType, axis.Units] = ... db.determinemotiontype(deviceRecord, periRecord); % Get resolution axis.Units.Resolution = axis.get('resolution'); end instance.Axes = [instance.Axes, axis]; end else % Integrated device or non-controller device. % Get resolution resolution = instance.get('resolution'); if (~isempty(resolution)) instance.IsAxis = true; end % Get database record for peripheral. periRecord = db.findperipheral(deviceRecord, instance.PeripheralId); instance.Name = db.getdevicename(deviceRecord, periRecord); % Get unit conversion properties from the database. if (~isempty(periRecord)) [instance.MotionType, instance.Units] = ... db.determinemotiontype(deviceRecord, periRecord); instance.Units.Resolution = resolution; end end instance.IO = Zaber.AsciiIoPort.detect(instance); end end
Protected instance methods
methods (Access = protected) function obj = AsciiDevice(aProtocol, aDeviceNumber, aDeviceId) % ASCIIDEVICE Constructor. Initializes properties to their default values. % % Note there is no way for code other than a subclass to initialize % other device properties after constructing the object this way. % Application code should use Zaber.AsciiDevice.initialize instead. obj = obj@Zaber.Device(aProtocol, aDeviceNumber, aDeviceId); end function error = multiaxiscommand(obj, aCommand, aData) % Helper for the various move... methods. error = []; if (~isempty(obj.Axes)) for (i = 1:length(obj.Axes)) error = obj.Axes(i).multiaxiscommand(aCommand, aData(i)); if (~isempty(error)) break; end end else reply = obj.request(aCommand, aData); if (isa(reply, 'Zaber.AsciiMessage') && reply.IsError) error = reply.DataString; end end end end
end


Dec 3, 2017 - Third exchange for SuperiorCoin!! BTC-Alpha
Nov 24, 2017 - New Fork coming up on Nov 24th to V11.01 Fork V6, Please update daemon before block 101,000 Download
Nov 14, 2017 - Second exchange for SuperiorCoin!! Stocks.exchange
Oct 17, 2017 - New exchange for SuperiorCoin!! SouthXchange
| Time Sent | Transaction Hash | Amount | Mixin |
|---|


[ aws . autoscaling ]
Creates a launch configuration.
If you exceed your maximum limit of launch configurations, which by default is 100 per region, the call fails. For information about viewing and updating this limit, see describe-account-limits .
For more information, see Launch Configurations in the Auto Scaling User Guide .
See also: AWS API Documentation
create-launch-configuration
--launch-configuration-name <value>
[--image-id <value>]
[--key-name <value>]
[--security-groups <value>]
[--classic-link-vpc-id <value>]
[--classic-link-vpc-security-groups <value>]
[--user-data <value>]
[--instance-id <value>]
[--instance-type <value>]
[--kernel-id <value>]
[--ramdisk-id <value>]
[--block-device-mappings <value>]
[--instance-monitoring <value>]
[--spot-price <value>]
[--iam-instance-profile <value>]
[--ebs-optimized | --no-ebs-optimized]
[--associate-public-ip-address | --no-associate-public-ip-address]
[--placement-tenancy <value>]
[--cli-input-json <value>]
[--generate-cli-skeleton <value>]
--launch-configuration-name (string)
The name of the launch configuration. This name must be unique within the scope of your AWS account.
The ID of the Amazon Machine Image (AMI) to use to launch your EC2 instances. For more information, see Finding an AMI in the Amazon Elastic Compute Cloud User Guide .
The name of the key pair. For more information, see Amazon EC2 Key Pairs in the Amazon Elastic Compute Cloud User Guide .
One or more security groups with which to associate the instances.
If your instances are launched in EC2-Classic, you can either specify security group names or the security group IDs. For more information about security groups for EC2-Classic, see Amazon EC2 Security Groups in the Amazon Elastic Compute Cloud User Guide .
If your instances are launched into a VPC, specify security group IDs. For more information, see Security Groups for Your VPC in the Amazon Virtual Private Cloud User Guide .
Syntax:
"string" "string" ...
--classic-link-vpc-id (string)
The ID of a ClassicLink-enabled VPC to link your EC2-Classic instances to. This parameter is supported only if you are launching EC2-Classic instances. For more information, see ClassicLink in the Amazon Elastic Compute Cloud User Guide .
--classic-link-vpc-security-groups (list)
The IDs of one or more security groups for the specified ClassicLink-enabled VPC. This parameter is required if you specify a ClassicLink-enabled VPC, and is not supported otherwise. For more information, see ClassicLink in the Amazon Elastic Compute Cloud User Guide .
Syntax:
"string" "string" ...
The user data to make available to the launched EC2 instances. For more information, see Instance Metadata and User Data in the Amazon Elastic Compute Cloud User Guide .
The ID of the instance to use to create the launch configuration.
The new launch configuration derives attributes from the instance, with the exception of the block device mapping.
To create a launch configuration with a block device mapping or override any other instance attributes, specify them as part of the same request.
For more information, see Create a Launch Configuration Using an EC2 Instance in the Auto Scaling User Guide .
The instance type of the EC2 instance. For information about available instance types, see Available Instance Types in the Amazon Elastic Compute Cloud User Guide.
The ID of the kernel associated with the AMI.
The ID of the RAM disk associated with the AMI.
--block-device-mappings (list)
One or more mappings that specify how block devices are exposed to the instance. For more information, see Block Device Mapping in the Amazon Elastic Compute Cloud User Guide .
Shorthand Syntax:
VirtualName=string,DeviceName=string,Ebs={SnapshotId=string,VolumeSize=integer,VolumeType=string,DeleteOnTermination=boolean,Iops=integer,Encrypted=boolean},NoDevice=boolean ...
JSON Syntax:
[
{
"VirtualName": "string",
"DeviceName": "string",
"Ebs": {
"SnapshotId": "string",
"VolumeSize": integer,
"VolumeType": "string",
"DeleteOnTermination": true|false,
"Iops": integer,
"Encrypted": true|false
},
"NoDevice": true|false
}
...
]
--instance-monitoring (structure)
Enables detailed monitoring (true ) or basic monitoring (false ) for the Auto Scaling instances.
Shorthand Syntax:
Enabled=boolean
JSON Syntax:
{
"Enabled": true|false
}
The maximum hourly price to be paid for any Spot Instance launched to fulfill the request. Spot Instances are launched when the price you specify exceeds the current Spot market price. For more information, see Launching Spot Instances in Your Auto Scaling Group in the Auto Scaling User Guide .
--iam-instance-profile (string)
The name or the Amazon Resource Name (ARN) of the instance profile associated with the IAM role for the instance.
EC2 instances launched with an IAM role will automatically have AWS security credentials available. You can use IAM roles with Auto Scaling to automatically enable applications running on your EC2 instances to securely access other AWS resources. For more information, see Launch Auto Scaling Instances with an IAM Role in the Auto Scaling User Guide .
--ebs-optimized | --no-ebs-optimized (boolean)
Indicates whether the instance is optimized for Amazon EBS I/O. By default, the instance is not optimized for EBS I/O. The optimization provides dedicated throughput to Amazon EBS and an optimized configuration stack to provide optimal I/O performance. This optimization is not available with all instance types. Additional usage charges apply. For more information, see Amazon EBS-Optimized Instances in the Amazon Elastic Compute Cloud User Guide .
--associate-public-ip-address | --no-associate-public-ip-address (boolean)
Used for groups that launch instances into a virtual private cloud (VPC). Specifies whether to assign a public IP address to each instance. For more information, see Launching Auto Scaling Instances in a VPC in the Auto Scaling User Guide .
If you specify this parameter, be sure to specify at least one subnet when you create your group.
Default: If the instance is launched into a default subnet, the default is true . If the instance is launched into a nondefault subnet, the default is false . For more information, see Supported Platforms in the Amazon Elastic Compute Cloud User Guide .
The tenancy of the instance. An instance with a tenancy of dedicated runs on single-tenant hardware and can only be launched into a VPC.
You must set the value of this parameter to dedicated if want to launch Dedicated Instances into a shared tenancy VPC (VPC with instance placement tenancy attribute set to default ).
If you specify this parameter, be sure to specify at least one subnet when you create your group.
For more information, see Launching Auto Scaling Instances in a VPC in the Auto Scaling User Guide .
Valid values: default | dedicated
--cli-input-json (string) Performs service operation based on the JSON string provided. The JSON string follows the format provided by --generate-cli-skeleton. If other arguments are provided on the command line, the CLI values will override the JSON-provided values.
--generate-cli-skeleton (string) Prints a JSON skeleton to standard output without sending an API request. If provided with no value or the value input, prints a sample input JSON that can be used as an argument for --cli-input-json. If provided with the value output, it validates the command inputs and returns a sample output JSON for that command.
To create a launch configuration
This example creates a launch configuration:
aws autoscaling create-launch-configuration --launch-configuration-name my-launch-config --image-id ami-c6169af6 --instance-type m1.medium
This example creates a launch configuration that uses Spot Instances:
aws autoscaling create-launch-configuration --launch-configuration-name my-launch-config --image-id ami-c6169af6 --instance-type m1.medium --spot-price "0.50"
This example creates a launch configuration with a key pair and a bootstrapping script:
aws autoscaling create-launch-configuration --launch-configuration-name my-launch-config --key-name my-key-pair --image-id ami-c6169af6 --instance-type m1.small --user-data file://myuserdata.txt
This example creates a launch configuration based on an existing instance. In addition, it also specifies launch configuration attributes such as a security group, tenancy, Amazon EBS optimization, and a bootstrapping script:
aws autoscaling create-launch-configuration --launch-configuration-name my-launch-config --key-name my-key-pair --instance-id i-7e13c876 --security-groups sg-eb2af88e --instance-type m1.small --user-data file://myuserdata.txt --instance-monitoring Enabled=true --no-ebs-optimized --no-associate-public-ip-address --placement-tenancy dedicated --iam-instance-profile my-autoscaling-role
Add the following parameter to add an Amazon EBS volume with the device name /dev/sdh and a volume size of 100.
Parameter:
--block-device-mappings "[{\"DeviceName\": \"/dev/sdh\",\"Ebs\":{\"VolumeSize\":100}}]"
Add the following parameter to add ephemeral1 as an instance store volume with the device name /dev/sdc.
Parameter:
--block-device-mappings "[{\"DeviceName\": \"/dev/sdc\",\"VirtualName\":\"ephemeral1\"}]"
Add the following parameter to omit a device included on the instance (for example, /dev/sdf).
Parameter:
--block-device-mappings "[{\"DeviceName\": \"/dev/sdf\",\"NoDevice\":\"\"}]"
None


--- title: Single gradient update or model evaluation over one batch of samples. type: docs repo: https://github.com/rstudio/keras menu: main: name: Single gradient update or model evaluation over one batch of samples. - keras parent: keras-reference aliases: - /reference/keras/train_on_batch.html - /keras/reference/train_on_batch.html - /guide/keras/reference/train_on_batch.html - /tools/tools/keras/reference/train_on_batch.html - /installation/keras/reference/train_on_batch.html - /tutorials/keras/reference/train_on_batch.html - /guide/tools/keras/reference/train_on_batch.html - /deploy/keras/reference/train_on_batch.html - /tools/keras/reference/train_on_batch.html - /tutorials/tools/keras/reference/train_on_batch.html ---
Single gradient update or model evaluation over one batch of samples.
train_on_batch(object, x, y, class_weight = NULL, sample_weight = NULL)
test_on_batch(object, x, y, sample_weight = NULL)
| object | Keras model object |
| x | input data, as an array or list of arrays (if the model has multiple inputs). |
| y | labels, as an array. |
| class_weight | named list mapping classes to a weight value, used for scaling the loss function (during training only). |
| sample_weight | sample weights, as an array. |
Scalar training or test loss (if the model has no metrics) or list of scalars
(if the model computes other metrics). The property model$metrics_names
will give you the display labels for the scalar outputs.
Other model functions:
compile.keras.engine.training.Model()
,
evaluate.keras.engine.training.Model()
,
evaluate_generator()
,
fit.keras.engine.training.Model()
,
fit_generator()
,
get_config()
,
get_layer()
,
keras_model_sequential()
,
keras_model()
,
multi_gpu_model()
,
pop_layer()
,
predict.keras.engine.training.Model()
,
predict_generator()
,
predict_on_batch()
,
predict_proba()
,
summary.keras.engine.training.Model()


|
tgbot-cpp
|
#include <KeyboardButton.h>
Public Types | |
| typedef std::shared_ptr< KeyboardButton > | Ptr |
Public Attributes | |
| std::string | text |
| bool | requestContact |
| bool | requestLocation |
This object represents one button of the reply keyboard. For simple text buttons String can be used instead of this object to specify text of the button. Optional fields are mutually exclusive.
Definition at line 19 of file KeyboardButton.h.
| typedef std::shared_ptr<KeyboardButton> TgBot::KeyboardButton::Ptr |
Definition at line 22 of file KeyboardButton.h.
| bool TgBot::KeyboardButton::requestContact |
Optional. If True, the user's phone number will be sent as a contact when the button is pressed. Available in private chats only
Definition at line 34 of file KeyboardButton.h.
| bool TgBot::KeyboardButton::requestLocation |
Optional. If True, the user's current location will be sent when the button is pressed. Available in private chats only.
Definition at line 39 of file KeyboardButton.h.
| std::string TgBot::KeyboardButton::text |
Text of the button. If none of the optional fields are used, it will be sent to the bot as a message when the button is pressed
Definition at line 28 of file KeyboardButton.h.


{% extends 'aiohttp_login/bootstrap-3/base.html' %} {% block auth_title %}Reset password{% endblock %} {% block auth_content %}
To reset your password, please, follow the link in the email we sent you.


Who We Are
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Morbi molestie egestas massa, et sollicitudin urna mattis faucibus. Praesent sagittis laoreet est, et efficitur enim lacinia id.Lorem ipsum dolor sit amet,
An award winning digital design and development company
Learn moreLorem ipsum dolor sit amet, consectetur adipiscing elit. Morbi molestie egestas massa, et sollicitudin urna mattis faucibus.  Morbi molestie egestas massa, et sollicitudin urna mattis faucibus.  Morbi molestie egestas massa, et sollicitudin urna mattis faucibus. Praesent sagittis laoreet est, et efficitur enim lacinia id.Lorem ipsum dolor sit amet,
Choose your perfect website from hundreds of high quality, responsive designs; built by the world's best website designers,everything you need to launch and run your site in one place.
Choose your perfect website from hundreds of high quality, responsive designs; built by the world's best website designers,everything you need to launch and run your site in one place.
Choose your perfect website from hundreds of high quality, responsive designs; built by the world's best website designers,everything you need to launch and run your site in one place.
Choose your perfect website from hundreds of high quality, responsive designs; built by the world's best website designers,everything you need to launch and run your site in one place.
Choose your perfect website from hundreds of high quality, responsive designs; built by the world's best website designers,everything you need to launch and run your site in one place.
Choose your perfect website from hundreds of high quality, responsive designs; built by the world's best website designers,everything you need to launch and run your site in one place.
Choose your perfect website from hundreds of high quality, responsive designs; built by the world's best website designers,everything you need to launch and run your site in one place.
Choose your perfect website from hundreds of high quality, responsive designs; built by the world's best website designers,everything you need to launch and run your site in one place.
engineer
manager


JACK SPARROW
Wordpress Theme Developer
Lorem ipsum dolor sit amet consectetur adipisicing elit. Sapiente iusto fugiat placeat expedita qui saepe nam et ullam nisi rem.
- JACK SPARROW
- December 15, 1997
- Bashundhra R/A, Baridhara, Dhaka-1229
-<EMAIL_ADDRESS>- +880<PHONE_NUMBER>
- www.mdrubel.info
jackSPARROW
Wordpress Theme Developer
Lorem ipsum, or lipsum as it is sometimes known, is dummy text used in laying out print, graphic or web designs. The passage is attributed
- Phone+880<PHONE_NUMBER>
- AddressBASHUNDHRA R/A, BARIDHARA, DHAKA-1229
-<EMAIL_ADDRESS>Experience
2010-2012
LOREM IPSUM
Lorem ipsum, or lipsum as it is sometimes known, is dummy text used in laying out print
2010-2012
LOREM IPSUM
Lorem ipsum, or lipsum as it is sometimes known, is dummy text used in laying out print
2010-2012
LOREM IPSUM
Lorem ipsum, or lipsum as it is sometimes known, is dummy text used in laying out print
2010-2012
LOREM IPSUM
Lorem ipsum, or lipsum as it is sometimes known, is dummy text used in laying out print
MY skills
Photoshop
Ms office
Illustrator
html
Photoshop
Ms office
Illustrator
html
Interests
EDUCATION
2010-2012
LOREM IPSUM
Lorem ipsum, or lipsum as it is sometimes known, is dummy text used in laying out print
2010-2012
LOREM IPSUM
Lorem ipsum, or lipsum as it is sometimes known, is dummy text used in laying out print
-
+880<PHONE_NUMBER>
-
<EMAIL_ADDRESS>-
BASHUNDHRA R/A, BARIDHARA, DHAKA-1229
Contact info
- +880<PHONE_NUMBER>
-<EMAIL_ADDRESS>- www.mdrubel.info


{% extends "html/base.html" %}
{% block content %}
To get started, head over to the Hurricane tab. To get detailed information, follow the Documentation tab. For a general overview, scroll down.Welcome to FlaPy Disaster
FlaPy Disaster implements the NOAA NWS23 hurricane model to calculate and display hurricane wind footprints. The UI is built usingPython/Flask, calculations are driven by an Scala/Akka server, and mapping is powered by Leaflet.js. Data can be imported from NOAA, Unisys, and user data files. The image above is an example of the visualization generated by the program.
Import Data
Calculate
Visualize


For a stateless platform, the web has become really stateful
SPAs introduce and deal with state all over the place
###Rule #1
##Don't do it
Write Stateless Code
Use functional paradigms
Prefer Data Transformations Over Modifications
Rely on your State Machine (router) for State Maintenance
What If There's Global Data?
Make a copy of the data and operate on that
...Then shoot the developer that created a global variable
###Rule #2
##Keep state near the ui
This is a two step process:
1. Modularize state data
2. Bundle it with the UI
###Frameworks Support This!
- Backbone -- Views and models are bound together
- React -- JSX interacts with state tree/hierarchy
- Angular -- 1.x has directives, 2.x has components
- Ember -- Components
###Rule #3
##Keep it encapsulated
###Think Object Oriented
- Create state/transaction objects
- Handle change through formal mutation
- Keep the data out of meddling hands
###Sometimes Ceremony is a Good Thing
Using getters and setters makes it obvious when things are modified
- Set the data with a setter function: stateObject.set(key, value)
- Get the data with a getter function: stateObject.get(key)
###Encapsulating Data Means Hiding
- Use data hiding to keep operations from mucking up your work
- Look to pointers and factories to help keep things under wraps
###Recap
- Avoid shared state
- Bind state to the UI
- Use OO principles to encapsulate your data
##Questions?
###I'm Chris Stead
#@cm_stead
##chrisstead.net