Content¶
The abundance file is a reformatted version of the file from the Nuclear Wallet cards (2005), as retrieved from Brookhaven National Laboratory. The abundances are given for all stable isotopes.
Directory: masses/ File: abundance.readme (December 10, 2007) *******************************************
abundance.datNatural abundances of stable isotopes
The abundance file is a reformatted version of the file from the Nuclear Wallet cards (2005), as retrieved from Brookhaven National Laboratory. The abundances are given for all stable isotopes.
Each record of the file contains:
Z : charge number A : mass number El : element symbol abundance: abundance in % uncert : uncertainties in abundance in %
The corresponding FORTRAN format is (2i4,1x,a2,1x,2f10.6)
Command-line parsing library
This module is an optparse-inspired command-line parsing library that:
- handles both optional and positional arguments
- produces highly informative usage messages
- supports parsers that dispatch to sub-parsers
The following is a simple usage example that sums integers from the command-line and writes the result to a file:
parser = argparse.ArgumentParser(
description='sum the integers at the command line')
parser.add_argument(
'integers', metavar='int', nargs='+', type=int,
help='an integer to be summed')
parser.add_argument(
'--log', default=sys.stdout, type=argparse.FileType('w'),
help='the file where the sum should be written')
args = parser.parse_args()
args.log.write('%s' % sum(args.integers))
args.log.close()
The module contains the following public classes:
- ArgumentParser – The main entry point for command-line parsing. As the
- example above shows, the add_argument() method is used to populate the parser with actions for optional and positional arguments. Then the parse_args() method is invoked to convert the args at the command-line into an object with attributes.
- ArgumentError – The exception raised by ArgumentParser objects when
- there are errors with the parser’s actions. Errors raised while parsing the command-line are caught by ArgumentParser and emitted as command-line messages.
- FileType – A factory for defining types of files to be created. As the
- example above shows, instances of FileType are typically passed as the type= argument of add_argument() calls.
- Action – The base class for parser actions. Typically actions are
- selected by passing strings like ‘store_true’ or ‘append_const’ to the action= argument of add_argument(). However, for greater customization of ArgumentParser actions, subclasses of Action may be defined and passed as the action= argument.
- HelpFormatter, RawDescriptionHelpFormatter, RawTextHelpFormatter,
- ArgumentDefaultsHelpFormatter – Formatter classes which may be passed as the formatter_class= argument to the ArgumentParser constructor. HelpFormatter is the default, RawDescriptionHelpFormatter and RawTextHelpFormatter tell the parser not to change the formatting for help text, and ArgumentDefaultsHelpFormatter adds information about argument defaults to the help.
All other classes in this module are considered implementation details. (Also note that HelpFormatter and RawDescriptionHelpFormatter are only considered public as object names – the API of the formatter objects is still considered an implementation detail.)
fudge.core.utilities.argparse.
ArgumentParser
(prog=None, usage=None, description=None, epilog=None, version=None, parents=[], formatter_class=<class 'fudge.core.utilities.argparse.HelpFormatter'>, prefix_chars='-', fromfile_prefix_chars=None, argument_default=None, conflict_handler='error', add_help=True)[source]¶Bases: fudge.core.utilities.argparse._AttributeHolder
, fudge.core.utilities.argparse._ActionsContainer
Object for parsing command line strings into Python objects.
fudge.core.utilities.argparse.
ArgumentError
(argument, message)[source]¶Bases: exceptions.Exception
An error from creating or using an argument (optional or positional).
The string value of this exception is the message, augmented with information about the argument that caused it.
fudge.core.utilities.argparse.
ArgumentTypeError
[source]¶Bases: exceptions.Exception
An error from trying to convert a command line string to a type.
fudge.core.utilities.argparse.
FileType
(mode='r', bufsize=-1)[source]¶Bases: object
Factory for creating file object types
Instances of FileType are typically passed as type= arguments to the ArgumentParser add_argument() method.
fudge.core.utilities.argparse.
HelpFormatter
(prog, indent_increment=2, max_help_position=24, width=None)[source]¶Bases: object
Formatter for generating usage messages and argument help strings.
Only the name of this class is considered a public API. All the methods provided by the class are considered an implementation detail.
fudge.core.utilities.argparse.
ArgumentDefaultsHelpFormatter
(prog, indent_increment=2, max_help_position=24, width=None)[source]¶Bases: fudge.core.utilities.argparse.HelpFormatter
Help message formatter which adds default values to argument help.
Only the name of this class is considered a public API. All the methods provided by the class are considered an implementation detail.
fudge.core.utilities.argparse.
RawDescriptionHelpFormatter
(prog, indent_increment=2, max_help_position=24, width=None)[source]¶Bases: fudge.core.utilities.argparse.HelpFormatter
Help message formatter which retains any formatting in descriptions.
Only the name of this class is considered a public API. All the methods provided by the class are considered an implementation detail.
fudge.core.utilities.argparse.
RawTextHelpFormatter
(prog, indent_increment=2, max_help_position=24, width=None)[source]¶Bases: fudge.core.utilities.argparse.RawDescriptionHelpFormatter
Help message formatter which retains formatting of all help text.
Only the name of this class is considered a public API. All the methods provided by the class are considered an implementation detail.
fudge.core.utilities.argparse.
Namespace
(**kwargs)[source]¶Bases: fudge.core.utilities.argparse._AttributeHolder
Simple object for storing attributes.
Implements equality by attribute names and values, and provides a simple string representation.
fudge.core.utilities.argparse.
Action
(option_strings, dest, nargs=None, const=None, default=None, type=None, choices=None, required=False, help=None, metavar=None)[source]¶Bases: fudge.core.utilities.argparse._AttributeHolder
Information about how to convert command line strings to Python objects.
Action objects are used by an ArgumentParser to represent the information needed to parse a single argument from one or more strings from the command line. The keyword arguments to the Action constructor are also all attributes of Action instances.
Keyword Arguments:
- option_strings – A list of command-line option strings which
should be associated with this action.
dest – The name of the attribute to hold the created object(s)
- nargs – The number of command-line arguments that should be
consumed. By default, one argument will be consumed and a single value will be produced. Other values include:
- N (an integer) consumes N arguments (and produces a list)
- ‘?’ consumes zero or one arguments
- ‘*’ consumes zero or more arguments (and produces a list)
- ‘+’ consumes one or more arguments (and produces a list)
Note that the difference between the default and nargs=1 is that with the default, a single value will be produced, while with nargs=1, a list containing a single value will be produced.
- const – The value to be produced if the option is specified and the
option uses an action that takes no values.
default – The value to be produced if the option is not specified.
- type – The type which the command-line arguments should be converted
to, should be one of ‘string’, ‘int’, ‘float’, ‘complex’ or a callable object that accepts a single string argument. If None, ‘string’ is assumed.
- choices – A container of values that should be allowed. If not None,
after a command-line argument has been converted to the appropriate type, an exception will be raised if it is not a member of this collection.
- required – True if the action must always be specified at the
command line. This is only meaningful for optional command-line arguments.
help – The help string describing the argument.
- metavar – The name to be used for the option’s argument with the
help string. If None, the ‘dest’ value will be used as the name.
This module contains a set of functions that are hopefully useful when using python.
fudge.core.utilities.brb.
Pause
(Prompt='Enter <RET> to continue : ', ExtraStr='')[source]¶Prompts and waits for user to enter a line. The line is returned. ExtraStr is added to the prompt string.
A flower-box ascii banner generator. The input string can have line feeds. Each line will get centered in the box.
fudge.core.utilities.brb.
doc
(a)[source]¶This function simply executes “print a.__doc__” where “a” is the argument.
fudge.core.utilities.brb.
docmethods
(o, Full=1)[source]¶This function attempts to print all methods and their documentation contained in the first argument.
fudge.core.utilities.brb.
objectoutline
(o, MaxLevel=1, Full=1)[source]¶This routine attempts to print the objects - methods, members and possible other things - that are a part of the first argument. It will recursively traverse each object found down to level MaxLevel.
fudge.core.utilities.brb.
objectoutline2
(o, MaxLevel, level, name, Full)[source]¶For internal use only.
fudge.core.utilities.brb.
objectvalues
(o)[source]¶Prints a list of all objects return by dir( o ) and their data (or object type) where “o” is the first argument.
fudge.core.utilities.brb.
py
(depth=1, start=0)[source]¶This routine prints all python scripts in sys.path[start:start+depth] in a nice format.
fudge.core.utilities.brb.
tdir
(a=None, w=5, pattern=None, wpattern=None)[source]¶This function is an attempt at improving the output of python’s dir function. It uses tlist to print the output in a more readable format. The argument w is passed to tlist. The argument pattern, if not None, is used to restrict the items displayed to those that match it. Pattern can be any pattern understood by the re module (e.g., to display all items containing the two consecutive letters “2d” set pattern to ”.*2d.*”). If pattern is None and wpattern is NOT None then pattern is set to ”.*” + wpattern + ”.*”.
fudge.core.utilities.brb.
tlist
(l, w=5, sep=None, rightJustify=0)[source]¶Calls tylist with arguments passed.
fudge.core.utilities.brb.
txlist
(l, w=5, sep=None, rightJustify=0)[source]¶Prints the list given by the first argument in a tabled format. The purpose of this function is to print a python list in a more readable format. The number of items from list printed per line is set by w. The argument sep, if not None, is printed as a separator between each item on a line. The items are left justified unless the argument rightJustify is true. This function prints each w consecutive items horizontally. Also see tylist.
fudge.core.utilities.brb.
tylist
(l, w=5, sep=None, rightJustify=0)[source]¶Prints the list given by the first argument in a tabled format. The purpose of this function is to print a python list in a more readable format. The number of items from list printed per line is set by w. The argument sep, if not None, is printed as a separator between each item on a line. The items are left justified unless the argument rightJustify is true. This function prints each consecutive item vertically while maintaining w columns. Also see txlist.
fudge.core.utilities.brb.
uniquify
(seq)[source]¶Fast implimentation of a function to strip out non-unique entries in a Python list, but preserving list order. Usage:
>>> print uniquify( [1,4,2,4,7,2,1,1,1,'s','a',0.1] )
[1, 4, 2, 7, 's', 'a', 0.10000000000000001]
This module contains the fudge exception classes.
fudge.core.utilities.fudgeExceptions.
ENDL_CheckerException
(value)[source]¶Bases: fudge.core.utilities.fudgeExceptions.FUDGE_Exception
This class is raised whenever a check method detects bad ENDL data.
fudge.core.utilities.fudgeExceptions.
ENDL_DesignerIsotopeReadException
[source]¶Bases: exceptions.Exception
This class is raised whenever read is called on a designer isotope.
fudge.core.utilities.fudgeExceptions.
ENDL_addFileException_FileExist
(value)[source]¶Bases: fudge.core.utilities.fudgeExceptions.FUDGE_Exception
This class is raised whenever endlZA.addFile is called and the file already exists.
fudge.core.utilities.fudgeExceptions.
ENDL_fixHeadersException_NoC10Data
(value)[source]¶Bases: fudge.core.utilities.fudgeExceptions.FUDGE_Exception
This class is raised whenever endlZA.fixHeaders needs missing header data and cannot find the C = 10, I = 0 which it assumes as valid header data.
This module contains the class fudgeTempFile which simplies the functions in the tempfile module.
fudge.core.utilities.fudgeFileMisc.
fudgeTempFile
(prefix=None, suffix='', dir=None, deleteOnClose=False)[source]¶Bases: object
This class creates a temporary file using tempfile.mkstemp and supports common functionallity for the file (e.g., write). Currently, reading from the temporary file is not supported.
close
(raiseIfClosed=True)[source]¶Closes the file if still opened. If raiseIfClosed is ‘True’ and file is already closed, a raise is executed.
Convert between Z, symbol and element name. adapted from endl_Z cmattoon, March 2011
fudge.core.utilities.fudgeZA.
LabelToZ
(label)[source]¶Returns the Z for the specified label or ‘None’ if no match for label.
fudge.core.utilities.fudgeZA.
SymbolToZ
(symbol)[source]¶Returns the Z for the specified symbol or ‘None’ if no match for symbol.
fudge.core.utilities.fudgeZA.
ZAToGNDName
(ZA)[source]¶Converts an ENDL ZA or ‘zaZZZAAA_suffix’ into a GND name. For example ENDL 94239 or ‘za094239’, is converted to ‘Pu239’.
fudge.core.utilities.fudgeZA.
ZToLabel
(Z)[source]¶Returns the label (i.e., name) for the specified Z or ‘None’ if Z is out-of-bounds.
pyparsing module - Classes and methods to define and execute parsing grammars
The pyparsing module is an alternative approach to creating and executing simple grammars, vs. the traditional lex/yacc approach, or the use of regular expressions. With pyparsing, you don’t need to learn a new syntax for defining grammars or matching expressions - the parsing module provides a library of classes that you use to construct the grammar directly in Python.
Here is a program to parse “Hello, World!” (or any greeting of the form C{“<salutation>, <addressee>!”}):
from pyparsing import Word, alphas
# define grammar of a greeting
greet = Word( alphas ) + "," + Word( alphas ) + "!"
hello = "Hello, World!"
print hello, "->", greet.parseString( hello )
The program outputs the following:
Hello, World! -> ['Hello', ',', 'World', '!']
The Python representation of the grammar is quite readable, owing to the self-explanatory class names, and the use of ‘+’, ‘|’ and ‘^’ operators.
The parsed results returned from C{parseString()} can be accessed as a nested list, a dictionary, or an object with named attributes.
fudge.core.utilities.pyparsing.
And
(exprs, savelist=True)[source]¶Bases: fudge.core.utilities.pyparsing.ParseExpression
Requires all given C{ParseExpressions} to be found in the given order. Expressions may be separated by whitespace. May be constructed using the ‘+’ operator.
fudge.core.utilities.pyparsing.
CaselessKeyword
(matchString, identChars='abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789_$')[source]¶fudge.core.utilities.pyparsing.
CaselessLiteral
(matchString)[source]¶Bases: fudge.core.utilities.pyparsing.Literal
Token to match a specified string, ignoring case of letters. Note: the matched results will always be in the case of the given match string, NOT the case of the input text.
fudge.core.utilities.pyparsing.
CharsNotIn
(notChars, min=1, max=0, exact=0)[source]¶Bases: fudge.core.utilities.pyparsing.Token
Token for matching words composed of characters not in a given set. Defined with string containing all disallowed characters, and an optional minimum, maximum, and/or exact length. The default value for C{min} is 1 (a minimum value < 1 is not valid); the default values for C{max} and C{exact} are 0, meaning no maximum or exact length restriction.
fudge.core.utilities.pyparsing.
Combine
(expr, joinString='', adjacent=True)[source]¶Bases: fudge.core.utilities.pyparsing.TokenConverter
Converter to concatenate all matching tokens to a single string. By default, the matching patterns must also be contiguous in the input string; this can be disabled by specifying C{‘adjacent=False’} in the constructor.
fudge.core.utilities.pyparsing.
Dict
(exprs)[source]¶Bases: fudge.core.utilities.pyparsing.TokenConverter
Converter to return a repetitive expression as a list, but also as a dictionary. Each element can also be referenced using the first token in the expression as its key. Useful for tabular report scraping when the first column can be used as a item key.
fudge.core.utilities.pyparsing.
Each
(exprs, savelist=True)[source]¶Bases: fudge.core.utilities.pyparsing.ParseExpression
Requires all given C{ParseExpressions} to be found, but in any order. Expressions may be separated by whitespace. May be constructed using the ‘&’ operator.
fudge.core.utilities.pyparsing.
Empty
[source]¶Bases: fudge.core.utilities.pyparsing.Token
An empty token, will always match.
fudge.core.utilities.pyparsing.
FollowedBy
(expr)[source]¶Bases: fudge.core.utilities.pyparsing.ParseElementEnhance
Lookahead matching of the given parse expression. C{FollowedBy} does not advance the parsing position within the input string, it only verifies that the specified parse expression matches at the current position. C{FollowedBy} always returns a null token list.
fudge.core.utilities.pyparsing.
Forward
(other=None)[source]¶Bases: fudge.core.utilities.pyparsing.ParseElementEnhance
Forward declaration of an expression to be defined later - used for recursive grammars, such as algebraic infix notation. When the expression is known, it is assigned to the C{Forward} variable using the ‘<<’ operator.
Note: take care when assigning to C{Forward} not to overlook precedence of operators. Specifically, ‘|’ has a lower precedence than ‘<<’, so that:
fwdExpr << a | b | c
thereby leaving b and c out as parseable alternatives. It is recommended that you explicitly group the values inserted into the C{Forward}:
fwdExpr << (a | b | c)
fudge.core.utilities.pyparsing.
GoToColumn
(colno)[source]¶Bases: fudge.core.utilities.pyparsing._PositionToken
Token to advance to a specific column of input text; useful for tabular report scraping.
fudge.core.utilities.pyparsing.
Group
(expr)[source]¶Bases: fudge.core.utilities.pyparsing.TokenConverter
Converter to return the matched tokens as a list - useful for returning tokens of ZeroOrMore and OneOrMore expressions.
fudge.core.utilities.pyparsing.
Keyword
(matchString, identChars='abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789_$', caseless=False)[source]¶Bases: fudge.core.utilities.pyparsing.Token
Token to exactly match a specified string as a keyword, that is, it must be immediately followed by a non-keyword character. Compare with C{Literal}:
Literal("if") will match the leading 'if' in 'ifAndOnlyIf'.
Keyword("if") will not; it will only match the leading 'if in 'if x=1', or 'if(y==2)'
Accepts two optional constructor arguments in addition to the keyword string: C{identChars} is a string of characters that would be valid identifier characters, defaulting to all alphanumerics + “_” and “$”; C{caseless} allows case-insensitive matching, default is False.
DEFAULT_KEYWORD_CHARS
= 'abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789_$'¶fudge.core.utilities.pyparsing.
LineEnd
[source]¶Bases: fudge.core.utilities.pyparsing._PositionToken
Matches if current position is at the end of a line within the parse string
fudge.core.utilities.pyparsing.
LineStart
[source]¶Bases: fudge.core.utilities.pyparsing._PositionToken
Matches if current position is at the beginning of a line within the parse string
fudge.core.utilities.pyparsing.
Literal
(matchString)[source]¶Bases: fudge.core.utilities.pyparsing.Token
Token to exactly match a specified string.
fudge.core.utilities.pyparsing.
MatchFirst
(exprs, savelist=False)[source]¶Bases: fudge.core.utilities.pyparsing.ParseExpression
Requires that at least one C{ParseExpression} is found. If two expressions match, the first one listed is the one that will match. May be constructed using the ‘|’ operator.
fudge.core.utilities.pyparsing.
NoMatch
[source]¶Bases: fudge.core.utilities.pyparsing.Token
A token that will never match.
fudge.core.utilities.pyparsing.
NotAny
(expr)[source]¶Bases: fudge.core.utilities.pyparsing.ParseElementEnhance
Lookahead to disallow matching with the given parse expression. C{NotAny} does not advance the parsing position within the input string, it only verifies that the specified parse expression does not match at the current position. Also, C{NotAny} does not skip over leading whitespace. C{NotAny} always returns a null token list. May be constructed using the ‘~’ operator.
fudge.core.utilities.pyparsing.
OneOrMore
(expr, savelist=False)[source]¶Bases: fudge.core.utilities.pyparsing.ParseElementEnhance
Repetition of one or more of the given expression.
fudge.core.utilities.pyparsing.
OnlyOnce
(methodCall)[source]¶Bases: object
Wrapper for parse actions, to ensure they are only called once.
fudge.core.utilities.pyparsing.
Optional
(exprs, default=<fudge.core.utilities.pyparsing._NullToken object>)[source]¶Bases: fudge.core.utilities.pyparsing.ParseElementEnhance
Optional matching of the given expression. A default return string can also be specified, if the optional expression is not found.
fudge.core.utilities.pyparsing.
Or
(exprs, savelist=False)[source]¶Bases: fudge.core.utilities.pyparsing.ParseExpression
Requires that at least one C{ParseExpression} is found. If two expressions match, the expression that matches the longest string will be used. May be constructed using the ‘^’ operator.
fudge.core.utilities.pyparsing.
ParseBaseException
(pstr, loc=0, msg=None, elem=None)[source]¶Bases: exceptions.Exception
Base exception class for all parsing runtime exceptions
fudge.core.utilities.pyparsing.
ParseElementEnhance
(expr, savelist=False)[source]¶Bases: fudge.core.utilities.pyparsing.ParserElement
Abstract subclass of C{ParserElement}, for combining and post-processing parsed tokens.
fudge.core.utilities.pyparsing.
ParseException
(pstr, loc=0, msg=None, elem=None)[source]¶Bases: fudge.core.utilities.pyparsing.ParseBaseException
Exception thrown when parse expressions don’t match class; supported attributes by name are:
- lineno - returns the line number of the exception text
- col - returns the column number of the exception text
- line - returns the line containing the exception text
fudge.core.utilities.pyparsing.
ParseExpression
(exprs, savelist=False)[source]¶Bases: fudge.core.utilities.pyparsing.ParserElement
Abstract subclass of ParserElement, for combining and post-processing parsed tokens.
fudge.core.utilities.pyparsing.
ParseFatalException
(pstr, loc=0, msg=None, elem=None)[source]¶Bases: fudge.core.utilities.pyparsing.ParseBaseException
User-throwable exception thrown when inconsistent parse content is found; stops all parsing immediately
fudge.core.utilities.pyparsing.
ParseResults
(toklist, name=None, asList=True, modal=True, isinstance=<built-in function isinstance>)[source]¶Bases: object
Structured parse results, to provide multiple means of access to the parsed data: - as a list (C{len(results)}) - by list index (C{results[0], results[1]}, etc.) - by attribute (C{results.<resultsName>})
asList
()[source]¶Returns the parse results as a nested list of matching tokens, all converted to strings.
asXML
(doctag=None, namedItemsOnly=False, indent='', formatted=True)[source]¶Returns the parse results as XML. Tags are created for tokens and lists that have defined results names.
dump
(indent='', depth=0)[source]¶Diagnostic method for listing out the contents of a C{ParseResults}. Accepts an optional C{indent} argument so that this string can be embedded in a nested display of other data.
get
(key, defaultValue=None)[source]¶Returns named result matching the given key, or if there is no such name, then returns the given C{defaultValue} or C{None} if no C{defaultValue} is specified.
fudge.core.utilities.pyparsing.
ParseSyntaxException
(pe)[source]¶Bases: fudge.core.utilities.pyparsing.ParseFatalException
Just like C{ParseFatalException}, but thrown internally when an C{ErrorStop} (‘-‘ operator) indicates that parsing is to stop immediately because an unbacktrackable syntax error has been found
fudge.core.utilities.pyparsing.
ParserElement
(savelist=False)[source]¶Bases: object
Abstract base level parser element class.
DEFAULT_WHITE_CHARS
= ' \n\t\r'¶addParseAction
(*fns, **kwargs)[source]¶Add parse action to expression’s list of parse actions. See L{I{setParseAction}<setParseAction>}.
copy
()[source]¶Make a copy of this C{ParserElement}. Useful for defining different parse actions for the same parsing pattern, using copies of the original parse element.
enablePackrat
()[source]¶Enables “packrat” parsing, which adds memoizing to the parsing logic. Repeated parse attempts at the same string location (which happens often in many complex grammars) can immediately return a cached value, instead of re-executing parsing/validating code. Memoizing is done of both valid results and parsing exceptions.
This speedup may break existing programs that use parse actions that have side-effects. For this reason, packrat parsing is disabled when you first import pyparsing. To activate the packrat feature, your program must call the class method C{ParserElement.enablePackrat()}. If your program uses C{psyco} to “compile as you go”, you must call C{enablePackrat} before calling C{psyco.full()}. If you do not do this, Python will crash. For best results, call C{enablePackrat()} immediately after importing pyparsing.
ignore
(other)[source]¶Define expression to be ignored (e.g., comments) while doing pattern matching; may be called repeatedly, to define multiple comment or other ignorable patterns.
leaveWhitespace
()[source]¶Disables the skipping of whitespace before matching the characters in the C{ParserElement}’s defined pattern. This is normally only used internally by the pyparsing module, but may be needed in some whitespace-sensitive grammars.
parseFile
(file_or_filename, parseAll=False)[source]¶Execute the parse expression on the given file or filename. If a filename is specified (instead of a file object), the entire file is opened, read, and closed before parsing.
parseString
(instring, parseAll=False)[source]¶Execute the parse expression with the given string. This is the main interface to the client code, once the complete expression has been built.
If you want the grammar to require that the entire input string be successfully parsed, then set C{parseAll} to True (equivalent to ending the grammar with C{StringEnd()}).
Note: C{parseString} implicitly calls C{expandtabs()} on the input string, in order to report proper column numbers in parse actions. If the input string contains tabs and the grammar uses parse actions that use the C{loc} argument to index into the string being parsed, you can ensure you have a consistent view of the input string by:
- calling C{parseWithTabs} on your grammar before calling C{parseString} (see L{I{parseWithTabs}<parseWithTabs>})
- define your parse action using the full C{(s,loc,toks)} signature, and reference the input string using the parse action’s C{s} argument
- explictly expand the tabs in your input string before calling C{parseString}
parseWithTabs
()[source]¶Overrides default behavior to expand <TAB>s to spaces before parsing the input string. Must be called before C{parseString} when the input grammar contains elements that match <TAB> characters.
scanString
(instring, maxMatches=9223372036854775807)[source]¶Scan the input string for expression matches. Each match will return the matching tokens, start location, and end location. May be called with optional C{maxMatches} argument, to clip scanning after ‘n’ matches are found.
Note that the start and end locations are reported relative to the string being parsed. See L{I{parseString}<parseString>} for more information on parsing strings with embedded tabs.
searchString
(instring, maxMatches=9223372036854775807)[source]¶Another extension to C{scanString}, simplifying the access to the tokens found to match the given parse expression. May be called with optional C{maxMatches} argument, to clip searching after ‘n’ matches are found.
setBreak
(breakFlag=True)[source]¶Method to invoke the Python pdb debugger when this element is about to be parsed. Set C{breakFlag} to True to enable, False to disable.
setDebug
(flag=True)[source]¶Enable display of debugging messages while doing pattern matching. Set C{flag} to True to enable, False to disable.
setDebugActions
(startAction, successAction, exceptionAction)[source]¶Enable display of debugging messages while doing pattern matching.
setFailAction
(fn)[source]¶Define action to perform if parsing fails at this expression. Fail acton fn is a callable function that takes the arguments C{fn(s,loc,expr,err)} where:
- s = string being parsed
- loc = location where expression match was attempted and failed
- expr = the parse expression that failed
- err = the exception thrown
The function returns no value. It may throw C{ParseFatalException} if it is desired to stop parsing immediately.
setParseAction
(*fns, **kwargs)[source]¶Define action to perform when successfully matching parse element definition. Parse action fn is a callable method with 0-3 arguments, called as C{fn(s,loc,toks)}, C{fn(loc,toks)}, C{fn(toks)}, or just C{fn()}, where:
- s = the original string being parsed (see note below)
- loc = the location of the matching substring
- toks = a list of the matched tokens, packaged as a ParseResults object
If the functions in fns modify the tokens, they can return them as the return value from fn, and the modified list of tokens will replace the original. Otherwise, fn does not need to return any value.
Note: the default parsing behavior is to expand tabs in the input string before starting the parsing process. See L{I{parseString}<parseString>} for more information on parsing strings containing <TAB>s, and suggested methods to maintain a consistent view of the parsed string, the parse location, and line and column positions within the parsed string.
setResultsName
(name, listAllMatches=False)[source]¶Define name for referencing matching tokens as a nested attribute of the returned parse results. NOTE: this returns a copy of the original C{ParserElement} object; this is so that the client can define a basic element, such as an integer, and reference it in multiple places with different names.
You can also set results names using the abbreviated syntax, C{expr(“name”)} in place of C{expr.setResultsName(“name”)} - see L{I{__call__}<__call__>}.
suppress
()[source]¶Suppresses the output of this C{ParserElement}; useful to keep punctuation from cluttering up returned output.
transformString
(instring)[source]¶Extension to C{scanString}, to modify matching text with modified tokens that may be returned from a parse action. To use C{transformString}, define a grammar and attach a parse action to it that modifies the returned token list. Invoking C{transformString()} on a target string will then scan for matches, and replace the matched text patterns according to the logic in the parse action. C{transformString()} returns the resulting transformed string.
validate
(validateTrace=[])[source]¶Check defined expressions for valid structure, check for infinite recursive definitions.
verbose_stacktrace
= False¶fudge.core.utilities.pyparsing.
QuotedString
(quoteChar, escChar=None, escQuote=None, multiline=False, unquoteResults=True, endQuoteChar=None)[source]¶Bases: fudge.core.utilities.pyparsing.Token
Token for matching strings that are delimited by quoting characters.
fudge.core.utilities.pyparsing.
RecursiveGrammarException
(parseElementList)[source]¶Bases: exceptions.Exception
Exception thrown by C{validate()} if the grammar could be improperly recursive
fudge.core.utilities.pyparsing.
Regex
(pattern, flags=0)[source]¶Bases: fudge.core.utilities.pyparsing.Token
Token for matching strings that match a given regular expression. Defined with string specifying the regular expression in a form recognized by the inbuilt Python re module.
compiledREtype
¶alias of SRE_Pattern
fudge.core.utilities.pyparsing.
SkipTo
(other, include=False, ignore=None, failOn=None)[source]¶Bases: fudge.core.utilities.pyparsing.ParseElementEnhance
Token for skipping over all undefined text until the matched expression is found. If C{include} is set to true, the matched expression is also parsed (the skipped text and matched expression are returned as a 2-element list). The C{ignore} argument is used to define grammars (typically quoted strings and comments) that might contain false matches.
fudge.core.utilities.pyparsing.
StringEnd
[source]¶Bases: fudge.core.utilities.pyparsing._PositionToken
Matches if current position is at the end of the parse string
fudge.core.utilities.pyparsing.
StringStart
[source]¶Bases: fudge.core.utilities.pyparsing._PositionToken
Matches if current position is at the beginning of the parse string
fudge.core.utilities.pyparsing.
Suppress
(expr, savelist=False)[source]¶Bases: fudge.core.utilities.pyparsing.TokenConverter
Converter for ignoring the results of a parsed expression.
fudge.core.utilities.pyparsing.
Token
[source]¶Bases: fudge.core.utilities.pyparsing.ParserElement
Abstract C{ParserElement} subclass, for defining atomic matching patterns.
fudge.core.utilities.pyparsing.
TokenConverter
(expr, savelist=False)[source]¶Bases: fudge.core.utilities.pyparsing.ParseElementEnhance
Abstract subclass of ParseExpression, for converting parsed results.
fudge.core.utilities.pyparsing.
Upcase
(*args)[source]¶Bases: fudge.core.utilities.pyparsing.TokenConverter
Converter to upper case all matching tokens.
fudge.core.utilities.pyparsing.
White
(ws=' trn', min=1, max=0, exact=0)[source]¶Bases: fudge.core.utilities.pyparsing.Token
Special matching class for matching whitespace. Normally, whitespace is ignored by pyparsing grammars. This class is included when some whitespace structures are significant. Define with a string containing the whitespace characters to be matched; default is C{” trn”}. Also takes optional C{min}, C{max}, and C{exact} arguments, as defined for the C{Word} class.
whiteStrs
= {'\t': '<TAB>', ' ': '<SPC>', '\n': '<LF>', '\r': '<CR>', '\x0c': '<FF>'}¶fudge.core.utilities.pyparsing.
Word
(initChars, bodyChars=None, min=1, max=0, exact=0, asKeyword=False)[source]¶Bases: fudge.core.utilities.pyparsing.Token
Token for matching words composed of allowed character sets. Defined with string containing all allowed initial characters, an optional string containing allowed body characters (if omitted, defaults to the initial character set), and an optional minimum, maximum, and/or exact length. The default value for C{min} is 1 (a minimum value < 1 is not valid); the default values for C{max} and C{exact} are 0, meaning no maximum or exact length restriction.
fudge.core.utilities.pyparsing.
WordEnd
(wordChars='0123456789abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ!"#$%&'()*+, -./:;<=>?@[\]^_`{|}~')[source]¶Bases: fudge.core.utilities.pyparsing._PositionToken
Matches if the current position is at the end of a Word, and is not followed by any character in a given set of wordChars (default=C{printables}). To emulate the C{} behavior of regular expressions, use C{WordEnd(alphanums)}. C{WordEnd} will also match at the end of the string being parsed, or at the end of a line.
fudge.core.utilities.pyparsing.
WordStart
(wordChars='0123456789abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ!"#$%&'()*+, -./:;<=>?@[\]^_`{|}~')[source]¶Bases: fudge.core.utilities.pyparsing._PositionToken
Matches if the current position is at the beginning of a Word, and is not preceded by any character in a given set of wordChars (default=C{printables}). To emulate the C{} behavior of regular expressions, use C{WordStart(alphanums)}. C{WordStart} will also match at the beginning of the string being parsed, or at the beginning of a line.
fudge.core.utilities.pyparsing.
ZeroOrMore
(expr)[source]¶Bases: fudge.core.utilities.pyparsing.ParseElementEnhance
Optional repetition of zero or more of the given expression.
fudge.core.utilities.pyparsing.
col
(loc, strg)[source]¶Returns current column within a string, counting newlines as line separators. The first column is number 1.
Note: the default parsing behavior is to expand tabs in the input string before starting the parsing process. See L{I{ParserElement.parseString}<ParserElement.parseString>} for more information on parsing strings containing <TAB>s, and suggested methods to maintain a consistent view of the parsed string, the parse location, and line and column positions within the parsed string.
fudge.core.utilities.pyparsing.
countedArray
(expr)[source]¶Helper to define a counted list of expressions. This helper defines a pattern of the form:
integer expr expr expr...
where the leading integer tells how many expr expressions follow. The matched tokens returns the array of expr tokens as a list - the leading count token is suppressed.
fudge.core.utilities.pyparsing.
delimitedList
(expr, delim=', ', combine=False)[source]¶Helper to define a delimited list of expressions - the delimiter defaults to ‘,’. By default, the list elements and delimiters can have intervening whitespace, and comments, but this can be overridden by passing C{combine=True} in the constructor. If C{combine} is set to True, the matching tokens are returned as a single token string, with the delimiters included; otherwise, the matching tokens are returned as a list of tokens, with the delimiters suppressed.
fudge.core.utilities.pyparsing.
dictOf
(key, value)[source]¶Helper to easily and clearly define a dictionary by specifying the respective patterns for the key and value. Takes care of defining the C{Dict}, C{ZeroOrMore}, and C{Group} tokens in the proper order. The key pattern can include delimiting markers or punctuation, as long as they are suppressed, thereby leaving the significant key text. The value pattern can include named results, so that the C{Dict} results can include named token fields.
fudge.core.utilities.pyparsing.
downcaseTokens
(s, l, t)[source]¶Helper parse action to convert tokens to lower case.
fudge.core.utilities.pyparsing.
getTokensEndLoc
()[source]¶Method to be called from within a parse action to determine the end location of the parsed tokens.
fudge.core.utilities.pyparsing.
keepOriginalText
(s, startLoc, t)[source]¶DEPRECATED - use new helper method C{originalTextFor}. Helper parse action to preserve original parsed text, overriding any nested parse actions.
fudge.core.utilities.pyparsing.
line
(loc, strg)[source]¶Returns the line of text containing loc within a string, counting newlines as line separators.
fudge.core.utilities.pyparsing.
lineno
(loc, strg)[source]¶Returns current line number within a string, counting newlines as line separators. The first line is number 1.
Note: the default parsing behavior is to expand tabs in the input string before starting the parsing process. See L{I{ParserElement.parseString}<ParserElement.parseString>} for more information on parsing strings containing <TAB>s, and suggested methods to maintain a consistent view of the parsed string, the parse location, and line and column positions within the parsed string.
fudge.core.utilities.pyparsing.
makeHTMLTags
(tagStr)[source]¶Helper to construct opening and closing tag expressions for HTML, given a tag name
fudge.core.utilities.pyparsing.
makeXMLTags
(tagStr)[source]¶Helper to construct opening and closing tag expressions for XML, given a tag name
fudge.core.utilities.pyparsing.
matchOnlyAtCol
(n)[source]¶Helper method for defining parse actions that require matching at a specific column in the input text.
fudge.core.utilities.pyparsing.
matchPreviousExpr
(expr)[source]¶Helper to define an expression that is indirectly defined from the tokens matched in a previous expression, that is, it looks for a ‘repeat’ of a previous expression. For example:
first = Word(nums)
second = matchPreviousExpr(first)
matchExpr = first + ":" + second
will match C{“1:1”}, but not C{“1:2”}. Because this matches by expressions, will not match the leading C{“1:1”} in C{“1:10”}; the expressions are evaluated first, and then compared, so C{“1”} is compared with C{“10”}. Do not use with packrat parsing enabled.
fudge.core.utilities.pyparsing.
matchPreviousLiteral
(expr)[source]¶Helper to define an expression that is indirectly defined from the tokens matched in a previous expression, that is, it looks for a ‘repeat’ of a previous expression. For example:
first = Word(nums)
second = matchPreviousLiteral(first)
matchExpr = first + ":" + second
will match C{“1:1”}, but not C{“1:2”}. Because this matches a previous literal, will also match the leading C{“1:1”} in C{“1:10”}. If this is not desired, use C{matchPreviousExpr}. Do not use with packrat parsing enabled.
fudge.core.utilities.pyparsing.
nestedExpr
(opener='(', closer=')', content=None, ignoreExpr=quotedString using single or double quotes)[source]¶Helper method for defining nested lists enclosed in opening and closing delimiters (“(” and ”)” are the default).
If an expression is not provided for the content argument, the nested expression will capture all whitespace-delimited content between delimiters as a list of separate values.
Use the ignoreExpr argument to define expressions that may contain opening or closing characters that should not be treated as opening or closing characters for nesting, such as quotedString or a comment expression. Specify multiple expressions using an Or or MatchFirst. The default is quotedString, but if no expressions are to be ignored, then pass None for this argument.
fudge.core.utilities.pyparsing.
nullDebugAction
(*args)[source]¶‘Do-nothing’ debug action, to suppress debugging output during parsing.
fudge.core.utilities.pyparsing.
oneOf
(strs, caseless=False, useRegex=True)[source]¶Helper to quickly define a set of alternative Literals, and makes sure to do longest-first testing when there is a conflict, regardless of the input order, but returns a C{MatchFirst} for best performance.
fudge.core.utilities.pyparsing.
operatorPrecedence
(baseExpr, opList)[source]¶Helper method for constructing grammars of expressions made up of operators working in a precedence hierarchy. Operators may be unary or binary, left- or right-associative. Parse actions can also be attached to operator expressions.
baseExpr - expression representing the most basic element for the nested
opList - list of tuples, one for each operator precedence level in the expression grammar; each tuple is of the form (opExpr, numTerms, rightLeftAssoc, parseAction), where:
- opExpr is the pyparsing expression for the operator;
- may also be a string, which will be converted to a Literal; if numTerms is 3, opExpr is a tuple of two expressions, for the two operators separating the 3 terms
- numTerms is the number of terms for this operator (must
- be 1, 2, or 3)
- rightLeftAssoc is the indicator whether the operator is
- right or left associative, using the pyparsing-defined constants opAssoc.RIGHT and opAssoc.LEFT.
- parseAction is the parse action to be associated with
- expressions matching this operator expression (the parse action tuple member may be omitted)
fudge.core.utilities.pyparsing.
removeQuotes
(s, l, t)[source]¶Helper parse action for removing quotation marks from parsed quoted strings. To use, add this parse action to quoted string using:
quotedString.setParseAction( removeQuotes )
fudge.core.utilities.pyparsing.
replaceHTMLEntity
(t)¶fudge.core.utilities.pyparsing.
replaceWith
(replStr)[source]¶Helper method for common parse actions that simply return a literal value. Especially useful when used with C{transformString()}.
fudge.core.utilities.pyparsing.
srange
(s)[source]¶Helper to easily define string ranges for use in Word construction. Borrows syntax from regexp ‘[]’ string range definitions:
srange("[0-9]") -> "0123456789"
srange("[a-z]") -> "abcdefghijklmnopqrstuvwxyz"
srange("[a-z$_]") -> "abcdefghijklmnopqrstuvwxyz$_"
The input string must be enclosed in []’s, and the returned string is the expanded character set joined into a single string. The values enclosed in the []’s may be:
a single character
an escaped character with a leading backslash (such as \- or \])
an escaped hex character with a leading '\0x' (\0x21, which is a '!' character)
an escaped octal character with a leading '\0' (\041, which is a '!' character)
a range of any of the above, separated by a dash ('a-z', etc.)
any combination of the above ('aeiouy', 'a-zA-Z0-9_$', etc.)
fudge.core.utilities.pyparsing.
upcaseTokens
(s, l, t)[source]¶Helper parse action to convert tokens to upper case.
fudge.core.utilities.pyparsing.
withAttribute
(*args, **attrDict)[source]¶Helper to create a validating parse action to be used with start tags created with makeXMLTags or makeHTMLTags. Use withAttribute to qualify a starting tag with a required attribute value, to avoid false matches on common tags such as <TD> or <DIV>.
Call withAttribute with a series of attribute names and values. Specify the list of filter attributes names and values as:
- keyword arguments, as in (class=”Customer”,align=”right”), or
- a list of name-value tuples, as in ( (“ns1:class”, “Customer”), (“ns2:align”,”right”) )
For attribute names with a namespace prefix, you must use the second form. Attribute names are matched insensitive to upper/lower case.
To verify that the attribute exists, but without specifying a value, pass withAttribute.ANY_VALUE as the value.
fudge.core.utilities.pyparsing.
indentedBlock
(blockStatementExpr, indentStack, indent=True)[source]¶Helper method for defining space-delimited indentation blocks, such as those used to define block statements in Python source code.
A valid block must contain at least one blockStatement.
fudge.core.utilities.pyparsing.
originalTextFor
(expr, asString=True)[source]¶Helper to return the original, untokenized text for a given expression. Useful to restore the parsed fields of an HTML start tag into the raw tag text itself, or to revert separate tokens with intervening whitespace back to the original matching input text. Simpler to use than the parse action C{keepOriginalText}, and does not require the inspect module to chase up the call stack. By default, returns a string containing the original parsed text.
If the optional C{asString} argument is passed as False, then the return value is a C{ParseResults} containing any results names that were originally matched, and a single token containing the original matched text from the input string. So if the expression passed to C{originalTextFor} contains expressions with defined results names, you must set C{asString} to False if you want to preserve those results name values.
Containers for a particle and a reaction, plus utility to parse in string representations to containers: >>> parseReaction(“n + Fe56 -> n[multiplicity:‘2’] + (Fe55_s -> gamma)”)
fudge.core.utilities.reactionStrings.
particleParser
()[source]¶Parse string of form “Pu239_e2[option1:’value’, option2:’value’ ... ]” into particle class.
fudge.core.utilities.reactionStrings.
particleString
(symbol, A, excitation=0, opts=None, decaysTo=None)[source]¶Bases: object
optionList
= ('multiplicity', 'emissionMode', 'decayRate')¶specialNames
= ('gamma', 'e')¶Wrapper for xml parsers (Etree, DOM, etc), in case we need to support multiple parsers. For now only supporting python’s xml.etree. This is only for reading (not writing) xml; creating new elements should happen within fudge


graph_diff.ordered_ant_algorithm package¶
Submodules¶
graph_diff.ordered_ant_algorithm.ant_graph module¶
-
class
graph_diff.ordered_ant_algorithm.ant_graph.
AntGraph
(graph: graph_diff.graph.graph_with_repetitive_nodes_with_root.GraphWithRepetitiveNodesWithRoot)[source]¶ Bases:
object
Graph representation for OrderedAntAlgorithm
graph_diff.ordered_ant_algorithm.ordered_ant_algorithm module¶
-
class
graph_diff.ordered_ant_algorithm.ordered_ant_algorithm.
OrderedAntAlgorithm
[source]¶ Bases:
graph_diff.graph_diff_algorithm.graph_diff_algorithm.GraphDiffAlgorithm
Realization of heuristic ant algorithm for graph difference problem. It is not an exact algorithm, so the mistakes may be made. TODO: add accuracy evaluation. Complexity is O(NI * (NA * E_1 + V_1) * V_2) TODO: add references.
-
MAX_NUMBER_OF_ITERATIONS_WITH_THE_SAME_SCORE
= 64¶
-
NUMBER_OF_AGENTS
= 16¶
-
NUMBER_OF_ITERATIONS
= 1000¶
-
P
= 0.1¶
-
-
graph_diff.ordered_ant_algorithm.ordered_ant_algorithm.
construct_matched_for_first
(graph1: graph_diff.graph.graph_with_repetitive_nodes_with_root.GraphWithRepetitiveNodesWithRoot, graph2: graph_diff.graph.graph_with_repetitive_nodes_with_root.GraphWithRepetitiveNodesWithRoot)[source]¶ Constructs map of definitely matched nodes :param graph1: first graph :param graph2: second graph :return: dict of matched nodes
graph_diff.ordered_ant_algorithm.parameters module¶
graph_diff.ordered_ant_algorithm.pathfinder module¶
-
class
graph_diff.ordered_ant_algorithm.pathfinder.
Pathfinder
(graph1: graph_diff.ordered_ant_algorithm.ant_graph.AntGraph, graph2: graph_diff.ordered_ant_algorithm.ant_graph.AntGraph, pheromon: [<class 'dict'>], matched: dict)[source]¶ Bases:
object
Class for probabilistic choice of a match of two graphs
-
ALPHA
= 1.0¶
-
BETA
= 3.0¶
-
choose
(u_score: dict, v)[source]¶ Probabilistic choice of a match for a given node. Label size complexity.
Parameters: - u_score – scores addition if v is matched with vertex u
- v – node to be found match with
Returns: chosen match node
-
Module contents¶
Module ant_algorithm contains realization of Ant Algorithm for graph difference problem. It is an heuristic algorithm so exact result is not guaranteed. Complexity of the method is O(NI * (NA * E_1 + V_1) * V_2), where - NI - number of iterations - NA - number of agents (number of independent route constructors) - E_1 - number of edges in the first graph - V_1 - number of nodes in the first graph - V_2 - number of nodes in the second graph TODO: add references TODO: add accuracy evaluation


Players: {{playerCount() | number}}
Name: {{player.fullname}}
Position: {{player.position}}
Number: {{player.jersey}}


| << Combat | Table of Contents | Patching STR# Resources >> |
Appendix II - Legal Status
Your legal status in a system is based on the crime tolerance of that system's government. (if the system is independent, it is based on the first government's [ID 128] crime tolerance) On this scale, enough "good" or "evil" points to equal the government's crime tolerance is given a value of 1:
Good Scale: Legal Status: 0 Clean 4 Citizen 16 Good Citizen 64 Upstanding Citizen 256 Leading Citizen 1024 Model Citizen 4096 Virtuous Citizen
Evil Scale: Legal Status: 0 No record 1 Minor Offender 4 Offender 16 Criminal 64 Wanted Criminal 256 Fugitive 1024 Hunted Fugitive 4096 Public Enemy The text strings listed above are given only by way of illustration, since they can be changed by editing STR# 134.
| << Combat | Table of Contents | Patching STR# Resources >> |
(©) 2000-2002 by Matt Burch and Ambrosia Software, Inc.


--- layout: data_model title: IPv4FlagsType this_version: 1.2 ---
These flag types are used to control or identify fragments in an IP packet. It is a three-bit field, each of the three bits are defined by a field with a string value that indicates the meaning of whether or not the bit is set.
| Field Name | Type | Description |
|---|---|---|
| Reserved0..1 | IntegerObjectPropertyType |
Bit 0: This bit value (0) is reserved and must be zero. |
| Do_Not_Fragment0..1 | DoNotFragmentType |
Bit 1: This is the "don't fragment" bit. Values are specified in the DoNotFragmentType. |
| More_Fragments0..1 | MoreFragmentsType |
Bit 2: This is the "more fragments" bit. Values are specified in the MoreFragmentsType. |


Bookstore
REST API
Bookstore API Documentation
Bookstore API UI
Count all books
Get all books
Get the book with id 1001


Prepare your courses and take advantage of the services of your supermarket or hypermarket, anywhere, everything with the mobile application My Store U!
At home, at work, or on vacation, your Stores application You have the possibility to prepare your next lessons your stores: Super U, Hyper U or Uexpress.


Renders [page:ArrowHelper arrows] to visualize an object's [page:Face3 face] normals.
Requires that face normals have been specified on all [page:Face3 faces] or calculated
with [page:Geometry.computeFaceNormals computeFaceNormals].
Note that this only works with the objects whose geometry is an instance of [page:Geometry].
For [page:BufferGeometry] use a [page:VertexNormalsHelper] instead.
geometry = new THREE.BoxGeometry( 10, 10, 10, 2, 2, 2 );
material = new THREE.MeshBasicMaterial( { color: 0xff0000 } );
box = new THREE.Mesh( geometry, material );
helper = new FaceNormalsHelper( box, 2, 0x00ff00, 1 );
scene.add( box );
scene.add( helper );
[example:webgl_helpers WebGL / helpers]
[page:Object3D object] -- object for which to render face normals.
[page:Number size] -- (optional) length of the arrows. Default is *1*.
[page:Hex color] -- (optional) hex color of the arrows. Default is *0xffff00*.
[page:Number linewidth] -- (optional) width of the arrow lines. Default is *1*.
See the base [page:LineSegments] class for common properties.
See [page:Object3D.matrixAutoUpdate]. Set to *false* here as the helper is using the objects's [page:Object3D.matrixWorld matrixWorld].
The object for which the face normals are being visualized.
Length of the arrows. Default is *1*.
See the base [page:LineSegments] class for common methods.
Updates the face normal preview based on movement of the object.
[link:https://github.com/mrdoob/three.js/blob/master/examples/jsm/helpers/FaceNormalsHelper.js examples/jsm/helpers/FaceNormalsHelper.js]


Education
Allen High School
Aug. 2020 - May 2024
Academic Achievements
USACO Platinum Division
Mar. 2021 - Present
- Top 300 pre-college competitors in the United States
PicoCTF 2021 7th Place Team
Mar. 2021
- 7th place pre-college team in PicoCTF 2021, a national cybersecurity competition out of 2000+ teams
AIME Qualifier
Feb. 2021
Texas UIL Computer Science State Qualifier
May 2021
National Cyber Scholarship Finalist
Apr. 2021
- Ranked 78th place nationally
Region 25 All-Region Cellist
Dec. 2018 - Present
- Three-time Region 25 Orchestra cellist
Research
Cyclic Base Ordering of Graphs
May 2021 - Aug. 2021
Leadership
AYSI Summer Camp Teaching Assistant
May 2020 - Jun. 2020
TA at summer camp focused on teaching artificial intelligence
JLTM Toastmasters VP
Mar. 2020 - Present
- Responsible for managing records for 100+ people


Temisan Otokuefor
Admin ID: 8342bed
<EMAIL_ADDRESS>Sign Out
Create Account
×
First Name
Last Name
Email Address
Role
...
Password
Create
View Recent
Recent Transactions
Date
Description
Amount
dd/mm/yy
Sms charge for March 2019
#52,00
dd/mm/yy
Your Account was Credited with the sum of
#20,000
dd/mm/yy
Sms charge for March 2019
#52,00
Load More
View All
All Accounts
ID
Name
Number
Actions
1
Temisan Otokuefor
0023575930
View
Activate
Dactivate
Delete
2
Temisan Otokuefor
0024585104
View
Activate
Dactivate
Delete
3
Temisan Otokuefor
0024696215
View
Activate
Dactivate
Delete
×
Deactivate This Account?
yes
No
×
Deactivate This Account?
yes
No
×
Deactivate This Account?
yes
No
×
Activate This Account?
yes
No
×
Activate This Account?
yes
No
×
Activate This Account?
yes
No
×
Delete Account?
This action will permanently delete this account
yes
No
×
Delete Account?
This action will permanently delete this account
yes
No
×
Delete Account?
This action will permanently delete this account
yes
No
×
Account Details
Account Name
Account Number
Account Balance
Account Type
Other Accounts
Temisan Otokuefor
0023575930
500,000.00
Savings Account
Current Account
×
Account Details
Account Name
Account Number
Account Balance
Account Type
Other Accounts
Temisan Otokuefor
0023575930
500,000.00
Savings Account
Current Account
×
Account Details
Account Name
Account Number
Account Balance
Account Type
Other Accounts
Temisan Otokuefor
0024585104
500,000.00
Savings Account
Domicilary Account


{% load static %} {% for each_car in car %} {% if each_car.number_plate|stringformat:"s" == contact.number_plate|stringformat:"s" %}
{{each_car.entry_time}}
{{each_car.name}}
{{each_car.service_used}}
{{each_car.phone}}
{{contact.info}}


5.1 "The Greps of Wrath"
This chapter continues our exploration of systems programming case
studies. Here, the focus is on Python scripts that perform more
advanced kinds of file and directory processing. The examples in this
chapter do system-level tasks such as converting files, comparing and
copying directories, and searching files and directories for
strings -- a task idiomatically known as "grepping."
Most of the tools these scripts employ were introduced in Chapter 2. Here, the goal is to show these tools in
action, in the context of more useful and realistic programs. As in
the prior chapter, learning about Python programming techniques such
as OOP and encapsulation is also a hidden subgoal of most of the
examples presented here.
|


Francis Young - The Abbey of Bury St Edmunds: history, legacy and discovery
Francis Young tells the history of Bury St Edmunds Abbey, one of the great ecclesiastical establishments of Medieval England, from the background to its founding in the 11th century, through to the Reformation, and its later history to the present day. He considers the importance of the Abbey to the church, the county of Suffolk and the country as a whole. The book includes lists of abbots, priors and sacrists, a full timeline, and a walkthrough of the Abbey as it was before the Reformation.
Richard Hobbs - The Mildenhall Treasure: late Roman silver plate from Suffolk, East Anglia
Discovered in Suffolk in 1942, the Mildenhall Treasure is one of the most important collections of late Roman silver tableware from the Roman Empire. This title features some of the finest pieces of Roman craftsmanship known from throughout the Roman Empire. It offers new perspectives on the Treasure and its significance within the wider Roman world.
David Butcher - Medieval Lowestoft: The origins and growth of a Suffolk coastal community
A history of the development of Lowestoft from its origins to the flourishing medieval town it became.
David Blakely - Ships, Shawls and Loyal Service: the stories of three East Anglian brothers
Ships, Shawls and Loyal Service relates the stories of three brothers who were born at the end of the 18th century into a long-established family which had its roots in rural Suffolk. The early history of the brothers’ family is also explored, including their grandfather’s business as proprietor of a stagecoach company in Ipswich and his acquaintance with the artist Thomas Gainsborough. This book will appeal to anyone interested in East Anglian life and trade in the 18th and 19th centuries.
Fiona Melrose - Midwinter
Father and son Landyn and Vale Midwinter, are men of the land, Suffolk farmers. Times are hard and they struggle to sustain their property, their livelihood and their heritage in the face of competition from big business. But an even bigger, more brutal fight is brewing: a fight between each other, about the horrible death of Cecelia, beloved wife and mother, in Zambia ten years earlier. A past they have both refused to confront until now.
Over the course of a particularly mauling Suffolk winter, Landyn and Vale grapple with their memories and their pain, raking over what remains of their fragile family unit, constantly at odds and under threat of falling apart forever. While Vale makes increasingly desperate decisions, Landyn retreats, finding solace in the land, his animals - and a fox who haunts the farm and seems to bring with her both comfort and protection.


TPN Calculator
TPN-like fluids
Home TPN Converter
TPN-like Fluids
Main Menu
Weight (kg):
Total volume (mL):
Goal rate (mL/hr):
Dextrose (%):
Sodium (mEq/kg/day):
Potassium (mEq/kg/day):
Acetate (mEq/kg/day):
Central
Peripheral
Calculate!


This is my first webpage!
This is super cool yay
Here are some things I'm going to learn
Check out Epicodus It's a great school for learning web programming!
Here is a link to my favorite things.


This is me in Amsterdam in an artist collaberation warehouse!
This is the warehouse I got to visit!This is a photo of a beautiful street in Paris!
When I went to the Louvre I got to see this hilarious statue.
I got to go to Bristol and had a ton of fun. I met this extremely friendly stray cat and fell in love.
I also got to go to Worms Head in Wales. It was so pretty and cold.
Here are links to other pages I've made!
My Favorite Things My First Webpage


Home
Add Recipe
Add Your Recipe
Recipe name
Recipe Ingredients (one per line)
Recipe Directions (one per line)
Image
Add Recipe
close
Close
arrow_forward
Hello, Welcome to bRecipe


[gecode-users] High memory consumption during engine declaration
Christian Schulte
cschulte at kth.se
Wed Nov 11 14:10:17 CET 2009
Hi,
I don't really know what could be the reason without further looking at the
program. The memory consumed looks massive, actually, almost impossible.
Let's do some math: the search tree has a depth of 45, say with
recomputation possibly using adaptive recomputation that might be around 10
spaces stored during search. That is, each space takes almost 100 Meg! A
thousand variables and 30000 propagators (which propagators do you use?)
should normally take much less.
So, looks really fishy.
Christian
--
Christian Schulte, www.ict.kth.se/~cschulte/
-----Original Message-----
From: users-bounces at gecode.org [mailto:users-bounces at gecode.org] On Behalf
Of benoit
Sent: Tuesday, November 10, 2009 11:11 AM
To: Christian Schulte
Cc: 'Mikael Zayenz Lagerkvist'; users at gecode.org
Subject: [gecode-users] High memory consumption during engine declaration
Good morning,
Thank you both for your replies.
> Another hint: if your model uses the standard Gecode search engines, you
can
> inquire how much memory is occupied by the nodes of the search tree. If
> there is a huge difference between what is reported by the search engine
and
> what is reported by your operating system, you program just has a memory
> leak.
>
I indeed use a standard Gecode search engine (Branch-and-Bound). I
followed you advice and performed the test: both values are coherent.
> Then, how deep is the search tree? How many variables and propagators does
> your problem have?
>
Here are the figures:
- Variables: 622
- Propagators: 25654
- Deep: 49
> In the end: we could say much more if you provided a little bit more
detail
> about what you observe. The information that your program uses a lot of
> memory is not that helpful in itself.
>
Mea culpa: the memory consumption reaches 862MB.
My message was inaccurate yesterday evening: the memory peak occurs when
the engine constructor is called. It's maybe consistent with the figures
provided above ?
Benoît
_______________________________________________
Gecode users mailing list
users at gecode.org
https://www.gecode.org/mailman/listinfo/gecode-users
More information about the gecode-users
mailing list


{% extends "admin/base_site.html" %} {% load i18n admin_urls %} {% load url from suit_compat %} {% block content %}
Are you sure you want to approve the {{ application.city }}, {{ application.country }} application?
Are you sure you want to reject the {{ application.city }}, {{ application.country }} application?


"Tiap kali bertekad makan 3 suap,
biasanya berakhir habis semua >_<
Help! Can't stop!"
~ Sunny Soon @un2sunny
Chocolate, more chocolate...
brought to you, with love, by @cokelatia
what?
#RockyBars [rok-ee bahrs]are freshly-baked, delicious and chewy cookie bars, contain chunks of dark & white chocolate, chocolate chips, caramelized candies, homemade marshmallow, love and passion - all in a bar! ;)
show me!
"Ada kejutan disetiap gigitan. Nyum!"
"Cokelat setan. Sangat jahat. Berbahaya!"
"Awalnya ditawarin ga mau. Pas cobain satu basa-basi, beneran mau nangis makannya..."
i want it!
You can definitely send your order NOW!
Just fill out the order form here
or,
send an email |<EMAIL_ADDRESS>call/sms | +62-22-70831808,
bbm | 2A0ED583,
mention | @cokelatia
with following order data:
Name, E-mail Address, Shipping Address, Phone Number, Quantity
10cmx30cm IDR 70,000.-
10cmx15cm IDR 40,000.-
Add cheese + IDR 10,000.-
Slice IDR 12,000.- (+ IDR 5,000 for additional Ice Cream topping)


1958 - Harrison became part of the Beatles when they were still a skiffle group called the Quarrymen, with McCartney and John Lennon as members.
1960 - Changed his band name to Beatles.Debut album, Please Please Me ,realesed.
1963 - With the Beatles (1963), included "Don't Bother Me", Harrison's first solo writing credit.
1966 - Harrison's first marriage, to model Pattie Boyd in 1966.
1967 - Influenced by eastern philosphy,visted Rishikesh ,India.
1968 - His song "The Inner Light" was recorded at EMI's studio in Bombay, featuring a group of local musicians playing traditional Indian instruments.
1970 - Reales album "All Thing Must Pass."Regarded by many as his best work, the album topped the charts on both sides of the Atlantic.
1971 - Responding to a request from Ravi Shankar, Harrison organised a charity event, the Concert for Bangladesh, which took place on 1 August 1971, drawing over 40,000 people to two shows in New York's Madison Square Garden.The goal of the event was to raise money to aid starving refugees during the Bangladesh Liberation War.
1973 Along with all Beatles member he became a Member of British Empire(MBE)
1980On murder of Jon Lenon,he had a great personal loss.Dedicated a tribute songs "All Those Year Ago."
2001 Dies at Los Angeles,US
2015 - Harrison was posthumously honoured with The Recording Academy's Grammy Lifetime Achievement Award at the Grammy Awards in February 2015
If you have time, you should read more about this incredible human being on his Wikipedia entry.


| Interface | Description |
|---|---|
| Light |
Represents a light source and the algorithm to light a point.
|
| Material |
Can shade a material given a list of lights and an intersection point.
|
| RayTracer |
Interface for tracing rays and shading points.
|
| Class | Description |
|---|---|
| AmbientOcclusionMaterial |
Implements the ambient occlusion material.
|
| BoundingBox |
Represents an axis-aligned box that bounds some geometry, including a list
of that geometry and possible nested bounding boxes.
|
| Color |
Represents an immutable ARGB color.
|
| DirectionalLight |
Represents an infinitely far away directional light.
|
| Intersection |
Records the results of an intersection hit.
|
| PhongMaterial |
Implementation of the Phong shading model.
|
| Renderer |
A renderer from geometry to image files.
|
| Triangle |
Represents an immutable triangle in 3D.
|
| TriangleComparator |
Compares triangles for sorting.
|
| UrtConnection |
Serves a particular connection from an URT controller.
|
| UrtServer |
Serves ray-tracing for the URT (universal ray-tracer) infrastructure.
|
| Vertex |
Immutable structure to store all information about a triangle vertex.
|
| Exception | Description |
|---|---|
| DegenerateTriangleException |
Thrown when a degenerate triangle is created.
|


Sadio Mane set to sign massive deal that proves he’s one of world’s biggest draws
by Jordan ChamberlainSadio Mane could be about to pen one of the biggest boot deals in football history with Puma.
That’s according to John Cross in the Mirror, who says the football giant wants to secure Mane’s allegiance and get him to switch from New Balance.
Mane will be paid a monumental eight-figure fee, likely over a number of years, for his affiliation.
Cross states Mane’s draw as Africa’s biggest and most marketable player is the reason for Puma’s interest, with the manufacturer recently securing Raheem Sterling as well.
Mane is indeed a global superstar. He jointly won last season’s Premier League Golden Boot, was instrumental in helping fire Liverpool to Champions League glory and got Senegal to the final of the AFCON…
We’d argue he should be in contention for the Ballon d’Or, actually, but it’s either going to be Lionel Messi of Barcelona or Mane’s team-mate Virgil van Dijk – which we’d have no problems with of course!
Mane is our most influential attacker right now, which is some compliment considering he plays alongside Mo Salah and Roberto Firmino.
Any financial boost he gets, he deserves. He’s one of the nicest, most humble people in football.


For Users
Nuxeo Mobile for iOS
8.3 Nuxeo Mobile for iOS provides an out of the box mobile experience with any customized Nuxeo Platform server. It lets you access content stored on Nuxeo Platform servers on your phone. Nuxeo Mobile provides a seamless experience on essential features such as searching, browsing, previewing documents (typically images, videos, text documents and notes), and managing favorite documents.
Nuxeo Web UI Preview Edition
8.3 The Nuxeo Web UI has been rewritten entirely, switching from JSF stack to Web Component (HTML) / Polymer framework, with a completely re-designed interface. It will be available in preview edition for the Nuxeo Platform 8.3 and fully available along with the LTS 2016. It allows enhanced productivity with direct access to last visited documents, collections, easy browsing between prev/next document, full screen suggester. Effort has been made for making the tasks validation flow highly efficient. With all those improvements, Nuxeo Web UI is a first class choice for projects where visual and workflows are important requirements.
Instant Share
8.1 A new feature allows to invite users to a given folder of the Nuxeo Platform with either Read or Edit permission, by email. Invited users do not have an account on the Nuxeo Platform instance. The access is temporary and any access remains tracked in the audit log, based on the used email address. Read more in the documentation.
Nuxeo Live Connect for Box
8.1 Nuxeo Live Connect has been improved and now integrates with Box.com. Nuxeo Live Connect allows to easily reference files that are stored in the cloud and have them participate to your business processes. Check the Nuxeo Live Connect documentation for more information.
Nuxeo Live Connect for One Drive
8.2 Nuxeo Live Connect has been improved and now integrates with One Drive. Nuxeo Live Connect allows to easily reference files that are stored in the cloud and have them participate to your business processes. It offers as usual with Live Connect: direct download from the Microsoft Cloud, full text indexing etc. We also have come out with a generic One Drive Java client and a generic file picker as well. Check the Nuxeo Live Connect documentation for more information.
Users and Groups Management Audit
8.2 Creation, Update and deletion of users and groups actions are now logged into the audit trail of Nuxeo Platform.
Nuxeo Drive Optimisations
8.3 At initial synchronisation, the time needed to retrieve the documents is 4 times lower and the number of children synchronized in a folder is no more limited to 1000.
JSF Web UI Evolutions
New Previewers
8.2 Preview now offers to see office documents with pdf.js, video documents with video.js and images with a JavaScript client side viewer. Markdown documents are rendered in HTML. Preview is opened in a fancybox.
Placeless Document Can Be Browsed
8.2 Placeless documents like persisted renditions can now be browsed in the JSF UI without any crash.
User Feedback on Permission Management Tab
8.1 Feedback using the Polymer element paper-toast has been implemented on the Permissions tab. It is used on the create, update and delete permission actions, as well as on the "send notification email" action.
No More Error Stack Trace by Default
8.2 By default the traces are hidden in error pages of Nuxeo, for security reasons. In order to activate the traces display in error pages of Nuxeo, the dev mode has to be set: org.nuxeo.dev in nuxeo.conf or in the admin center.
Smart Search is Back
8.1 Smart Search, that allows users to build their own queries, has been re-integrated to the Search tab, consistently with other search options. Smart Search is delivered as a Nuxeo Package.
Confirmation Pop-up Before Purge
8.1 In the Admin Center, when removing the permissions of a given user, you now have to confirm on a pop-up that you really want to purge all the permissions.
Password Protection
8.2 When a user changes their password, they are now required to fill in the old password value.
See Assigned Groups Before Validating Invitation
8.2 When validating an invitation request, Administrator can now see the groups the user will be granted.
More Friendly "Http Transport returned a 0 status code" Error
8.1 When this error happens, the message is now displayed as a warning and translated in a more friendly way.
Do Not Checkout a Document When Putting It in the Trash
8.3 Now, putting a checked-in document in the trash will not check it out, thus not spuriously changing its quota size. This behavior can be also activated in Nuxeo 7.10 since HF10 using:
<extension target="org.nuxeo.runtime.ConfigurationService" point="configuration"> <property name="org.nuxeo.trash.keepCheckedIn">true</property> </extension>
Nuxeo Explorer Improvements
8.3 We reviewed the browsing pattern, simplifying each view to navigate between Extension Points, Services, Operations, Components and Bundles. We've also extended the XML generation feature to help developers have a working sample. The documentation has been completed and will be maintained regularly.
CSV Importer Small Improvements
Import Time Reduction
8.3 Now, the time needed to import an element in a large collection has been greatly reduced.
Type Attribute Not Mandatory
8.2 Type attribute is not mandatory anymore when updating documents. It must be given only for document creation.
Possible to Redefine
dc:created
Attribute Value
8.2 It is now possible to set
dc:created
property using CSV importer. It used to be overridden with the date of import.
Nuxeo Spreadsheet
Locale is Respected
8.2 Locale setting is now taken into account when using Nuxeo Spreadsheet for the JSF Web UI.
No More Error Stack Trace
8.2 By default the traces are hidden in error pages of Nuxeo, for security
reasons. In order to activate the traces display in error pages of Nuxeo, the dev mode has to be set (
org.nuxeo.dev
in
nuxeo.conf
or in the Admin Center.)
Overriding Subject of the Permission Assignment Email Notification
8.2 It is now possible to override the subject of the notification that is
sent when assigning a permission to someone on a given document. You need to override the label property
label.subject.new.permission
.
Documents Created by Copy Can Have Their Own Dublincore Schema Metadata Values
8.2 Metadata
dc:creator
, dc:creationDate
, dc:modification
and dc:contributors
are now reseted for documents created from a template (workspace template). You can also enable this behavior
for all kind of document copies by setting nuxeo.dclistener.reset-creator-on-copy
configuration property to true.
Nuxeo Showcase Content
8.3 The Nuxeo Showcase Content addon imports a set of showcase content so that the repository is not empty for your first steps: office documents, images, videos. The content of this addon has been updated with new sample documents (reports, case studies, etc.). This addon is a good way to start with your Nuxeo Platform.


AFTER completing the Preparation to the left:
-
Step 1:
Do this Start-the-Session Quiz.

-
Just hand-write your answers on paper or type your answers into a file,
whichever is easier for you.
-
Step 2:
Check your own answers by watching the videos listed below.
-
Of course, do the quiz BEFORE checking its answers!
-
Check your answers carefully!
-
Step 3:
Turn in your answers to the Before-the-Session Quiz
in the usual way, on Moodle,
via the item named
Turn in your Before-the-Session Quiz here.
-
Step 4:
Get help on anything that is not clear to you.
Videos with solutions to the Start-the-Session Quiz:
-
Solutions to the Start-the-Session Quiz:
Video
[9:00]
For your reference, here is a written
Answer Key to the above Start-the-Session Quiz.


Hello Everyone
Collaborate
with me on Github
Have A Look
Instagram Posts
Connect
with me on Linkedin


This page is using a test layout!
Here is my awesome test page!
Here is the entire model that was sent to this template:
{"name"=>"awesome", "description"=>"I was testing to see how awesome I am.", "images"=>["q.jpg", "w.jpg", "e.jpg"], "something"=>"else", "mdl_name"=>"awesome", "mdl_type"=>"tests", "timestamp"=>2012-06-20 18:49:40 -0700, "mdl_url"=>"http://localhost:4000/tests/awesome"}


This email was sent to you by rosymerry.com. To ensure that our updates get to you(not bulk or junk folders), please add our e-mail address to your address book or safe list.
If you have any questions regarding your orders or products, please contact us at
service@rosymerry.com.


| 100 |
100Ω Resistor |
package 0805 [SMD]; resistance 100Ω; tolerance ±5% |
| 100 |
100Ω Resistor |
package 0805 [SMD]; resistance 100Ω; tolerance ±5% |
| 10k |
10kΩ Resistor |
package 0805 [SMD]; resistance 10kΩ; tolerance ±5% |
| 10k |
10kΩ Resistor |
package 0805 [SMD]; resistance 10kΩ; tolerance ±5% |
| 10k |
10kΩ Resistor |
package 0805 [SMD]; resistance 10kΩ; tolerance ±5% |
| 10k |
10kΩ Resistor |
package 0805 [SMD]; resistance 10kΩ; tolerance ±5% |
| 10k1 |
10kΩ Resistor |
package 0805 [SMD]; resistance 10kΩ; tolerance ±5% |
| 10k2 |
10kΩ Resistor |
package 0805 [SMD]; resistance 10kΩ; tolerance ±5% |
| 1k |
1kΩ Resistor |
package 0805 [SMD]; resistance 1kΩ; tolerance ±5% |
| 330 |
330Ω Resistor |
package 0805 [SMD]; resistance 330Ω; tolerance ±5% |
| 510 |
510Ω Resistor |
package 0805 [SMD]; resistance 510Ω; tolerance ±5% |
| ard_left |
Generic female header - 12 pins |
package THT; hole size 1.0mm,0.508mm; pins 12; form ♀ (female); pin spacing 0.1in (2.54mm); row single |
| ard_right |
Generic female header - 12 pins |
package THT; hole size 1.0mm,0.508mm; pins 12; form ♀ (female); pin spacing 0.1in (2.54mm); row single |
| btn1 |
Generic male header - 2 pins |
package THT; hole size 1.0mm,0.508mm; pins 2; form ♂ (male); pin spacing 0.1in (2.54mm); row single |
| btn2 |
Generic male header - 2 pins |
package THT; hole size 1.0mm,0.508mm; pins 2; form ♂ (male); pin spacing 0.1in (2.54mm); row single |
| C1 |
Electrolytic Capacitor |
package 0405 [SMD, electrolytic]; voltage 6.3V; capacitance 220µF |
| light |
Generic double row male header - 2 pins |
package THT; hole size 1.0mm,0.508mm; variant variant 2; pins 2; form ♂ (male); pin spacing 0.1in (2.54mm); row double |
| noise |
Generic male header - 3 pins |
package THT; hole size 1.0mm,0.508mm; pins 3; form ♂ (male); pin spacing 0.1in (2.54mm); row single |
| NPN |
NPN-Transistor |
package SOT-23 [SMD]; type NPN |
| particle |
Generic male header - 6 pins |
package THT; hole size 1.0mm,0.508mm; pins 6; form ♂ (male); pin spacing 0.1in (2.54mm); row single |
| R1 |
150Ω Resistor |
package 0805 [SMD]; resistance 150Ω; tolerance ±5% |
| rpi zero w |
2x20 female headers |
package THT; hole size 1.0mm,0.508mm; pins 20x2; form ♀ (female); pin spacing 0.1in (2.54mm); row double |
| status |
RGB LED (com. cathode, rgb) |
package 5 mm [THT]; rgb RGB; pin order rgb; polarity common cathode |
| temp |
Generic male header - 3 pins |
package THT; hole size 1.0mm,0.508mm; variant variant 1; form ♂ (male); pins 3; pin spacing 0.1in (2.54mm); row single |


Compare the outputs from exiftool against exiftool.js and Gomfunkel's node-exif
| tag | exiftool | exiftool.js | Gomfunkel | Redaktor |
|---|---|---|---|---|
| BitsPerSample | 8 | - | - | - |
| CaptureConditionsPAR | 1 | - | - | - |
| CircleOfConfusion | 0.022 mm | - | - | - |
| ColorComponents | 3 | - | - | - |
| ColorSpace | sRGB | sRGB | 1 | - |
| ComponentsConfiguration | Y, Cb, Cr, - | Y, Cb, Cr, - | - | - |
| Compression | JPEG (old-style) | - | 6 | 6 |
| EncodingProcess | Baseline DCT, Huffman coding | - | - | - |
| ExifByteOrder | Little-endian (Intel, II) | - | - | - |
| ExifImageHeight | 856 | 856 | 856 | 856 |
| ExifImageWidth | 1500 | 1500 | 1500 | 1500 |
| ExifVersion | 0200 | 0200 | - | 2 |
| FilmCategory | 2 | - | - | - |
| FilmGencode | 2 | - | - | - |
| FilmProductCode | 37 | - | - | - |
| FilmSize | 1 | - | - | - |
| FlashpixVersion | 0101 | 0101 | - | 1.01 |
| FocalPlaneResolutionUnit | inches | 2 | 2 | - |
| FocalPlaneXResolution | 1407 | 1407 | 1407 | 1407 |
| FocalPlaneYResolution | 1407 | 1407 | 1407 | 1407 |
| FrameNumber | 0 | - | - | - |
| ImageHeight | 8 | - | - | - |
| ImageRotationStatus | 0 | - | - | - |
| ImageSize | 8x8 | - | - | - |
| ImageSourceEK | 1 | - | - | - |
| ImageWidth | 8 | - | - | - |
| JFIFVersion | 1.02 | - | - | - |
| Make | Eastman Kodak Company | Eastman Kodak Company | Eastman Kodak Company | Eastman Kodak Company |
| MetadataNumber | 0100 | - | - | - |
| Model | Kodak 1640 Film Scanner | Kodak 1640 Film Scanner | Kodak 1640 Film Scanner | Kodak 1640 Film Scanner |
| ModelAndVersion | Version 9 | - | - | - |
| Orientation | Horizontal (normal) | 1 | 1 | 1 |
| ResolutionUnit | inches | 2 | 2 | - |
| RollGuidElements |<PHONE_NUMBER>0000000000000000000000 | - | - | - |
| SBAExposureRecord | (Binary data 368 bytes) | - | - | - |
| SBAInputImageBitDepth | 12 12 12 | - | - | - |
| SBAInputImageColorspace | 3 | - | - | - |
| SBA_RGBShifts | 0 0 0 | - | - | - |
| ScaleFactor35efl | 1.4 | - | - | - |
| Software | Kodak Digital Central Lab System | Kodak Digital Central Lab System | Kodak Digital Central Lab System | Kodak Digital Central Lab System |
| SpatialFrequencyResponse | Spatial freq. (cy/sample)=0,0.02500000037,0.05000000075,0.07500000298,0.1000000015,0.125,0.150000006,0.174999997,0.200000003,0.224999994,0.25,0.275000006,0.3000000119,0.3249999881,0.349999994,0.375,0.400000006,0.4250000119,0.4499999881,0.474999994,0.5; Horizontal SFR (Lum.) film included=1,1.042600036,1.039999962,1.026000023,1.006000042,1.090000033,1.031900048,0.9664999843,0.7580000162,0.6704999804,0.5690000057,0.4704999924,0.400000006,0.3519999981,0.2969999909,0.2319999933,0.1780000031,0.1484999955,0.1509999931,0.1689999998,0.03999999911 | 344 | - | - |
| ThumbnailImage | (Binary data 18979 bytes) | - | - | - |
| ThumbnailLength | 18979 | - | 18979 | 18979 |
| ThumbnailOffset | 910 | - | 880 | 880 |
| UserAdjSBA_RGBShifts | (Binary data 5 bytes) | - | - | - |
| XResolution | 216 | 216 | 72 | 72 |
| YCbCrPositioning | Centered | 1 | 1 | 1 |
| YCbCrSubSampling | YCbCr4:2:0 (2 2) | - | - | - |
| YResolution | 216 | 216 | 72 | 72 |


(.–.) HIV Mexico (n=) (.) DRMs transmission persons sharing network City resistance HIVDR drug genetic {border-style using px;} sequences #ffffff;} .–., clusters age including individuals enrolment metropolitan municipalities HIV- mutations shared threshold viral ART associated data included Condesa low-frequency observed year Madero local municipality putative study surveillance other <. (/) City’s Dis; Infect analysis area boosted clustering estimated first-line links missing old pretreatment px; sequence specific support variants version years {font-family (%) AIDS; Biol; DRMs. Drug San distance events font-size frequency model obtained performed prevalence residence risk ritonavir; size spread strongly supported (Table ). (aOR = ., DRM Data Evol; Gustavo Juárez Pretreatment P = .) Stanford Variables different diffusion double; drug-resistant high inferred low minority networks pairs phylogenetic reverse sequencing study, > Clinic Figure Iztapalapa, JAC Mexican Research Resistance State age, analyses analysis. antiretroviral border-color border-width cluster considering diagnosed edges epidemiological evidence fitness individuals. likely linked location mainly methods molecular odds participants pol presence regimens represent representative role sex, shown solid; transition versus younger {font-style {font-weight <.% (.% (Figure c). (a) (b) (in .%, .%–.%) AIDS Abstract Antimicrob Benito Cluster Clusters Crude Genetic JAC. Mexico. NNRTIs Nacional Number Obregón P < .) P = .), Sanger-like Table University WHO. al.HIV appears area. assess black bold colour coloured courier; defined denote detection diagnoses dispersal distribution dynamics em; epidemic epidemic. especially figure frequent frequently geographic geographical growth higher important include increased integrase load major migration network. next-generation number old, online print provided pt;} regression sampling sensitivity sexual significant similar states suggests transcriptase use used variants. white within-host


7 Dec 2015
Issues in Tech
Before joining Devbootcamp I worked in IT Support for 5 years. Most recently I worked at a major corporation located in silicon valley. I think that the biggest issue that I saw during my time is the near abuse of contract work. As companies continue to look for ways to cut costs, one way that has been used is to hire workers on contract. The reason this cuts on costs is because of benefits. Basically contract workers aren't provided with benefits from the company. This includes health insurance, stock options, pensions, paid-time-off etc.
Thousands of temporary employees dubbed permatemps sued Microsoft in the 90's and won. The reason was Microsoft basically used these temps as full hires, without any of the full hire benefits.
These days, companies skirt the issue by having mandatory extended breaks in between contracts. This way the temp workers are unemployed for a few months and can be hired back as temps again following the break.
I don't want to stir the pot too much, but I think it's in the best interest of people in the tech industry to be aware of these issues.


| DOSE: |
16 mg |
oral |
2C-E |
(powder / crystals) |
16mgs
A Late Winters Night Trip part 2
I sat down on the couch in front of a glass table. It was 9:30 and I had a movie playing on the TV. I had everything I needed laid out before me on the table -scale, 2ce, half a gel cap, a knife. I thought to myself 'This half of a gel cap, it's like a tiny shotglass', and then I got to work. I loaded up the partial gel cap, and weighed and reweighed it repeatedly while adding and remove product with the knife. I wanted around a 16mg trip tonight, and I weighed and reweighed accordingly until it was weighed correctly.
I placed the gel cap on my tongue, and I breathed in before swallowing. When I breathed in, I (on accident) sucked the 2ce into the back of my throat. I swallowed the empty cap and chugged some of my drink to try and make the strange buzzing feeling in my throat go away, go figure it came in waves. It went away permanently after about 15 minutes or so.
By about 11 I was feeling it and had retreated to bed. I began to roll around in the dark, feeling more and more like I was rolling as my mind and body became more and more activated by the 2ce. As they were activated, I felt my / body feeling similar to x / teeth grinding / darkness / paranoia / lightness / prayer / examined and judged personal relationships with those close to me and how to beset improve them (massive hours long introspective session) / visions of many things, notably large morphing objects and patterns, faces meshed into eachother at angles to one another/ sounds / coincidence, or the feeling of the existance of a cause and effect relationship between two or more things that would normally seem unrelated in the physical world.
Like hearing and controlling very clear synthesizer noisers of escalating volume with a visual component of morphing constiuency. Then, just when the synthesizers reach some kind of crescendo or movement where they get really loud and come down like a hammer, and the universe seems like its about to crack apart around me from it and I begin to want to open my eyes and distract myself - a car revs somewhere outside in a street.
I hear it from my room and it feels like the sounds and visions I had amplified in my mind with the help of the 2ce,
caused the car to rev, or the sound to happen. Synesthesia as always was present, this time manifesting for a breif moment as seeing and feeling a clear picture in my head of my toe as I felt it drag along a blanket I was under. Paranoia was present, with a few nervous peaks out the window and a paranoic slant to alot of the introspective session (and a huge positive negative duality portion). I remember feeling like perhaps going beyond duality is leaving this world, as from all I can see this world is duality incarnate.
There are positive and negative poles at the atomic level, and my mind pointed to these as evidence that I should push positivity and lead a positive life. The teeth grinding was extreme this time and I had to really try not to bite down (I held my teeth slack just clear of biting down), I think I want a mouth guard next time. It came in waves, echoes, pulsations. sort of light, stronger, strong strongest and maybe a quiver of the extremities at this point and then release back to light for a few seconds or however long, and repeating this cycle, slowly falling in intensity and eventually back to baseline about 5 or 6 hours later.
With baseline comes sleep, but not very much sleep as I had to get up in the morning and go out, something I loathe to do the morning after a trip -but it worked out just fine, I caught up on sleep the next day and wrote this report the next night. This was approximately my 8th dose of 2ce ranging from 12-20mgs. Until next time.
Orlninu
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.


--- title: "FB 的邮件和谢谢你" layout: "post" permalink: "/2014/01/fb.html" uuid: "3423106851757832970" guid: "tag:blogger.com,1999:blog-5396845717692802313.post-3423106851757832970" date: "2014-01-22 03:38:00" updated: "2014-01-22 03:38:06" description: blogger: siteid: "5396845717692802313" postid: "3423106851757832970" comments: "0" categories: author: name: "姚竹君" url: "https://plus.google.com/105231678775170479823?rel=author" image: "//lh4.googleusercontent.com/-016Uu3F5JfU/AAAAAAAAAAI/AAAAAAAAAG8/p9bZ4HROaxk/s512-c/photo.jpg" ---


Struct Complex
Inherited Members
System.Object.Equals(System.Object, System.Object)
System.Object.GetType()
System.Object.ReferenceEquals(System.Object, System.Object)
Namespace: Vim.Math3d
Assembly: Vim.Math3D.dll
[DataContract]
public readonly struct Complex : IEquatable<Complex>, IComparable<Complex>
Constructors
View SourceComplex(Double)
public Complex(double value)
Complex(Double, Double)
public Complex(double real, double imaginary)
Complex((Double real, Double imaginary))
public Complex((double real, double imaginary) tuple)
Fields
View SourceImaginary
[DataMember]
public readonly double Imaginary
MaxValue
public static Complex MaxValue
MinValue
public static Complex MinValue
NumComponents
public const int NumComponents = 2
One
public static Complex One
Real
[DataMember]
public readonly double Real
UnitImaginary
public static Complex UnitImaginary
UnitReal
public static Complex UnitReal
Zero
public static Complex Zero
Methods
View SourceAlmostEquals(Complex, Single)
public readonly bool AlmostEquals(Complex x, float tolerance = 1E-07F)
AlmostZero(Single)
public readonly bool AlmostZero(float tolerance = 1E-07F)
AnyComponentNegative()
public readonly bool AnyComponentNegative()
CompareTo(Complex)
public readonly int CompareTo(Complex x)
Create(Double, Double)
public static Complex Create(double real, double imaginary)
Create((Double real, Double imaginary))
public static Complex Create((double real, double imaginary) tuple)
Deconstruct(out Double, out Double)
public readonly void Deconstruct(out double real, out double imaginary)
Dot(Complex)
public readonly double Dot(Complex value)
Dot(Complex, Complex)
public static double Dot(Complex value1, Complex value2)
Equals(Object)
public override readonly bool Equals(object obj)
Overrides
System.ValueType.Equals(System.Object)
View Source
Equals(Complex)
public readonly bool Equals(Complex x)
GetComponent(Int32)
public readonly double GetComponent(int n)
GetHashCode()
public override readonly int GetHashCode()
Overrides
System.ValueType.GetHashCode()
View Source
IsInfinity()
public readonly bool IsInfinity()
IsNaN()
public readonly bool IsNaN()
Magnitude()
public readonly double Magnitude()
MagnitudeSquared()
public readonly double MagnitudeSquared()
MaxComponent()
public readonly double MaxComponent()
MinComponent()
public readonly double MinComponent()
ProductComponents()
public readonly double ProductComponents()
SetImaginary(Double)
public readonly Complex SetImaginary(double x)
SetReal(Double)
public readonly Complex SetReal(double x)
SumComponents()
public readonly double SumComponents()
SumSqrComponents()
public readonly double SumSqrComponents()
ToString()
public override readonly string ToString()
Overrides
System.ValueType.ToString()
Operators
View SourceAddition(Double, Complex)
public static Complex operator +(double value1, Complex value2)
Addition(Complex, Double)
public static Complex operator +(Complex value1, double value2)
Addition(Complex, Complex)
public static Complex operator +(Complex value1, Complex value2)
Division(Double, Complex)
public static Complex operator /(double value1, Complex value2)
Division(Complex, Double)
public static Complex operator /(Complex value1, double value2)
Division(Complex, Complex)
public static Complex operator /(Complex value1, Complex value2)
Equality(Complex, Complex)
public static bool operator ==(Complex x0, Complex x1)
GreaterThan(Complex, Complex)
public static bool operator>(Complex x0, Complex x1)
GreaterThanOrEqual(Complex, Complex)
public static bool operator >=(Complex x0, Complex x1)
Implicit((Double real, Double imaginary) to Complex)
public static implicit operator Complex((double real, double imaginary) tuple)
Implicit(Complex to (Double real, Double imaginary))
public static implicit operator (double real, double imaginary)(Complex self)
Inequality(Complex, Complex)
public static bool operator !=(Complex x0, Complex x1)
LessThan(Complex, Complex)
public static bool operator <(Complex x0, Complex x1)
LessThanOrEqual(Complex, Complex)
public static bool operator <=(Complex x0, Complex x1)
Multiply(Double, Complex)
public static Complex operator *(double value1, Complex value2)
Multiply(Complex, Double)
public static Complex operator *(Complex value1, double value2)
Multiply(Complex, Complex)
public static Complex operator *(Complex value1, Complex value2)
Subtraction(Double, Complex)
public static Complex operator -(double value1, Complex value2)
Subtraction(Complex, Double)
public static Complex operator -(Complex value1, double value2)
Subtraction(Complex, Complex)
public static Complex operator -(Complex value1, Complex value2)
UnaryNegation(Complex)
public static Complex operator -(Complex value)
Implements
System.IEquatable<T>
System.IComparable<T>