lclpy.localsearch.move package¶
Submodules¶
lclpy.localsearch.move.abstract_move module¶
-
class
lclpy.localsearch.move.abstract_move.
AbstractMove
¶ Bases:
abc.ABC
Template to create Move-objects.
This object is used to explore a neighbourhood and alter the state of a solution. It can also be used to generate valid moves in the neighbourhood.
-
get_move_type
()¶ Returns the move type.
This function is used in the implementation of delta evaluation. If this is not implemented or wanted, this method does not need to be implemented.
- Returns
The move type.
- Return type
str
-
abstract
get_moves
()¶ A generator used to return all valid moves in the neighbourhood.
- Yields
tuple of int – The next valid move.
-
abstract
get_random_move
()¶ A method used to generate a random move in the neighbourhood.
- Returns
A random valid move.
- Return type
tuple of int
-
abstract
move
(data, move)¶ Performs a move.
- Parameters
data – The dataset that is being explored. It will be altered after the method call.
move (tuple of int) – A representation of a valid move.
-
abstract
undo_move
(data, move)¶ Undoes a move.
Make sure you only undo a move after it’s has been performed.
- Parameters
data – The dataset that is being explored. It will be altered after the method call.
move (tuple of int) – A representation of the move one wishes to undo
-
lclpy.localsearch.move.array_reverse_order module¶
-
class
lclpy.localsearch.move.array_reverse_order.
ArrayReverseOrder
(size)¶ Bases:
lclpy.localsearch.move.abstract_move.AbstractMove
Implements a reverse order move function for 1 dimensional numpy arrays.
The move function performs and generates moves that reverses the order of values in an interval of a one-dimensional array. Note that a move is represented as a tuple of int. The move (x, y) represents reversing of the order of the values in the interval of indices [x, y] of the array. Note that the moves are equivalent to 2-opt.
- Parameters
size (int) – The size of the numpy array that will be altered.
-
_size
¶ The size of the numpy array that is altered.
- Type
int
Examples
Get all possible moves, you should NEVER do this. You should evaluate only one move at a time. This example is simply to show the behaviour of get_moves and how to perform and undo a move:
An example of generating some random moves with get_random_move:
-
get_move_type
()¶ Returns the move type.
- Returns
The move type.
- Return type
str
-
get_moves
()¶ Iterate over all valid moves.
- Yields
tuple of int – The next valid move.
-
get_random_move
()¶ This method is used to generate one random move.
- Returns
A random valid move.
- Return type
tuple of int
-
move
(array, move)¶ Performs the move asked.
- Parameters
array (numpy.ndarray) – The array that will be altered.
move (tuple of int) – Represents 1 unique move. Valid moves can be retrieved by using get_random_move and get_move.
-
undo_move
(array, move)¶ Undoes the move asked.
- Parameters
array (numpy.ndarray) – The array that will be altered.
move (tuple of int) – Represents 1 unique move. Valid moves can be retrieved by using get_random_move and get_move.
lclpy.localsearch.move.array_swap module¶
-
class
lclpy.localsearch.move.array_swap.
ArraySwap
(size)¶ Bases:
lclpy.localsearch.move.abstract_move.AbstractMove
Implements a swap move function for 1 dimensional numpy arrays.
The move function performs and generates moves that swap 2 values in a one-dimensional array. Note that a move is represented as a tuple of int. The move (x, y) represents the swap of the values from the indices x and y of the array.
- Parameters
size (int) – The size of the numpy array that will be altered.
-
_size
¶ The size of the numpy array that is altered.
- Type
int
Examples
Get all possible moves, you should NEVER do this. You should evaluate only one move at a time. This example is simply to show the behaviour of get_moves and how to perform and undo a move:
An example of generating some random moves with get_random_move:
-
get_move_type
()¶ Returns the move type.
- Returns
The move type.
- Return type
str
-
get_moves
()¶ Iterate over all valid moves.
- Yields
tuple of int – The next valid move.
-
get_random_move
()¶ This method is used to generate one random move.
- Returns
A random valid move.
- Return type
tuple of int
-
move
(array, move)¶ Performs the move asked.
- Parameters
array (numpy.ndarray) – The array where items will be swapped.
move (tuple of int) – Represents 1 unique move. Valid moves can be retrieved by using get_random_move and get_move.
-
undo_move
(array, move)¶ Undoes the move asked.
- Parameters
array (numpy.ndarray) – The array where items will be swapped.
move (tuple of int) – Represents 1 unique move. Valid moves can be retrieved by using get_random_move and get_move.
lclpy.localsearch.move.multi_neighbourhood module¶
-
class
lclpy.localsearch.move.multi_neighbourhood.
MultiNeighbourhood
(move_func_list, weights=None)¶ Bases:
lclpy.localsearch.move.abstract_move.AbstractMove
Implements a class that can be used to combine different move functions.
Moves are represented in the following way:
(index move function, a representation of a move from said move function)
Note that all move functions must work on the same type of data structure. Combining move functions meant for different data structures won’t work.
- Parameters
move_func_list (list of AbstractMove or tuple of AbstractMove) – A list or tuple that contains the move functions one wishes to combine.
weights (list of int or tuple of int, optional) – A list or tuple that contains weights to increase or decrease the chance of a move function being used to generate a random move. The weight for a function must have the same index as the function. Weights are positive numbers and need to be defined for every move function. In the default case, every function will have the same weight. Note that it’s perfectly possible to pass the probabilities instead of the weights.
-
_move_func_list
¶ Contains all used move functions.
- Type
tuple of AbstractMove
-
_size
¶ The size of _move_func_list.
- Type
int
-
_tresholds
¶ Tresholds associated with the move functions.
- Type
tuple of float
Examples
Get all possible moves, you should NEVER do this. You should evaluate only one move at a time. This example is simply to show the behaviour of get_moves and how to perform and undo a move:
An example of generating some random moves with get_random_move with default weights (every move function has the same chance of being chosen):
An example of generating some random moves with get_random_move with defined weights (swap weight: 1, reverse weight: 3):
An example of generating some random moves with get_random_move with defined probabilities (swap probability: 0.25, reverse probability: 0.75). Note that the results are exactly the same as the results of the previous doctest:
Test of using delta evaluation with a multineighbourhood:
-
get_move_type
()¶ Returns the move type.
- Returns
The move type.
- Return type
str
-
get_moves
()¶ A generator used to return all valid moves in the neighbourhood.
Note that all moves of all neighbourhoods are included. Duplicate moves are possible. All moves are generated for one neighbourhood, after which they will all be generated for next neighbourhood until no remain. The neighbourhoods will be visited in the order their move functions had in move_func_list when it was passed to the constructor.
- Yields
tuple of int – The next valid move.
-
get_random_move
()¶ A method used to generate a random move in the neighbourhood.
- Returns
A random valid move.
- Return type
tuple of int
-
move
(data, move)¶ Performs a move.
- Parameters
data – The dataset that is being explored. It will be altered after the method call.
move (tuple of int) – A representation of a valid move.
-
select_get_moves
(neighbourhood_nr)¶ A generator used to return all moves from a specific neighbourhood.
- Yields
tuple of int – The next valid move from the specified neighbourhood.
-
select_random_move
(neighbourhood_nr)¶ A method used to generate a random move from a specific neighbourhood.
- Parameters
neighbourhood_nr (int) – Number of the neighbourhood. This number is the index of the neighbourhood in the list of move functions given to the constructor.
- Returns
A random valid move from the specified neighbourhood.
- Return type
tuple of int
-
size
()¶ Function to get amount of neighbourhoods in the multi neighbourhood.
- Returns
The amount of neighbourhoods.
- Return type
int
-
undo_move
(data, move)¶ Undoes a move.
Make sure you only undo a move after it’s has been performed.
- Parameters
data – The dataset that is being explored. It will be altered after the method call.
move (tuple of int) – A representation of the move one wishes to undo.
lclpy.localsearch.move.tsp_array_swap module¶
-
class
lclpy.localsearch.move.tsp_array_swap.
TspArraySwap
(size)¶ Bases:
lclpy.localsearch.move.array_swap.ArraySwap
Implements a swap move for 1 dimensional numpy arrays for tsp problems.
In TSP problems swapping the first location with another is pointless. This class does not generate swaps with the first location from the neighbourhood. In all other respects this class is identical to it’s base class Arrayswap.
The move function performs and generates moves that swap 2 values in a one-dimensional array. Note that a move is represented as a tuple of int. The move (x, y) represents the swap of the values from the indices x and y of the array.
- Parameters
size (int) – The size of the numpy array that will be altered.
-
_size
¶ The size of the numpy array that is altered.
- Type
int
Examples
Get all possible moves, you should NEVER do this. You should evaluate only one move at a time. This example is simply to show the behaviour of get_moves and how to perform and undo a move:
..doctest:
>>> import numpy >>> from lclpy.localsearch.move.tsp_array_swap import TspArraySwap ... # init array, a move will be performed on this array >>> array = numpy.array([0, 1, 2, 3, 4]) ... # init >>> swap = TspArraySwap(len(array)) ... # get all possible moves in all_moves >>> all_moves = [] >>> for move in swap.get_moves(): ... all_moves.append(move) >>> all_moves [(1, 2), (1, 3), (1, 4), (2, 3), (2, 4), (3, 4)] >>> # picking an arbitrary move >>> # Never pick a move like this yourself. It only is done here for >>> # the sake of showing you a clear example. >>> a_move = all_moves[1] >>> a_move (1, 3) >>> # performing the move on the array >>> swap.move(array, a_move) >>> array array([0, 3, 2, 1, 4]) >>> # undoing the move on the array >>> swap.undo_move(array, a_move) # undoes the move >>> array array([0, 1, 2, 3, 4])
An example of generating some random moves with get_random_move:
-
get_moves
()¶ This is a generator used to return all valid moves.
Note that the swaps with the first position aren’t included. When solving TSP problems, the start position doesn’t matter.
- Yields
tuple of int – The next valid move.
-
get_random_move
()¶ This method is used to generate one random move.
Note that the swaps with the first position aren’t included. When solving TSP problems, the start position doesn’t matter.
- Returns
A random valid move.
- Return type
tuple of int
Module contents¶
This package contains everything related to move functions, classes who are used to alter the state of the problems and are able to generate valid “moves” in the neighbourhood.


--- layout: default title: Kodeplay - Resources. section_id: resources ---
Start a business like shopify or etsy.
Start a minimal, fast loading ecommerce site with jekyll.
Opencart. Download
Jekyll. Download


Use the title
(or data-title
)
and data-content
attributes with static strings.
Use ng-template
s with nzbPopoverTitle
and nzbPopoverContent
to enable variable interpolation and the popover API.
This popover has been shown for
seconds!
data-
attributes
This demo sets data-animation="false"
.
nzbPopoverOptions
This demo sets animation to false using
[nzbPopoverOptions]="{{ '{' }}animation: false{{ '}' }}"
.
Demonstrates the
enable()
, disable()
and toggleEnabled()
methods.
<EMAIL_ADDRESS>release there is a bug that
calls toggle()
on a popover even if it is disabled. This
means that the user must, in some cases, click twice to show the popover if
it has been disabled then enabled. This issue has been fixed in the development branch,
and should go away with the next Bootstrap release.
More info...
Demonstrates the
show()
, hide()
and toggle()
methods.
Note that the popover target has data-trigger="manual"
, so clicking
on it will not open the popover.
Demonstrates how you can use the status
observable and data
property to set up a listener that closes
the popover on a click outside.


Simple Cloning
Name
E-mail
Website
clone
delete
Nested Cloning
Name
Contact Information
E-mail
Website
Phone
clone
delete
clone
delete
Limit clones to max 3
Name
E-mail
Website
clone
delete
Animated with custom events
Name
E-mail
Website
clone
delete


OAuth 2.0 Provider Implementation Tutorial¶
Activate the virtual environment ./venv.
$ . ./venv/bin/activate
Add the new provider to functional tests¶
Change directory to ./tests/functional_tests/.
$(venv) cd ./tests/functional_tests/
Create the expected values module for the new provider by copying the tests/functional_tests/expected_values/new_provider.py.template file to tests/functional_tests/expected_values/eventbrite.py.
$(venv) cp expected_values/new_provider.py.template expected_values/eventbrite.py
Create the functional tests config from the template tests/functional_tests/config-template.py.
$(venv) cp config-template.py config.py
Add a new provider slug to the INCLUDE_PROVIDERS list in the config in correct alphabetical order and comment out all the other providers.
# tests/functional_tests/config.py
# Only providers included here will be tested.
# This is a convenience to easily exclude providers from tests by commenting
# them out.
INCLUDE_PROVIDERS = [
# 'behance',
# 'bitly',
# 'deviantart',
'eventbrite',
# 'facebook',
# 'foursquare',
# 'google',
# 'github',
# 'linkedin',
# 'paypal',
# 'reddit',
# 'vk',
# 'windowslive',
# 'yammer',
# 'yandex',
]
Run the test. Make sure that you have the virtual environment active.
$(venv) py.test -vv
The test should fail with the No record for the provider "provider_slug" was not found in the config! exception. Replace the 'provider_slug' value on line 7 with the slug of the new provider.
# tests/functional_tests/expected_values/eventbrite.py
# (...)
conf = fixtures.get_configuration('eventbrite')
Run the test again.
$(venv) py.test -vv
It should fail again, this time with this exception: No record for the provider "eventbrite" was not found in the config!. We need to add a record for the new provider to the actual config.
- Register by the provider and fill out ALL possible user profile fields.
- Register an OAuth 2.0 application by the provider.
- Find the OAuth 2.0 flow and user info endpoints in the provider’s API documentation.
- Make a domain alias for localhost.
- Launch the ./examples/flask/functional_test application.
- Create a new class for the provider.
- Override the OAuth 2.0 enpoints.
- Add the provider to functional tests.
- Add an entry to the functional tests config.
- Comment out all other providers in the INCLUDE_PROVIDERS list.
- Refresh the functional tests app and click on the link of the new provider.
- On the consent page open the browser inspector and copy the login, password and consent button(s) xpaths to the expected values file.
- If there was a problem debug, identify the problem and handle it in the _x_credentials_parser() method.
- If everything went good there should be a syntax highlighted json response.
- If the json response has any properties which were not automatically parsed to the user object you need to override the _x_user_parser() method.
- Stop the functional tests app.
- Run py.test -vv tests/functional_tests
- A Firefox window should open and the tests should fill out the consent form and hit the consent button.
- Add the provider’s OAuth 2.0, API and app dashboard links if any to the docstring.


13.0.2
(json-schema
13.0.2
(#282) if
/then
/else
is dependent on serialized sequence but shouldn't be.
(#281) Use environment-specific line endings for indented formatting.
13.0.2
(#271) Concurrency issue while validating meta-schemas in parallel.
Fixed the contains
/ minContains
relationship to respect when minContains
is zero. The spec specifies that contains
should pass in this case. References: Specification discussion and test discussion.
13.0.1
(#269) The reported bug was that the download method in the schema options wasn't always hitting. What ended up being the issue was that the schema draft wasn't always being determined correctly, and with the recent changes in v13, schemas were always being evaluated as draft 2019-09, even if the $schema
keyword declared otherwise. This had some side effects around always processing $ref
-sibling keywords, which drafts prior to 2019-09 don't allow.
13.0.0
Released on 3 May, 2020
breaking changefeaturepatch
(#260) Performance enhancements for JsonPointer
. Also updates how evaluated properties & items are tracked in schemas.
(#263) JsonSchemaOptions.BasicDownload
shouldn't write to the console.
(#265) DateTime
serialization doesn't format ISO-8601 properly.
(#261) More enhancements around how evaluated properties & items are tracked in schemas.
(#241) Complete overhaul of the schema format
keyword validation system.
(#267) JSON parsing should throw when there is more content after the completion of the value.
(#266) Migrated JsonSchemaOptions
to be used as an instance class so that several schemas can be used with differing options.
Bug Fixes
- ISO 8601 DateTime serialization now uses the
O
format instead of thes
format. (See .NetDateTime
formatting.) Additionally, deserialization now assumes universal times. - Setting
JsonSerializerOptions.CustomDateTimeSerializationFormat
now automatically setsDateTimeSerializationFormat
toCustom
.
Additions
JsonOptions.RequireIsolatedJsonDuringParse
- Specifies whether content is allowed after JSON parsing completes a value. The default behavior is the same as in v12: additional content is allowed.JsonSchema
ProcessingVersion
- Allows a schema to be explicitly processed as a specific draft. Normally, this would be assessed during the first validation by examining the set of keywords present (including the$schema
). This allows subversion of this process. It also works together with the newJsonSchemaOptions.DefaultProcessingVersion
property to indicate exactly which draft is being used.Validate()
andValidateSchema()
now accept an optionalJsonSchemaOptions
parameter.Validate(SchemaValidationContext)
has been made public. This is to be used by custom keywords, not to initiate validation.
JsonSchemaOptions
:- Static
Default
- the default instance of the options. Used to create new instances when not provided by the user. - Parameterless and copy constructors.
LogMetaSchemaValidation
- A value oftrue
will instruct the logging subsystem to not create log entries when validating metaschemas. This can help isolate logs that pertain directly to a validation.DefaultProcessingVersion
- A priority-ordered list of schema draft versions that will serve to determine which draft will be used for a schema.
- Static
IRequireAnnotations
- Schema keywords can implement this interface to indicate that they require annotation results from other keywords in order to do their job properly. Examples of these are theunevaluated*
keywords, which require some special property & item tracking. Not having these keywords in your schemas can increase performance significantly as optimizations have been added for when these keywords are absent.SchemaValidationContext
ShouldTrackValidatedValues
- Works together withIRequireAnnotations
keywords to control how evaluated properties & items are tracked.Options
- The set of options used during the specific validation pass.
IFormatValidator
- See "Formats" section below for more details on the changes on how schema formatting has changed.
Breaking Changes
FluentBuilderExtensions.Format(JsonSchema, Format)
(used for fluent-building schemas) replaced with two new versions:FluentBuilderExtensions.Format(JsonSchema, string)
FluentBuilderExtensions.Format(JsonSchema, IFormatValidator)
GetterExtensions.Format(JsonSchema)
now returnsstring
of the format key instead of aFormat
instance.Format
class changed toFormats
static class.- All static properties that represent formats have been changed to return
IFormatValidator
. GetFormat(string)
now returnsIFormatValidator
.- See "Formats" section below for more details on the changes on how schema formatting has changed.
- All static properties that represent formats have been changed to return
JsonSchema
RegisterSubschemas(Uri, JsonSchemaRegistry)
🠖RegisterSubschemas(SchemaValidationContext)
ResolveSubschema(JsonPointer, Uri)
🠖ResolveSubschema(JsonPointer, Uri, JsonSchemaVersion)
IJsonSchemaKeyword
RegisterSubschemas(Uri, JsonSchemaRegistry)
🠖RegisterSubschemas(SchemaValidationContext)
ResolveSubschema(JsonPointer, Uri)
🠖ResolveSubschema(JsonPointer, Uri, JsonSchemaVersion)
- Same change applied to all keywords.
IJsonSchemaDependency
RegisterSubschemas(Uri, JsonSchemaRegistry)
🠖RegisterSubschemas(SchemaValidationContext)
ResolveSubschema(JsonPointer, Uri)
🠖ResolveSubschema(JsonPointer, Uri, JsonSchemaVersion)
- Same change applied to both implementations.
JsonSchemaOptions
migrated to an instance class. This class can be passed into the validation methods and will be added to the context.- The exception to this migration is the
Download
property, which remains static.
- The exception to this migration is the
FormatKeyword.Value
now returnsstring
instead ofFormat
.
Format Overhaul
As was discussed in #241, the format validation framework had its issues.
- It was difficult or confusing to add custom formats.
- Overriding existing formats just didn't work right.
As such, it has been overhauled to use individual format validator classes. Each of these classes implements a new interface, IFormatValidator
, and handles validation for a single format.
By default, the formats defined by the spec have default implementations and are pre-registered. New formats can be added by implementing IFormatValidator
and supplying an instance to the new Formats.RegisterValidator(IFormatValidator)
static method. Additionally, this same method can be used to supercede the in-built registrations. The static properties are still there and will return the handler for that format, even when overridden.
A minor behavior change is that serialization will no longer throw an exception when encountering unknown formats. It will still throw on validation if configured to do so, however.
12.3.1
Released on 6 Mar, 2020
patch
(#253) Some performance and logging enhancements as suggested by a schema benchmark test.
12.3.0
Released on 20 Feb, 2020
featurepatch
(#254) Include properties and item indices for additional*
and unevaluated*
schema keywords.
(#255) Added writeOnly
to draft 7 metaschema in accordance with JSON Schema correction.
(#257) Fixed debug logging so that it only processes the output strings when configured to log.
Also added .ToJson()
override for IEnumerable<int>
. Previously only supported IEnumerable<double>
.
Fixed a bug with $ref
-sibling keywords not being processed for draft 2019-09.
Fixed several bugs in JSON Path evaluation in accordance with additions to the test report site.
12.2.0
Released on 11 Feb, 2020
feature
Inspired by a fabulous test report site by GitHub user cburgmer JsonPath now supports some new syntaxes.
- Various bracketed key notations:
$["key"]
, etc. - Negative indexes for "from last" queries:
$[-1]
. - Backward navigation and negative steps in slice queries:
$[3:0:-2]
. - Comparisons with null in expressions:
<EMAIL_ADDRESS>== null)]
.
The remaining items will not be supported for now. Support may be added with sufficient pressure from the user base, however.
12.1.0
Released on 4 Feb, 2020
feature
(JSON Schema Spec #248) Added properties ValidatedItems
and LocallyValidatedItems
to SchemaValidationContext
in order to fix a bug where unevaluatedItems
was not considering all items that failed validation.
12.0.3
Released on 22 Jan, 2020
patch
(#248) $ref
and $recursiveRef
schema keywords were not passing up evaluated properties/items, so unevaluatedProperties
and unevaluatedItems
keywords could not "see through" them.
12.0.2
Released on 5 Jan, 2020
patch
(#243) Bugs with JSON Path implementation
ArgumentOutOfRangeException
thrown when array index overlaps instance but is out of range of instance. Should just return items within the overlap.- Wildcard search operator should only return child objects, not also the root object.
12.0.1
Released on 19 Dec, 2019
patch
(#241) Creating an override for a schema format causes ArgumentException
because the key is already added.
12.0.0
Released on 18 Dec, 2019
breaking changefeaturepatch
This change primarily adds .Net Core 3.0 support. It has also been updated to support null reference types.
Logging
Some cursory verbose logging has been introduced to allow the client to see what decisions Manatee.Json is making during (primarily) schema validation and serialization. The JsonOptions.Log
static property has been introduced for this purpose. It is of type ILog
which exposes a single method, Verbose(string, LogCategory)
.
The log categories currently are general, serialization, and schema. This allows the client to enable or disable certain activities, so that, for instance, they can only enable schema validation logging if they wish. The JsonOptions.LogCategory
static property controls what categories are actually sent.
There is no default implementation for ILog
. Keeping this option null will ensure faster processing in production scenarios. This logging feature is intended for research and debugging purposes only as there are a lot of logs which can add processing time.
Bug fixes
unevaluatedItems
would not properly process items that nested keywords touched but failed. See JSON-Schema-Test-Suite #291 for details and an example of the logging mentioned above.
Breaking Changes
JsonValue
parameterless constructor removed. UseJsonValue.Null
instead.JsonValue
parameterized constructor arguments changed to non-nullable or will throwArgumentNullException
.JsonArray.OfType(JsonValueType)
now throwsArgumentNullException
when passed a null array.JsonSyntaxException.Source
replaced bySourceData
so that it doesn't hideException.Source
.SerializationContext
used only for serialization now.DeserializationContext
now introduced for deserialization. This changes method signatures forISerializer
. Additional notes below.
Serialization changes
In an effort to reduce memory footprint, a single SerializationContext
/DeserializationContext
instance will be retained throughout the serialization/deserialization process. To facilitate this, new instances will no longer be created when a serializer needs to serialize an object's contents; instead it will "push" new details onto the existing context, serialize, then "pop" the details when finished.
For example, the internal ListSerializer
in versions up to v11 would serialize a list's contents using this code:
for (int i = 0; i < array.Length; i++)
{
var newContext = new SerializationContext(context)
{
CurrentLocation = context.CurrentLocation.CloneAndAppend(i.ToString()),
InferredType = list[i]?.GetType() ?? typeof(T),
RequestedType = typeof(T),
Source = list[i]
};
array[i] = context.RootSerializer.Serialize(newContext);
}
However, creating a new context instance for each item is resource intensive and creates a lot of work for the garbage collector afterward.
Instead we simply push new details onto the existing context before we serialize an item, then pop those details afterward, like this:
for (int i = 0; i < array.Length; i++)
{
context.Push(list[i]?.GetType() ?? typeof(T), typeof(T), i.ToString(), list[i]);
array[i] = context.RootSerializer.Serialize(context);
context.Pop();
}
The values that we push are
- The inferred type of the object we're pushing (or the requested type if the inferred type is null)
- The requested type
- The JSON path segment (in this case the index)
- The object to be serialized
These are maintained in a stack internally to the context object and are removed on the Pop()
call, keeping the context synchronized with the serialization process.
11.0.4
Released on 27 Nov, 2019
patch
(#231) $ref
throwing SchemaNotFoundException
when $id
is an anchor-type reference in drafts 07 and earlier. (These are disallowed for draft 2019-09. The functionality was split out to the $anchor
keyword.)
Fixed an issue where not all evaluated properties were being reported to be used by unevaluatedProperties
. This came out of a JSON Schema Slack conversation.
11.0.3
Released on 26 Oct, 2019
patch
(#226) Fixes for JSON Patch move and add operations.
11.0.2
Released on 14 Oct, 2019
patch
Fixed an issue with deserialization name transformations where the function was passed the member name instead of the JSON key value.
11.0.1
Released on 29 Sep, 2019
patch
(#215) IndexOutOfRangeException
thrown on JSON Path arrays when index equals array count.
The schema format
keyword was incorrectly failing for some keywords when value type is not a string.
Minor serialization improvements.
11.0.0
Released on 18 Sep, 2019
Beta releases
- v11.0.0 beta 7 - Released on 29 Aug, 2019
- v11.0.0 beta 6 - Released on 24 Jul, 2019
- v11.0.0 beta 5 - Released on 21 Jul, 2019
- v11.0.0 beta 4 - Released on 19 Jul, 2019
- v11.0.0 beta 3 - Released on 18 Jul, 2019
- v11.0.0 beta 2 - Released on 10 Jul, 2019
- v11.0.0 beta 1 - Released on 1 Jul, 2019 (introduces breaking changes)
- v10.2.0 beta 2 - Released on 28 Jun, 2019
- v10.2.0 beta 1 - Released on 22 Jun, 2019
NOTE The properties for the new drafts contain version names like "Draft2019_06". Since this depends on when the spec is released, these may change between the beta and the official release without incrementing the major version.
breaking changefeature
Breaking changes
Schema
In order to support some new independent reference tests, some changes were made to the schema validation logic to include a validation-run-independent schema registry, separate from the static one. The first two changes support this requirement:
IJsonSchemaKeyword.RegisterSubschemas(Uri? baseUri, JsonSchemaRegistry localRegistry)
- The second parameter is new.SchemaValidationContext
now requires a source context from which to copy values.JsonSchemaOptions.OutputFormat
now has a default value ofFlag
, which only returns whether an instance is valid, without any error details. This greatly improves performance out of the box. Configuration is required to generate error details.JsonSchemaoptions.RefResolutionStrategy
now has a default value ofProcessSiblingId
to conform with the draft-08 definition of$ref
and$recursiveRef
.
Additionally, it was pointed out on the JSON Schema spec repo that format
is not specifically intended for strings, but can also be used to validate other types. To address this, the StringFormat
type has been renamed to Format
and now accepts JsonValue
instead of merely string
, although one string formats are defined by the spec. Formatting for other types as well as their validation logic will need to be provided by the consumer (you).
Serialization
IResolver.Resolve<T>()
removed since it wasn't used internally anywhere.IResolver.Resolve(Type, Dictionary<SerializationInfo, object>)
- The second parameter is new.
Other breaking changes
Dropped multi-target support. Now only targeting .Net Standard 2.0. This is still compatible with .Net Framework 4.6.1 and higher.
Obsolete items removed
SchemaErrorMessages
- Error messages are now customizable via theErrorTemplate
static property on those keywords which have it.FluentBuilderExtensions.Items(this JsonSchema, params JsonSchema[])
- The compiler could not distinguish between the single-schema usage ofitems
and the array-usage which only contained a single schema. Instead, multiple calls toItem
should be used. This is also more consistent with howDefinition
andProperty
work.
Non-breaking changes
(#175) JSON Schema draft-08 support.
(#209) PropertiesKeyword
does not return nested results. This was fixed as part of #175.
(#205) Schema equality doesn't capture extra properties on second schema. E.g. for a.Equals(b)
if b
has a property that doesn't exist in a
, .Equals()
still returns true. The collection comparison has been fixed.
(#201) CompilerAttributes causes errors in .Net Standard versions. This dependency has been removed.
(#211) @desmondgc Date/Time format validation within schemas is insufficient. Default implementation now uses DateTime.TryParseExact()
with support for fractional seconds.
(#219) $ref
resolution fails when using a relative URI as the $id
for the root schema. Added a new option JsonSchemaOptions.DefaultBaseUri
as suggested by the spec. The default value for this option is manatee://json-schema/
.
JsonSchemaRegistry
is no longer static, but all previously existing functionality is still static. All instance functionality is internal.- Minor memory usage improvements for JSON Schema validation.
- Added the following to
JsonSchemaOptions
to more finely control the output, which can have a significant effect on performance.IgnoreErrorsForChildren<T>()
- Prevents collection of errors and annotations generated by subschemas for a given keyword throughout the entire schema structure.IgnoreErrorsForChildren(JsonPointer)
- Prevents collection of errors and annotations generated by subschemas of a specified location within the schema.ShouldReportChildErrors(IJsonSchemaKeyword, SchemaValidationContext)
- To be used by custom keywords, determines whether errors and annotations should be reported based on the above settings.
10.1.4
Released on 8 Jun, 2019
patch
(#206) @Kimtho fixed JSON Patch replace
verb. Thanks!
10.1.3
Released on 14 May, 2019
patch
(#203) Adjacent (consecutive) escape sequences that contained Unicode values were always considered as a surrogate pair even if they were just two separate characters.
Updating schema test suite references exposed a bug in additionalProperties
keyword implementation in that it would look into applicator keywords (anyOf
, allOf
, etc.). This bug was fixed.
10.1.2
Released on 21 Nov, 2018
patch
BUG FIX: There was a concurrency issue when determining the correct internal serializer to use.
10.1.1
Released on 21 Nov, 2018
patch
BUG FIX: Generic collections typed with abstract and interface types were not saving the instance type for the items.
10.1.0
Released on 16 Nov, 2018
feature patch
Expanded on the fixes from 10.0.5 and added the JsonSchemaOptions.AllowUnknownFormats
static property to control behavior when unknown string formats are encountered.
10.0.5
Released on 15 Nov, 2018
patch
(#193) Invalid string formats were not being included in the schema validation result data when the format was not recognized. It would just fail. Now the result object will contain a new isKnownFormat
key in the AdditionalInfo
property to indicate whether the specified keyword was recognized.
(#194) Schema validations that occurred through $ref
keywords were not being reported at all. Instead the report would state that the error occurred at the $ref
, but would give no further information.
10.0.4
Released on 8 Oct, 2018
patch
User-defined serialization should have priority over built-in ones.
Enum deserialization should be smarter about detecting numeric or string formatting.
10.0.3
Released on 8 Oct, 2018
patch
Fixed issue with serialization of non-enumerated IEnumerable<T>
types like .Where()
and .Select()
queries.
Added missing XML comments on some types.
10.0.2
Released on 4 Oct, 2018
patch
Removed compiler warnings for using JsonSchema
.
10.0.1
Released on 3 Oct, 2018
patch
Fixed issue where a class with a nullable struct fails to serialize.
Fixed issue where a non-null object with all properties as default values would be serialized to null
then summarily removed from the serialization output. This is bad because null is different than a non-null default object.
10.0.0
Released on 30 Sep, 2018
breaking change feature
Summary
(#147) Updated how custom serialization is handled. Rather than registering independent methods (CustomSerializations
), custom sub-serializer implementations that each handle specific scenarios can be registered. Each implementation specifies whether it can handle the (de)serialization based on the expected type, the serializer options, and (for deserialization, specifically) the JSON value. It will also specify whether it should maintain referential integrity.
(#132) Changed parsing and schema errors to use JSON Pointers to indicate the locations of errors instead of JSON Paths. The reasoning behind this is JSON Path is a query syntax that can return multiple values, whereas JSON Pointer was specifically designed to represent a single path resulting in a single value.
(#175 (Part 1) In preparation for JSON Schema draft-08, the JSON Schema implementation has been overhauled. The key takeaways from this work are:
- The schema drafts are no longer represented by multiple classes, but rather a single
JsonSchema
class that is capable of modeling all of the drafts. - The
JsonSchema
type does not expose keywords as properties, but is a container of keyword implementations. This allows for easier extension.
(#112) Another change intended to support JSON Schem draft-08 is a standardized output format. The validation results have been restructured to conform to this proposal.
(#177) Opened up the StringFormat
class (schema format
keyword) for extension and customization.
(#152) Updated referential integrity for serialization to use JSON Pointers that point elsewhere in the structure instead of the previous #Def
and #Ref
tags. Now you will see something more like {"$ref":"#/property1/array/3/data"}
in the serialized JSON for references. The idea of the #Def
tag has been removed.
In addition to the below listings, the entire JSON Schema implementation has been overhauled. Please see the JSON Schema documentation for details.
Changes
JsonSyntaxException
-string Path
property replaced byJsonPointer Location
property.JsonOptions.PrettyPrintIndent
- Updated fromchar
tostring
to support indentations like multiple spaces.
New types
SerializerFactory
ISerializer
Removed types
CustomSerializations
JsonSerializationAbstractionMap
(previously obsolete)JsonSerializationTypeRegistry
(previously obsolete)TypeRegistrationException
Functional changes
- Updated the default enumeration serialization method from using numeric values to using named values. (See
JsonSerializerOptions.EnumSerializationFormat
.)
9.9.4 & 9.9.5
Released on 23 August, 2018
patch
(#179) Fixed concurrency issue that may occur while auto-serializing a single object type for the first time on two threads simultaneously.
9.9.3
Released on 12 Jul, 2018
patch
Fixed bug where attempting to download schemas behind https
links would throw the least helpful of exceptions: a message-less Exception
.
9.9.2
Released on 8 Jun, 2018
patch spec
(#170) JSON-Schema.org updated the meta-schemas for all drafts to be more inline with the specifications. This update matches those changes.
9.9.1
Released on 13 Jun, 2018
patch
(#167) JSON Schema: required
is only processed when properties
is present.
9.9.0
Released on 9 May, 2018.
feature
(#161) Added the ability to customize schema error messages.


{% block content %}
Create Board
Log out
Cover:
*click to upload cover
Name:
0/40
Description:
0/200
Create
Cancel
{% endblock %}


The Veterans Patriot Action Conference is one of the younger combat veteran organizations on the block, incorporated in the Summer of 2015. We are a non-profit veteran organization under provisions of IRS 501 (c) 19.
We believe that veterans represent a vast, and untapped, reservoir of values, ethos, mission-first outlook and personal honor; attributes that ae sadly fading from the American culture.
We believe that the military veteran is the final American institutional reservoir of these key values shaped and inculcated through the crucible of honorable service.
We believe that the values of Duty, Honor, Country and Competence in the face of adversity are qualities that have become a rarity in our society, yet, are ingredients indispensable to the sustainment of a viable republic.
We believe that veterans must stick together in a world, at least for the moment, that claims to approve of us and of our honorable service, a condition that can change rapidly, as those of us who served in Vietnam will vouch.
We believe that most veterans carry into civilian life, whether after three years or after thirty years of honorable service, a sense of purpose summarized by their open-ended military oaths, which state in part...
" I ... do solemnly swear (or affirm) that I will support and defend the Constitution of the United States against all enemies, foreign or domestic, that I will bear true faith and allegiance to the same; that I take this obligation freely, without any mental reservations or purpose of evasion ... So help me God."
These we call Vets in the Fight®, men and women whose conduct and actions represent the values espoused in their oaths.
Vets in the Fight® is also a concept aimed at giving substance to those special qualities in continuing service to our Nation.
Vets in the Fight® must: Vote, they must serve in public office, they must hold government accountable in adherence to the US Constitution, as written.
The Veterans Patriot Action Conference (VPAC for short) held its first conference on 18 -19 February 2016, in Charleston, SC. Over 100 special operations and other service veterans and wives from across the country assembled for VPAC I, where we were given a world level perspective on national security by distinguished professionals, like:
Admiral James ‘Ace’ Lyons
Lieutenant General Tom McInerney
Lieutenant Colonel Jay Delancy
and other subject matter experts
You see, we wanted to gain a better understanding of our operational and civic environment, and to begin maturing the VPAC approach to providing veterans a venue beyond just a beer and barbecue (although, we’ll do that, too.) In the course of VPAC I, it became clear that what we’d initiated was a veteran forum, a kind of think-tank, a problem-solving environment, where we applied our varied experience and the military decision- making process (MDMP) to the resolution of those issues. One of our key issues was to give veterans a voice in their Republic, hence the adoption of the Vets in the Fight® concept.
On Day 2 of our VPAC I, we were honored to have visits by Dr. Ben Carson, world-renowned surgeon, and by Mr. Donald Trump, accomplished businessman, both candidates running in the 2016 South Carolina Presidential Primary Elections the following day. (All candidates were invited to VPAC I, but only Dr. Carson and Mr. Trump responded.) Each of them brought his own approach to national security, and each contributed to maturing our Vets in the Fight® concept. Mr. Trump, especially, was interested in our top veteran issues. He gave us a thumbs-up on our VPAC efforts and accepted a Vets in the Fight® challenge coin that sits today on display behind his Oval Office desk.
We will continue the VPAC forum, a continuing conference at physical locations as well as virtually online. This website is part of the online conversation about key issues, to include Women in Ground Combat and the VPAC 21 st Century Warrior Veterans Health System.
Come join us as we give voice to you, part of the 18 million military veterans living in the United States, the Nation underwritten by your service in peace and war.
Take Action Now!


JavaScript is disabled on your browser.


input_deck = Frost.Read("Your Directory")
You need to add this utility code to your code to make it work.
value = input_deck.melting_points["titanium"]
Seems you have a file melting_points.xxx in your directory.


1. How to install modifiers¶
1.1. Scripts¶
For almost all scripts you can use Tampermonkey extension for your browser. Here are some links to extensions:
Edge (not Chrome-based version);
Right after extension installation you can install any of scripts:
Open one of the script files in Github like that.
Then press Raw button. Copy an url of the page into a clipboard.
Open Tampermonkey extension
.Paste the url into Install from URL field and press Install button.
Press another Install button.
Your are DONE!
Script will be enabled automatically on a page with url which matches the regexp in @include section of the script header.
1.2. Styles¶
Under construction.


Review of Class 3
Thematic Mapping
What does the term choropleth mean?
What does the term choropleth mean?
What is an Ecological Fallacy?
What is an Ecological Fallacy?
What problem is notated on the left, and how is it fixed on the right?
Class 4
Map Projections
A "Developable Surface" it is not....
To get to a 'Flat Map' we have to go through a series of progressive steps
= Earth > Geoid > Ellipsoid > Reference Sphere > Plane
How to get to Planar from Sphere?
Use a lightbulb!
What happens to the map units when transforming from GCS to PCS?
A painful process...resulting in geometric distortions
Different Projection Systems are good at some things, and bad at others....
Preserving direction (azimuthal or zenithal), a trait possible only from one or two points to every other point
Preserving shape locally (conformal or orthomorphic)
Preserving area (equal-area or equiareal or equivalent or authalic)
Preserving distance (equidistant), a trait possible only between one or two points and every other point
Preserving shortest route, a trait preserved only by the gnomonic projection
Projections fall in to the 'family' groupings; each 'family' typified by what they preserve...
Comparison of Map distortion @ South America
Projections are also grouped based on their 'Projection Surfaces' ...
A good example of a planar projection is a polar stereographic projection...
A good example of a cylindrical projection is - of course - the Mercator Projection...
A good example of a conic projection is an Albers Equal Area Projection often used for USA...
Map Projections
Datums & Coordinate Systems
'Center' of North America- Meades Ranch, Kansas | NAD27
Best known grid system of international scope = UTM
Map Projections
Break | Lab


| PostgreSQL 9.0.10 Documentation | ||||
|---|---|---|---|---|
| Prev | Up | Chapter 7. Queries | Next |
After a query has produced an output table (after the select list has been processed) it can optionally be sorted. If sorting is not chosen, the rows will be returned in an unspecified order. The actual order in that case will depend on the scan and join plan types and the order on disk, but it must not be relied on. A particular output ordering can only be guaranteed if the sort step is explicitly chosen.
The ORDER BY clause specifies the sort order:
SELECT select_list FROM table_expression ORDER BY sort_expression1 [ASC | DESC] [NULLS { FIRST | LAST }] [, sort_expression2 [ASC | DESC] [NULLS { FIRST | LAST }] ...]
The sort expression(s) can be any expression that would be valid in the query's select list. An example is:
SELECT a, b FROM table1 ORDER BY a + b, c;
When more than one expression is specified, the later values are used to sort rows that are equal according to the earlier values. Each expression can be followed by an optional ASC or DESC keyword to set the sort direction to ascending or descending. ASC order is the default. Ascending order puts smaller values first, where "smaller" is defined in terms of the < operator. Similarly, descending order is determined with the > operator. [1]
The NULLS FIRST and NULLS LAST options can be used to determine whether nulls appear before or after non-null values in the sort ordering. By default, null values sort as if larger than any non-null value; that is, NULLS FIRST is the default for DESC order, and NULLS LAST otherwise.
Note that the ordering options are considered independently for each sort column. For example ORDER BY x, y DESC means ORDER BY x ASC, y DESC, which is not the same as ORDER BY x DESC, y DESC.
A sort_expression can also be the column label or number of an output column, as in:
SELECT a + b AS sum, c FROM table1 ORDER BY sum; SELECT a, max(b) FROM table1 GROUP BY a ORDER BY 1;
both of which sort by the first output column. Note that an output column name has to stand alone, that is, it cannot be used in an expression — for example, this is not correct:
SELECT a + b AS sum, c FROM table1 ORDER BY sum + c; -- wrong
This restriction is made to reduce ambiguity. There is still ambiguity if an ORDER BY item is a simple name that could match either an output column name or a column from the table expression. The output column is used in such cases. This would only cause confusion if you use AS to rename an output column to match some other table column's name.
ORDER BY can be applied to the result of a UNION, INTERSECT, or EXCEPT combination, but in this case it is only permitted to sort by output column names or numbers, not by expressions.
| [1] | Actually, PostgreSQL uses the default B-tree operator class for the expression's data type to determine the sort ordering for ASC and DESC. Conventionally, data types will be set up so that the < and > operators correspond to this sort ordering, but a user-defined data type's designer could choose to do something different. |


Destination
Start Date
End Date
Type of the travel
What type of trip are you taking?
Beach
City
Country
WARNING !
End date must be no more than 8 days from today's date.
Click to continue.
Pack My Bags
×
click to shop!


--- layout: post title: PEAR Update Issues On Snow Leopard date: 2009-10-09 13:39:13.000000000 +01:00 categories: - PHP tags: - osx - pear - snow leopard status: publish type: post published: true meta: _edit_last: '4005008' author: Marcus Ramsden ---
So I just came across some weirdness on my default install of PHP on Snow Leopard. I wanted to install the latest version of PHPUnit in order to carry out some testing, but it was asking me to update PEAR.
So I ran the usual PEAR update command;
[code language="shell"]
$ sudo pear upgrade pear
[/code]
This appeared to run without any issues. But subsequently whenever I attempted to run PEAR I was greeted with the following error message;
[code language="shell"]
/usr/local/bin/pear: fork: Resource temporarily unavailable
[/code]
I took a look inside the offending file as it is just a simple command to run the PEAR script. It looked like this;
[code language="shell"]
pear /usr/lib/php/pearcmd.php
[/code]
Obviously the script was infinitely attempting to spawn itself causing the resource temporarily unavailable error. So the simple fix was to change the script to the following;
[code language="shell"]
php /usr/lib/php/pearcmd.php $@
[/code]
I'm not quite sure why the script changed when I upgraded but it appeared to. I figured I should pop this note up in case anyone else gets caught out, or indeed I forget and get caught out again. Any insight on why this might have happened would be appreciated.


|
SlowDown Algorithmic Regularization (SDAR)
Algorithmic Regularization with slowdown method for integrating few-body motions
|
A class contains the Kepler orbital parameters and initial step size. More...
#include <information.h>
Public Member Functions | |
| Information () | |
More... | |
| bool | checkParams () |
| check whether parameters values are correct initialized More... | |
| void | reserveMem (const int _nmax) |
| reserve memory of binarytree list More... | |
| COMM::BinaryTree< Tparticle > & | getBinaryTreeRoot () const |
| get the root of binary tree More... | |
| void | calcDsAndStepOption (const Float _sd_org, const int _int_order, const Float _G) |
| calculate ds from the inner most binary with minimum period, determine the fix step option More... | |
| void | generateBinaryTree (COMM::ParticleGroup< Tparticle, Tpcm > &_particles, const Float _G) |
| generate binary tree for the particle group More... | |
| void | clear () |
| clear function More... | |
| void | printColumnTitle (std::ostream &_fout, const int _width=20) |
| print titles of class members using column style More... | |
| void | printColumn (std::ostream &_fout, const int _width=20) |
| print data of class members using column style More... | |
| void | writeBinary (FILE *_fout) const |
| write class data to file with binary format More... | |
| void | readBinary (FILE *_fin) |
| read class data to file with binary format More... | |
Public Attributes | |
| Float | ds |
| FixStepOption | fix_step_option |
More... | |
| COMM::List< COMM::BinaryTree< Tparticle > > | binarytree |
More... | |
A class contains the Kepler orbital parameters and initial step size.
The class has members to generate the Kepler orbital binary tree of the particle group and store the information in binarytree. \ It also provides the initial step size estimator and the option of fix step.
|
inline |
a list of binary tree that contain the hierarchical orbital parameters of the particle group.
initializer, set ds to zero, fix_step_option to none
|
inline |
calculate ds from the inner most binary with minimum period, determine the fix step option
Estimate ds first from the inner most binary orbit (eccentric anomaly), set fix_step_option to later
| [in] | _sd_org | original slowdown factor of the group |
| [in] | _int_order | accuracy order of the symplectic integrator. |
| [in] | _G | gravitational constant |
|
inline |
check whether parameters values are correct initialized
|
inline |
clear function
|
inline |
generate binary tree for the particle group
| [in] | _particles | particle group |
|
inline |
get the root of binary tree
|
inline |
print data of class members using column style
print data of class members in one line for column style. Notice no newline is printed at the end
| [out] | _fout | std::ostream output object |
| [in] | _width | print width (defaulted 20) |
|
inline |
print titles of class members using column style
print titles of class members in one line for column style
| [out] | _fout | std::ostream output object |
| [in] | _width | print width (defaulted 20) |
|
inline |
read class data to file with binary format
| [in] | _fp | FILE type file for reading |
|
inline |
reserve memory of binarytree list
|
inline |
write class data to file with binary format
| [in] | _fp | FILE type file for output |
| COMM::List<COMM::BinaryTree<Tparticle> > AR::Information< Tparticle, Tpcm >::binarytree |
fix step option for integration
| Float AR::Information< Tparticle, Tpcm >::ds |
| FixStepOption AR::Information< Tparticle, Tpcm >::fix_step_option |
initial step size for integration


Mortgage Dashboard
Total Principal
$0.00
Total Interest
$0.00
Total Cost
$0.00
Your monthly payments
$0.00
Loan amount
$0.00
Term
0
Interest rate
0%
Amortization Table
| Month | Payment | Principal | Interest | Total Interest | Balance |
|---|---|---|---|---|---|
| Month | Payment | Principal | Interest | Total Interest | Balance |


This release note is divided into the following sections:
Introduction,
Documentation,
What's New,
Upgrading And
Compatibility Information,
Host Support,
Dependencies,
Device Support,
Validation Information,
Known Issues,
Benchmarks,
Versioning,
Technical Support
And Product Updates,
SYS/BIOS <IP_ADDRESS> is a GA release of SYS/BIOS
6.34.04.
SYS/BIOS is a real-time operating system that provides
pre-emptive deterministic multithreading.
The SYS/BIOS releases introduce a completely new SYS/BIOS kernel
and toolset. The SYS/BIOS releases include numerous major
enhancements, including completely new kernel APIs. They also include
compatibility layers and tooling to facilitate easy porting of
applications
developed on DSP/BIOS 5.x releases.
A number of
tools and libraries that were provided as an
integrated part of DSP/BIOS 5.x releases must now be downloaded
separately to
obtain a functional solution. It is essential for even experienced
DSP/BIOS
users to refer to the Getting Started
Guide and to the Upgrading and Compatibility Information
section for
further details.
Please read the Getting Started Guide for help installing and setting
up your environment to use SYS/BIOS <IP_ADDRESS>.
back to top
The following documentation is provided with this release. These
documents are also available via teh CCS Eclipse help table of
contents.
License and manifest.
Additional online sources of documentation.
Release
notes from previous releases are also available in the
release notes archive
directory.
back to top
SYS/BIOS
<IP_ADDRESS> GA
Release (this release).
- Misc bug fixes, see below.
Defects Fixed in
SYS/BIOS
<IP_ADDRESS> GA (Fixes since SYS/BIOS <IP_ADDRESS>):
ID
Headline
SDOCM00097542 (M3 target): unresolved symbols when BIOS.taskEnabled = false, or BIOS.swiEnabled = false
SDOCM00097540 OMAP/64T AMMU ROV view shows bogus names for Large Page descriptors
SDOCM00097536 Custom build flow doesn't support package.bld flow with non-co-located source files.
SDOCM00097452 Add triggerSensitivity and targetProcList instance param to GIC Hwi
SDOCM00097450 Add Generic Timer support for A15
SDOCM00097448
Do not open example .c files by default (update Example.xs file) --
causes undesired focus change in TRex
SDOCM00097446 Need to deliver ti.sysbios.fatfs.utils utilties for Windows as well as Linux
SDOCM00097444 Change default timer frequency and timer intNum for Vayu C6000 GP Timers
SDOCM00097442 BIOS needs to support Secure Kernel for 6614
SDOCM00097440 BIOS c66 support needs to do 2 mfence operations to workaround mfence errata
SDOCM00097438 Add Long Descriptor format support to A15 MMU module
SDOCM00097436 M3 Hwi_reconfig() writes to const array can result in bus error if array is in flash.
SDOCM00097434 OMAP5430 C64T is not supported in 6.34.00
back to top
SYS/BIOS
releases have many significant changes from
DSP/BIOS 5.x. It is important to understand the information
below in order to
successfully use SYS/BIOS and to migrate applications from DSP/BIOS
5.x.
SYS/BIOS
software downloads
SYS/BIOS 6.34
- Binary
Compatibility. A few fields have been added to several data
structures which means that SYS/BIOS 6.34 is not binary compatible
SYS/BIOS 6.33. The safest thing to do is to rebuild all source
code against the .h files provided with SYS/BIOS 6.34. Note that only
the following externally visible structures have changed:
Task_Params, Task_Struct, HeapMem_Params. If your source
code does not use these structures directly, then you may not need to
recompile. Be careful when using other libraries from other
sources (like the NDK stack or other libraries provided with an
SDK or otherwise). These libraries should also be recompiled
against SYS/BIOS 6.34.
- MSP430
Clock. The Clock module for the MSP430 now uses the periodic
timer mode (TickMode_PERIODIC) by default. SYS/BIOS 6.33
used TickMode_DYNAMIC. You can change this default using
the ‘Clock.tickMode’ configuration parameter in your .cfg file.
TickMode_DYNAMIC minimizes the need for periodic interrupts, but adds
some constraints on the application. See
http://processors.wiki.ti.com/index.php/SYS/BIOS_for_the_MSP430#Clock_Tick_Suppression
for more information about MSP430 clock modes.
- This release requires XDC 3.24.01 or later.
- This
release requires Arm codegen 5.0.1 or later. 5.0.1 will be
provided with CCSv5.3 and is available separately for use in CCSv5.2.
SYS/BIOS 6.33
- The
default directory for SYS/BIOS is changing to match CCSv5.1.0, "C:\ti"
is the new default directory (SDOCM00086138 -- BIOS installer needs to
change its default directory to match CCSv5.1.0)
- RTDX
has been removed and is no longer supported.
Only stop mode is supported for Realtime Analysis (RTA).
SYS/BIOS 6.32
- For
TI816X devices (ie Netra), GPTimers 3 and 7 have been removed from the
list of usable timers due to anomalous behavior when clocked at 32KHz
resulting in two interrupts for every period when run in continuous
mode.
- We
are planning to remove support for the whole_program and
whole_program_debug profiles because of build time problems and
compatibility problems when using different compiler
versions. SYS/BIOS 6.32 will output a warning
message when
the whole_program or whole_program_debug profiles are
used.
We are now providing pre-built libraries which can be selected via the
BIOS.libType configuration parameter (see section 7.6.1 of the BIOS
User's Guide for details). The instrumented
library contains Assert() and Log statements. The
non-instrumented library does not. The custom
library can
be used to build a custom BIOS library which will be built using
#define constants reflecting some of the key configuration parameters
from your application .cfg file. The
non-instrumented
library and custom library should give you similar or better
performance
to SYS/BIOS 6.31 using the whole_program profile.
- .taskStackSection
has been renamed – The .taskStackSection linker section has been
renamed to be a subsection of .far, .bss, or .ebss as appropriate for
the given target. This allows BIOS to be used with
CCS-supplied
linker .cmd files for the MSP430, Stellaris and 28x devices.
This
section is used to place the stacks for tasks created at configuration
time. The new name is provided in the
Task.defaultStackSection field in your configuration. If you
reference ‘.taskStackSection’ in your .cfg file, you should change the
code to use Task.defaultStackSection.
SYS/BIOS 6.31
- Added
an assert to GateMutex. GateMutex_enter() calls
BIOS_getThreadType() to validate the calling context.
GateMutex_enter() will raise an assert if called from Hwi or Swi
context. GateMutex internally calls
Semaphore_pend/post to
provide the mutex. Semaphore_pend() cannot be called from Swi
or
Hwi context if the semaphore is not available. Note that a
GateMutex gate is registered with the TI compiler’s RTS library to make
the RTS library reentrant. Calling printf() and a
few other
RTS functions from Swi or Hwi context will yield this
assert.
- This
assert check will catch bad code
that could cause a rare crash. While not recommended, this
assert
can be disabled by adding ‘GateMutex.common$.diags_ASSERT =
Diags.ALWAYS_OFF;’ to your .cfg file.
- Text
footprint on the C6x
increased by 2K due to Exception.enablePrint default now being set to
‘true’ by default. This enables better diagnostic output when
an
exception occurs. You can set this config parameter to
‘false’ to
save memory and get a shorter, less informative diagnostic string.
- MMU
and Cache are now enabled by default for Arm9.
- Arm9
applications will have larger data/text footprint
due to the 16kbyte MMU table and MMU initialization code.
- Moved
ti.sysbios.arm.Cache module to ti.sysbios.arm.arm9.Cache since this
module is Arm9-specific. .cfg scripts will have to be updated
to
use new name (‘ti.sysbios.family.arm.arm9.Cache’) and .c files will
have to change to use ‘#include
<ti/sysbios/arm/arm9/Cache.h>’.
- Use
BIOS_exit() rather than System_exit() if called from ISR or Swi context
to avoid Assert() in GateMutex module. BIOS_exit()
and
System_exit() both flush the SysMin trace buffer using CIO.
The
CIO library is protected by GateMutex.
DA830
ROM
- BIOS
6.30 and 6.31 cannot be used with the
DA830 ROM. BIOS 6.21 is the preferred version for DA830 ROM.
The
'ti.sdo.io' and 'ti.sdo.utils' packages are no longer provided with
SYS/BIOS
- These
packages are now provided in a
separate
"IPC" product. Users of these packages simply need to add
this
other product directory to their package path (XDCPATH) to build their
applications.
The
ti.sysbios.ipc package and its modules have been deprecated
- The
Semaphore, Event, and Mailbox modules were moved from the
ti.sysbios.ipc package into the ti.sysbios.knl package. Please update
your applications to use the ti.sysbios.knl package versions of the
Semaphore, Event, and Mailbox modules. Using the ipc package versions
of these modules will result in build warnings. In a subsequent release
of BIOS, using any module within the ipc package will result in a build
error.
The
ti.sysbios.family.arm.m3.Exception module has been deprecated
- The
ti.sysbios.family.arm.m3.Exception module functionality has been
enhanced and merged into the ti.sysbios.family.arm.m3.Hwi module.
Please update your applications to use the ti.sysbios.family.arm.m3.Hwi
module to configure exception handling. By default, exceptions will be
reported to CIO with an Error message. Details of the exception can be
seen using Hwi module's "Exception" ROV view. At the expense of
additonal code size, some of this detailed information can ALSO be
routed to the CIO console by setting the Hwi.enableException
configuration flag to true.
Placing of sections using
MEM configs is no longer supported (ie MEM.TEXTSEG is unsupported)
- All
of the legacy MEM memory segment placment functionality has been
removed. Legacy BIOS users must use Program.sectMap to place memory
sections.
The
ti.sysbios.family.c64p.Cache.initSize configuration item is no longer
supported
- The
ti.sysbios.family.c64p.Cache module no longer supports setting the
Cache sizes. These settings are now managed within a platform and can
be configured using the platform wizard.
SYS/BIOS no
longer
contains all the tools and objects you will need
- The
XDC tools now provide the
SYS/BIOS configuration tools and Platform support.
XDC also includes a minimal run-time environment that provides the LOG,
System,
Asserts, Error handling, Timestamp, and Memory Allocation APIs that
will be
used by SYS/BIOS applications. Please refer to the Getting Started Guide on where to
download the XDC tools and
run-time.
Migrating DSP/BIOS
5.x applications to SYS/BIOS
- SYS/BIOS has different APIs
compared to those in
DSP/BIOS 5.x. Configuration scripts are also incompatible between the
two
releases. To provide easy migration of DSP/BIOS 5.x
applications, an API
compatibility layer is provided along with a conversion tool that
converts
configuration scripts to work with XDC and SYS/BIOS. The
API compatibility
layer provides 100% C source code compatibility with the exception of a
few
APIs that are no longer supported. For more complete details
of migrating
DSP/BIOS 5.x applications and configuration scripts, please refer
to Migrating
a DSP/BIOS 5 Application to SYS/BIOS.
- As mentioned
above, some APIs previously supported in
DSP/BIOS 5.x releases will no longer be supported in this release or
the
compatibility layer. Complete details are provided in the
Migration document referenced
above.
back to top
- Supported
Operating Systems
- Windows
7, Windows XP, Windows Vista
- Linux
[RH4], Ubuntu [10.04]
back to top
- Required Software
- Code Composer Studio v5.2.x or later
- Code Generation Tools
- C28X
version 6.0.2 or later
- C6X version 7.3.1 or later
- ARM version 4.9.1 or later, M3/M4 version 5.0.1 or later
- MSP430 version 4.1.0 or later
- XDCtools <IP_ADDRESS> or later
- Required Hardware
- See Device Support Section below.
back to top
Click here
for the list of supported devices.
back to top
Click
here
for the list of compilers used to build and validate this release
(scroll down to Supported Targets section).
back to top
The
following issues are known to affect this release:
- If
this version of SYS/BIOS is installed on the same system
as SYS/BIOS 6.31.00.xx or older, and use the same
version of
CCS, the user may see two "SYS/BIOS" folders in the examples when
creating a new project. The Eclipse plugins were
updated to
fix this in SYS/BIOS <IP_ADDRESS> and later. To work around
this
issue remove all versions of SYS/BIOS older than <IP_ADDRESS>.
ID
Headline
SDOCM00082528 Linker command file
inserted regardless of platform selected for C28 examples
SDOCM00074130 ROV should reference kernel
object names versus object addresses
SDOCM00068360 No data displayed in RTA
Exec Graph when attaching to running target
back to top
For a full description of Benchmarks please see the
appendices in the SYS/BIOS
6 User's
Guide.
back to top
All releases
have 4 digits (M.mm.pp.bb).
This includes GA and pre-releases (engineering, alpha/EA, beta, etc.).
Pre-releases are denoted with a suffix (e.g. <IP_ADDRESS>-eng or
<IP_ADDRESS>-beta).
This product's version follows a version format, M.mm.pp.bb, where M is a single digit
Major number, mm
is 2 digit minor number, pp
is a 2 digit patch number, and b
is an unrestricted set of digits used as an incrementing build counter.
To
support multiple side-by-side installations of the product, the product
version is encoded in the top level directory (e.g. bios_6_30_00_00).
Subsequent
releases of patch upgrades will be identified by the patch number, ex.
SYS/BIOS <IP_ADDRESS> with directory bios_6_30_01_15. Typically, these
patches only include critical bug fixes.
Please note that
version numbers and compatibility keys are NOT the same. For an
explanation of compatibility keys, please refer to the 'Upgrade and
Compatibility Information' section.
back to top
Technical
Support and Product Updates
back to top
Last
updated: December 06, 2012 Build Ver: <IP_ADDRESS> Rev: j22


What type of website do you want?
E-commerce
Blogs and Personal
Informational
Online Community
Others
What is your budget?
Under 1 thousand
1 to 3 thousands(include)
3 to 5 thousands (include)
5 to 10 thousands (include)
Over 10 thousands (include)
How did you find us?
Search engine
Newspaper
Friend recommendation
Clear Form Submit Form


java(1) java(1) Name java - the Java application launcher SYNOPSIS java [ options ] class [ argument ... ] java [ options ] -jar file.jar [ argument ... ] options Command-line options. class Name of the class to be invoked. file.jar Name of the jar file to be invoked. Used only with -jar. argument Argument passed to the main function. DESCRIPTION The java tool launches a Java application. It does this by starting a Java runtime environment, loading a specified class, and invoking that class's main method. The method must be declared public and static, it must not return any value, and it must accept a String array as a parameter. The method dec‐ laration must look like the following: public static void main(String args[]) By default, the first non-option argument is the name of the class to be invoked. A fully-qualified class name should be used. If the -jar option is specified, the first non-option argument is the name of a JAR archive containing class and resource files for the application, with the startup class indicated by the Main-Class manifest header. The Java runtime searches for the startup class, and other classes used, in three sets of locations: the bootstrap class path, the installed extensions, and the user class path. Non-option arguments after the class name or JAR file name are passed to the main function. OPTIONS The launcher has a set of standard options that are supported on the cur‐ rent runtime environment and will be supported in future releases. In addition, the current implementations of the virtual machines support a set of non-standard options that are subject to change in future releases. Standard Options -client Select the Java HotSpot Client VM. A 64-bit capable jdk currently ignores this option and instead uses the Java Hotspot Server VM. For default VM selection, see Server-Class Machine Detection @ http://docs.oracle.com/javase/7/docs/tech‐ notes/guides/vm/server-class.html -server Select the Java HotSpot Server VM. On a 64-bit capable jdk only the Java Hotspot Server VM is supported so the -server option is implicit. For default VM selection, see Server-Class Machine Detection @ http://docs.oracle.com/javase/7/docs/tech‐ notes/guides/vm/server-class.html -agentlib:libname[=options] Load native agent library libname, e.g. -agentlib:hprof -agentlib:jdwp=help -agentlib:hprof=help For more information, see JVMTI Agent Command Line Options @ http://docs.oracle.com/javase/7/docs/plat‐ form/jvmti/jvmti.html#starting. -agentpath:pathname[=options] Load a native agent library by full pathname. For more information, see JVMTI Agent Command Line Options @ http://docs.oracle.com/javase/7/docs/plat‐ form/jvmti/jvmti.html#starting. -classpath classpath -cp classpath Specify a list of directories, JAR archives, and ZIP archives to search for class files. Class path entries are separated by colons (:). Specifying -classpath or -cp overrides any setting of the CLASSPATH environment variable. If -classpath and -cp are not used and CLASSPATH is not set, the user class path consists of the current directory (.). As a special convenience, a class path element containing a base‐ name of * is considered equivalent to specifying a list of all the files in the directory with the extension .jar or .JAR (a java pro‐ gram cannot tell the difference between the two invocations). For example, if directory foo contains a.jar and b.JAR, then the class path element foo/* is expanded to a A.jar:b.JAR, except that the order of jar files is unspecified. All jar files in the speci‐ fied directory, even hidden ones, are included in the list. A classpath entry consisting simply of * expands to a list of all the jar files in the current directory. The CLASSPATH environment vari‐ able, where defined, will be similarly expanded. Any classpath wildcard expansion occurs before the Java virtual machine is started -- no Java program will ever see unexpanded wildcards except by querying the environment. For example; by invoking Sys‐ tem.getenv("CLASSPATH"). For more information on class paths, see Setting the Class Path @ http://docs.oracle.com/javase/7/docs/tech‐ notes/tools/index.html#classpath. -Dproperty=value Set a system property value. -d32 -d64 Request that the program to be run in a 32-bit or 64-bit environ‐ ment, respectively. If the requested environment is not installed or is not supported, an error is reported. Currently only the Java HotSpot Server VM supports 64-bit opera‐ tion, and the "-server" option is implicit with the use of -d64. And the "-client" option is ignored with the use of -d64. This is subject to change in a future release. If neither -d32 nor -d64 is specified, the default is to run in a 32-bit environment, except for 64-bit only systems. This is subject to change in a future release. -enableassertions[:<package name>"..." | :<class name> ] -ea[:<package name>"..." | :<class name> ] -disableassertions[:<package name>"..." | :<class name> ] -da[:<package name>"..." | :<class name> ] Disable assertions. This is the default. With no arguments, disableassertions or -da disables assertions. With one argument ending in "...", the switch disables assertions in the specified package and any subpackages. If the argument is simply "...", the switch disables assertions in the unnamed package in the current working directory. With one argument not ending in "...", the switch disables assertions in the specified class. To run a program with assertions enabled in package com.wom‐ bat.fruitbat but disabled in class com.wombat.fruitbat.Brickbat, the following command could be used: java -ea:com.wombat.fruitbat... -da:com.wombat.fruitbat.Brickbat <Main Class> The -disableassertions and -da switches apply to all class loaders and to system classes (which do not have a class loader). There is one exception to this rule: in their no-argument form, the switches do not apply to system. This makes it easy to turn on asserts in all classes except for system classes. A separate switch is pro‐ vided to enable asserts in all system classes; see -disablesys‐ temassertions below. Enable assertions. Assertions are disabled by default. With no arguments, enableassertions or -ea enables assertions. With one argument ending in "...", the switch enables assertions in the specified package and any subpackages. If the argument is simply "...", the switch enables assertions in the unnamed package in the current working directory. With one argument not ending in "...", the switch enables assertions in the specified class. If a single command line contains multiple instances of these switches, they are processed in order before loading any classes. So, for example, to run a program with assertions enabled only in package com.wombat.fruitbat (and any subpackages), the following command could be used: java -ea:com.wombat.fruitbat... <Main Class> The -enableassertions and -ea switches apply to all class loaders and to system classes (which do not have a class loader). There is one exception to this rule: in their no-argument form, the switches do not apply to system. This makes it easy to turn on asserts in all classes except for system classes. A separate switch is pro‐ vided to enable asserts in all system classes; see -enablesys‐ temassertions below. -enablesystemassertions -esa Enable asserts in all system classes (sets the default assertion status for system classes to true). -disablesystemassertions -dsa Disables asserts in all system classes. -help or -? Display usage information and exit. -jar Execute a program encapsulated in a JAR file. The first argument is the name of a JAR file instead of a startup class name. In order for this option to work, the manifest of the JAR file must contain a line of the form Main-Class: classname. Here, classname identi‐ fies the class having the public static void main(String[] args) method that serves as your application's starting point. See the jar(1) and the Jar trail of the Java Tutorial @ http://docs.oracle.com/javase/tutorial/deployment/jar for informa‐ tion about working with Jar files and Jar-file manifests. When you use this option, the JAR file is the source of all user classes, and other user class path settings are ignored. Note that JAR files that can be run with the "java -jar" option can have their execute permissions set so they can be run without using "java -jar". Refer to Java Archive (JAR) Files @ http://docs.oracle.com/javase/7/docs/tech‐ notes/guides/jar/index.html. -javaagent:jarpath[=options] Load a Java programming language agent, see java.lang.instrument @ http://docs.oracle.com/javase/7/docs/api/java/lang/instrument/pack‐ age-summary.html. -jre-restrict-search Include user-private JREs in the version search. -no-jre-restrict-search Exclude user-private JREs in the version search. -showversion Display version information and continue. (See also -version.) -splash:imagepath Show splash screen with image specified by imagepath. -verbose -verbose:class Display information about each class loaded. -verbose:gc Report on each garbage collection event. -verbose:jni Report information about use of native methods and other Java Native Interface activity. -version Display version information and exit. (See also -showversion.) -version:release Specifies that the version specified by release is required by the class or jar file specified on the command line. If the version of the java command invoked does not meet this specification and an appropriate implementation is found on the system, the appropriate implementation will be used. release not only can specify an exact version, but can also specify a list of versions called a version string. A version string is an ordered list of version ranges separated by spaces. A version range is either a version-id, a version-id followed by a star (*), a ver‐ sion-id followed by a plus sign (+) , or two version-ranges com‐ bined using an ampersand (&). The star means prefix match, the plus sign means this version or greater, and the ampersand means the logical anding of the two version-ranges. For example: -version:"1.6.0_13 1.6*&1.6.0_10+" The meaning of the above is that the class or jar file requires either version 1.6.0_13, or a version with 1.6 as a version-id pre‐ fix and that is not less than 1.6.0_10.. The exact syntax and defi‐ nition of version strings may be found in Appendix A of the Java Network Launching Protocol & API Specification (JSR-56). For jar files, the usual preference is to specify version require‐ ments in the jar file manifest rather than on the command line. See the following NOTES section for important policy information on the use of this option. Non-Standard Options -X Display information about non-standard options and exit. -Xint Operate in interpreted-only mode. Compilation to native code is disabled, and all bytecodes are executed by the interpreter. The performance benefits offered by the Java HotSpot VMs' adaptive com‐ piler will not be present in this mode. -Xbatch Disable background compilation. Normally the VM will compile the method as a background task, running the method in interpreter mode until the background compilation is finished. The -Xbatch flag dis‐ ables background compilation so that compilation of all methods proceeds as a foreground task until completed. -Xbootclasspath:bootclasspath Specify a colon-separated list of directories, JAR archives, and ZIP archives to search for boot class files. These are used in place of the boot class files included in the Java platform JDK. Note: Applications that use this option for the purpose of overrid‐ ing a class in rt.jar should not be deployed as doing so would con‐ travene the Java Runtime Environment binary code license. -Xbootclasspath/a:path Specify a colon-separated path of directires, JAR archives, and ZIP archives to append to the default bootstrap class path. -Xbootclasspath/p:path Specify a colon-separated path of directires, JAR archives, and ZIP archives to prepend in front of the default bootstrap class path. Note: Applications that use this option for the purpose of overrid‐ ing a class in rt.jar should not be deployed as doing so would con‐ travene the Java Runtime Environment binary code license. -Xcheck:jni Perform additional checks for Java Native Interface (JNI) func‐ tions. Specifically, the Java Virtual Machine validates the parame‐ ters passed to the JNI function as well as the runtime environment data before processing the JNI request. Any invalid data encoun‐ tered indicates a problem in the native code, and the Java Virtual Machine will terminate with a fatal error in such cases. Expect a performance degradation when this option is used. -Xfuture Perform strict class-file format checks. For purposes of backwards compatibility, the default format checks performed by the JDK's virtual machine are no stricter than the checks performed by 1.1.x versions of the JDK software. The -Xfuture flag turns on stricter class-file format checks that enforce closer conformance to the class-file format specification. Developers are encouraged to use this flag when developing new code because the stricter checks will become the default in future releases of the Java application launcher. -Xnoclassgc Disable class garbage collection. Use of this option will prevent memory recovery from loaded classes thus increasing overall memory usage. This could cause OutOfMemoryError to be thrown in some applications. -Xincgc Enable the incremental garbage collector. The incremental garbage collector, which is off by default, will reduce the occasional long garbage-collection pauses during program execution. The incremental garbage collector will at times execute concurrently with the pro‐ gram and during such times will reduce the processor capacity available to the program. -Xloggc:file Report on each garbage collection event, as with -verbose:gc, but log this data to file. In addition to the information -verbose:gc gives, each reported event will be preceeded by the time (in sec‐ onds) since the first garbage-collection event. Always use a local file system for storage of this file to avoid stalling the JVM due to network latency. The file may be truncated in the case of a full file system and logging will continue on the truncated file. This option overrides -verbose:gc if both are given on the command line. -Xmnsize or -XX:NewSize Sets the size of the young generation (nursery). -Xmsn Specify the initial size, in bytes, of the memory allocation pool. This value must be a multiple of 1024 greater than 1MB. Append the letter k or K to indicate kilobytes, or m or M to indicate megabytes. The default value is chosen at runtime based on system configuration. For more information, see HotSpot Ergonomics @ http://docs.oracle.com/javase/7/docs/tech‐ notes/guides/vm/gc-ergonomics.html Examples: -Xms6291456 -Xms6144k -Xms6m -Xmxn Specify the maximum size, in bytes, of the memory allocation pool. This value must a multiple of 1024 greater than 2MB. Append the letter k or K to indicate kilobytes, or m or M to indicate megabytes. The default value is chosen at runtime based on system configuration. For more information, see HotSpot Ergonomics @ http://docs.oracle.com/javase/7/docs/tech‐ notes/guides/vm/gc-ergonomics.html Examples: -Xmx83886080 -Xmx81920k -Xmx80m On Solaris 7 and Solaris 8 SPARC platforms, the upper limit for this value is approximately 4000m minus overhead amounts. On Solaris 2.6 and x86 platforms, the upper limit is approximately 2000m minus overhead amounts. On Linux platforms, the upper limit is approximately 2000m minus overhead amounts. -Xprof Profiles the running program, and sends profiling data to standard output. This option is provided as a utility that is useful in pro‐ gram development and is not intended to be used in production sys‐ tems. -Xrs Reduces use of operating-system signals by the Java virtual machine (JVM). In a previous release, the Shutdown Hooks facility was added to allow orderly shutdown of a Java application. The intent was to allow user cleanup code (such as closing database connections) to run at shutdown, even if the JVM terminates abruptly. Sun's JVM catches signals to implement shutdown hooks for abnormal JVM termination. The JVM uses SIGHUP, SIGINT, and SIGTERM to initi‐ ate the running of shutdown hooks. The JVM uses a similar mechanism to implement the pre-1.2 feature of dumping thread stacks for debugging purposes. Sun's JVM uses SIGQUIT to perform thread dumps. Applications embedding the JVM frequently need to trap signals like SIGINT or SIGTERM, which can lead to interference with the JVM's own signal handlers. The -Xrs command-line option is available to address this issue. When -Xrs is used on Sun's JVM, the signal masks for SIGINT, SIGTERM, SIGHUP, and SIGQUIT are not changed by the JVM, and signal handlers for these signals are not installed. There are two consequences of specifying -Xrs: o SIGQUIT thread dumps are not available. o User code is responsible for causing shutdown hooks to run, for example by calling System.exit() when the JVM is to be termi‐ nated. -Xssn Set thread stack size. -XX:AllocationPrefetchStyle=n Sets the style of prefetch used during allocation. default=2. -XX:+AggressiveOpts Enables aggressive optimization. -XX:+|-DisableAttachMechanism This option specifies whether tools (such as jmap and jconsole) are allowed to attach to the JVM. By default, this feature is disabled. That is, attaching is enabled. Example usage: java -XX:+DisableAttachMechanism -XXLargePageSizeInBytes=n This option specifies the maximum size for large pages. -XX:MaxGCPauseMillis=n Sets a target for the maximum GC pause time. This is a soft goal, and the JVM will make its best effort to achieve it. -XX:NewSize Sets the size of the young generation (nursery). Sames as -Xmnsize. -XX:ParallelGCThreads=n Sets the number of GC threads in the parallel collectors. -XX:PredictedClassLoadCount=n This option requires that the UnlockExperimentalVMOptions flag be set first. Use the PredictedClassLoadCount flag if your application loads a lot of classes, and especially if class.forName() is used heavily. The recommended value is the number of classes loaded as shown in the output from -verbose:class. Example usage: java -XX:+UnlockExperimentalVMOptions -XX:PredictedClassLoadCount=60013 -XX:+PrintCompilation Prints verbose output from the HotSpot dynamic runtime compiler. -XX:+PrintGCDetails -XX:+PrintGCTimeStamps Prints garbage collection output along with time stamps. -XX:SoftRefLRUPolicyMSPerMB=0 This flag enables aggressive processing of software references. Use this flag if HotSpot GC is impacted by the software reference count. -XX:TLABSize=n Thread local allocation buffers (TLAB) are enabled by default in HotSpot. HotSpot automatically sizes TLABs based on allocation pat‐ terns. The -XX:TLABSize option allows fine-tuning the size of TLABs. -XX:+UseAltSigs The VM uses SIGUSR1 and SIGUSR2 by default, which can sometimes conflict with applications that signal-chain SIGUSR1 and SIGUSR2. The -XX:+UseAltSigs option will cause the VM to use signals other than SIGUSR1 and SIGUSR2 as the default. -XX:+|-UseCompressedOops Enables compressed references in 64-bit JVMs. This option is true by default. -XX:+UseConcMarkSweepGC or -XX:+UseG1GC These flags enable either the Concurrent Mark Sweep (CMS) or the G1 garbage collectors. -XX:+|-UseLargePages Use this flag to enable large page support. Large pages are enabled by default on Solaris. -XX:+UseParallelOldGC Enables the parallel garbage collectors, which are optimized for throughput and average response time. NOTES The -version:release command line option places no restrictions on the complexity of the release specification. However, only a restricted sub‐ set of the possible release specifications represent sound policy and only these are fully supported. These policies are: 1. Any version, represented by not using this option. 2. Any version greater than an arbitrarily precise version-id. For example: "1.6.0_10+" This would utilize any version greater than 1.6.0_10. This is use‐ ful for a case where an interface was introduced (or a bug fixed) in the release specified. 3. A version greater than an arbitrarily precise version-id, bounded by the upper bound of that release family. For example: "1.6.0_10+&1.6*" 4. "Or" expressions of items 2. or 3. above. For example: "1.6.0_10+&1.6* 1.7+" Similar to item 2. this is useful when a change was introduced in a release (1.7) but also made available in updates to previous releases. EXIT STATUS The following exit values are generally returned by the launcher, typi‐ cally when the launcher is called with the wrong arguments, serious errors, or exceptions thrown from the Java Virtual Machine. However, a Java application may choose to return any value using the API call Sys‐ tem.exit(exitValue). o 0: Successful completion o >0: An error occurred SEE ALSO o javac(1) o jdb(1) o javah(1) o jar(1) o The Java Extensions Framework @ http://docs.oracle.com/javase/7/docs/technotes/guides/exten‐ sions/index.html o Security Features @ http://docs.oracle.com/javase/7/docs/technotes/guides/secu‐ rity/index.html. o HotSpot VM Specific Options @ http://java.sun.com/docs/hotspot/VMOptions.html. 20 Mar 2012 java(1)


The creator of this application is James Barciz.
TwitOff! is an application which aims to predict between two Twitter users, given a record of the past N Tweets, who is more likely to say a particular user-created Tweet.
The algorithm used to predict a Twitter user at this stage will be a simple Logistic Regression from the Scikit Learn library.


Class SphericalSurfaceNP
A spherical surface with a non periodic u/v system. It also has no poles. It cannot represent a whole sphere, there must be some part
which is outside the usable area. The center, xAxis, yAxis and zAxis define a coordinate system. The plane defined by (center, xAxis and yAxis)
is the equator plane of the sphere, (center+zAxis) is the north pole. (center-zAxis9 is the south pole, which may not be part of the used area.
The u/v system is the u/v system of the equator area. The point of the sphere for a provided u/v point is the projection of this point from the south pole
to the surface. All circular arcs on the sphere (e.g. planar intersections) are elliptical arcs in the u/v system (or lines, when they pass the north pole)
Inheritance
System.Object
SphericalSurfaceNP
Implements
System.Runtime.Serialization.ISerializable
Inherited Members
System.Object.Equals(System.Object)
System.Object.Equals(System.Object, System.Object)
System.Object.GetHashCode()
System.Object.GetType()
System.Object.MemberwiseClone()
System.Object.ReferenceEquals(System.Object, System.Object)
System.Object.ToString()
Assembly: CADability.dll
Syntax
[Serializable]
public class SphericalSurfaceNP : ISurfaceImpl, ISurface, IOctTreeInsertable, IJsonSerialize, ISerializable
Constructors
|
Improve this Doc
View Source
SphericalSurfaceNP()
Declaration
protected SphericalSurfaceNP()
|
Improve this Doc
View Source
SphericalSurfaceNP(GeoPoint, GeoVector, GeoVector, GeoVector)
Declaration
public SphericalSurfaceNP(GeoPoint center, GeoVector xAxis, GeoVector yAxis, GeoVector zAxis)
Parameters
|
Improve this Doc
View Source
SphericalSurfaceNP(GeoPoint, Double, Boolean, ICurve[])
Constructs a non periodic spherical surface with center
and radius
. The z-axis will be oriented
so that the "south pole" falls into an unused part of the sphere. The edges are orientedCurves
bound the sphere
so that when you walk along the curve (outwardOriented
==true: on the outside, false: on the inside of the sphere), the
used surfaces is on the left side of the curve. The curves must all be connected and define one or more closed loops on the surface.
Declaration
public SphericalSurfaceNP(GeoPoint center, double radius, bool outwardOriented, ICurve[] orientedCurves)
Parameters
| Type |
Name |
Description |
| GeoPoint |
center |
|
| System.Double |
radius |
|
| System.Boolean |
outwardOriented |
true: the center is on the inside, false: the center is on the outside of the surface
|
| ICurve[] |
orientedCurves |
|
|
Improve this Doc
View Source
SphericalSurfaceNP(SerializationInfo, StreamingContext)
Declaration
protected SphericalSurfaceNP(SerializationInfo info, StreamingContext context)
Parameters
| Type |
Name |
Description |
| System.Runtime.Serialization.SerializationInfo |
info |
|
| System.Runtime.Serialization.StreamingContext |
context |
|
Properties
|
Improve this Doc
View Source
IsUPeriodic
Declaration
public override bool IsUPeriodic { get; }
Property Value
| Type |
Description |
| System.Boolean |
|
Overrides
|
Improve this Doc
View Source
IsVPeriodic
Declaration
public override bool IsVPeriodic { get; }
Property Value
| Type |
Description |
| System.Boolean |
|
Overrides
|
Improve this Doc
View Source
UvChangesWithModification
Declaration
public override bool UvChangesWithModification { get; }
Property Value
| Type |
Description |
| System.Boolean |
|
Overrides
Methods
|
Improve this Doc
View Source
Clone()
Declaration
public override ISurface Clone()
Returns
Overrides
|
Improve this Doc
View Source
CopyData(ISurface)
Declaration
public override void CopyData(ISurface CopyFrom)
Parameters
Overrides
|
Improve this Doc
View Source
Derivation2At(GeoPoint2D, out GeoPoint, out GeoVector, out GeoVector, out GeoVector, out GeoVector, out GeoVector)
Declaration
public override void Derivation2At(GeoPoint2D uv, out GeoPoint p, out GeoVector du, out GeoVector dv, out GeoVector duu, out GeoVector dvv, out GeoVector duv)
Parameters
Overrides
|
Improve this Doc
View Source
FixedU(Double, Double, Double)
Declaration
public override ICurve FixedU(double u, double vmin, double vmax)
Parameters
| Type |
Name |
Description |
| System.Double |
u |
|
| System.Double |
vmin |
|
| System.Double |
vmax |
|
Returns
Overrides
|
Improve this Doc
View Source
FixedV(Double, Double, Double)
Declaration
public override ICurve FixedV(double v, double umin, double umax)
Parameters
| Type |
Name |
Description |
| System.Double |
v |
|
| System.Double |
umin |
|
| System.Double |
umax |
|
Returns
Overrides
|
Improve this Doc
View Source
GetExtrema()
Declaration
public override GeoPoint2D[] GetExtrema()
Returns
Overrides
|
Improve this Doc
View Source
GetImplicitPolynomial()
Declaration
public override Polynom GetImplicitPolynomial()
Returns
Overrides
|
Improve this Doc
View Source
GetModified(ModOp)
Declaration
public override ISurface GetModified(ModOp m)
Parameters
| Type |
Name |
Description |
| ModOp |
m |
|
Returns
Overrides
|
Improve this Doc
View Source
GetNaturalBounds(out Double, out Double, out Double, out Double)
Declaration
public override void GetNaturalBounds(out double umin, out double umax, out double vmin, out double vmax)
Parameters
| Type |
Name |
Description |
| System.Double |
umin |
|
| System.Double |
umax |
|
| System.Double |
vmin |
|
| System.Double |
vmax |
|
Overrides
|
Improve this Doc
View Source
GetProjectedCurve(ICurve, Double)
Declaration
public override ICurve2D GetProjectedCurve(ICurve curve, double precision)
Parameters
| Type |
Name |
Description |
| ICurve |
curve |
|
| System.Double |
precision |
|
Returns
Overrides
|
Improve this Doc
View Source
GetPropertyEntry(IFrame)
Declaration
public override IPropertyEntry GetPropertyEntry(IFrame frame)
Parameters
| Type |
Name |
Description |
| IFrame |
frame |
|
Returns
Overrides
|
Improve this Doc
View Source
PointAt(GeoPoint2D)
Declaration
public override GeoPoint PointAt(GeoPoint2D uv)
Parameters
Returns
Overrides
|
Improve this Doc
View Source
PositionOf(GeoPoint)
Declaration
public override GeoPoint2D PositionOf(GeoPoint p)
Parameters
Returns
Overrides
|
Improve this Doc
View Source
ReverseOrientation()
Declaration
public override ModOp2D ReverseOrientation()
Returns
Overrides
|
Improve this Doc
View Source
SameGeometry(BoundingRect, ISurface, BoundingRect, Double, out ModOp2D)
Declaration
public override bool SameGeometry(BoundingRect thisBounds, ISurface other, BoundingRect otherBounds, double precision, out ModOp2D firstToSecond)
Parameters
Returns
| Type |
Description |
| System.Boolean |
|
Overrides
|
Improve this Doc
View Source
UDirection(GeoPoint2D)
Declaration
public override GeoVector UDirection(GeoPoint2D uv)
Parameters
Returns
Overrides
|
Improve this Doc
View Source
VDirection(GeoPoint2D)
Declaration
public override GeoVector VDirection(GeoPoint2D uv)
Parameters
Returns
Overrides
Explicit Interface Implementations
|
Improve this Doc
View Source
IJsonSerialize.GetObjectData(IJsonWriteData)
Declaration
void IJsonSerialize.GetObjectData(IJsonWriteData data)
Parameters
|
Improve this Doc
View Source
IJsonSerialize.SetObjectData(IJsonReadData)
Declaration
void IJsonSerialize.SetObjectData(IJsonReadData data)
Parameters
|
Improve this Doc
View Source
ISerializable.GetObjectData(SerializationInfo, StreamingContext)
Declaration
void ISerializable.GetObjectData(SerializationInfo info, StreamingContext context)
Parameters
| Type |
Name |
Description |
| System.Runtime.Serialization.SerializationInfo |
info |
|
| System.Runtime.Serialization.StreamingContext |
context |
|
Implements
System.Runtime.Serialization.ISerializable