| Package | Description |
|---|---|
| org.apache.commons.collections |
This package contains the interfaces and utilities shared across all the subpackages of this component.
|
| org.apache.commons.collections.bag | |
| org.apache.commons.collections.buffer |
This package contains implementations of the
Buffer interface. |
| org.apache.commons.collections.collection |
This package contains implementations of the
Collection interface. |
| org.apache.commons.collections.functors |
This package contains implementations of the
Closure ,
Predicate ,
Transformer and
Factory interfaces. |
| org.apache.commons.collections.iterators |
This package contains implementations of the
Iterator interface. |
| org.apache.commons.collections.list |
This package contains implementations of the
List interface. |
| org.apache.commons.collections.map | |
| org.apache.commons.collections.set |
| Modifier and Type | Method and Description |
|---|---|
static Predicate |
PredicateUtils.allPredicate(Collection predicates)
Create a new Predicate that returns true only if all of the specified
predicates are true.
|
static Predicate |
PredicateUtils.allPredicate(Predicate[] predicates)
Create a new Predicate that returns true only if all of the specified
predicates are true.
|
static Predicate |
PredicateUtils.andPredicate(Predicate predicate1,
Predicate predicate2)
Create a new Predicate that returns true only if both of the specified
predicates are true.
|
static Predicate |
PredicateUtils.anyPredicate(Collection predicates)
Create a new Predicate that returns true if any of the specified
predicates are true.
|
static Predicate |
PredicateUtils.anyPredicate(Predicate[] predicates)
Create a new Predicate that returns true if any of the specified
predicates are true.
|
static Predicate |
PredicateUtils.asPredicate(Transformer transformer)
Create a new Predicate that wraps a Transformer.
|
static Predicate |
PredicateUtils.eitherPredicate(Predicate predicate1,
Predicate predicate2)
Create a new Predicate that returns true if one, but not both, of the
specified predicates are true.
|
static Predicate |
PredicateUtils.equalPredicate(Object value)
Creates a Predicate that checks if the input object is equal to the
specified object using equals().
|
static Predicate |
PredicateUtils.exceptionPredicate()
Gets a Predicate that always throws an exception.
|
static Predicate |
PredicateUtils.falsePredicate()
Gets a Predicate that always returns false.
|
static Predicate |
PredicateUtils.identityPredicate(Object value)
Creates a Predicate that checks if the input object is equal to the
specified object by identity.
|
static Predicate |
PredicateUtils.instanceofPredicate(Class type)
Creates a Predicate that checks if the object passed in is of
a particular type, using instanceof.
|
static Predicate |
PredicateUtils.invokerPredicate(String methodName)
Creates a Predicate that invokes a method on the input object.
|
static Predicate |
PredicateUtils.invokerPredicate(String methodName,
Class[] paramTypes,
Object[] args)
Creates a Predicate that invokes a method on the input object.
|
static Predicate |
PredicateUtils.neitherPredicate(Predicate predicate1,
Predicate predicate2)
Create a new Predicate that returns true if neither of the specified
predicates are true.
|
static Predicate |
PredicateUtils.nonePredicate(Collection predicates)
Create a new Predicate that returns true if none of the specified
predicates are true.
|
static Predicate |
PredicateUtils.nonePredicate(Predicate[] predicates)
Create a new Predicate that returns true if none of the specified
predicates are true.
|
static Predicate |
PredicateUtils.notNullPredicate()
Gets a Predicate that checks if the input object passed in is not null.
|
static Predicate |
PredicateUtils.notPredicate(Predicate predicate)
Create a new Predicate that returns true if the specified predicate
returns false and vice versa.
|
static Predicate |
PredicateUtils.nullIsExceptionPredicate(Predicate predicate)
Gets a Predicate that throws an exception if the input object is null,
otherwise it calls the specified Predicate.
|
static Predicate |
PredicateUtils.nullIsFalsePredicate(Predicate predicate)
Gets a Predicate that returns false if the input object is null, otherwise
it calls the specified Predicate.
|
static Predicate |
PredicateUtils.nullIsTruePredicate(Predicate predicate)
Gets a Predicate that returns true if the input object is null, otherwise
it calls the specified Predicate.
|
static Predicate |
PredicateUtils.nullPredicate()
Gets a Predicate that checks if the input object passed in is null.
|
static Predicate |
PredicateUtils.onePredicate(Collection predicates)
Create a new Predicate that returns true if only one of the specified
predicates are true.
|
static Predicate |
PredicateUtils.onePredicate(Predicate[] predicates)
Create a new Predicate that returns true if only one of the specified
predicates are true.
|
static Predicate |
PredicateUtils.orPredicate(Predicate predicate1,
Predicate predicate2)
Create a new Predicate that returns true if either of the specified
predicates are true.
|
static Predicate |
PredicateUtils.transformedPredicate(Transformer transformer,
Predicate predicate)
Creates a predicate that transforms the input object before passing it
to the predicate.
|
static Predicate |
PredicateUtils.truePredicate()
Gets a Predicate that always returns true.
|
static Predicate |
PredicateUtils.uniquePredicate()
Creates a Predicate that returns true the first time an object is
encountered, and false if the same object is received
again.
|
| Modifier and Type | Method and Description |
|---|---|
static Predicate |
PredicateUtils.allPredicate(Predicate[] predicates)
Create a new Predicate that returns true only if all of the specified
predicates are true.
|
static Predicate |
PredicateUtils.andPredicate(Predicate predicate1,
Predicate predicate2)
Create a new Predicate that returns true only if both of the specified
predicates are true.
|
static Predicate |
PredicateUtils.anyPredicate(Predicate[] predicates)
Create a new Predicate that returns true if any of the specified
predicates are true.
|
static Transformer |
TransformerUtils.asTransformer(Predicate predicate)
Creates a Transformer that calls a Predicate each time the transformer is used.
|
static int |
CollectionUtils.countMatches(Collection inputCollection,
Predicate predicate)
Counts the number of elements in the input collection that match the predicate.
|
static Closure |
ClosureUtils.doWhileClosure(Closure closure,
Predicate predicate)
Creates a Closure that will call the closure once and then repeatedly
until the predicate returns false.
|
static Predicate |
PredicateUtils.eitherPredicate(Predicate predicate1,
Predicate predicate2)
Create a new Predicate that returns true if one, but not both, of the
specified predicates are true.
|
static boolean |
CollectionUtils.exists(Collection collection,
Predicate predicate)
Answers true if a predicate is true for at least one element of a collection.
|
static void |
CollectionUtils.filter(Collection collection,
Predicate predicate)
Filter the collection by applying a Predicate to each element.
|
static Iterator |
IteratorUtils.filteredIterator(Iterator iterator,
Predicate predicate)
Gets an iterator that filters another iterator.
|
static ListIterator |
IteratorUtils.filteredListIterator(ListIterator listIterator,
Predicate predicate)
Gets a list iterator that filters another list iterator.
|
static Object |
CollectionUtils.find(Collection collection,
Predicate predicate)
Finds the first element in the given collection which matches the given predicate.
|
static Closure |
ClosureUtils.ifClosure(Predicate predicate,
Closure trueClosure)
Create a new Closure that calls another closure based on the
result of the specified predicate.
|
static Closure |
ClosureUtils.ifClosure(Predicate predicate,
Closure trueClosure,
Closure falseClosure)
Create a new Closure that calls one of two closures depending
on the specified predicate.
|
static Predicate |
PredicateUtils.neitherPredicate(Predicate predicate1,
Predicate predicate2)
Create a new Predicate that returns true if neither of the specified
predicates are true.
|
static Predicate |
PredicateUtils.nonePredicate(Predicate[] predicates)
Create a new Predicate that returns true if none of the specified
predicates are true.
|
static Predicate |
PredicateUtils.notPredicate(Predicate predicate)
Create a new Predicate that returns true if the specified predicate
returns false and vice versa.
|
static Predicate |
PredicateUtils.nullIsExceptionPredicate(Predicate predicate)
Gets a Predicate that throws an exception if the input object is null,
otherwise it calls the specified Predicate.
|
static Predicate |
PredicateUtils.nullIsFalsePredicate(Predicate predicate)
Gets a Predicate that returns false if the input object is null, otherwise
it calls the specified Predicate.
|
static Predicate |
PredicateUtils.nullIsTruePredicate(Predicate predicate)
Gets a Predicate that returns true if the input object is null, otherwise
it calls the specified Predicate.
|
static Predicate |
PredicateUtils.onePredicate(Predicate[] predicates)
Create a new Predicate that returns true if only one of the specified
predicates are true.
|
static Predicate |
PredicateUtils.orPredicate(Predicate predicate1,
Predicate predicate2)
Create a new Predicate that returns true if either of the specified
predicates are true.
|
static Bag |
BagUtils.predicatedBag(Bag bag,
Predicate predicate)
Returns a predicated (validating) bag backed by the given bag.
|
static Buffer |
BufferUtils.predicatedBuffer(Buffer buffer,
Predicate predicate)
Returns a predicated (validating) buffer backed by the given buffer.
|
static Collection |
CollectionUtils.predicatedCollection(Collection collection,
Predicate predicate)
Returns a predicated (validating) collection backed by the given collection.
|
static List |
ListUtils.predicatedList(List list,
Predicate predicate)
Returns a predicated (validating) list backed by the given list.
|
static Map |
MapUtils.predicatedMap(Map map,
Predicate keyPred,
Predicate valuePred)
Returns a predicated (validating) map backed by the given map.
|
static Set |
SetUtils.predicatedSet(Set set,
Predicate predicate)
Returns a predicated (validating) set backed by the given set.
|
static SortedBag |
BagUtils.predicatedSortedBag(SortedBag bag,
Predicate predicate)
Returns a predicated (validating) sorted bag backed by the given sorted bag.
|
static SortedMap |
MapUtils.predicatedSortedMap(SortedMap map,
Predicate keyPred,
Predicate valuePred)
Returns a predicated (validating) sorted map backed by the given map.
|
static SortedSet |
SetUtils.predicatedSortedSet(SortedSet set,
Predicate predicate)
Returns a predicated (validating) sorted set backed by the given sorted set.
|
static Collection |
CollectionUtils.select(Collection inputCollection,
Predicate predicate)
Selects all elements from input collection which match the given predicate
into an output collection.
|
static void |
CollectionUtils.select(Collection inputCollection,
Predicate predicate,
Collection outputCollection)
Selects all elements from input collection which match the given predicate
and adds them to outputCollection.
|
static Collection |
CollectionUtils.selectRejected(Collection inputCollection,
Predicate predicate)
Selects all elements from inputCollection which don't match the given predicate
into an output collection.
|
static void |
CollectionUtils.selectRejected(Collection inputCollection,
Predicate predicate,
Collection outputCollection)
Selects all elements from inputCollection which don't match the given predicate
and adds them to outputCollection.
|
static Closure |
ClosureUtils.switchClosure(Predicate[] predicates,
Closure[] closures)
Create a new Closure that calls one of the closures depending
on the predicates.
|
static Closure |
ClosureUtils.switchClosure(Predicate[] predicates,
Closure[] closures,
Closure defaultClosure)
Create a new Closure that calls one of the closures depending
on the predicates.
|
static Transformer |
TransformerUtils.switchTransformer(Predicate[] predicates,
Transformer[] transformers)
Create a new Transformer that calls one of the transformers depending
on the predicates.
|
static Transformer |
TransformerUtils.switchTransformer(Predicate[] predicates,
Transformer[] transformers,
Transformer defaultTransformer)
Create a new Transformer that calls one of the transformers depending
on the predicates.
|
static Transformer |
TransformerUtils.switchTransformer(Predicate predicate,
Transformer trueTransformer,
Transformer falseTransformer)
Create a new Transformer that calls one of two transformers depending
on the specified predicate.
|
static Predicate |
PredicateUtils.transformedPredicate(Transformer transformer,
Predicate predicate)
Creates a predicate that transforms the input object before passing it
to the predicate.
|
static Closure |
ClosureUtils.whileClosure(Predicate predicate,
Closure closure)
Creates a Closure that will call the closure repeatedly until the
predicate returns false.
|
| Modifier and Type | Method and Description |
|---|---|
static Bag |
PredicatedBag.decorate(Bag bag,
Predicate predicate)
Factory method to create a predicated (validating) bag.
|
static SortedBag |
PredicatedSortedBag.decorate(SortedBag bag,
Predicate predicate)
Factory method to create a predicated (validating) bag.
|
| Constructor and Description |
|---|
PredicatedBag(Bag bag,
Predicate predicate)
Constructor that wraps (not copies).
|
PredicatedSortedBag(SortedBag bag,
Predicate predicate)
Constructor that wraps (not copies).
|
| Modifier and Type | Method and Description |
|---|---|
static Buffer |
PredicatedBuffer.decorate(Buffer buffer,
Predicate predicate)
Factory method to create a predicated (validating) buffer.
|
| Constructor and Description |
|---|
PredicatedBuffer(Buffer buffer,
Predicate predicate)
Constructor that wraps (not copies).
|
| Modifier and Type | Field and Description |
|---|---|
protected Predicate |
PredicatedCollection.predicate
The predicate to use
|
| Modifier and Type | Method and Description |
|---|---|
static Collection |
PredicatedCollection.decorate(Collection coll,
Predicate predicate)
Factory method to create a predicated (validating) collection.
|
| Constructor and Description |
|---|
PredicatedCollection(Collection coll,
Predicate predicate)
Constructor that wraps (not copies).
|
| Modifier and Type | Interface and Description |
|---|---|
interface |
PredicateDecorator
Defines a predicate that decorates one or more other predicates.
|
| Modifier and Type | Class and Description |
|---|---|
class |
AllPredicate
Predicate implementation that returns true if all the
predicates return true.
|
class |
AndPredicate
Predicate implementation that returns true if both the predicates return true.
|
class |
AnyPredicate
Predicate implementation that returns true if any of the
predicates return true.
|
class |
EqualPredicate
Predicate implementation that returns true if the input is the same object
as the one stored in this predicate by equals.
|
class |
ExceptionPredicate
Predicate implementation that always throws an exception.
|
class |
FalsePredicate
Predicate implementation that always returns false.
|
class |
IdentityPredicate
Predicate implementation that returns true if the input is the same object
as the one stored in this predicate.
|
class |
InstanceofPredicate
Predicate implementation that returns true if the input is an instanceof
the type stored in this predicate.
|
class |
NonePredicate
Predicate implementation that returns true if none of the
predicates return true.
|
class |
NotNullPredicate
Predicate implementation that returns true if the input is not null.
|
class |
NotPredicate
Predicate implementation that returns the opposite of the decorated predicate.
|
class |
NullIsExceptionPredicate
Predicate implementation that throws an exception if the input is null.
|
class |
NullIsFalsePredicate
Predicate implementation that returns false if the input is null.
|
class |
NullIsTruePredicate
Predicate implementation that returns true if the input is null.
|
class |
NullPredicate
Predicate implementation that returns true if the input is null.
|
class |
OnePredicate
Predicate implementation that returns true if only one of the
predicates return true.
|
class |
OrPredicate
Predicate implementation that returns true if either of the predicates return true.
|
class |
TransformedPredicate
Predicate implementation that transforms the given object before invoking
another
Predicate . |
class |
TransformerPredicate
Predicate implementation that returns the result of a transformer.
|
class |
TruePredicate
Predicate implementation that always returns true.
|
class |
UniquePredicate
Predicate implementation that returns true the first time an object is
passed into the predicate.
|
| Modifier and Type | Field and Description |
|---|---|
static Predicate |
FalsePredicate.INSTANCE
Singleton predicate instance
|
static Predicate |
TruePredicate.INSTANCE
Singleton predicate instance
|
static Predicate |
ExceptionPredicate.INSTANCE
Singleton predicate instance
|
static Predicate |
NotNullPredicate.INSTANCE
Singleton predicate instance
|
static Predicate |
NullPredicate.INSTANCE
Singleton predicate instance
|
| Modifier and Type | Method and Description |
|---|---|
static Predicate |
FalsePredicate.getInstance()
Factory returning the singleton instance.
|
static Predicate |
TruePredicate.getInstance()
Factory returning the singleton instance.
|
static Predicate |
UniquePredicate.getInstance()
Factory to create the predicate.
|
static Predicate |
ExceptionPredicate.getInstance()
Factory returning the singleton instance.
|
static Predicate |
NotNullPredicate.getInstance()
Factory returning the singleton instance.
|
static Predicate |
NullPredicate.getInstance()
Factory returning the singleton instance.
|
static Predicate |
InstanceofPredicate.getInstance(Class type)
Factory to create the identity predicate.
|
static Predicate |
AnyPredicate.getInstance(Collection predicates)
Factory to create the predicate.
|
static Predicate |
NonePredicate.getInstance(Collection predicates)
Factory to create the predicate.
|
static Predicate |
AllPredicate.getInstance(Collection predicates)
Factory to create the predicate.
|
static Predicate |
OnePredicate.getInstance(Collection predicates)
Factory to create the predicate.
|
static Predicate |
EqualPredicate.getInstance(Object object)
Factory to create the identity predicate.
|
static Predicate |
IdentityPredicate.getInstance(Object object)
Factory to create the identity predicate.
|
static Predicate |
NullIsExceptionPredicate.getInstance(Predicate predicate)
Factory to create the null exception predicate.
|
static Predicate |
NotPredicate.getInstance(Predicate predicate)
Factory to create the not predicate.
|
static Predicate |
NullIsTruePredicate.getInstance(Predicate predicate)
Factory to create the null true predicate.
|
static Predicate |
NullIsFalsePredicate.getInstance(Predicate predicate)
Factory to create the null false predicate.
|
static Predicate |
AnyPredicate.getInstance(Predicate[] predicates)
Factory to create the predicate.
|
static Predicate |
NonePredicate.getInstance(Predicate[] predicates)
Factory to create the predicate.
|
static Predicate |
AllPredicate.getInstance(Predicate[] predicates)
Factory to create the predicate.
|
static Predicate |
OnePredicate.getInstance(Predicate[] predicates)
Factory to create the predicate.
|
static Predicate |
AndPredicate.getInstance(Predicate predicate1,
Predicate predicate2)
Factory to create the predicate.
|
static Predicate |
OrPredicate.getInstance(Predicate predicate1,
Predicate predicate2)
Factory to create the predicate.
|
static Predicate |
TransformerPredicate.getInstance(Transformer transformer)
Factory to create the predicate.
|
static Predicate |
TransformedPredicate.getInstance(Transformer transformer,
Predicate predicate)
Factory to create the predicate.
|
Predicate |
WhileClosure.getPredicate()
Gets the predicate in use.
|
Predicate |
IfClosure.getPredicate()
Gets the predicate.
|
Predicate |
PredicateTransformer.getPredicate()
Gets the predicate.
|
Predicate[] |
NullIsExceptionPredicate.getPredicates()
Gets the predicate being decorated.
|
Predicate[] |
AndPredicate.getPredicates()
Gets the two predicates being decorated as an array.
|
Predicate[] |
AnyPredicate.getPredicates()
Gets the predicates, do not modify the array.
|
Predicate[] |
PredicateDecorator.getPredicates()
Gets the predicates being decorated as an array.
|
Predicate[] |
SwitchClosure.getPredicates()
Gets the predicates, do not modify the array.
|
Predicate[] |
SwitchTransformer.getPredicates()
Gets the predicates, do not modify the array.
|
Predicate[] |
NotPredicate.getPredicates()
Gets the predicate being decorated.
|
Predicate[] |
OrPredicate.getPredicates()
Gets the two predicates being decorated as an array.
|
Predicate[] |
NonePredicate.getPredicates()
Gets the predicates, do not modify the array.
|
Predicate[] |
AllPredicate.getPredicates()
Gets the predicates, do not modify the array.
|
Predicate[] |
OnePredicate.getPredicates()
Gets the predicates, do not modify the array.
|
Predicate[] |
NullIsTruePredicate.getPredicates()
Gets the predicate being decorated.
|
Predicate[] |
TransformedPredicate.getPredicates()
Gets the predicate being decorated.
|
Predicate[] |
NullIsFalsePredicate.getPredicates()
Gets the predicate being decorated.
|
| Modifier and Type | Method and Description |
|---|---|
static Predicate |
NullIsExceptionPredicate.getInstance(Predicate predicate)
Factory to create the null exception predicate.
|
static Predicate |
NotPredicate.getInstance(Predicate predicate)
Factory to create the not predicate.
|
static Transformer |
PredicateTransformer.getInstance(Predicate predicate)
Factory method that performs validation.
|
static Predicate |
NullIsTruePredicate.getInstance(Predicate predicate)
Factory to create the null true predicate.
|
static Predicate |
NullIsFalsePredicate.getInstance(Predicate predicate)
Factory to create the null false predicate.
|
static Predicate |
AnyPredicate.getInstance(Predicate[] predicates)
Factory to create the predicate.
|
static Predicate |
NonePredicate.getInstance(Predicate[] predicates)
Factory to create the predicate.
|
static Predicate |
AllPredicate.getInstance(Predicate[] predicates)
Factory to create the predicate.
|
static Predicate |
OnePredicate.getInstance(Predicate[] predicates)
Factory to create the predicate.
|
static Closure |
SwitchClosure.getInstance(Predicate[] predicates,
Closure[] closures,
Closure defaultClosure)
Factory method that performs validation and copies the parameter arrays.
|
static Transformer |
SwitchTransformer.getInstance(Predicate[] predicates,
Transformer[] transformers,
Transformer defaultTransformer)
Factory method that performs validation and copies the parameter arrays.
|
static Closure |
IfClosure.getInstance(Predicate predicate,
Closure trueClosure)
Factory method that performs validation.
|
static Closure |
WhileClosure.getInstance(Predicate predicate,
Closure closure,
boolean doLoop)
Factory method that performs validation.
|
static Closure |
IfClosure.getInstance(Predicate predicate,
Closure trueClosure,
Closure falseClosure)
Factory method that performs validation.
|
static Predicate |
AndPredicate.getInstance(Predicate predicate1,
Predicate predicate2)
Factory to create the predicate.
|
static Predicate |
OrPredicate.getInstance(Predicate predicate1,
Predicate predicate2)
Factory to create the predicate.
|
static Predicate |
TransformedPredicate.getInstance(Transformer transformer,
Predicate predicate)
Factory to create the predicate.
|
| Constructor and Description |
|---|
AllPredicate(Predicate[] predicates)
Constructor that performs no validation.
|
AndPredicate(Predicate predicate1,
Predicate predicate2)
Constructor that performs no validation.
|
AnyPredicate(Predicate[] predicates)
Constructor that performs no validation.
|
IfClosure(Predicate predicate,
Closure trueClosure)
Constructor that performs no validation.
|
IfClosure(Predicate predicate,
Closure trueClosure,
Closure falseClosure)
Constructor that performs no validation.
|
NonePredicate(Predicate[] predicates)
Constructor that performs no validation.
|
NotPredicate(Predicate predicate)
Constructor that performs no validation.
|
NullIsExceptionPredicate(Predicate predicate)
Constructor that performs no validation.
|
NullIsFalsePredicate(Predicate predicate)
Constructor that performs no validation.
|
NullIsTruePredicate(Predicate predicate)
Constructor that performs no validation.
|
OnePredicate(Predicate[] predicates)
Constructor that performs no validation.
|
OrPredicate(Predicate predicate1,
Predicate predicate2)
Constructor that performs no validation.
|
PredicateTransformer(Predicate predicate)
Constructor that performs no validation.
|
SwitchClosure(Predicate[] predicates,
Closure[] closures,
Closure defaultClosure)
Constructor that performs no validation.
|
SwitchTransformer(Predicate[] predicates,
Transformer[] transformers,
Transformer defaultTransformer)
Constructor that performs no validation.
|
TransformedPredicate(Transformer transformer,
Predicate predicate)
Constructor that performs no validation.
|
WhileClosure(Predicate predicate,
Closure closure,
boolean doLoop)
Constructor that performs no validation.
|
| Modifier and Type | Method and Description |
|---|---|
Predicate |
FilterIterator.getPredicate()
Gets the predicate this iterator is using.
|
Predicate |
FilterListIterator.getPredicate()
Gets the predicate this iterator is using.
|
| Modifier and Type | Method and Description |
|---|---|
void |
FilterIterator.setPredicate(Predicate predicate)
Sets the predicate this the iterator to use.
|
void |
FilterListIterator.setPredicate(Predicate predicate)
Sets the predicate this the iterator to use.
|
| Constructor and Description |
|---|
FilterIterator(Iterator iterator,
Predicate predicate)
Constructs a new
FilterIterator that will use the
given iterator and predicate. |
FilterListIterator(ListIterator iterator,
Predicate predicate)
Constructs a new
FilterListIterator . |
FilterListIterator(Predicate predicate)
Constructs a new
FilterListIterator that will not function
until setListIterator is invoked. |
| Modifier and Type | Method and Description |
|---|---|
static List |
PredicatedList.decorate(List list,
Predicate predicate)
Factory method to create a predicated (validating) list.
|
| Constructor and Description |
|---|
PredicatedList(List list,
Predicate predicate)
Constructor that wraps (not copies).
|
| Modifier and Type | Field and Description |
|---|---|
protected Predicate |
PredicatedMap.keyPredicate
The key predicate to use
|
protected Predicate |
PredicatedMap.valuePredicate
The value predicate to use
|
| Modifier and Type | Method and Description |
|---|---|
static Map |
PredicatedMap.decorate(Map map,
Predicate keyPredicate,
Predicate valuePredicate)
Factory method to create a predicated (validating) map.
|
static SortedMap |
PredicatedSortedMap.decorate(SortedMap map,
Predicate keyPredicate,
Predicate valuePredicate)
Factory method to create a predicated (validating) sorted map.
|
| Constructor and Description |
|---|
PredicatedMap(Map map,
Predicate keyPredicate,
Predicate valuePredicate)
Constructor that wraps (not copies).
|
PredicatedSortedMap(SortedMap map,
Predicate keyPredicate,
Predicate valuePredicate)
Constructor that wraps (not copies).
|
| Modifier and Type | Method and Description |
|---|---|
static Set |
PredicatedSet.decorate(Set set,
Predicate predicate)
Factory method to create a predicated (validating) set.
|
static SortedSet |
PredicatedSortedSet.decorate(SortedSet set,
Predicate predicate)
Factory method to create a predicated (validating) sorted set.
|
| Constructor and Description |
|---|
PredicatedSet(Set set,
Predicate predicate)
Constructor that wraps (not copies).
|
PredicatedSortedSet(SortedSet set,
Predicate predicate)
Constructor that wraps (not copies).
|
Copyright © 2001–2015 The Apache Software Foundation. All rights reserved.


const val EXTRA_WRITE_DATA: String
Intent extra key for a boolean indicating whether database writes should be made in this activity. This is useful if we want to make database writes in the calling activity.
If this is not specified when starting the activity, the value of DEFAULT_WRITE_DATA will be used.


Home > JavaScript Questions > What will be the output of the following code:
The code will not display the values 0, 1, 2, 3, and 4 as might be expected;
rather, it will display 5, 5, 5, 5, and 5.
The reason for this is that each function executed within the loop will be executed after the
entire loop has completed and all will therefore reference the last value stored in i,
which was 5.
Closures can be used to prevent this problem by creating a unique scope for each iteration,
storing each unique value of the variable within its scope, as follows:


Id: ef74400
Branch: master
Date: 05:39 - 2020-08-10
By: @fredrikj31
Messages: Added support for multiple rooms


Here’s how to make plots for a simulation of 1rx1 with 1000ps windows:
ssh node6 cd /data/people/mlerner mkdir correlated_dynamics cd correlated_dynamics mkdir ptraj_files mkdir ptraj_files/images mkdir ptraj_files/1rx1
write_ptraj_input_files.py –strip-water –strip-hydros –input-dir=. –mdcrd=1rx1.trj –structure-name=1rx1 –start=100 –stop=1000 –window-size=200 –window-spacing=100
# # Standard defaults are windowsize of 1000ps (1NS) and windowspacing of 100ps. # write_ptraj_input_files.py --strip-water --strip-hydros --input-dir=. --mdcrd=1rx1.mdcrd --structure-name=1rx1 --start=500 --stop=5500 --ps=5 --window-size=1000 --window-spacing=500 nohup run_ptraj.py --input-dir=. --prmtop=1rx1.prmtop --structure=1rx1& cd ptraj_files/1rx1 bzip2 *.dat #* cd ../..
nohup do_correlated_md_analysis.py --output-dir=ptraj_files --structure-name=1rx1 --start=500 --stop=5500 --window-size=1000 --non-ca-resis=160,161-175&
nohup make_correlated_dynamics_plots.py --structure-name=1rx1 --start=500 --stop=5500 --window-size=1000 --window-spacing=500& make_movies.py --structure-name=1rx1 --plot-types=ca,avg,max,min,abs,straight,mainheavy cd ptraj_files tar cvf 1rx1_100ps_movies.tar 1rx1BigAnimatedMovies.html images/animated_* mv 1rx1_100ps_movies.tar ~ cd ..
The scripts have many options, and we’ll describe a standard setup here. You’ll need a couple of things before you begin:
- An MD trajectory from sander. In this example, it will be called 1rx1.mdcrd.
- The paramater/topology file corresponding to that trajectory. Ours will be called 1rx1.prmtop
- Sufficient disk space and processor power. This can easily eat up several gigs of disk space, and we usually run things with 2G of memory.
First of all, we need to set up a directory structure to store our files. We need a main directory which will contain all of our results (correlated_dynamics). Inside that, we need to store the images and the data. We’ll store images and data in ptraj_files. Images will go in ptraj_files/images. We’ll have different directories for each different structure that we study. These examples will be for the DHFR structure 1RX1, and we’ll store data in ptraj_files/1rx1. Assuming we do all of this on node6 of our cluster, here’s how to set up the directories:
ssh node6 cd /data/people/mlerner mkdir correlated_dynamics cd correlated_dynamics mkdir ptraj_files mkdir ptraj_files/images mkdir ptraj_files/1rx1
We use ptraj to calculate the correlation matrices. So, we need to write out lots of ptraj input files and then we need to run them. This sets up all of the calculations that we’ll use, so it’s important to get the options right.
- structure-name should be the same thing you specified earlier. 1rx1 in our case.
- input-dir is the path to the directory that contains the trajectory and parameter/topology file.
- strip-water and strip-hydros tell us whether or not to include waters and hydrogens in our calculations. Waters are almost never worth including. Hydrogens can be interesting, but it’s very easy to run out of memory on reasonably-sized systems, so we typically exclude them.
- ps tells us how often (in picoseconds) frames were written to the mdcrd file.
- start and stop tell us (in ps) when to start and stop the windows. window-size tells us how long each window should be (in ps). window-spacing tells us how often to write out windows (in ps). The defaults are to write out windows of length 1ns (1000ps) every 100ps.
- There are several other options, including the ability to insert user-specified commands directly to the ptraj input files. Please use the help option for more information.
Finally, these files can take up a lot of disk space. We typically compress things with bzip2. The scripts are smart enough to decompress things on the fly later on.
so, here’s how we set up and run ptraj:
# # Standard defaults are windowsize of 1000ps (1NS) and windowspacing of 100ps. # write_ptraj_input_files.py --strip-water --strip-hydros --input-dir=. --mdcrd=1rx1.mdcrd --structure-name=1rx1 --start=500 --stop=5500 --ps=5 --window-size=1000 --window-spacing=100 nohup run_ptraj.py --input-dir=. --prmtop=1rx1.prmtop --structure=1rx1& cd ptraj_files/1rx1 bzip2 *.dat cd ../..
Ptraj calculates correlations between each atom. We also want to calculate the following quantities:
- Correlations between alpha-carbons.
- Correlations between main-chain heavy atoms
- The following quantities on a per-residue basis:
- average
- maximum
- minimum
- largest absolute value
If hydrogens are included, we will also calculate correlations between potential hydrogen-bond donors and acceptors.
Since we are calculating alpha-carbon correlations, it is important to provide a list of residues that do not contain alpha carbons (non-ca-resis). In this case, 160 is our cofactor and 161-175 are our counter-ions. We could have excluded these during the write_ptraj_input_files.py command, but chose not to.
All of our files follow a standard naming convention, so telling each successive command the start, stop, spacing and size of the windows is enough to make sure that the correct files are read in.
nohup do_correlated_md_analysis.py --input-dir=. --structure-name=1rx1 --start=500 --stop=5500 --window-size=1000 --non-ca-resis=160,161-175&
Now we have calculated everything and it’s time to make the plots. make_correlated_dynamics_plots.py makes the individual plots and has many different options (again, use help to list them all). Here is a standard run.
- we specify the structure and the details about the windows as before.
- plot-types is a comma-separated list of plot types. The standard ones that we use are ca,avg,max,min,abs,straight,mainheavy and the command-line help will detail other options for you. Since we don’t specify this on the command-line below, it will default to the standard options.
nohup make_correlated_dynamics_plots.py --input-dir=. --structure-name=1rx1 --start=500 --stop=5500 --window-size=1000&
That produces plots of each of the individual windows. It’s worth examining these on their own. However, it’s often a lot more interesting to look at movies of these all pasted together. The convert program is used to do this. If it’s not installed, it’s easy to install on OS X, Linux and Windows. make_movies.py calls convert appropriately:
make_movies.py --structure-name=1rx1 --plot-types=ca,avg,max,min,abs,straight,mainheavy
Finally, we may wish to move the movies to another machine for viewing. The movies are in the images subdirectory. make_movies.py also generates an html file that shows all of the movies with thumbnails. Here’s how to collect the movies and html file:
cd ptraj_files tar cvf 1rx1_100ps_movies.tar 1rx1BigAnimatedMovies.html images/animated_* mv 1rx1_100ps_movies.tar ~ cd ..
make_correlated_dynamics_plots.py has several useful options.
- Residues of interest can be marked with mark-resis. This is useful in several cases, including:
- marking loops, helices or other regions of interest
- marking every 10th residue to show a grid (especially useful for orientation in the main-chain heavy plots)
- you can select different color maps with the cmap option.
Please read through the command-line help for a detailed, up-to-date explanation.
The bzip2’d files are very small. However, especially when dealing with main-chain heavy atoms, they can be quite slow. numpy has an internal format that is much faster to read. You can use convert_to_numpy_format.py to covert your output to this format. It looses a small amount of precision, but that seems to be completely negligible. All of the correlated-dynamics scripts will deal transparently with any combination of .dat, .numpy and .bz2 files. You specify things as above and it’ll figure out how to read .dat or .numpy or .numpy.bz2 without any trouble.
The movie files are created as animated GIFs. This has the advantage that they can be played anywhere. However, they can be quite large. Sophisticated tools such as mencoder (http://www.mplayerhq.hu) can use two-pass encoding to convert them into much smaller AVI files. We find that the XVid codec produces good quality movies. Codecs and encoders are frequently updated, and it is suggested that users consult websites like the one mentioned above for the most current information.
Usage: write_ptraj_input_files.py [options] Please make sure that you have created the following directories: output-dir output-dir/structure-name output-dir/images This script will emit the PDB file that you will use as a reference structure later on. It will live in <outputdir>/<structure>_ref.pdb.1 Options: -h, --help show this help message and exit --structure-name=STRUCTURENAME Name of your structure. E.g. 1RX1 or 1SGZ. [default: 1rx1] --output-dir=OUTPUTDIR Directory where we will put our results. This should be the same as the directory where we put our ptraj files before, and it should contain the .dat files that ptraj outputs. [default: ptraj_files/] The images will go to <outputdir>/images and the html file will be in <outputdir> --start=START Time, in ps, to start the windows. [default: 500] --stop=STOP Time, in ps, to stop the windows. [default: 10500] --window-size=WINDOWSIZE Length, in ps, of window size. [default: 1000] --window-spacing=WINDOWSPACING Spacing between windows, in ps. [default: 100] --input-dir=INPUTDIR Directory that contains our input files. It should contain the prmtop file and the mdcrd file. [default: ./] --mdcrd=MDCRD Comma-separated list of mdcrd files --ps=PS Number of ps per frame. [default: 5] --align=ALIGN How to align. 'all' means 'rms first *'. 'none' means no alignment. Any other string will be treated as the alignment string. For example, if you say ':1-428@CA' the ptraj file will say 'rms first :1-428@CA'. [default: all] --strip-hydros Strip the hydrogens out during the ptraj runs. --strip-waters Strip the waters out during the ptraj runs. This assumes they're named WAT. --write-covar Write out the covariance matrix [default: False] --other-ptraj-strips=OTHER_PTRAJ_STRIPS Comma-separated list of other things that ptraj should strip. For example, could be :WAT,:BOB and we would add two lines, one saying strip :WAT and one saying strip :BOB.
Usage: run_ptraj.py [options] Please make sure that you have created the following directories: output-dir output-dir/structure-name output-dir/images Options: -h, --help show this help message and exit --structure-name=STRUCTURENAME Name of your structure. E.g. 1RX1 or 1SGZ. [default: 1rx1] --output-dir=OUTPUTDIR Directory where we will put our results. This should be the same as the directory where we put our ptraj files before, and it should contain the .dat files that ptraj outputs. [default: ptraj_files/] The images will go to <outputdir>/images and the html file will be in <outputdir> -i INPUTDIR, --input-dir=INPUTDIR Directory that contains our input files. It should contain the prmtop file and the mdcrd file. [default: ./] -p PRMTOP, --prmtop=PRMTOP Name of prmtop file
Usage: do_correlated_md_analysis.py [options] Please make sure that you have created the following directories: output-dir output-dir/structure-name output-dir/images Options: -h, --help show this help message and exit --structure-name=STRUCTURENAME Name of your structure. E.g. 1RX1 or 1SGZ. [default: 1rx1] --output-dir=OUTPUTDIR Directory where we will put our results. This should be the same as the directory where we put our ptraj files before, and it should contain the .dat files that ptraj outputs. [default: ptraj_files/] The images will go to <outputdir>/images and the html file will be in <outputdir> --start=START Time, in ps, to start the windows. [default: 500] --stop=STOP Time, in ps, to stop the windows. [default: 10500] --window-size=WINDOWSIZE Length, in ps, of window size. [default: 1000] --window-spacing=WINDOWSPACING Spacing between windows, in ps. [default: 100] --non-ca-resis=NON_CA_RESIS Comma separated list of residues that don't contain alpha carbons. We need this to make some of our output images. [default: []], but you could say 160,161 for example
Usage: make_correlated_dynamics_plots.py [options] Please make sure that you have created the following directories: output-dir output-dir/structure-name output-dir/images This will spit out an html file that will show you your images. If you need to look at the images on another machine, tar up the html file and output-dir/images together and move that to the other machine. Options: -h, --help show this help message and exit --structure-name=STRUCTURENAME Name of your structure. E.g. 1RX1 or 1SGZ. [default: 1rx1] --output-dir=OUTPUTDIR Directory where we will put our results. This should be the same as the directory where we put our ptraj files before, and it should contain the .dat files that ptraj outputs. [default: ptraj_files/] The images will go to <outputdir>/images and the html file will be in <outputdir> --start=START Time, in ps, to start the windows. [default: 500] --stop=STOP Time, in ps, to stop the windows. [default: 10500] --window-size=WINDOWSIZE Length, in ps, of window size. [default: 1000] --window-spacing=WINDOWSPACING Spacing between windows, in ps. [default: 100] --cmap=CMAP Color map to use when making the plots. Our custom cmaps are Normal and Scaled. Standard matplotlib cmaps ['Spectral', 'summer', 'RdBu', 'gist_earth', 'Set1', 'Set2', 'Set3', 'Dark2', 'hot', 'RdPu', 'YlGnBu', 'RdYlBu', 'gist_stern', 'cool', 'gray', 'GnBu', 'gist_ncar', 'gist_rainbow', 'bone', 'RdYlGn', 'spring', 'Accent', 'PuBu', 'spectral', 'gist_yarg', 'BuGn', 'YlOrRd', 'Greens', 'PRGn', 'gist_heat', 'Paired', 'hsv', 'Pastel2', 'Pastel1', 'copper', 'OrRd', 'jet', 'BuPu', 'Oranges', 'PiYG', 'YlGn', 'gist_gray', 'flag', 'BrBG', 'Reds', 'RdGy', 'PuRd', 'Blues', 'Greys', 'autumn', 'pink', 'binary', 'winter', 'prism', 'YlOrBr', 'Purples', 'PuOr', 'PuBuGn'] are also supported.[default: Normal] --plot-types=PLOTTYPES Comma-separated list of plot types. [default: ['ca', 'avg', 'max', 'min', 'abs', 'straight', 'mainheavy', 'allheavy', 'sidechainhbond', 'hbond']] --mark-resis=MARKRESIS A list of residues to mark on the plots. [default: []] --highlight=HIGHLIGHT How strongly to highlight the marked residues. Note that --highlight-mode tells us how exactly we will do the highlighting. 0.1 and 0.2 are decent values if you want to use this feature for most plots, although you'll need something stronger for the absolute value plots. [default: 0.2] --highlight-mode=HIGHLIGHTMODE When highlight-mode is 'negative' we put a white block down on top of the marked residues, the opacity of which is controled by --highlight. When it's 'positive', we put that white block down on squares of residues that are *not* highlighted instead. When it's 'supernegative', we do just like 'negative' except that the block will be twice as opaque where the highlighted rows and columns intersect. Positive and supernegative seem to be more useful than negative. [default: positive] --skip-resis=SKIPRESIS A list of residues that will be skipped in the plots. [default: []] --no-ticks do not include tick marks on the axes --dpi=DPI dpi for figures [default: 200] --title=TITLE If no title is specified, one will be automatically generated. Note that the title is part of the filename that we save. [default: none]
Usage: make_movies.py [options] Please make sure that you have created the following directories: output-dir output-dir/structure-name output-dir/images Options: -h, --help show this help message and exit --structure-name=STRUCTURENAME Name of your structure. E.g. 1RX1 or 1SGZ. [default: 1rx1] --output-dir=OUTPUTDIR Directory where we will put our results. This should be the same as the directory where we put our ptraj files before, and it should contain the .dat files that ptraj outputs. [default: ptraj_files/] The images will go to <outputdir>/images and the html file will be in <outputdir> --plot-types=PLOTTYPES Comma-separated list of plot types. [default: ['ca', 'avg', 'max', 'min', 'abs', 'straight', 'mainheavy', 'allheavy', 'sidechainhbond', 'hbond']] --no-slow-movies Set this if you do not want to generate the movies that have 0.5s spacing between the frames. --movie-link=MOVIELINK 'fast' if you want the thumbnails to link to the fast images, anything else for the slow ones. [default: fast]
Usage: This will convert the .dat or .dat.bz2 files to numpy versions. It will not automatically delete the .dat(.bz2) files. If your input files are bz2, your output files will be too. If you already have a corresponding .numpy or .numpy.bz2 file, we won't write out a new file. Options: -h, --help show this help message and exit --dir=DIR Directory in which the files reside. [default: .] --structure-name=STRUCTURENAME Name of your structure. E.g. 1RX1 or 1SGZ --compression=COMPRESSION Type of compression currently used on files. Leave blank for uncompressed, .bz2 if they're .bz2 files. Note that it's '.bz2' not 'bz2'. [default: ] --all-dat-files By default, we will only convert the all_atom_correlmat files. If you use this option, we will convert all dat files. Don't forget, though, that you'll still have to call this command twice if you have some files that are bzipped and some that are not.


@examples The following example shows how to call various methods on the CorString class.
Public Sub Main() Const Sentence As String = "This string consists of a single short sentence." Dim Words() As String Dim Word As Variant Words = CorString.Split(Sentence, " ") For Each Word In Words Debug.Print CorString.Format("'{0}'", Word) Next End Sub ' This code produces the following output. ' ' 'This' ' 'string' ' 'consists' ' 'of' ' 'a' ' 'single' ' 'short' ' 'sentence.'


Classes
ListVoicesRequest
The top-level message sent by the client for the ListVoices
method.
ListVoicesResponse
The message returned to the client by the ListVoices
method.
Voice
Description of a voice supported by the TTS service.
SynthesizeSpeechRequest
The top-level message sent by the client for the
SynthesizeSpeech
method.
SynthesisInput
Contains text input to be synthesized. Either text
or ssml
must be supplied. Supplying both or neither returns
[google.rpc.Code.INVALID_ARGUMENT][]. The input size is limited to
5000 characters.
VoiceSelectionParams
Description of which voice to use for a synthesis request.
AudioConfig
Description of audio data to be synthesized.
SynthesizeSpeechResponse
The message returned to the client by the SynthesizeSpeech
method.
Timepoint
This contains a mapping between a certain point in the input text and a corresponding time in the output audio.


Notable changes
Security
- fix: CVE-2022-31197 Fixes SQL generated in PgResultSet.refresh() to escape column identifiers so as to prevent SQL injection.
- Previously, the column names for both key and data columns in the table were copied as-is into the generated
SQL. This allowed a malicious table with column names that include statement terminator to be parsed and
executed as multiple separate commands.
- Also adds a new test class ResultSetRefreshTest to verify this change.
- Reported by Sho Kato
Changed
- chore: skip publishing pgjdbc-osgi-test to Central
- chore: bump Gradle to 7.5
- test: update JUnit to 5.8.2
Added
- chore: added Gradle Wrapper Validation for verifying gradle-wrapper.jar
- chore: added "permissions: contents: read" for GitHub Actions to avoid unintentional modifications by the CI
- chore: support building pgjdbc with Java 17
Commits by author
Dave Cramer (9):
bump gradle to version 3 to fix compile errors with jdk17 PR 2550
update the website content PR 2578
Sehrope Sarkuni (1):
Fix SQL generated in PgResultSet.refresh() to escape column identifiers so as to prevent SQL injection.
Vladimir Sitnikov (34):
bump system-stubs-jupiter to 2.0.1 to support Java 16+
update JUnit to 5.8.2
migrate DriverTest to JUnit5
bump Gradle to 7.5


Books in the COINS documentation behave in a similar way to the menus in the rest of COINS OA, and in fact use the same system. A book can contain documentation topics and other books, in the same way that a COINS menu can contain runnable functions and other menus. If you want to create your own documentation book, you need to add it to the existing documentation menu structure by creating a user-defined copy of one of the documentation books, and adding your new book to this copy.
----------------------------------------------------------------------------------------- Version 0.0.1 - Nov 6th, 2019 (Nicholas Knight) ----------------------------------------------------------------------------------------- - Added New book procedure


Improve this Doc
Ionic's grid system is based on [flexbox](http://www.w3.org/TR/css3-flexbox/), a CSS feature supported by all devices that Ionic supports. The grid is composed of three units — _grid_, _rows_ and _columns_.
_For more detailed docs, Check out the [API docs](../api/components/grid/Grid)._
The grid system is made of a 12 columns, and each `ion-col` can be sized by setting the `col-` attribute.
Demo
Demo Source
``` html
This column will take 12 columns
This column will take 6 columns
```
An `ion-col` can be sized for different breakpoints by setting the `col--`.
``` html
This column will be 12 columns wide by default,
9 columns at the small breakpoint,
6 at the medium breakpoint, 4 at large, and 3 at xl.
```


Comics legend Frank Miller claims ex-wife stole rough sketches: lawsuit
by nypost.comKa-pow!
Comic book legend Frank Miller — who penned “The Dark Knight Returns” and “Sin City” — socked his ex-wife with a lawsuit Monday for allegedly swiping valuable rough sketches of his work and trying to sell them under the table.
Lynn Varley, an award-winning comic book colorist who collaborated with Miller on many of his early tomes, is allegedly hiding preliminary sketches she squirreled away before the couple’s divorce, Miller claims in his Manhattan Supreme Court lawsuit.
Varley filed for divorce in 2006, after 20 years of marriage. In 2011, while the duo was still married, they cut a deal to divvy up illustrations and artwork they owned, according to the court documents.


| Interface | Description |
|---|---|
| GameRules |
| Class | Description |
|---|---|
| AttackDamage |
Map of attack damage values and durability costs for various weapon types, until better item type
support is available.
|
| GlowAchievement |
Name mappings for Bukkit Achievements.
|
| GlowBiome |
Mappings for Biome id values.
|
| GlowBiomeClimate | |
| GlowDisplaySlot |
ID number mappings for
DisplaySlot s. |
| GlowEffect |
Conversion of data classes to raw values for Effects.
|
| GlowEnchantment |
Definitions of enchantment types.
|
| GlowParticle |
Id mappings for particles.
|
| GlowPotionEffect |
Definitions of potion effect types.
|
| GlowSound | |
| GlowStatistic |
Name mappings for statistics.
|
| GlowTree | |
| ItemIds |
Temporary mappings for Minecraft's string-based item ids.
|
| ResourcePackStatus |
Mappings for resource pack status codes.
|
| Enum | Description |
|---|---|
| GlowBlockEntity |
Name mappings for magic values in UpdateBlockEntity packet.
|
Copyright © 2021. All rights reserved.


In our portfolio, you can browse the latest products developed for our clients for different corporate purposes. Our qualified team of interface designers and software developers is always ready to create something unique for you.
10
DreamSoft is a team of highly experienced app designers and developers creating unique software for you.
Get in touchapp developed
consultants
awards won
employees


Dev Extravaganza is a 3-day workshop series in association with GitHub empowering all the budding developers with real-world knowledge and experience, bridging the gap between school and the industry. The series will focus on the practical sides of Web development, Game development, and Deployment while having fun with some of the best technologies in the current industry and winning some exciting goodies from Github.
It will cover 4 workshops:
- GitHub Workshop
- A hands-on workshop on Git and GitHub. You will learn how to work on development projects using GitHub and will be introduced to GitHub essentials like repositories, branches, issues, pull requests
- Twilio 201
- Clone a simple memes app and create a Twilio account. Text a number and receive back a random meme, gif, or any piece of content you want. Through this simple application, you'll get familiar with the Twilio SMS API, how to use the Twilio console and JavaScript programming.
- AWS
- You will go through building an Event Suggestion Generator web application using the EventBrite API, setting up a Flask application, fetch data from Eventbrite’s API, configuring a database using AWS Elastic Beanstalk, and deploy to Amazon Web Services.
- Unity
- Interact with a 3D car racing game written in C# and developed using the Unity Game Engine. You will learn how to set up the Unity Engine on your computer, explore the project files, fix broken functions in the game, and publish your games for others to play!


JS9 is the latest in the SAOimage line of astronomical image display programs developed at the Center for Astrophysics | Harvard & Smithsonian (CfA.) Our previous effort, SAOimage DS9, has been the de facto standard desktop image display for more than 30 years. Now, with JS9, you can view and manipulate astronomical image data in your browser as well as on the desktop.
Please choose from the following topics:
JS9 provides astronomical image display capabilities both on the desktop and in your browser. JS9 takes its name as well as its core functionality from the de facto standard DS9 image display program for desktop use. JS9, on the other hand, can be run either on the desktop or in a browser. It also can be used without any installation at all by dragging/dropping a FITS file onto the JS9 website. In all three cases, the JS9 display consists of one or more HTML components that are added to a web page. At a minimum, the JS9 display will contain an image display canvas. It usually also will display a menubar containing several pull-down menus and a colorbar. Traditionally, the menubar is placed on top of the image canvas and the colorbar below, but web page designers (as well as individual users) have complete control over component placement. JS9 also can display an info box, a command-line window, a pan window, a zoom window, as well as other plugins. All of these plugin windows can be brought up dynamically from the View menu.
Astronomical image data usually is offered on a JS9 web page as one or more clickable URLs. When you click on a data URL, it is displayed on the JS9 image canvas. Multiple images can be loaded into a single JS9 display. The File menu allows you to switch between these images.
Once an image is loaded, you can move the mouse (or a single finger on a touch screen) to display position and pixel value information. Pressing the left mouse button and moving the mouse (or using two fingers on a touch screen) will change the contrast/bias of the displayed image, bringing image features into relief.
These mouse/touch actions are configurable, both by web page developers and by users. See the Mouse Touch plugin for more information.
Menu options allow you to change the scaling algorithm and/or color map, add geometric regions of interest, change world coordinate system (WCS) parameters, and run site-specific astronomical analysis tasks on the original FITS data.
The following menus are in the default JS9 menu bar. Of course, web designers have control over which menus are displayed (or even whether the menu bar itself is displayed.) Thus, not all of the menus listed below will be found on all JS9-enabled web pages.
Some menu options have keystroke accelerators and these are shown on the right-hand side of the menu option. Thus, for example, to open a local file, you can select the File:open...:local file menu option, or press the Meta-o key combination when the mouse is inside the JS9 display.
Note that the default menubar has a style in which all of the major menus are shown at the top-level of the menubar. This is the classic style. JS9 also supports a mac style menubar, in which the File, Edit and View menus are placed on the left side of the menubar and the Help menu on the right. The other main menus are displayed as submenus within the View menu.
The default top-level JS9 menus are:
File: The File menu displays the currently loaded images, either directly in the menu, or, if there "too many" images (as defined by the JS9.globalOpts.imagesFileSubmenu variable), using an images submenu. The displayed image is marked with a starburst. To display a different image, simply choose it from the menu. The File menu also contains the following submenus and options:
Edit: allows you to copy and paste regions, positions, and pixel values to/from the clipboard:
View: displays a list of available plugin, including the following core options:
The View menu also contains the following Display Options submenus:
Zoom: The zoomIn and zoomOut menu options zoom the primary image in or out by a factor of two. The zoomToFit options calculates a zoom factor that fits the entire image into the JS9 display. You also can set the zoom factor to a pre-specified value using menu options or you can specify a floating point zoom factor in the other zoom text box. The pan to center option pans to the center of the image, while the reset pan/zoom sets the zoom to 1 and centers the display.
The align pan/zoom ... submenu allows you to change the pan and zoom of the current image to match a target image, assuming both have WCS info available. Pixel size (i.e. as specified by the FITS CDELT1 parameter) will be taken into account when zooming, but not image rotation or flip (from the WCS params.) This is quicker than the wcs reproject algorithm for aligning images that are similar.
The Zoom menu also supports image flip around the x or y axes, image rotation by +/- 90 degrees or by an arbitrary angle. There also is an option to rotate the image so that north is up in the current coordinate system. Flipping and rotation are performed on the displayed pixels (so no change is made to the WCS). The rotation is much faster than the more general WCS-based rotation/reprojection in the WCS menu. Note that arbitrary rotation is performed in terms of an absolute angle: if you rotate by 20 degrees and then do it again, there is no change. Also, setting the rotation to 0 sets the angle to 0. Flipping and rot90, however, are relative to the current state of the display. This differs from DS9, where the actions are linked to the x and y axes. Thus, flipping by x twice will return you to the original orientation, whereas flipping a second time does nothing in DS9.
Scale: Each scale option specifies a different scaling algorithm to use when converting image pixel values to RGB values. (The procedure for doing this conversion is detailed in the DS9 documentation titled "How It Works".) The log scale, for example, is especially useful with X-ray data. Histogram equalization (histeq) tries to maximize contrast across the range of data values and is useful in a wide variety of cases. The current scale is marked with a starburst.
You also can change the low and high values used to clip the image data before scaling by changing the low and/or high values in the text boxes of the Data Limits section. These values are set initially with the data's min and max values or the z1,z2 values calculated by the IRAF zscale algorithm (depending on the value of the web site's JS9.imageOpts.scaleclipping parameter. The default usually is "dataminmax".) Finally, you can use the Scale Controls plugin to set the clipping values to data min/max, zscale z1/z2 or zscale z1/max, or set the clipping values using the pixel distribution plot.
Colormap: Each colormap option specifies a different distribution of RGB values to use when converting image pixel values to RGB. (The procedure for doing this conversion is detailed in the DS9 documentation titled "How It Works".) Choose the colormap you like best, or try different ones to see how data features can be brought to the fore by color and contrast/bias.
The image filters menu option displays the JS9Filters plugin, which offers a number of well-known image processing functions that act directly on the displayed RGB image data (not the underlying raw astronomical data, as with the Gaussian blur in the Analysis menu.) Thus, when you can run one of these routines on an image, its effect will be undone if you redraw the image by changing the contrast/bias, colormap, etc. Also, since these functions act on the current RGB image, their effect is cumulative. See the JS9.FilterRGBImage() section in the JS9 Public API for more information about the individual functions. Note that not all functions in the public API call are implemented here: some of them seemed pretty useless for our data (they can be added easily.)
You can enter a floating point value into the contrast and bias text boxes to set the contrast/bias. Note that the contrast value ranges from 0 to 10 and the bias ranges from 0 to 1 (following DS9 conventions.)
The reset contrast/bias option restores the original contrast/bias value (which is especially useful if you changed the contrast/bias or scale and now can't see any features at all!)
The opacity option allows you to set the overall opacity for all pixels in the image. Values range from 0 (transparent) to 1 (opaque.) More opacity options can be found in Color Controls (see below.)
The load option brings up a File menu from which you can choose a user-defined colormap to load.
The save option saves the active colormap definition for the currently displayed image to a file (useful for editing to make a new colormap.)
The invert option inverts the colormap (e.g., in the gray map, this will change white to black and vice versa.)
If you have three images of the same size, scale, and pointing direction (e.g., three energy cuts of a Chandra data set), you can display each one separately and assign to them one of the red, green, or blue colormaps. If you then select the rgb mode menu option, they will be displayed as one RGB composite image. The current image (as shown in the File menu) determines which of the three independent colormaps is changed by the contrast/bias manipulation. To remove an image from the RGB composite, give it a different colormap. Re-join (or add a new image) by assigning one of the RGB colormaps. Simply turn off RGB mode to display the images separately.
Regions: Astronomical regions format is described here. Choose the appropriate menu option to create a region of type annulus, box, circle, ellipse, line, point, polygon, text. (see below for details on how to use regions.) One or more regions can be created and manipulated on a single image.
By default, a region is created in the center of the image when it is selected in the Regions menu. You can turn off auto-creation by deselecting the menu adds region @ center option. With auto-creation turned off, the 'a' key will add the last selected region at the current mouse position.
The list menu option will display all regions.
The load ... menu option will load a file of regions and display them on the current image. Regions can be specified using the a dialect of the widely-used DS9/Funtools regions format, as described here.
The save ... display a dialog box allowing you to save selected or all regions in one of these formats:
The copy to ... menu option will copy regions from the current image to a specified image (or to all images.) If one or more regions are actively selected in the current image, they alone will be copied. Otherwise, all regions will be copied.
The remove menu option will delete all regions.
The selected regions ... submenu contains options that apply to the selected region(s), including the ability to edit, list, save, remove, or copy the selected region(s). The submenu also allows you to change the following properties of selected regions by entering text values:
The selected regions submenu also supports the ability to toggle the "source"/"background" or "include"/"exclude" tags (which is heavily used in X-ray astronomy.)
The onchange submenu contains the following options:
WCS: Use this menu option to select a world coordinate system when displaying pixel positions and regions (assuming the data file supports WCS.) Available systems are: FK4, FK5, ICRS, galactic, or ecliptic. The native option chooses the system stored in the data file. The image and physical systems will display only image coordinates (not WCS coordinates.) Physical coordinates are tied to the original (block 1) file coordinates while image coordinates are tied to the current image data being displayed. Server-side X-ray analysis routines operating on the original file generally want physical coords rather than image coords. Browser-based plugin routines generally use image coordinates to operate on the in-memory image data.
You also can choose the units in which WCS information is displayed: degrees, radians, or sexagesimal. Image and physical coordinates are displayed in units of pixels.
The alternate wcs menu option allows you to choose an alternate world coordinate system, if one or more are defined in the current FITS file. The submenu lists the WCS version (i.e. the letter "A" - "Z", or "default") and, if present, the WCSNAME header parameter associated with this WCS.
The reproject menu option allows you to reproject the image using the WCS associated with another displayed image. The reprojected data is placed in a new raw data layer called "reproject". You can switch between layers using the View->raw data layers option. If the display wcs-aligned option is set, the reprojected image will be aligned with the wcs reference image. If you change the pan/zoom of the latter, the former will be re-aligned. (The converse is not true: changing the reprojected image does not change the wcs reference image.) You can also reproject other images in this display using the WCS info from the currently displayed image.
Analysis: JS9 supports both client-side analysis (i.e., analysis in the browser) and server-side analysis (where requests are made to a back-end server, and returned results are displayed in the browser.)
Client-side analysis tasks can be written using the JS9 Plugin capability, and the Analysis menu lists the currently loaded Analysis Plugins. For example, JS9 supplies the Imexam plugin, which offers the following tasks:
JS9 supplies a few other client-side analysis tasks:
In addition, each JS9 site can define server-side analysis tasks to be run from the Analysis menu. Server-side tasks are of two types:
For example, the JS9 web page at https://js9.si.edu offers the following tasks:
If you drag and drop a FITS file onto a JS9 web page connected to a remove server (such as https://js9.si.edu), the FITS file will, of course, not be accessible on the server (it's only stored in the browser.) As a result, no server-side analysis tasks will be available. But if the remote server supports proxy loading of FITS data, the Analysis menu will display an option to upload FITS to make tasks available. Select this option and your FITS file will be sent to the server so that server-side analysis can be performed.
The server-side params submenu contains the following options:
Help: Show this and other JS9 help pages. The Help menu also contains help for Plugins, including the Imexam plugins listed above.
In keeping with the needs of mobile devices, JS9 utilizes a single mouse button for user interaction. Keyboard input also is minimized. Moving the mouse (or a single finger on a tablet) over the image will display the position/value of individual pixels. Pressing and moving the mouse (or two fingers) will change the contrast and bias of the image.
Regions are geometric shapes that can be used to mark part of an image for analysis. JS9 allows you to create the following region types: annulus, box, circle, ellipse, line, point, polygon. A text region also can be created to annotate an image. When one of these options is selected, the region is created in the center of the image. It then can be dragged to the desired location. Arrow keys also will move the region one screen pixel in the specified direction. A selected region can be deleted by pressing the Delete key (where available. On a tablet, use the delete option in the configuration menu.)
Click inside a region to select it and display the resize/rotate controls around its perimeter. Grabbing a handle allows the size of the region to be adjusted or rotated. In the case of the box and ellipse regions, the width and height are controlled separately. Click outside the region to de-select (or click another region to select that one.)
For a line region, the end-points serve as both resize controls (arrow icon) and stretch points (hand icon.) You might have to move the mouse around a bit to switch from one to another. The control action is to resize the region in both directions (i.e., the same as other regions.) The stretch action allows you to move this end-point while the other one remains fixed.
A double-click inside a region brings up a configuration menu. You can change various values associated with a region by entering new values in the appropriate text boxes and the clicking Apply.
The configuration menu has the following standard options:
In addition, regions of different type support specific configuration
parameters in this menu.
The annulus region supports:
The meta key is the Command key on a Mac and the Control key everywhere else.
Pressing the meta key disables the value/position display. It also disables execution of plugin callbacks on all mouse events. See Local Tasks for more information about plugins and browser-based analysis.
When a keyboard is available, pressing the meta key while clicking in the primary image window will pan the image so that the mouse location is in the center of the display (this panning is disabled inside a region.)
Within a polygon or a line, if you press meta and click the mouse on the polygon or line border, a new point will be added at that point. If you press the meta key and click on an existing point, it will be deleted.
Within an annulus, if you press meta and click the mouse, the annuli of the annulus region are replaced by an equivalent set of circles which can be resized (or deleted) individually, but not moved. Press meta and click the mouse again to finalize the region with the new annuli. Press shift-meta and click the mouse to cancel the edit and restore the original annuli.
You can drag and drop FITS images and binary tables, PNG images, and JPEG images onto JS9 to display the image data. All browser-based functions (scaling, colormap, pan, zoom, regions, WCS) should work as expected. You can execute server-side analysis tasks on the FITS files if the back-end server is running on your local host machine. In this case, you probably will need to set your DataPath variable in the Analysis menu to help JS9 locate the original data file.
The JS9 Display can be resized using the the View:resize:change width/height menu option (or the JS9.ResizeDisplay() JavaScript routine.) The View menu's resize parameter can be two values (width and height) or a single value representing both. In addition, if an image containing wcs info is being displayed, you can append a single quote to specify a size in arc minutes (e.g., 5') or a double quote to specify a size in arc seconds (e.g., 300".)
The View:resize:set to image size option will set the display size to the size of the current image. The View:resize:set size to full window option will resize the JS9 display to the size of the browser window's window.innerWidth and window.innerHeight properties, and will scroll the display to the center of the window. (Note that the rest of the web page is still available via scrolling, including the menubar.) The View:resize:reset to original size option will set the display size back to the original size. Display resize can be turned off by setting the JS9.globalOpts.resize variable to false in the js9prefs.js file.
Also by default, the JS9 Display can be resized using a grab handle in the lower right-hand corner of the display. This feature can be turned off setting the JS9.globalOpts.resizeHandle variable to false in the js9prefs.js file.
See Known Issues for a discussion of limitations imposed on resize by Webkit browsers such as Chrome and Safari.


Home
About Us
Accomodations
Things To Do
Contact Us
Name
Email Address
Address
Phone
Comments
Created with
FormToEmail
Designed by Two Guy's Web of Lies


Device Pixel Ratio matchMedia Audio extension Video extension User Agent innerWidth (window) Page Width Width (viewport) Device-Width innerHeight (window) Page Height Height (viewport) Device-Height
Performance
Now method
Performance Timing
Performance Memory
ES5 Promises Service Worker fetch object History geolocation Web Storage WebSocket Page Visibility Drag & Drop
Touch Device Orientation Device Motion listenForDeviceMovement
rAF
Indexed DB
getUserMedia URL
requestFullScreen cancelFullScreen fullscreen properties
html imports ShadowDOM html templates Custom elements
Web SQL
File Reader Blob
FileWriter LocalFileSystem DirectoryReader DirectoryEntry FileEntry
requestFileSystem requestFileSystemSync resolveLocalFileSystemURL resolveLocalFileSystemSyncURL storageInfo getAsEntry method
CSS3 tap-highlight-color JS tap-highlight-color
CSS3 Animation keyframes CSS3 Animation JS Animation
CSS3 Transform JS Transform
CSS3 Transition JS Transition
CSS3 box-shadow, text-shadow & border-radius JS box-shadow, text-shadow & border-radius


18
1 After David finished talking with Saul, he met Saul's son, Jonathan. Jonathan immediately liked David; in fact, he began to love him.
2 From that day, Saul kept David with him to serve him; he did not let him return home.
3 Because he loved David so much, Jonathan made a solemn agreement with David. They promised each other that they would always be friends.
4 Jonathan took off his own outer robe and gave it to David. He also gave David his soldier's tunic, his sword, his bow and arrows, and his belt.
5 David went wherever Saul sent him. And whatever Saul told him to do, David did it very successfully. As a result, Saul appointed David as a commander in the army. All the officers and other men in the army approved of that.
6 But when the men in the army were returning home after David had killed Goliath, Israelite women came out from many cities and towns. They greeted King Saul while they were singing and dancing very joyfully, playing tambourines and lyres.
7 As they danced, they sang this song:
"Saul has killed a thousand enemy soldiers,
But David has killed ten thousand of them."
8 When Saul heard them singing that, he did not like it. He became very angry. He said to himself, "They are saying that David killed ten thousand men, but that I have killed only one thousand. Soon they will want to make him their king!"
9 From that time, Saul watched David very closely because he was suspicious that David would try to become king.
10 The next day, an evil spirit sent by God suddenly took control of Saul. He began to act like a madman, inside his house. David was playing the lyre for him, as he did every day. Saul was holding a spear in his hand,
11 and he hurled it at David, thinking, "I will fasten David to the wall with the spear!" He did that two times, but David jumped aside both times.
12 Because it became evident that Yahweh had abandoned Saul but that he was helping David, Saul was afraid of David.
13 So he appointed David as a commander of a thousand soldiers and sent David away from him, hoping that David would be killed in a battle. But when David led his soldiers in their battles,
14 he always had great success, because Yahweh was helping him.
15 When Saul heard that David and his soldiers were very successful, he became more afraid of David.
16 But all the people of Israel and of Judah loved David, because he led the soldiers very successfully in the battles.
17 One day Saul said to David, "I am ready to give you my oldest daughter, Merab, to be your wife. I will do that if you serve me bravely by fighting battles for Yahweh against the Philistines." He said that because he thought, "I will not try to get rid of David by myself. I will allow the Philistines to do that."
18 But David said to Saul, "I am not a very important person, and my family is not very important. Also my clan is not a very important Israelite clan. So I do not deserve to become your son-in-law."
19 So, when it was time for Merab to be given to David to become his wife, instead, Saul gave her to a man named Adriel, from Meholah.
20 However, Saul's other daughter, Michal, fell in love with David. When they told Saul about that, he was pleased.
21 He thought, "I will give Michal to him, in order that she may trap him, and the Philistines will be able to kill him." So he said to David, "You can marry Michal," and by saying that, he indicated for the second time that David would become his son-in-law.
22 Saul told his servants, "Talk to David privately, and say to him, 'Listen, the king is pleased with you, and all of us his servants love you. So now we think that you should marry Michal and become the king's son-in-law.'~"
23 So they said that to David. But David said, "It would be a great honor to become the king's son-in-law. But I do not think that I should do that, because I am only a poor and insignificant man."
 In that way he will get revenge on his enemies.'~" But what Saul really wanted was that the Philistines would kill David while he was trying to kill them.
26 When the servants told that to David, he was very pleased that he could become the king's son-in-law by doing that. The king had said how many days he would allow for David to do that.
27 But before that time ended, David and his men went and killed, not one hundred, but two hundred Philistines! He brought their foreskins to Saul, and counted them while Saul was watching, in order to prove that he had fulfilled what the king required so that he could become Saul's son-in-law. So then Saul was obligated to allow David to marry his daughter Michal.
28 But when Saul realized that Yahweh was helping David, and that his daughter loved David,
29 he became more afraid of David. So as long as Saul lived, he was David's enemy.
30 The Philistine armies repeatedly came to fight the Israelites, but every time they fought, David and his soldiers were more successful than any of Saul's other army commanders. As a result, David became very famous.


Hong Kong part of China 'no matter what happens' in elections: Foreign minister
TOKYO: Hong Kong is a part of China "no matter what happens", Chinese Foreign Minister Wang Yi said Monday (Nov 25), with the crisis-hit city's pro-democracy looking set for a crushing victory in community-level elections at the weekend.
The results of Sunday's elections in the semi-autonomous city have sent the Beijing-backed government a clear message of public support for the demands of a protest movement that has gripped the territory for months.
READ: Hong Kong democrats score landslide victory in local elections amid political crisis
READ: Chinese state media urge Hong Kongers to 'vote to end violence'
Counting was still under way following record turnout, but partial results indicated that candidates favouring greater democracy were on course to seize a shock majority of the normally establishment-dominated 18 district councils.
"It's not the final result yet. Let's wait for the final result, OK? However, it is clear that no matter what happens, Hong Kong is a part of China and a special administrative region of China," Wang told reporters after he met with Japanese Prime Minister Shinzo Abe in Tokyo.
"Any attempt to mess up Hong Kong, or even damage its prosperity and stability, will not succeed."
READ: Record turnout in Hong Kong local elections amid calls for full democracy
Follow us on Telegram for the latest on Hong Kong: https://cna.asia/telegram


| Public fields | ||
| ghk | const | |
| sigfree | const | |
| SigLT | const | |
| Public methods | ||
| GHKMNP | ||
| SetGHK | ||
| vfunc | Compute and return the vector of log-likelihoods at the current parameters. | |
| Enumerations | ||
| Anonymous enum 1 |
| Public fields | ||
| Npts | const | # of nodes in quadrature |
| Public methods | ||
| GQMNP | ||
| vfunc | Compute and return the vector of log-likelihoods at the current parameters. |
| Public fields | ||
| betas | const | Array of J-1 parameter blocks, one for each equation except Y=0. |
| indY | const | N x J matrix of permutations the first column is index of Y second column is first non-Y choice third column is second non-Y choice etc. |
| J | const | J : number of options |
| Jvals | const | integer codes of choices |
| namearray | const | Labels for variables |
| NN | const | indexing vector |
| nX | const | K : number of X variables |
| X | const | X : matrix of exog variables |
| Y | const | Y : discrete endog vector |
| Public methods | ||
| Estimate | Estimate the model using Simplex and BHHH, print results. | |
| MNP | Create a new MNP model. |
| Enumerations | ||
| Anonymous enum 1 | identity, onlydiag, lowertriangle, SigmaOptions |
| fn | string, a file to load the data from using Ox Database.Load()
|
| Yname | string, name or label of the column in the file that contains Y Yname can contain any integers. MNP will translate the unique sorted values into 0...Jvals-1 |
| Xnames | a string of the form var1 var2 ... varN |


Welcome to the Bus Mall focus group. Look at these awesome products we are thinking about selling you! Choose the one from each set that you would want the most. When finished we will save your user data use it to make sure we only bring you the MOST desired items in the weekly Bus-Mall flyer.


| void dg_blmc_robots::DGMSolo12::calibrate_joint_position |
( |
const blmc_robots::Vector12d & |
zero_to_index_angle | ) |
|
|
private |
Calibrate the robot joint position.
- Parameters
-
| zero_to_index_angle | is the angle between the theoretical zero and the next positive angle. |
| bool dg_blmc_robots::DGMSolo12::calibrate_joint_position_callback |
( |
dg_blmc_robots::JointCalibration::Request & |
req, |
|
|
dg_blmc_robots::JointCalibration::Response & |
res |
|
) |
| |
Ros callback for the callibration procedure.
Warning the robot will move to the next the joint index and back to "0" upon this call. Be sure that no controller are running in parallel.
- Parameters
-
| req | nothing |
| res | True if everything went well. |
- Returns
- true if everything went well.
-
false if something went wrong.
| void dg_blmc_robots::DGMSolo12::get_sensors_to_map |
( |
dynamic_graph::VectorDGMap & |
map | ) |
|
get_sensors_to_map acquieres the sensors data and feed it to the input/output map
- Parameters
-
Joint data.
Additional data.
Robot status.
| void dg_blmc_robots::DGMSolo12::initialize_hardware_communication_process |
( |
| ) |
|
initialize_hardware_communication_process is the function that initialize the hardware.
Load the calibration parameters.
Initialize the user commands.
| void dg_blmc_robots::DGMSolo12::set_motor_controls_from_map |
( |
const dynamic_graph::VectorDGMap & |
map | ) |
|
set_motor_controls_from_map reads the input map that contains the controls and send these controls to the hardware.
- Parameters
-
| blmc_robots::Vector12d dg_blmc_robots::DGMSolo12::ctrl_joint_torques_ |
|
private |
ctrl_joint_torques_ the joint torques to be sent.
Used in this class to perform a local copy of the control. This is need in order to send this copy to the blmc_robots::Solo class
| blmc_robots::Solo12 dg_blmc_robots::DGMSolo12::solo_ |
|
private |
Entries for the real hardware.
test_bench_ the real test bench hardware drivers.
| blmc_robots::Vector12d dg_blmc_robots::DGMSolo12::zero_to_index_angle_from_file_ |
|
private |
These are the calibration value extracted from the paramters.
They represent the distance between the theorical zero joint angle and the next jont index.
The documentation for this class was generated from the following files:


LibraData is a place for UVA researchers to share data publicly, and is part of the Libra Scholarly Repository suite of services which includes works of UVA scholarship such as articles, books, theses, and data.
Step One: Start with the LibraData Checklist
Step Two: Select the dataverse in which you want to add a dataset.You can create a dataset at the main level of LibraData or in a sub-dataverse.
Search below for datasets in LibraData and all of UVa Dataverse
*Access to some datasets in these dataverses may require UVa authentication.


If you are upgrading from a previous version of QPT, see Updating QPT below.
jre/bin
), and is available as a system update for the Mac. Verify that it is working
as follows:
$ java -version java version "1.6.0_15" Java(TM) SE Runtime Environment (build 1.6.0_15-b03-226) Java HotSpot(TM) 64-Bit Server VM (build 14.1-b02-92, mixed mode)If you're using the OT distribution, you may need to type the full path. If you're using a Mac and have just installed Java 1.6, you may need to change a symbolic link to get it working. Go to
/System/Library/Frameworks/JavaVM.framework/Versions
and change the
CurrentJDK
link to point to 1.6
. You need to be root
or use sudo
to do this.
.ocs
directory in you home directory
and put the file there:
$ mkdir ~/.ocs $ cd ~/.ocs $ curl -O http://build.cl.gemini.edu:9999/runtime/launcher/launcher.jar ... $ cdIf you don't have
curl
, use your web browser or wget
.
I recommend creating an alias to make it simpler to run the launcher. You should add this to your standard list of shell aliases. Try it out on its own and you should see a pithy error message.
$ alias launcher='java -Xmx512m -jar ~/.ocs/launcher.jar' $ launcher Sorry, what application are we talking about? You need -a or -i, or both. Let me help you. Try: java -jar launcher.jar -?This may seem like a lot of work, but you only have to do it once. It will allow you to download and run any of the HLPG OSGi-based programs.
$ launcher -h:build.cl.gemini.edu -i:qpt -vNow we can run QPT. The first time you run it, it will download all its components from
build.cl.gemini.edu
, so it may take a little while to get going the first
time, especially in the north.
$ launcher -a:qpt Welcome to Oscar. ================= ...
There is also a quiet mode that suppresses console output (actually it just redirects
it to some files under ~/.ocs
.
$ launcher -a:qpt -n &
~/ocs/hostname/
. Be sure
QPT is not running.
$ cd ~/.ocs $ cd hostname $ ls qpt $ mv qpt qpt-1.0.0You may then run this older version by specifying the new name:
$ launcher -a:qpt-1.0.0To install the new version, go to step 3 of the installation instructions above.
launcher -a:qpt -uand then jump to step 3 of the installation instructions above.


This document is designed to help NetBeans module writers with installing help into the IDE and correctly setting up context-sensitive help for their modules. The document covers the following topics:
The IDE's architecture enables you to:
In order to take advantage of these help features, a NetBeans module writer must be aware of different aspects of the NetBeans help system, specifically:
There is an overview of adding help to various GUI NetBeans components in the JavaHelp Integration API. This section expands a bit on the information provided there.
If your node extends AbstractNode
or one of its subclasses, you should
implement the getHelpCtx
method to return a
HelpCtx
for the node. The HelpCtx
includes the specific
Help ID for the help topic for this node. If the node is selected in the explorer
and the user hits the F1 key, then the help associated with this node will be
displayed.
public class MyNode extends AbstractNode{ public HelpCtx getHelpCtx() { return new HelpCtx("org.netbeans.modules.xml.tree.nodes.XMLDataNode"); } // other methods... }
Wizards are basically a series of Swing Components that are displayed via a
WizardDescriptor.Iterator
object. The object that the developer
creates must implement the
WizardDescriptor.Panel
interface which includes a method that the
developer implements to return the actual Swing Component that is to be displayed
(usually a JPanel
is returned). Additionally, the developer must implement
the getHelp
method and return a HelpCtx
for this particular
wizard step. By default, the Help button is displayed on the resulting
JDialog
and when the user selects this Help button, the getHelp
method is called for the currently displayed WizardDescriptor.Panel
object.
public class MyWizardPanel implements WizardDescriptor.Panel { private JPanel p; public Component getComponent() { if (p == null) { p = new JPanel(); p.setLayout(new BorderLayout()); p.add(/* etc. */); } return p; } public HelpCtx getHelp() { return new HelpCtx("org.netbeans.modules.xml.core.wizard.DocumentPanel"); } // other methods... }
There are two different ways in which you can set help on a NetBeans dialog.
If you wish to display a dialog of some sort, you typically create the Swing
components you wish to display and then create a
DialogDescriptor
object which is a NetBeans object that is used
to describe the behavior or the dialog. To display help:
DialogDescriptor
object - As a rule, setting
the help ID on the DialogDescriptor
is the preferred way to set a
help ID for a dialog. There are a couple of ways to do this:
DialogDescriptor
constructors
that includes
a HelpCtx
.
setHelpCtx
on the previously created DialogDescriptor
:
DialogDescriptor dd = new DialogDescriptor(...); dd.setHelpCtx(new HelpCtx("dialog_help_id"));
DialogDescriptor
constructor takes an Object
which
is typically the Swing Component to display in the JDialog
. If you
set the help ID string property on the Swing component, then this help id
will be used as the help id for the JDialog
and the corresponding
help will be displayed if the user selects the Help button.
JPanel p = new JPanel(); // ...add Swing components to p ... HelpCtx.setHelpIDString(p, "panel_help_id"); DialogDescriptor dd = new DialogDescriptor(p, "Dialog Title");
If you do not supply a HelpCtx
object for the DialogDescriptor
or set the help ID string for the displayed Swing Component, then no Help
button will be displayed on the JDialog
that is displayed for this DialogDescriptor
.
When creating a Property Sheet, the developer creates a
Sheet.Set
object. To populate the Sheet.Set
the developer
creates and adds a number of
Node.Property
objects. To display help for the Property Sheet,
you must call the setValue
method and set the helpID
property:
Sheet sheet = Sheet.createDefault(); Sheet.Set ps = sheet.get(Sheet.PROPERTIES); ps.setValue("helpID", "org.netbeans.modules.xml.tree.nodes.XMLDataNode.Properties");
Property sheets can actually contain multiple tabs, each having their own help associated with them. The method described above to set the help id of a Property Sheet still applies, the only difference is the way in which the additional Property Sheet is created:
Sheet sheet = Sheet.createDefault(); Sheet.Set referenceTab = new Sheet.Set(); referenceTab.setValue("helpID", "org.netbeans.modules.xml.tree.nodes.XMLDataNode.ReferenceProperties"); referenceTab.setName("referenceTab"); // NOI18N sheet.put(referenceTab);
You can also set an individual help ID for each property (Node.Property
)
in a property sheet. Presently Sun Java Studio and NetBeans help is not provided on a per-property
basis - help on individual properties is provided in the form of a tooltip.
Some Properties displayed on a Property Sheet require a custom editor. The
user accesses the editor by selecting the "..." button on an entry for a specific
Property when the user selects that Property. The developer of the custom editor
provides a Swing Component (typically a JPanel) which is ultimately displayed
in a JDialog
. If Help is to be supplied on the resulting JDialog
,
then the help ID string of the supplied Swing Component must be set.
public MyPropertyEditor extends PropertyEditorSupport{ public Component TreeNodeFilterCustomEditor() { JPanel p = new JPanel(); // ...add Swing components to p... HelpCtx.setHelpIDString(p, "org.netbeans.modules.xml.tax.beans.editor.TreeNodeFilterCustomEditor"); return p; } // other methods... }
Some Custom Property Editors display a number of tabs. Depending on the tab that is displayed, different Help may need to be displayed. In this case, you should set the help ID on the property editor's JTabbedPane. If you want the help ID to change when the user switches tabs, then you should listen for changes in the selected tab, and change the ID on the JTabbedPane each time.
For NetBeans 3.4 and earlier, you can set help IDs on tabs as shown in this example:
class MyTabPane extends JTabbedPane implements ChangeListener { private HelpCtx[] helps = new HelpCtx[3]; public MyTabPane() { add(new Panel1()); helps[0] = new HelpCtx("help_1"); // etc. stateChanged(null); addChangeListener(this); } public void stateChanged(ChangeEvent ignore) { HelpCtx.setHelpIDString(this, helps[getSelectedIndex()]); } }
In NetBeans releases later than 3.4, you can use the HelpCtx.Provider
to simplify
the process, as shown in the following example:
class MyTabPane extends JTabbedPane implements HelpCtx.Provider { private HelpCtx[] helps = new HelpCtx[3]; public MyTabPane() { add(new Panel1()); helps[0] = new HelpCtx("help_1"); // etc. } public HelpCtx getHelpCtx() { return helps[getSelectedIndex()]; } }
In NetBeans IDE 3.6, the help system has been upgraded to use v. 2.0 of JavaHelp software. The most visible benefit of the upgrade is better merging of TOC and index. NetBeans IDE uses the Unite-Append merge type for the table of contents and the Sort merge type for the index. These merge types are set in the master help set and propogate to any help sets that merge into the product, unless those help sets override them with other merge types. For more information on merge types, see the JavaHelp release notes.
The biggest resulting impact for module authors is the need to more carefully design TOCs and indexes so that entries from different help sets merge comprehensibly for users. Here are some general tips and rules of thumb:
<?xml version='1.0' encoding='ISO-8859-1' ?> <!DOCTYPE toc PUBLIC "-//Sun Microsystems Inc.//DTD JavaHelp TOC Version 1.0//EN" "http://java.sun.com/products/javahelp/toc_1_0.dtd"> <toc version="1.0"> <tocitem text="Core IDE Help"> <tocitem text="HTTP Monitor"> <tocitem text="Monitoring Data Flow on the Web Server" target="ctx_monitorintro" /> <tocitem text="Viewing HTTP Monitor Data Records" target="monitor_view" /> <tocitem text="Using the HTTP Monitor Toolbar" target="monitor_sort" /> <tocitem text="Editing and Replaying Monitor Data Records" target="monitor_resend" /> <tocitem text="Saving HTTP Monitor Data Records" target="monitor_store" /> <tocitem text="Deleting HTTP Monitor Data Records" target="monitor_delete" /> <tocitem text="Deploying the HTTP Monitor for a Web Module" target="monitor_servconfig" /> </tocitem> </tocitem> </toc><
In order to use the result help set within the IDE at runtime, a couple of things need to be added to various files associated with the module. These are outlined in part in the reference documentation. This description assumes you are using a NetBeans module project.
A module's help set should be defined by creating a package-info.java
file in the same package as the help set
and adding the @HelpSetRegistration
annotation to it. You will want to specify a position for the help set;
this mainly affects the order into which help sets are merged into the table of contents.
Help files should be kept under the regular src subdirectory
off of the module root directory. Like source code, all JavaHelp documentation
must be placed into a globally unique package to avoid conflicts. If two modules
put help files into the same package, it will result in broken links.
You should therefore use a distinctive "package"
name prefix. It is conventional to use module.code.name.base.docs
,
e.g. for a module named org.netbeans.modules.foo
, place the JavaHelp
into org.netbeans.modules.foo.docs
(plus perhaps subpackages).
This section includes any additional comments or issues regarding Help for IDE modules.
It is therefore necessary for all Help IDs to be unique. The best way to
avoid collisions to preface all Help IDs with the standard package name
of the module it comes from. Thus for the Execution tabs of the property
sheet for a form object node, you should set the help ID to
org.netbeans.modules.form.FormDataObject.executionTabProperties
or similar.
HelpCtx
methods that take strings as parameters are included in the IDE's list of
NOI18N patterns and therefore are not internationalized. You do not need to
add // NOI18N to lines containing these strings.
Questions or comments? Send to nbdev.
@FOOTER@


This page is still under heavy development but works fine, you might have to click headers or refresh the page to apply certain changes.
| Coin ^v | Current price ^v | 24h high ^v | 24h low ^v | Volume ^v | {{header}} min^v | Ignore | |
|---|---|---|---|---|---|---|---|
| {{coin.coin}} | {{coin.current}} | {{coin.high}} | {{coin.low}} | {{coin.volume}} | Price change | {{logItem.toFixed(1)}}% | X |
| Volume change | {{logItem}}% |


AJAX Hello World
AJAX example
Type Something:
This is where the php stuff will go
At the bottom of every page make sure you include the following button:


Mama,life has just begun But now I have to go away. Mama, wuwuwu Didn't meant to make you cry, If I can come back someday to you. Carry on Carry on As if nothing really matters.